Opens in a new tabSkip to content
Agent LighthouseAgent Lighthouse

    Searches the text of every published page. The evidence sources themselves are not in this index — search all of them on the trusted sources page.

    GitHub ↗
    Browse checks and page contents
    answer-readiness/og-type

    og:type set and appropriate

    What it checks

    AI agents use og:type to classify page content as either a website, article, product, or other entity type. Without it, agents default to treating the page as generic content, missing opportunities for type-specific handling like article freshness scoring.

    Why it matters

    Open Graph consumers read og:type to decide which object vocabulary applies to the page — article, website, product, video.* and so on. That choice decides which additional properties they look for and render. A page declaring the wrong type is interpreted as the wrong kind of object.

    Evidence

    • The Open Graph protocol lists og:type among the four required basic properties and ties it to further requirements: “The type of your object, e.g., ‘video.movie’. Depending on the type you specify, other properties may also be required.” — ogp.me (verified 2026-08-21)
    • The protocol defines the type vocabulary the audit should validate against (article, book, profile, website, music.*, video.*) — ogp.me (verified 2026-08-21)
    • Meta’s webmaster guide lists og:type among the tags to add to “improve distribution of your content”, alongside the core four read by facebookexternalhit/1.1 — developers.facebook.com/…/webmasters (verified 2026-08-21)

    Limits

    The audit’s stated mechanism — that AI agents apply “article freshness scoring” or recency weighting keyed on og:type="article" — has no source. OpenAI’s crawler documentation mentions no HTML metadata — developers.openai.com/…/bots (verified 2026-08-21). Google’s AI-features page describes query fan-out and snippet controls, with no reference to Open Graph — developers.google.com/…/ai-features (verified 2026-08-21); and og:* properties are absent from Google’s supported-meta-tags list — developers.google.com/…/special-tags (verified 2026-08-21). Where an engine does consume content typing, the documented vehicle is schema.org structured data (e.g. Article with datePublished), not og:type — developers.google.com/…/article (verified 2026-08-21).

    The B grade covers presence of a valid OGP type only. The “appropriate” half of this audit is URL-substring blog detection, warning on non-article values. No source supports it, and per the review findings above it is effectively dead code in production.

    How it scores

    og:type is one of the four required properties in the de-facto Open Graph protocol, and adoption is enormous. Meta names it as a tag that changes distribution handling. But the type-selects-behavior effect is documented only in spec terms, and no vendor documents the value-appropriateness effect this audit actually scores.

    Sources