Autonomous Agentic AI Pipeline

Free browser tool / Googlebot text search

Robots meta tag reference: every directive

Every robots meta directive that matters in 2026, in one table: syntax, effect, and the default when the tag is absent. Directives are case-insensitive and comma-separated. Unknown values are ignored, so a typo silently disables the whole intent.

The full directive table

DirectiveEffectDefault if absent
indexPage may be indexedYes, indexed
noindexDrop from index, do not storeIndexed
followCrawl links on the pageYes, followed
nofollowDo not crawl links on the pageFollowed
noneSame as noindex, nofollowBoth allowed
noarchiveNo cached copy in search resultsCache allowed
nosnippetNo text snippet or video previewSnippet allowed
max-snippet: NSnippet capped at N characters, 0 means noneUnspecified
max-image-preview: settingnone, standard, large, or none-larger for AMPUnspecified
max-video-preview: NVideo preview capped at N secondsUnspecified
notranslateNo translation offered in resultsTranslation allowed
noimageindexPage images not indexedImages indexed
unavailable_after: RFC dateDrop from results after the dateNo expiry
nositelinkssearchboxNo sitelinks search boxBox possible
indexifembeddedIndex even with noindex when embedded via iframeNoindex wins

Where the tag goes

The tag sits in the head of the document. Google reads the first head block it finds, even if the document has a second head later in the markup, and it does not read robots meta in the body. One tag per page is the safe pattern; if two tags on the same page conflict, Google applies the most restrictive combination across them.

If you do not specify a tag at all, the effective value is index, follow. Explicitly writing that is legal but redundant.

User-agent overrides

Each user-agent line is an independent grant. You can tighten rules per bot:

<meta name="robots" content="nofollow">
<meta name="googlebot" content="noindex">
<meta name="googlebot-news" content="nosnippet">

Google applies the union of the most restrictive directives it reads for itself. A directive under googlebot applies to Googlebot only; every other engine falls back to the robots line. Bing reads bingbot the same way. Directives Bing does not support, like unavailable_after, are ignored by that engine even when Google honors them.

Copy-paste starter head block

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Page title here</title>
<meta name="description" content="One or two sentences that a result page can show as the snippet.">
<meta name="robots" content="index, follow">
</head>

For a page that must stay out of Google but stay crawlable for other engines' link discovery:

<meta name="googlebot" content="noindex">

What the tag does not do

It does not stop crawling
The page is fetched first, then parsed. Save crawl budget with robots.txt, not noindex.
It does not work on PDFs or images
Use the X-Robots-Tag header for anything that is not HTML.
It does not act instantly
Directives apply at recrawl time. Until then the old state persists in the index.
It does not override canonical
Conflicting noindex plus canonical gives Google two contradictory instructions; results are unpredictable. Choose one.

Verify any page in one paste: the meta robots checker parses the head of a live URL and shows which directives Google will read, with a companion FAQ for edge cases.

Related pages