Technical SEO

Meta Robots Tag Preview

Compose and validate meta robots directives. Preview noindex, nofollow, nosnippet, and max-snippet combinations, see the exact HTML output, and catch configuration mistakes before they hit production.

Technical SEOs, developers, and CMS administrators use meta robots tags to control how individual pages are indexed and how snippets appear in search results. A single mistyped directive can drop a page from the index or waste crawl budget on pages that should never rank. When to use it: Before deploying a new template, during a site migration, when tuning snippet behavior for landing pages, or when auditing why a page vanished from search results. What it solves: Builds the correct content attribute from your directive choices, flags redundant combinations like nosnippet with max-snippet:0, and shows the exact HTML tag so there is no guesswork. Why it matters: Google processes dozens of directives, and combining them incorrectly produces unpredictable indexing. Previewing the tag and validating the combinations catches these mistakes in seconds instead of waiting days for a crawl to reveal them.

Indexing

index (allow the page in search results) follow (crawl links on the page)

Snippet Controls

nosnippet (no text snippet in results) noarchive (no cached copy) noimageindex (do not index images) notranslate (no auto-translate)

max-snippet

max-video-preview

Generated HTML

Content Attribute

Parsed Directives

How Meta Robots Tag Generation Works

Every change you make to the toggles re-runs the directive builder. The builder always starts with the two core directives, index or noindex and follow or nofollow, then appends any optional directives you enabled in a stable order so the output is predictable.

The max-snippet and max-video-preview values are only included when you change them away from the default of -1. This keeps the generated tag minimal, which reduces the chance of conflicting with directives injected by a CMS or tag manager.

Conflict detection runs on every render. It checks for combinations that waste directives or produce unpredictable results, such as nosnippet paired with max-snippet:0 (redundant) or noindex with follow in a configuration that may not match your intent.

Output formatting produces both the full HTML tag ready to paste into your head and the raw content attribute value, which is useful when a CMS exposes the content field separately from the tag wrapper.

Before / After Examples

Example 1: Block a Page from the Index

❌ Before (Page indexed by default)

<head>
  <title>Internal Draft</title>
  <!-- No robots directive -->
</head>

<!-- Page is fully indexable -->

✅ After (Explicit noindex)

<head>
  <title>Internal Draft</title>
  <meta name="robots" content="noindex, follow" />
</head>

<!-- Blocked from results, links still crawled -->

Example 2: Limit Snippet Length

❌ Before (Uncontrolled snippet)

<meta name="robots" content="index, follow" />

<!-- Google picks any snippet length -->

✅ After (Capped at 160 chars)

<meta name="robots" content="index, follow, max-snippet:160" />

<!-- Snippet capped at 160 characters -->

Example 3: Conflicting Directives

❌ Before (Redundant combination)

<meta name="robots"
      content="index, follow, nosnippet, max-snippet:0" />

<!-- nosnippet already blocks snippets -->

✅ After (Single clear directive)

<meta name="robots" content="index, follow, nosnippet" />

<!-- One directive, no conflict -->

Use Cases

Developer	Production	Workflow
Test robots directives in a local dev environment	Block thin or duplicate pages from the index	Pre-launch SEO checklist before a site goes live
Debug why a staging page is being indexed	Tune snippet length for high-traffic landing pages	Monthly audit of index coverage in Search Console
Verify CMS template output for robots meta	Prevent internal search result pages from ranking	Investigate sudden drops in organic impressions
Validate directives across a JS framework build	Apply noimageindex on photography-heavy pages	Document the robots policy for client handoff

Common Mistakes & Troubleshooting

Using robots.txt disallow instead of noindex

Blocking a page in robots.txt prevents crawling, but search engines may still index the URL and sometimes show a snippet without the noindex directive. If your goal is to keep the page out of results, use noindex.

❌ Disallow: /private/  (in robots.txt, page may still be indexed)
✅ <meta name="robots" content="noindex" />  (on the page itself)

Placing the tag after other meta tags incorrectly

The robots meta tag must live inside the head section. If a CMS or tag manager injects it into the body, crawlers will ignore it. Always verify the rendered HTML, not just the template source.

❌ <body><meta name="robots" content="noindex" /></body>
✅ <head><meta name="robots" content="noindex" /></head>

Conflicting robots tags on the same page

If two robots meta tags appear on one page, Google uses the first one it encounters and ignores the rest. Duplicate tags usually come from a theme default plus a plugin override.

❌ <meta name="robots" content="index" />
   <meta name="robots" content="noindex" />
✅ <meta name="robots" content="noindex" />  (one tag only)

