LLMaoLLMao

    AI search visibility report · 2026-06-07

    How AI assistants see web.dev

    web.dev has an AI visibility score of 66/100. The site passed 23 of 34 tests. Its strongest areas are Technical Accessibility and Schema.org Markup. The areas to improve are Content Freshness and Authority & Trust Signals.

    How ChatGPT, Claude and Perplexity read web.dev

    Readability80/100

    Result: strong. 4 of 4 tests passed.

    Content is clear and uses appropriate sentence lengths, though technical complexity is moderate.

    Schema.org Markup88/100

    Result: strong. 5 of 5 tests passed.

    Valid JSON-LD present for Organization and WebSite, but Article schema is incomplete (missing headline).

    Authority & Trust Signals32/100

    Result: weak. 1 of 5 tests passed.

    Strong trust pages (Privacy/Terms) but fails on direct contact information and explicit author credentials in schema.

    Citation & Source Quality72/100

    Result: average. 3 of 4 tests passed.

    Good use of inline citations for internal navigation, but lacks links to external authoritative primary sources like W3C.

    Content Freshness0/100

    Result: weak. 0 of 4 tests passed.

    While content mentions 2026 dates, there are no machine-readable publication or modification dates in schema or meta tags.

    Content Structure79/100

    Result: average. 3 of 4 tests passed.

    Excellent use of semantic HTML and organization, but critically fails by having 0 H1 tags despite 49 total headings.

    Entity Definition70/100

    Result: average. 3 of 4 tests passed.

    Strong brand consistency and About page, but lacks Person schema for authors.

    Technical Accessibility100/100

    Result: strong. 4 of 4 tests passed.

    Perfect technical setup with full AI crawler access, social meta tags, and JS-independent content.

    How web.dev can improve its AI visibility

    • Fix Heading Hierarchy (Missing H1) (high priority)
    • Add Contact Information Signals (high priority)
    • Expose Publication and Modification Dates (medium priority)
    • Implement Author Person Schema (medium priority)
    • Strengthen Primary Source Citations (low priority)

    How web.dev compares to its competitors