Content-Type Schema Alignment

What this parameter measures

Does your page's schema.org @type agree with the content type its URL implies? That is the question this parameter answers. friendly4AI derives two signals: a schema signal from the JSON-LD @type tokens (mapping HowTo to a tutorial, DefinedTerm to a glossary, Product/SoftwareApplication/Service to a product, ComparisonTable/ItemList to a comparison, Review/AggregateRating to a review), and a URL signal from path fragments such as /how-to/, /glossary/, /compare/, /review/, and /product/. Generic Article or BlogPosting types count as no specific schema signal. It then compares the two.

Why it matters for AI-readiness

AI systems lean on structured data to classify what a page is before they decide how to use it. A how-to page without HowTo schema, or a glossary entry without DefinedTerm, loses the classification cue that triggers rich, content-type-specific citations — the model sees prose where it could have seen a labelled tutorial or definition. Worse, schema that contradicts the URL sends a confused signal that can suppress citations entirely. Aligning the two makes your page unambiguous to the systems that route AI answers.

How we score it

Under the v4.4 methodology, this Discovery parameter compares the schema signal against the URL signal. It passes (100) when a specific @type is present and the URL agrees with it, or when the URL is neutral (no content-type fragment) so there is nothing to contradict. It scores partial (50) when the URL signals a specific type but no matching @type schema is present — for example a /glossary/ URL with no DefinedTerm schema. It fails (0) only on disagreement: both signals fire and point to different content types. When neither signal fires the parameter is skipped (not_applicable_no_signal) rather than scored, so generic pages are never penalised.

How to fix common issues

• 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.
• Close partials by pairing a content-typed URL with the recommended schema — a /how-to/ page should carry HowTo JSON-LD.
• Fix conflicts by aligning the schema with what the page actually is; do not leave Product schema on a /review/ URL.
• Prefer specific types over generic Article/BlogPosting, which the scanner reads as no schema signal.
• Keep URL path conventions consistent with the page's true content type so the URL signal stays trustworthy.
• Re-scan after the change to confirm the schema and URL signals now agree.