Set robots meta directives correctly

SkillSearch

robots-meta is a skill that guides an AI agent through checking robots meta directives on HTML pages. It is used when the check applies to all pages, when auditing pages that have disappeared from search results, or when comparing staging and production meta tag parity. It helps find accidental noindex tags that silently remove pages from search results.

Available today. Use it from your connected AI after setup.

Have access to the HTML pages or templates whose robots meta directives need checking.

Then ask your AI: use the Set robots meta directives correctly skill

What your AI can do with it

  • Inspect the <head> of every HTML page for <meta name="robots"> tags
  • Verify that noindex directives are intentional and remove them from pages that should rank
  • Detect conflicting or duplicate crawler-specific tags such as googlebot or bingbot
  • Explain the difference between robots.txt and meta robots, and how noindex, follow affects
  • Review metadata generation, rendered HTML, structured data, and response headers for viola
  • Compare staging and production meta tag parity

Getting started

  1. Have access to the HTML pages or templates whose robots meta directives need checking.
  2. Add the robots-meta skill to the agent's available skills.
  3. Ask the agent to audit the pages, mentioning whether the check applies to all pages or to specific ones.
  4. Review the flagged routes or templates and apply the suggested fixes.
  5. Optionally ask the agent to explain robots.txt versus meta robots for the team.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/robots-meta/SKILL.md and read by ahel’s review.

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/en/rules/seo/robots-meta

Signals

GitHub stars
74k
Forks
7k
Last commit
Aug 2026

Questions

When should this skill be used?
When the check applies to all HTML pages, when auditing pages that have disappeared from search results, or when checking staging versus production meta tag parity.
What does it check?
It inspects the <head> for <meta name="robots"> tags, verifies content values are intentional, and looks for conflicting crawler-specific tags like googlebot.
Advanced
Item type
skill
Key
robots-meta
Source
github.com/thedaviddias/front-end-checklist