Before posting a Cards issue, please READ the following:
If you are posting about any issue with your site, please include a link to the publically-accessible URL where your Card markup is visible, or we will be unable to help you. If you are new to the forums, we don’t initially allow URLs to be posted (this is an anti-spam measure for new users), so please simply add some spaces, or surround the link with backticks (`) which will mark the link as code.
You should make sure that you’ve checked the items below, and perform your own troubleshooting before asking for additional help. Posts that indicate that none of these checks have been performed will not be prioritised for attention.
As of early 2018, cards no longer require approval (including player cards)
- The not whitelisted error message from the Validator is misleading, and almost certainly means that the tool cannot see or find any
twitter:card markup in your page.
- If you see a message saying that you need to submit your card for approval, you’ve probably specified an incorrect card type in the markup.
Please review the following if you are having other issues:
-
No metatags found is probably a result of an error fetching the page
- perhaps your host is blocking Twitter’s IP range, listed here
- does the page have a valid
Content-Type header?
- are your tags static (see below), or are they being added by JavaScript on page load?
- when you view the source of your page in a browser, the expected Twitter Cards meta tags should be shown
- if you execute
curl -v -A Twitterbot <url> at the command prompt, does your page still show the twitter:card tags in the <head> section of the page? Does your server return a 200 response code and a valid Content-Type header?
- is your page adding the tags after it is loaded, for instance using JavaScript (e.g. Angular, Meteor, Google Tags Manager)? The crawler and validator cannot execute JavaScript and the tags must be static.
- is your site accessible by the
Twitterbot/1.0 user-agent? Are all the files (including image files) accessible to Twitterbot? you should check http://your-site-url/robots.txt and ensure that it allows access to our crawler. If your images are on a different domain, also make sure you check the robots.txt file for that domain.
- are you using a Wordpress (or other CMS/blogging platform) plugin? We provide our own official Wordpress plugin, but cannot easily provide support for those built by third parties. Check that the configuration includes all of the required tags. Avoid using multiple plugins at the same time, as tags will override one another.
- are you putting the top-level site URL into the Validator, or the specific URL where your markup is present? you’ll need to make sure that you provide a link to where your Card markup is visible in the page.
- are you using a supported Card type? Product, Gallery and Photo card types were removed in mid-2015. Is the card type spelled correctly, or is there a typo?
- if your image is not showing, is it accessible on a URL that is not blocked by your
robots.txt file? Does it conform to our size constraints? Are you using an absolute and full URL (including the http protocol piece), not a relative one?
- if you see a validator message about
Fetching the page failed because other errors or similar, check your SSL configuration. The certificate and server name must match (or be aliased to match) due to Java security constraints. More in this thread.
- are you using a fully qualified DNS domain name? The crawler does not support dotted IP addresses as domain references, and cannot access localhost.
There is much more Troubleshooting information on our Developer site.