How do I install the Schema Noindex Conflict skill?

Run npx skillmds@latest add thedaviddias/schema-noindex-conflict in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Schema Noindex Conflict safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Schema Noindex Conflict?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Schema Noindex Conflict free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Schema Noindex Conflict?

thedaviddias (@thedaviddias) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Schema Noindex Conflict by thedaviddias

Name: Schema Noindex Conflict
Author: thedaviddias

File contents

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.

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

---name: schema-noindex-conflictdescription: Use when applies to any site that uses structured data for rich results. Use when investigating why valid schema markup does not produce rich results in Google Search.---# Schema + Noindex ConflictInvesting 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## CheckFor 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.## FixFor 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.## ExplainExplain 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 ReviewReview 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

Frequently asked questions

Schema Noindex Conflict