Content-Type Schema Alignment

Content-Type Schema Alignment checks whether your page's schema.org JSON-LD @type matches the content type its URL implies — say, a /how-to/ URL backed by HowTo schema. friendly4AI scores this for Bing, not Google. If the two signals agree, the page passes. If the URL implies a type but no matching schema exists, it scores partial. If schema and URL contradict each other, it fails.

What does this parameter measure?

friendly4AI reads two signals off your homepage HTML and URL path, then checks whether they line up.

The schema signal comes from the JSON-LD @type tokens. HowTo means a tutorial, DefinedTerm means a glossary, Product/SoftwareApplication/Service means a product, ComparisonTable/ItemList means a comparison, and Review/AggregateRating means a review. Generic Article or BlogPosting types tell the scanner nothing specific, so they count as no schema signal.

The URL signal comes from path fragments: /how-to/, /glossary/, /compare/, /review/, /product/.

Why does it matter for AI-readiness?

AI systems read structured data to classify a page before they decide what to do with it. A how-to page with no HowTo schema, or a glossary entry with no DefinedTerm, throws away the classification cue that triggers content-type-specific citations. The model sees plain prose where it could have read a labelled tutorial or definition.

Schema that contradicts the URL is worse. The mixed signal can suppress citations outright. When the schema and the URL agree, the page's type is unambiguous to the engines that route AI answers.

How is it scored?

This Discovery parameter (v4.5 methodology) scores the schema signal against the URL signal:

• Pass (100) — a specific @type is present and the URL agrees with it, or the URL is neutral (no content-type fragment) so there's nothing to contradict.
• Partial (50) — the URL signals a specific type but no matching @type schema is present, for example a /glossary/ URL with no DefinedTerm schema.
• Fail (0) — both signals fire and point to different content types: schema says one thing, URL says another.

When neither signal fires, the parameter is skipped (not_applicable_no_signal) instead of scored, so generic pages are never penalised.

How do I fix it?

• Add the schema.org @type that matches your content: HowTo for tutorials, DefinedTerm for glossary entries, SoftwareApplication or Product for product pages, Review for reviews.
• To close a partial, pair the content-typed URL with the schema it expects — a /how-to/ page should carry HowTo JSON-LD. See structured-data-coverage and faq-schema for related schema checks.
• To fix a conflict, align the schema with what the page actually is. Don't leave Product schema on a /review/ URL.
• Use specific types over generic Article/BlogPosting, which the scanner treats as no schema signal.
• Keep your URL path conventions consistent with the page's real content type, so the URL signal stays trustworthy — see url-stability.
• Re-scan after the change to confirm the schema and URL signals now agree.