Does your og:type match the page and carry the right extra fields?
Confirms each page's og:type matches its actual content and includes the matching namespace properties.
What this signal tests
We check whether your og:type matches the page's actual content vertical (article for articles, product for product pages, profile for author bios, website for static and home pages) and whether the corresponding Open Graph namespace fields are present. For og:type=article, that means article:published_time and article:author. For og:type=product, product:price:amount and product:price:currency.
Why it matters for your visibility in AI
The right og:type plus the right namespace fields gives AI preview tools typed information without requiring full JSON-LD. An AI tool showing a preview of an article can pick up the publish date and author from Open Graph alone, even on sites that have not implemented Schema.org Article markup. For products, AI shopping previews extract the price and currency the same way. This is the most efficient fallback layer in your metadata stack. Schema.org is the richest source, og:type with namespace is the lightweight version, and bare Open Graph is the minimum. Sites that get the type wrong (using og:type=website on an article, for instance) miss the typed fields entirely and present worse previews than competitors with consistent typing. Fixing this is usually a one-line template change with disproportionately large gains in preview quality.
Pass criteria at a glance
| Criterion | Passes when |
|---|---|
| og:type matches vertical and required namespace fields present. |
How we test it
We parse the og:type tag on each page and compare it to the actual content nature. If og:type is article, we then require article:published_time (in ISO 8601) and article:author. If og:type is product, we require product:price:amount (a number) and product:price:currency (an ISO 4217 code). The signal fails when og:type does not match the content, or when the required namespace fields are missing for the declared type.
Show technical detection method
If og:type=article require article:published_time + article:author; if og:type=product require product:price:amount + product:price:currency.
If your site fails: how to fix it
- Audit your page templates and confirm that og:type is set correctly per template: article for blog posts and editorial content, product for product pages, profile for author bios, website for the homepage and most static pages.
- For article-type pages, add article:published_time (ISO 8601 with timezone), article:modified_time, article:author (your author profile URL or name), article:section (the category), and article:tag (one tag per meta tag for multiple tags).
- For product-type pages, add product:price:amount as a bare number and product:price:currency as an ISO 4217 code. Optional fields like product:availability and product:condition improve commerce previews.
- For profile-type pages, add profile:first_name, profile:last_name, and profile:username if applicable.
- Make sure namespace field values match your visible content and any JSON-LD you also emit. Inconsistencies between Open Graph and Schema.org reduce trust in both.
- Validate by pasting a sample URL into Facebook's Sharing Debugger, which surfaces all Open Graph fields including namespace properties.
Quick facts
| Maturity | ESTABLISHED |
|---|---|
| Weight | medium |
| Category | Structured Data |
Primary sources
Related signals
Frequently asked questions
What og:type should I use for landing pages or marketing pages?
Use website. The og:type=website value covers any page that does not fit the more specific verticals. Marketing pages, about pages, contact pages, pricing pages, and landing pages all default to website. Only switch to article, product, or profile when the page genuinely is that type of content.
If I already have JSON-LD with Article, do I still need article:published_time?
Yes, for now. Open Graph and Schema.org are read by different AI tools at different stages. JSON-LD is richer; Open Graph is faster to parse and more universal. Belt-and-braces is the standard pattern: emit both, keep them consistent, and benefit from whichever the consuming tool prefers.
Are there Open Graph types beyond the four common ones?
Yes, the Open Graph spec also defines video.*, music.*, and book.* namespaces with their own typed fields. These are rarer because most sites do not publish primary video, music, or book content, but if you do, using the specific type with its namespace fields is worth the small effort. For everything else, the four common types cover 95% of the web.
Run your own scan
Run a free scan and see how your site grades across all 155 AI-readiness signals.