LLMaoLLMao

    AI search visibility report · 2026-10-18

    How AI assistants see dev.to

    dev.to has an AI visibility score of 56/100. The site passed 17 of 34 tests. Its strongest areas are Technical Accessibility and Content Freshness. The areas to improve are Schema.org Markup and Readability.

    How ChatGPT, Claude and Perplexity read dev.to

    Readability40/100

    Result: weak. 0 of 4 tests passed.

    Sentences are too long and the reading ease score is low, making the content difficult to parse.

    Schema.org Markup0/100

    Result: weak. 0 of 5 tests passed.

    Total absence of JSON-LD schema is a critical failure for LLM optimization.

    Authority & Trust Signals60/100

    Result: average. 2 of 5 tests passed.

    Trust pages and publication dates are excellent, but contact details and author credentials lack structured verification.

    Citation & Source Quality72/100

    Result: average. 3 of 4 tests passed.

    Inline citations are present, but the site lacks links to high-authority external domains like .gov or .edu.

    Content Freshness75/100

    Result: average. 3 of 4 tests passed.

    Content is extremely fresh with daily updates, though explicit update signals like changelogs are missing.

    Content Structure61/100

    Result: average. 2 of 4 tests passed.

    Semantic HTML is strong, but the heading hierarchy is broken and paragraph structure is inconsistent.

    Entity Definition64/100

    Result: average. 3 of 4 tests passed.

    The brand is consistent and an about page exists, but the lack of Organization and Person schema hinders entity clarity.

    Technical Accessibility100/100

    Result: strong. 4 of 4 tests passed.

    Excellent technical setup with full AI crawler access and strong social meta tags.

    How dev.to can improve its AI visibility

    • Add JSON-LD Structured Data (high priority)
    • Repair Heading Hierarchy (high priority)
    • Enhance Contact and Author Transparency (medium priority)
    • Improve Content Readability (medium priority)
    • Implement Update Signals (low priority)

    How dev.to compares to its competitors