schema-noindex-conflict

Installation
SKILL.md

Schema + Noindex Conflict

Investing in rich result schema on pages that are blocked from indexing wastes development effort — Google explicitly states it does not process structured data on noindexed pages.

Quick Reference

  • Rich result schema (Review, Product, FAQ, etc.) has no effect on pages Google cannot index
  • A page with noindex will not earn rich results even if it has valid structured data
  • Pages blocked in robots.txt are never fetched, so their schema is never processed
  • Audit all pages with schema markup to confirm they are crawlable and indexable

Check

For every page containing a <script type='application/ld+json'> block with a rich result schema type, check: (1) Is the page blocked by robots.txt? (2) Does <meta name='robots'> contain noindex? (3) Does the canonical tag point to a different URL? Flag any conflicts.

Fix

For pages where rich results are desired: remove the noindex directive, unblock the URL in robots.txt, and ensure the canonical tag is self-referencing. If the page must remain noindexed, remove the schema markup — it serves no purpose.

Installs
4
GitHub Stars
73.9K
First Seen
Aug 11, 2026
schema-noindex-conflict — thedaviddias/front-end-checklist