The tags, all of them, in one row
Social tags are the part of the head nobody looks at until a link is shared into a channel of two hundred people.
-
01
Every og tag on the page
Title, description, image, url, type, site name, locale, and anything else the page declares in the og namespace. Not a fixed shortlist.
-
02
Every twitter tag on the page
Card type, title, description, image, site and creator. Absent tags come back empty rather than being quietly filled in from Open Graph.
-
03
Beside the page title and description
In the same row, so where the social title has drifted from the page title you can see whether it was a decision or an accident.
-
04
Twenty-five pages, one CSV
Sort by og:image and every page sharing one generic default graphic lines up together, which is usually more of them than expected.
Five things that break a preview
None of these affect rankings. All of them affect whether a shared link looks like something worth clicking.
-
No og:image
The single tag that decides whether a shared link renders as a card or as a grey rectangle with a domain name on it.
-
A relative image URL
og:image needs an absolute URL. A relative path is a broken preview on every platform at once, and it looks correct in the source.
-
og:title identical to the page title everywhere
Perfectly fine as a default. Worth knowing whether it is a default or a decision, because a title written for a search result and one written for a feed are rarely the same sentence.
-
A missing og:description
Some platforms fall back to the meta description, some show nothing at all. Neither is a choice you made.
-
No twitter:card
X falls back to Open Graph, so this is often fine. It stops being fine the moment you want the large image layout, which needs the card type stated explicitly.
What it will not tell you
Stated here rather than discovered later.
-
01
It reads tags, it does not render previews
There is no thumbnail here. For that, use the platform's own debugger, which is also the only thing that can clear its cache.
-
02
It does not fetch the image
Whether the URL in og:image resolves, what size the file is, and whether a given platform will accept it are all unchecked.
-
03
Static HTML only
Tags injected after load are not in the HTML the server sent, and most social crawlers do not run JavaScript either, so an empty row here is often an accurate preview of the problem.
-
04
Twenty-five URLs per run
It runs in a browser tab. Enough for a template check across a section, not for a whole catalogue.
Reasonable questions
Do Open Graph tags affect SEO?
Not directly. They affect what a shared link looks like, which affects whether it gets clicked and shared again. Treat them as presentation rather than ranking.
Do I need Twitter Card tags if I already have Open Graph?
Usually not. X reads Open Graph as a fallback. The exception is the card type, which you need to state if you want the large image layout rather than the small one.
What size should the og:image be?
1200 by 630 pixels is the widely used ratio and it survives most platforms' cropping. Using an absolute URL matters more than hitting the exact dimensions.
I fixed the tags and the preview has not changed.
Platforms cache previews, sometimes for a long time. Each has a debugger that forces a refresh. What this tool can confirm is the part you control: that the tag is correct on the page.
Social tags are part of the pages table
The same run returns titles, meta descriptions, headings, word counts, links, images and structured data as well. It is one tool with seven tables and seven CSV exports, not seven separate tools you have to run one after another.
Other checks the same tool runs: Bulk SEO checker, Meta tag checker, Heading checker, Alt text checker, Word count checker, Canonical checker, Schema checker