The meta robots tag is a single line of HTML that controls how a search engine treats a specific page once it's been crawled — whether to index it, whether to follow its outbound links, whether to show a cached snapshot, and several narrower directives besides. This tool builds a correct, properly-formatted tag from a set of checkboxes, so the exact comma-separated directive syntax never has to be typed from memory.
Why this is a page-level control, distinct from robots.txt
It's worth being precise about where this directive actually lives in a crawler's process, because confusing it with robots.txt is a common and consequential mistake. Robots.txt is a single file, fetched once per site (or per subdomain), consulted before a crawler decides whether to request a given URL at all — it's a gatekeeper sitting in front of the actual page. The meta robots tag, by contrast, lives inside a specific page's own <head>, and can only be read after a crawler has successfully fetched and parsed that page. This ordering has a direct, practical consequence: a page blocked by robots.txt will never have its meta robots tag seen or honored at all, because the crawler stops before it ever gets that far. If you want a specific page to have a real, reliably-enforced noindex, the page must be crawlable — no robots.txt Disallow rule blocking it — precisely so the crawler can actually reach and read the noindex instruction sitting inside it.
Each directive, and what it's actually for
noindex is the most consequential directive here: it tells a search engine not to include the page in its index at all, meaning the page won't appear in search results under any query. This is the correct tool for pages that should stay live and accessible but shouldn't be discoverable through search — thank-you pages, internal search result pages, duplicate content variants, admin or account pages that happen to be technically public. nofollow, when applied at the page level via this tag, tells a crawler not to pass any ranking signal through the links found on that page — a narrower, less commonly needed directive than link-level rel="nofollow" attributes, generally reserved for pages whose entire outbound link set shouldn't carry endorsement weight. noarchive prevents a search engine from showing a cached, saved snapshot of the page — relevant for pages whose content changes frequently or shouldn't be viewable in an outdated form. nosnippet suppresses any text, image, or video preview in the search result listing, while still allowing the bare page to be indexed and shown as a plain link. noimageindex prevents images on the page from being indexed by image search specifically, without affecting the page's own indexing. notranslate asks Google not to offer an automatic translation of the page in search results. max-snippet, max-image-preview, and max-video-preview give finer control over how much preview content search results are allowed to show, rather than an all-or-nothing suppress.
The most damaging mistake: noindex leaking into production
Of every mistake covered in this tool's documentation across the site, an accidental noindex on a production page is probably the single most damaging and hardest to notice without deliberately checking for it. A staging or development environment commonly has a sitewide noindex applied — entirely correctly, since a staging site genuinely shouldn't be indexed — but that same template, if promoted to production without the noindex being explicitly removed or made environment-conditional, silently starts telling search engines to drop pages that were previously ranking perfectly well. Because the page renders completely normally to a human visitor, and because deindexing from an existing noindex tag doesn't happen instantly (it typically takes effect the next time the page is recrawled), this exact mistake can go unnoticed for days or weeks while organic traffic quietly drains away, with no obvious symptom pointing directly at the cause until someone thinks to check the actual meta robots tag in the page's rendered HTML.
Combining directives correctly
Multiple directives combine into a single comma-separated list inside one content attribute — content="noindex, nofollow", not two separate meta tags. It's also worth knowing that noindex and nofollow combined is sometimes written as the shorthand none, which is exactly equivalent to noindex, nofollow together — some templating systems or CMS platforms use one form or the other by convention, and both are correctly interpreted by every major search engine.
When a separate googlebot-specific tag is actually needed
By default, a single <meta name="robots" content="..."> tag applies identically to every crawler that respects the directive. A separate <meta name="googlebot" content="..."> tag is only needed in the rare case where you specifically want Google's crawler to behave differently from other search engines' crawlers — genuinely uncommon, and worth adding only when there's a concrete, specific reason for the divergence rather than as a default habit.
The HTTP header alternative
Everything this tool generates as a <meta> tag has an equivalent HTTP response header form — X-Robots-Tag: noindex, nofollow, sent alongside the page response itself rather than embedded inside the HTML. This matters for content that isn't HTML at all: a PDF, an image, or any other file type served directly has no <head> element to put a meta tag inside, so the HTTP header is the only way to apply the same directives to that kind of file. For ordinary HTML pages, the meta tag and the header achieve an identical effect, and which one a given site uses is usually just a matter of which is easier to configure within its specific server or CMS setup — a templating engine that can easily inject a meta tag into every page's head, versus a server or CDN configuration that can easily attach a header rule to a whole path pattern at once.
Directives this tool intentionally leaves out
A handful of older or narrower robots directives exist beyond what this tool generates — unavailable_after, for instance, which tells a search engine to stop showing a page in results after a specific date, useful for genuinely time-limited content like an expired promotion or a closed job posting. These are legitimate but considerably less commonly needed than the directives this tool focuses on, and are worth knowing exist even if a dedicated generator field for each isn't included here.
Templating logic, CMS conditionals, and environment variables all introduce room for a meta robots tag to render differently than intended in a specific context. Always check the actual rendered HTML of a live, important page — via view-source or a tool like this one's SERP preview and schema validator siblings — rather than trusting that the template code looks correct in isolation.