Schema + Noindex Conflict
SkillSearchschema-noindex-conflict is a skill for AI agents that investigates why valid schema markup does not produce rich results in Google Search. It applies to any site that uses structured data for rich results, helping the agent find the cause when markup passes validation but rich results still fail to appear.
Use Schema + Noindex Conflict in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Schema + Noindex Conflict and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Schema + Noindex Conflict skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have an agent that can load and use skills.
What your AI can do with it
- Investigates why valid schema markup does not produce rich results in Google Search
- Applies to any site that uses structured data for rich results
- Guides an agent through diagnosing structured data that passes validation but shows
Getting started
- Have an agent that can load and use skills.
- Add the schema-noindex-conflict skill to the agent's available skills.
- Ask the agent to investigate why valid structured data on a site fails to produce rich results in Google Search.
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
- Oct 2026
Questions
- When should this skill be used?
- Use it when investigating why valid schema markup does not produce rich results in Google Search, on any site that uses structured data for rich results.
- Does it fix schema markup errors?
- It is designed for cases where the schema markup is valid but rich results still do not appear, not for fixing invalid markup.
- Does it work for sites other than Google Search?
- The skill is described for rich results in Google Search; other search engines are not covered.
Advanced
- Item type
- skill
- Key
schema-noindex-conflict- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist