executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
robots-metaUse when applies to all HTML pages. Use when auditing pages that have disappeared from search results or when checking staging vs. production meta tag parity.
Independent GitHub snapshot · Automated classification · Original documentation governs
An accidental noindex on a key landing page silently removes it from search results; audit every page's robots directive to avoid invisible ranking losses.
<meta name="robots" content="..."> in <head> to control indexing per-pagenoindex only on pages that should not appear in search resultsnoindex, nofollow on pages you want crawled for PageRank flowgooglebot, bingbot) override the generic robots tag for that crawlerInspect <head> for <meta name="robots" content="...">. Verify the content value is intentional (e.g., production pages should not have noindex). Check for conflicting googlebot-specific tags.
Remove or update the noindex directive from pages that should appear in search results. For pages that must be blocked, confirm noindex is intentional. Remove duplicate or conflicting robots meta tags.
Explain the difference between robots.txt and meta robots, when each should be used, and why noindex combined with follow still allows link equity to flow.
Review metadata generation, rendered HTML, structured data, and response headers related to Set robots meta directives correctly. 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/robots-meta