技能创建器
skill-creator
创建、改进和评估自定义技能,把专业流程转化为可重复使用的 AI 能力。
schema-noindex-conflict【数据与研究】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.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
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.
noindex will not earn rich results even if it has valid structured dataFor 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.
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 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.
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