Skip to content

thedaviddias/Front-End-Checklist / skills/robots-meta

robots-meta

Verified

Use 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.

FileKindSize
SKILL.mdskill md1.9 KB
references/rule.mdmarkdown4.4 KB
---
name: robots-meta
description: "Use 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."
metadata:
  category: seo
  priority: high
  difficulty: beginner
  estimatedTime: "10"
  source: frontendchecklist.io
  url: https://frontendchecklist.io/rules/seo/robots-meta
---

# Set robots meta directives correctly

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.

## Quick Reference

- Place `<meta name="robots" content="...">` in `<head>` to control indexing per-page
- Use `noindex` only on pages that should not appear in search results
- Avoid `noindex, nofollow` on pages you want crawled for PageRank flow
- Crawler-specific tags (`googlebot`, `bingbot`) override the generic `robots` tag for that crawler

## Check

Inspect `<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.

## Fix

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

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.

## Code Review

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
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall