thedaviddias/Front-End-Checklist / skills/schema-noindex-conflict
schema-noindex-conflict
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.1 KB |
| references/rule.md | markdown | 4.2 KB |
SKILL.md
View on GitHub---
name: schema-noindex-conflict
description: "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."
metadata:
category: seo
priority: high
difficulty: intermediate
estimatedTime: "10"
source: frontendchecklist.io
url: https://frontendchecklist.io/rules/seo/schema-noindex-conflict
---
# 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/rules/seo/schema-noindex-conflict
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |