This post contains affiliate links. If you buy something through one of them, Veravix may earn a commission at no extra cost to you.
Open Graph tags are meta tags in the head of a page that tell Facebook, LinkedIn and other sites which title, description and image to show when someone shares your link. The Open Graph protocol at ogp.me lists four as required for every page: og:title, og:type, og:image and og:url. In practice most sites add a few more. I fetched the homepages of 71 well-known sites on 16 November 2026, read 64 of them, and 59 had at least one Open Graph tag, but only 47 had all four required ones.
I ran the survey because both of my own sites needed a snippet to print these tags at all, and I wanted to know what the sites people copy actually do. Everything below comes from that run or from the protocol and Meta’s own sharing guide, and I say which is which.
The four tags the spec requires, and what each one does
The protocol says to place them as <meta> tags in the <head>, using property and content attributes. The four required properties are:
og:titleis the title as it should appear when shared. Meta’s guide says to write it without branding such as your site name.og:typeis the kind of object, such aswebsiteorarticle. Meta’s guide adds that if you leave it out the default iswebsite.og:imageis the URL of the preview image.og:urlis the canonical URL, which Meta says should be the plain URL without session variables or tracking parameters, because likes and shares aggregate at that address.
The protocol lists og:description, og:site_name and og:locale as optional but generally recommended. It also says that a page with an og:image should specify og:image:alt, and that when a tag appears more than once the first one from top to bottom wins.
What 64 real homepages publish
The survey fetched the homepage of each of 71 domains with a plain script. Seven returned nothing usable (six refused it with a 403, one did not answer), leaving 64. Percentages below are of those 64 unless stated. Homepages only: an article page can carry different tags, and a site that prints nothing on its homepage may still print tags on its posts.
| What I checked | Sites |
|---|---|
| At least one Open Graph tag | 59 of 64 |
| All four required tags | 47 of 64 |
Missing og:type (of the 59 with any tag) |
8: Adobe, Gymshark, HubSpot, Intuit, Node.js, Peak Design, php.net, Skims |
Missing og:image (of the 59) |
5: BrĂ¼Mate, Huel, Mailgun, Peak Design, Skims |
og:description |
56 |
og:site_name |
47 |
og:locale |
20 |
og:image:width and og:image:height |
26 |
og:image:secure_url |
15 |
og:image:alt |
8 |
fb:app_id |
8 |
Two details stand out. First, the tags most guides call optional are the ones nearly everyone adds: 56 of the 59 carry a description. Second, the one the spec marks as recommended for accessibility, og:image:alt, is nearly absent, at 8 sites. Eight sites with tags had no og:type, which Meta says falls back to website, so the missing tag costs little on a homepage, but it does break the protocol’s own definition of a complete set.
Five sites printed no Open Graph tags at all in what my script received: debian.org, theguardian.com, trello.com, and my own veravix.com and repairpicks.com, whose homepages are plain blog rolls. I did not check the others’ article pages, and a news site such as The Guardian may serve a bot different markup from the one a browser gets.
X cards, and the tags built for X
X reads its own twitter: tags and falls back to Open Graph for some of them. I could not cite X’s documentation for this: the old card markup page redirected to a generic developer overview on 16 November 2026, so I am reporting only what the sites do. Of the 64, 56 print at least one twitter: tag, 44 use the summary_large_image card and 6 use summary. Six sites print twitter: tags with no card type: Hostinger, Intuit, The New York Times, Peak Design, Skims and The Guardian.
The preview image: where sites go wrong
I downloaded the image each site names in og:image. All 54 loaded with a 200 status and an image content type, and none used a relative URL. The formats were PNG on 26 sites, JPEG on 25, WebP on 2 and GIF on 1. That matters because Meta’s guide lists the MIME types for og:image:type as image/jpeg, image/gif or image/png. WebP is outside that list, and nobody in my sample used AVIF.
The median image was 77 KB. Ten were over 300 KB, and the largest two, Hostinger’s (a GIF) and Shopify’s, were each above 2.5 MB. Eight sites name an http:// image rather than https://: 4ocean, Allbirds, Kith, Native, Rothy’s, Squarespace, Taylor Stitch and Ugmonk.
Meta’s guide has two rules worth acting on. Images are cached by URL, so to change a preview after it has been shared you have to change the image’s URL, not just overwrite the file. And you should give the width and height, so the image loads properly the first time it is shared. Only 26 of the 54 sites do. If you do not want to design a 1200 by 630 image yourself, a freelance designer on Fiverr can make a reusable template, and you only need it once per site.
Title and description length
Meta’s guide says the description is usually 2 to 4 sentences. The sites in my sample are much shorter: the median description was 144 characters, and 18 ran past 160. The median title was 48 characters and 10 passed 60. Only 7 sites wrote an og:description that differs from their meta description, so most simply reuse one text for both.
What I found on my own site
I should say plainly what the survey showed about this site. Veravix’s homepage prints no Open Graph tags. Its posts do, through a small snippet I added earlier, and when I read it on 16 November 2026 it had three weaknesses. It prints og:type as website on every post, where article is the better type. It gives no image width, height or alt text. And the image it names is an AVIF file, a format that was absent from all 54 images in the sample and is not on Meta’s list of types. I have not tested how each network treats AVIF, so I am noting it rather than claiming it breaks previews. I upgraded the snippet the same day: posts now print article, the image size and alt text, and a link to the PNG original instead of the AVIF copy, and the homepage prints a basic set of tags too.
How to add Open Graph tags in WordPress
You have two options, and one of them is probably already installed.
- A plugin. On wordpress.org, Yoast SEO shows 10 million or more active installs, Rank Math 4 million, All in One SEO 2 million, Jetpack 3 million and The SEO Framework 200,000. Each of those handles social tags among other jobs. A single-purpose plugin, Social Preview and Open Graph Tags, has 50,000 installs and was updated on 28 September 2026. If you already run one of the big SEO plugins, check its social settings before adding anything.
- A snippet. If you do not want a plugin, a short function hooked to
wp_headcan print the tags. That is what both of my sites use, because neither runs an SEO plugin. It needs the post title, an excerpt, the permalink and the featured image URL, and it must run only on single posts. Do not run a snippet and a plugin together, or every tag appears twice. I found that out on 16 November 2026 by adding a second snippet to a page that already had one, and had to remove it.
Whichever route you take, check the result by viewing the page source and searching for og:, then paste the URL into Meta’s Sharing Debugger. Meta says the debugger shows which tags its crawler reads and any errors, and that it triggers a fresh scrape, so you can use it to refresh a preview after a fix. If a staging copy is available, make the change there first, as the guide on what website staging is explains.
For other files crawlers read from a site, see the posts on robots.txt for AI crawlers and security.txt, which use the same list of sites.
Sources read on 16 November 2026: the Open Graph protocol at ogp.me, Meta’s “A Guide to Sharing for Webmasters” (updated 30 June 2026), and the wordpress.org plugin directory for install counts. Survey data comes from the homepages of 71 domains fetched by script on the same day, with the image of each named og:image downloaded and measured.

Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.