No card found (Card error) in Validator


Description of issue:
The Twitter card validator is reporting the following:

INFO:  Page fetched successfully
INFO:  8 metatags were found
ERROR: No card found (Card error)

From what I can tell, all the proper tags are in place.

Of note: the site is using OG tags, not Twitter card tags.

URL affected (must be public):

Troubleshooting steps attempted [note that we will not prioritise posts unless there is evidence of following the troubleshooting guides]: All steps in the troubleshooting guide were followed. Here is relevant output from curling:

* Connected to ( port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *
* Server certificate: RapidSSL SHA256 CA
* Server certificate: GeoTrust Global CA
> GET /patreon/jobs/570189?gh_src=ogdb4u1 HTTP/1.1
> Host:
> User-Agent: Twitterbot
> Accept: */*
< HTTP/1.1 200 OK
< Server: nginx
< Date: Tue, 07 Nov 2017 21:54:56 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 69390
< ETag: W/"efd812fd8e95062af1150599b80d6b8b"
< Cache-Control: max-age=0, private, must-revalidate
< X-Request-Id: CC1C7BE2E502_0A6401A401BB_5A022BB0_62D4370D7
< X-Runtime: 0.018919
< Strict-Transport-Security: max-age=31557600; includeSubdomains; preload
< X-Download-Options: noopen
< X-XSS-Protection: 1; mode=block

<!DOCTYPE html>
<head prefix="og:">
<!-- <snip -->
  <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<!-- <snip -->
  <meta id="viewport" name="viewport" content ="width=device-width, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no" />
  <meta id="rendered-by" content="jben" />
 <!-- <snip -->
    <meta property="og:title" content="Senior Site Reliability Engineer"></meta>
    <meta property="og:description" content="San Francisco"></meta>
    <meta property="og:url" content=""></meta>
    <meta property="og:image" content=""></meta>
<!-- <snip -->

Any thoughts or ideas?


There’s no og:type - that’s the thing that maps to the Twitter card type.


Aha! I didn’t see that in the documentation. Is there somewhere I can read more? Thanks Andy!


Covered here


Awesome. I think it might be helpful to be explicit that og:type is required, but I defer to y’all on that. Thanks for the assistance! :sparkling_heart:


Thanks for the feedback, will see what we can do to make this more clear and obvious!

closed #7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.