No Social Schema

Every time someone drops your URL into a chat, a post, or a DM, the receiving platform sends a scraper to your page and tries to build a preview card. If you have not told it what title, description, and image to use, it guesses. Sometimes it grabs your logo. Sometimes it grabs a stock footer image or nothing at all. "No Social Schema" is the audit flag that says you left that guess up to chance across the whole platform ecosystem, and you should not.

What "social schema" actually covers

People lump three separate things under this label, and it helps to keep them straight because they are validated by different tools and consumed by different platforms.

Open Graph protocol. Created by Facebook, now the de facto standard used by Facebook, LinkedIn, Pinterest, Slack, Discord, WhatsApp, iMessage, and most link unfurlers. These are <meta property="og:*"> tags: og:title, og:description, og:image, og:url, and og:type at minimum.

Twitter Cards. X reads its own <meta name="twitter:*"> tags. If they are absent it falls back to Open Graph, which is why a page with only OG tags still unfurls on X, but you lose control of the card format (summary versus large image).

Social profile linkage via schema.org. This is the JSON-LD piece: an Organization or Person node with a sameAs array pointing at your official Facebook, X, LinkedIn, YouTube, and Instagram profiles. This is what search engines read to connect your website to your verified social identity, and it is the part most people forget entirely.

Why it matters, and why it does not (be honest about this)

Let me be straight: Open Graph tags are not a Google ranking factor. Google has said for years that it does not use Open Graph or Twitter Card data to rank pages. So if a consultant tells you adding og:title will lift your rankings, be skeptical.

What it actually does is protect click through and brand perception. A link with a clean, deliberate preview card gets more clicks in social feeds and in Slack channels than a naked URL or a broken image box. That downstream traffic and engagement is real, and it feeds the signals that do matter. The sameAs piece is different: that genuinely helps search engines build your entity in the Knowledge Graph and disambiguate your brand from similarly named ones. So treat the OG and Twitter tags as conversion and brand hygiene, and treat sameAs as entity SEO.

The share preview flow

How to detect it

Do not eyeball view source and call it done. Use validators that render the card the way the real platform will.

• Screaming Frog SEO Spider. Configure it to extract Open Graph and Twitter Card meta with custom extraction or the built in fields, crawl the site, and filter for URLs missing og:title or og:image. This is how you find the flag at scale rather than page by page.
• Facebook Sharing Debugger and LinkedIn Post Inspector. Paste a URL and see exactly what each platform scraped, plus the cached version. The debugger also forces a re-scrape, which you need after any fix because these platforms cache aggressively.
• X (Twitter) Card Validator behavior. The classic validator was deprecated, so test by pasting the link into a draft post and watching the unfurl, or check that twitter:card and a valid image are present in the source.
• Google Rich Results Test and Schema Markup Validator. These check the JSON-LD Organization and its sameAs array, the entity piece that OG tags do not cover.
• Sitebulb reports missing Open Graph and Twitter tags as a hint level issue across the crawl, which is handy for a prioritized punch list.

How to fix it, step by step

1. Add the core Open Graph block to every indexable page template: og:title, og:description, og:type (usually website or article), og:url (the canonical URL), and og:image.
2. Get the image right. Use a dedicated share image at 1200 by 630 pixels, under about 5 MB, served over HTTPS at an absolute URL. Do not point og:image at a tiny logo, because platforms crop and it looks amateur.
3. Add Twitter Card tags: twitter:card set to summary_large_image for most content, plus twitter:title, twitter:description, and twitter:image. If you only add OG, X will still work but you cannot force the large image format.
4. Add the sameAs array to your Organization JSON-LD, listing only profiles you actually control and keep active. A dead Google Plus link or an abandoned account does more harm than omission.
5. Re-scrape. Run the URL through the Facebook Sharing Debugger and LinkedIn Post Inspector to clear their caches, or your fix will not show for days.

Do and don't

What good looks like

Paste any page of the site into Slack and the FB debugger and you get a deliberate card: correct title, correct description, a crisp 1200x630 image, and the right canonical target. X shows a large image card. Your Organization JSON-LD validates clean and lists every social profile you actively run. No page in a Screaming Frog crawl is missing og:title or og:image. That is the whole job.

FAQ