Use the narrowest true type

What does this finding mean?

The report identifies this check as schema-specific-type in Structured data. The category carries up to 16 of the 100 rubric points. This is a category weight, not an automatic deduction for this finding. Read the scan detail for the measured state, overlapping signals and any score cap.

Confirm the page purpose, then use the narrowest accurate type. Keep supporting publisher and website entities separate from the main article, product or profile.

Why does this matter for AI retrieval?

Valid markup labels the entities and content already visible on a page. Parsers can use those explicit relationships. No schema type guarantees selection by ChatGPT, Claude, Perplexity or Gemini, and this score is our rubric rather than a vendor ranking formula.

How do I check and resolve it?

1. Read the page and confirm its purpose. A technical guide can use TechArticle; a product page needs Product, and a local business profile needs the appropriate business type.
2. Replace generic WebPage-only markup with the narrowest accurate type for the main content. Preserve site-level Organization and WebSite nodes as supporting entities.
3. Fill the fields required by the chosen type with real visible facts. Do not invent prices, ratings, authors or publication dates to complete a template.

Adapt the example to the reported issue and the actual route. Placeholder names, URLs and dates must be replaced with facts from your site.

Copy code

<script type="application/ld+json">
{"@context":"https://schema.org","@type":"TechArticle",
 "headline":"Actual technical guide headline",
 "description":"The visible description of this guide",
 "datePublished":"2026-10-18","dateModified":"2026-10-18",
 "mainEntityOfPage":{"@id":"https://example.com/guide/"},
 "author":{"@type":"Person","@id":"https://example.com/authors/actual-author/",
   "name":"Actual author","url":"https://example.com/authors/actual-author/"},
 "publisher":{"@id":"https://example.com/#publisher"}}
</script>
<!-- Define the referenced publisher once. Replace example dates with real dates. -->

Verify the result

Validate the chosen type and inspect the mainEntity relationships. Rescan the exact route to confirm that the scanner classifies the main content correctly.

Open the related tool or technical guide, then run a new scan of the affected URL. Keep unknown checks marked unknown until you have a complete response.

Copy a prompt for your coding agent

Paste this into Codex, Claude Code or Cursor from your own repository. Include the scan's exact URL and detail so the agent can verify the observation.

Copy prompt for coding agent

Investigate the scanner finding "Use the narrowest true type" (schema-specific-type) in this repository.
Observation: The schema type is too generic for the main content this page presents.
Required change: Confirm the page purpose, then use the narrowest accurate type. Keep supporting publisher and website entities separate from the main article, product or profile.
Inspect the existing route, shared layouts and configuration first. Confirm the finding against the actual response before editing. Preserve intentional access restrictions, existing content and unrelated changes. Use only factual identity and date values. Make the smallest appropriate fix, verify the deployed HTML or resource response and run the relevant project checks. Explain any measurement that remains unknown. Do not promise search rankings or AI citations.
Reference: https://letthebots.in/fixes/schema-specific-type/