Schema + Noindex Conflict
SkillSearchSchema-noindex-conflict is an agent skill for SEO work. It guides an agent through finding pages where valid structured data cannot earn rich results in Google Search because the page is noindexed or blocked in robots.txt, and explains how to fix or remove the markup.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent environment that can load skills.
Then ask your AI: use the Schema + Noindex Conflict skill
What your AI can do with it
- Detects schema markup on pages blocked by robots.txt
- Finds pages where meta robots contains noindex alongside rich result schema
- Checks whether canonical tags point to a different URL
- Recommends fixes: remove noindex, unblock robots.txt, self-reference canonicals
- Advises removing schema from pages that must stay noindexed
- Reviews templates and metadata generation for schema and noindex conflicts
Getting started
- Have an agent environment that can load skills.
- Add the skill files to the agent's skills directory.
- Give the agent access to the site's pages, robots.txt, and rendered HTML.
- Ask the agent to audit pages with structured data for noindex or robots.txt conflicts.
- Apply the recommended fixes and have the agent verify the final page output.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/schema-noindex-conflict/SKILL.md and read by ahel’s review.
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
noindexwill 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.
Explain
Explain why Google does not process structured data on pages it cannot index, how to identify schema+noindex conflicts in a large site, and how to prioritize which pages need indexing to unlock rich results.
Code Review
Review metadata generation, rendered HTML, structured data, and response headers related to Schema + Noindex Conflict. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/seo/schema-noindex-conflict
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- Why doesn't my valid schema markup produce rich results?
- Google does not process structured data on pages it cannot index. If a page has noindex or is blocked in robots.txt, its rich result schema has no effect even when the markup is valid.
- What should I do with schema on a page that must stay noindexed?
- Remove the schema markup. It serves no purpose on a page Google will not index.
Advanced
- Item type
- skill
- Key
schema-noindex-conflict- Source
- github.com/thedaviddias/front-end-checklist