Do your pages have the four basic preview tags every AI tool expects?
Confirms every page declares title, type, image, and URL via Open Graph for clean previews.
What this signal tests
We check whether every page on your site includes the four required Open Graph meta tags (og:title, og:type, og:image, og:url) in the page head. Open Graph is the universal preview standard used by Slack, Discord, LinkedIn, Facebook, and increasingly AI chat tools when they show a link preview or extract a basic summary of your page.
Why it matters for your visibility in AI
Open Graph is the lingua franca of link previews. When someone pastes your URL into ChatGPT, Slack, a research note, or any modern AI chat, the tool reads these four tags to produce a clean card. Without them, the preview falls back to whatever the AI can extract from raw HTML, which is unreliable and often produces broken images, missing titles, or stale text. This is distinct from Schema.org markup. Schema.org describes meaning (this is an article, this is a product); Open Graph describes presentation (this is the title, this is the image, this is the canonical URL). AI tools use both for different purposes. Schema.org drives semantic understanding; Open Graph drives the visible card. Both are essential, but Open Graph is often the first thing a user sees about your link, which makes weight on this signal high.
Pass criteria at a glance
| Criterion | Passes when |
|---|---|
| All four required OG tags present. |
How we test it
We fetch each page and parse the head for meta tags with property attributes of og:title, og:type, og:image, and og:url. Each must be present and non-empty. og:url must be an absolute URL matching the canonical URL of the page (no trailing slashes mismatched, no www inconsistency). og:image must be a fully-qualified URL (not a relative path) and ideally large enough for high-quality previews (at least 1200 by 630 pixels).
Show technical detection method
Parse <meta property=og:title|og:type|og:image|og:url>; require all four non-empty.
If your site fails: how to fix it
- Add the four required Open Graph meta tags to your page template's head section, populated from the page's title, type (article, product, website, profile), canonical URL, and a representative image URL.
- Make og:url match your canonical URL exactly, with the same protocol (https), same domain (with or without www, consistent across the site), and same trailing slash convention.
- Make og:image a fully-qualified absolute URL. Relative URLs work in some clients but not others. Use at least 1200 by 630 pixels for the main share image; smaller images often render too small in modern previews.
- Choose og:type carefully: website for the homepage and most static pages, article for editorial content, product for product pages, profile for author bios.
- Add the supplementary tags og:description (a one to two sentence summary) and og:site_name (the brand name) for fuller previews. These are not required but significantly improve preview quality.
- Validate by pasting a sample URL into Facebook's Sharing Debugger and LinkedIn's Post Inspector, which show exactly how the preview will render.
Quick facts
| Maturity | ESTABLISHED |
|---|---|
| Weight | high |
| Category | Structured Data |
Primary sources
Related signals
Frequently asked questions
Why does og:image need to be so large?
Modern preview clients render share images at high resolution. A 1200 by 630 image (the Facebook-recommended size) renders crisply on retina displays and at the large card sizes Slack, Discord, and AI tools now use by default. Smaller images get upscaled and look blurry. 1200 by 630 is a single image you can reuse for all platforms.
Should I have a unique og:image per page or one site-wide image?
Unique per page where possible. Articles should use a featured image, products should use the main product image, the homepage uses the brand image. A site-wide fallback is fine when the page has no natural image, but page-specific images dramatically improve click-through from previews because they convey what the page is actually about.
Is Open Graph the same as Twitter Card markup?
Closely related but separate. Twitter (X) Cards use the twitter:* namespace and offer slightly different presentation options. The good news is Twitter Cards fall back to Open Graph when Twitter-specific tags are missing, so well-formed Open Graph alone covers Twitter previews in most cases. Adding Twitter-specific tags is optional polish, not a separate requirement.
Does Open Graph affect SEO ranking?
Not directly in classic Google search, but it heavily affects click-through rates from social and AI previews, which feed back into engagement metrics. AI tools also use og:title and og:description as fallback for when JSON-LD is missing. The practical SEO benefit is real even if Google does not weight Open Graph as a primary ranking factor.
Run your own scan
Run a free scan and see how your site grades across all 155 AI-readiness signals.