Forgetting to remove noindex on launch

Staging environments often carry noindex tags. If those tags ship to production, the entire site disappears from search results. Add a pre-launch check that asserts no page in the production build contains noindex.

❌ Staging noindex tag left in production template
✅ Automated check: assert no noindex in production HTML

Assuming nofollow blocks page indexing

nofollow controls link following, not page indexing. A page with nofollow on all links can still be fully indexed and rank. Combine nofollow with noindex only when you want both behaviors.

❌ content="nofollow"  (page still indexable)
✅ content="noindex, nofollow"  (blocked and links not followed)

Best Practices

✓

Use noindex, not robots.txt, to remove from results

noindex guarantees the page is excluded from search results while still allowing crawlers to see the directive. robots.txt disallow only blocks crawling.

✓

Keep one robots tag per page

Duplicate tags cause crawlers to use only the first one. Audit your templates so the tag is rendered exactly once.

✓

Verify with a live fetch after deploy

After pushing changes, fetch the page as Googlebot and confirm the rendered HTML contains the expected directive. Client-side injection may not appear in a static fetch.

✓

Document your directive policy

Write down which page types get which directives. This prevents conflicting choices when multiple people manage the site over time.

✓

Audit noindex tags quarterly

Use the Search Console coverage report to find pages that carry noindex unexpectedly. Stale noindex tags are one of the most common causes of lost organic traffic.

✓

Pair noindex with a crawlable exit

If a page is noindexed but contains links to live pages, keep follow enabled so link equity still flows. Use nofollow only when the outbound links are untrusted.

✓

Avoid noarchive for compliance reliance

Google no longer shows a visible cached link, so noarchive has little effect there. Do not depend on it as a sole compliance control.

✓

Test max-snippet before rolling out site-wide

Snippet limits change how pages appear in results. Test on a few high-traffic pages first and watch click-through before applying the directive everywhere.

Frequently Asked Questions

What does a meta robots tag actually control? +

A meta robots tag tells search engine crawlers what they may do with a single page. The two core directives are index/noindex (whether the page may appear in search results) and follow/nofollow (whether links on the page may be followed to discover other pages). Additional directives like nosnippet, noarchive, noimageindex, max-snippet, and max-video-preview fine-tune how the page is presented in results. All of this runs on a per-page basis and does not replace robots.txt, which controls crawling at the site level.

What is the difference between noindex and disallow in robots.txt? +

noindex is a page-level directive that blocks a page from appearing in search results while still allowing it to be crawled. disallow in robots.txt blocks crawling entirely. The critical difference: if a page is blocked in robots.txt but has no noindex tag, search engines may still index the URL (and sometimes the content) because they never see the noindex directive. If your goal is to keep a page out of the index, use noindex, not just robots.txt disallow.

Should I use nofollow on internal links? +

For internal links, nofollow is almost always unnecessary and can waste crawl budget. Google treats nofollow as a hint, not a hard rule, and on internal links it mostly signals that you do not trust your own pages. Reserve nofollow for external links you cannot vouch for, paid links, or user-generated content. Modern best practice is to leave internal links followed unless you have a specific reason not to.

What does max-snippet:N do and when would I use it? +

max-snippet:N limits the number of characters Google may show in the search result snippet for that page. A value of 0 means no snippet text at all; -1 (the default) means no limit. You might set max-snippet:50 to force a short, punchy description, or pair it with nosnippet to suppress the snippet entirely. Keep in mind that forcing a very short snippet can reduce click-through if the truncated text does not communicate value.

Can meta robots directives conflict with each other? +

Yes. The most common conflicts are nosnippet combined with max-snippet:N (the snippet is already suppressed, so max-snippet has no effect) and noindex combined with follow in a way that suggests you still want link equity passed while blocking the page itself. This tool flags those combinations so you can decide whether the redundancy is intentional. Conflicting directives waste crawl budget and produce unpredictable indexing behavior.

Does noarchive still work in Google? +

The noarchive directive historically prevented search engines from showing a cached copy of the page. Google removed the visible "Cached" link from search results in 2024, so noarchive has little practical effect in Google today. Other search engines may still honor it. If you rely on noarchive for compliance reasons, keep it, but do not expect it to meaningfully change how your pages appear in Google results.

How does this meta robots generator work? +

You toggle the directives you need, and the tool builds the corresponding meta tag in real time: the content attribute value, the full HTML tag, and a readable list of every directive it contains. It also checks for redundant or conflicting combinations, such as nosnippet paired with max-snippet:0, and warns you before you deploy. Everything runs in your browser; nothing is sent to a server.