Free · Fast · Privacy-first

Meta Robots Tag Generator

The meta robots tag gives you precise per-page control over search engine indexing, link-following, snippet display, and caching behaviour that the broad-strokes robots.txt file simply cannot match.

⚡

All major robots directives: noindex, nofollow, noarchive, nosnippet

🔒

Combined directive support

✨

Googlebot-specific directives

⚡

No sign-up required

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this Meta Tags to your website

Drop the Meta Tags into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/seo-tools/meta-tags?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Meta Tags by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/seo-tools/meta-tags?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Meta Tags by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Meta Robots Tags vs robots.txt: Choosing the Right Indexing Control Method

Two complementary mechanisms control how search engines interact with your content, and understanding which one to use for each scenario is the foundation of correct indexing management on any site beyond a handful of pages. Robots.txt is a plain text file at your domain root that controls crawler access at the URL pattern level, telling crawlers which URLs they are allowed to fetch at all. The meta robots tag is an HTML element embedded inside the head section of each page that controls indexing behaviour at the individual page level, telling search engines what to do with the page once they have crawled it. They operate at different stages of the crawl-index pipeline and serve fundamentally different purposes. Robots.txt operates at the crawl stage and prevents crawlers from fetching certain URLs at all, saving your crawl budget for important pages and protecting server resources from unnecessary bot traffic. The meta robots tag operates at the index stage, where the crawler has already fetched and read the page and respects the noindex directive when deciding whether to include the URL in search results.

The directives available in the meta robots tag go well beyond the basic noindex and nofollow pair that most site owners are familiar with, and the extended directives unlock fine-grained control over how Google presents your content in search results. The noarchive directive prevents Google from showing a cached version of your page in results, which is useful for time-sensitive content like news articles or for pages you update so frequently that cached versions would be misleading or display outdated information. The nosnippet directive prevents Google from displaying any text or video snippet from the page, which suits premium or paywalled content where you want the URL to appear but do not want the algorithm to expose your content in the snippet. The max-snippet:N directive sets a specific character limit on text snippets, useful for subscription or metered content. The max-image-preview directive set to standard, large, or none controls the size of image thumbnails shown alongside your result. The max-video-preview directive controls video preview length. Together these extended directives give you precise editorial control over how Google presents your content without fully removing it from search.

The single most important operational rule that catches teams out repeatedly is never to block in robots.txt a page you also intend to mark noindex via the meta robots tag, because the two directives operate at incompatible stages of the crawl-index pipeline. If robots.txt blocks the page from being fetched, crawlers never read the page at all and therefore never see the noindex meta tag in its head section. The page may still appear in search results as a URL-only result with no title or description if it has any inbound links from elsewhere on the web, because Google can include URLs in its index based on link references even when it has never successfully crawled the destination. For pages you want completely removed from search results, follow the correct sequence: first ensure the page is crawlable and not blocked in robots.txt, second add the noindex meta robots tag, third wait for Google to recrawl and process the directive, and only after noindex has been confirmed in Search Console can you optionally add a robots.txt block for crawl efficiency.

Combining directives correctly inside a single meta robots tag is also a frequent source of subtle bugs that depress site performance for months before anyone notices. The directives are comma-separated inside the content attribute, for example content noindex, nofollow or content noindex, follow, and the order does not affect interpretation. However certain combinations create logical conflicts that confuse search engines and produce unpredictable results. Combining noindex with a canonical tag on the same page tells Google simultaneously not to index the page and to consolidate ranking signals onto another URL, which is contradictory because a noindex page has no ranking signals to consolidate. Combining noindex with hreflang declarations sends similarly mixed messages about whether the page exists as a translation target. Combining nofollow with internal navigation links accidentally blocks ranking authority flow through your own site. Audit your meta robots implementations alongside your canonical, hreflang, and internal linking strategy to catch these conflicts before they affect ranking quality.

Google Search Central: Robots Meta Tag Reference Google Search Central: robots.txt Specifications

How to use this tool

💡

Select the directives you need and the generator will produce the correctly formatted meta robots tag HTML.

How It Works

Step-by-step guide to meta robots tag generator:

1
Choose your directives
Select from the available directives based on what you want each crawler to do with the page. Index or noindex controls whether the page appears in search results. Follow or nofollow controls whether ranking signals pass through the links on the page. Noarchive prevents the cached version from being shown. Nosnippet blocks the description snippet from appearing alongside the URL. Max-snippet, max-image-preview, and max-video-preview offer fine-grained display controls for premium or metered content.
2
Select the target bot
Choose robots for the default rule that applies to every compliant crawler across the web, which is the right choice for the vast majority of meta robots implementations. Choose googlebot to set a Google-specific directive that overrides the generic robots rule on that page for Google crawlers only. Choose bingbot for a Bing-specific directive. You can include multiple meta robots tags on the same page with different bot targets when you need different behaviour per crawler, although most sites get by with a single default robots tag.
3
Generate the tag
Click Generate to produce the correctly formatted meta robots tag HTML using the standard meta name and content attribute syntax expected by every major search engine. The generator handles directive ordering, comma separation, and escaping for you, eliminating the manual typos that frequently cause robots directives to fail silently. Copy the resulting tag block, which is ready to paste into any HTML page without modification regardless of which CMS or framework powers the site.
4
Add to your page head
Paste the tag into the head section of every page where the directive should apply, placing it near the top of the head before any large script blocks so it is parsed early by crawlers that may abort processing on heavy pages. Confirm the tag is present by viewing the page source after deploying, ideally using Search Console's URL Inspection tool which shows exactly how Googlebot reads the page including the meta robots directive it extracts. Monitor the Coverage report over subsequent recrawl cycles to verify Google is respecting the directive as intended.

Real-world examples

Common situations where this approach makes a real difference:

Staging site protection

A developer spinning up a staging site on a public subdomain of the live production domain adds noindex meta robots tags to every page on the staging environment before pointing the DNS record at the new server, preventing staging content from appearing in search results during the testing window. The team also adds HTTP basic authentication as a belt-and-braces measure, but the noindex tag remains the primary defence because authentication can be temporarily disabled for client review sessions and the noindex continues protecting the environment from accidental indexing. Once the production launch is complete, the noindex tags are removed from the production deployment so the live pages can rank, while the staging environment retains them indefinitely.

Thin content exclusion

An e-commerce site running a Magento installation discovers via a Screaming Frog crawl that hundreds of automatically generated filtered category pages with little unique content beyond a filter parameter are being indexed alongside the main category pages, splitting ranking authority and competing against the canonical category URLs in search results. The SEO team adds noindex meta robots tags to every filter parameter combination via a template-level change, while keeping the canonical tags pointing to the main category as a complementary signal. Over the following indexing cycles Google drops the thin variants from search results and concentrates ranking authority onto the main category pages, which subsequently climb measurably for their target queries.

User account pages

A SaaS platform adds noindex, nofollow meta robots tags to every user dashboard, account settings page, billing page, and internal application route to prevent private user content from being indexed by accident and to stop search engines from following any links on those pages back into authenticated areas. The combination of noindex and nofollow ensures these pages contribute no ranking signals to public search and pass no equity through their internal links, which is exactly the desired behaviour for authenticated application surfaces that should never appear in any search context regardless of how they are linked elsewhere on the web or from internal navigation paths.

When to use this guide

Use this when you need to prevent specific pages from appearing in search results, stop link equity flowing through certain pages, or control how snippets and cached versions of pages appear in Google.

Pro tips

Get better results with these expert suggestions:

Never block noindex pages in robots.txt simultaneously

This is the single most common meta robots implementation error and it produces exactly the opposite outcome from what teams intend when they apply both controls. If robots.txt blocks a URL from being crawled, Google never fetches the page and therefore never reads its noindex tag, leaving the URL potentially indexable as a title-less search result if it has any inbound links anywhere on the web. Always allow crawlers to access pages you want noindexed so they can fetch the page, read the directive, and respect it. Use robots.txt blocks only for pages where crawling itself is wasteful and you do not need the noindex layer.

Use noindex on filtered e-commerce pages

Product category pages with filter parameters like color=red, size=L, or sort=price_asc create dozens or hundreds of near-duplicate URLs that compete against each other and against the main category page for the same ranking signals. Adding noindex to every filtered variant while keeping canonical tags pointing to the main category page concentrates your indexing budget and ranking authority on the main category URL without splitting it across hundreds of thin variants. The combined noindex plus canonical pattern is one of the highest-leverage technical SEO wins available on any e-commerce site running faceted navigation.

Add noindex to thank-you and confirmation pages

Post-conversion pages including order confirmations, form thank-you pages, account setup completion screens, password reset confirmations, and similar acknowledgement pages should always carry noindex meta robots tags. These pages have no search ranking value because they only make sense in the context of an immediately preceding action, and they create a poor user experience when they appear in search results as out-of-context entry points into checkout or account flows. Implement the noindex via a template-level change so every page of this type inherits the directive automatically without depending on per-page manual configuration that inevitably drifts.

Monitor noindex pages in Search Console

Google Search Console's Pages report includes an Excluded by noindex tag section listing every page Google has discovered but respects as noindex according to the directive in your page head. Review this list quarterly to confirm only intended pages appear in the excluded set, and investigate any unexpected entries promptly because finding important content pages in this list almost always indicates a noindex tag was applied accidentally through a template misconfiguration, a CMS bug, or an SEO plugin setting that nobody documented. Catching these errors quickly limits the traffic damage.

Do not use noindex and canonical together on the same page

Adding a canonical tag to a page while also marking it noindex creates a logical conflict. If you don't want a page indexed, use noindex. If you want it indexed but under a different URL, use canonical without noindex.

Use noindex for thank-you and confirmation pages

Post-conversion pages (order confirmations, form thank-you pages) should be marked noindex to prevent them from ranking in search and showing as entry points to a checkout flow with no context.

Prefer robots.txt for blocking entire sections

Meta robots tags work at the page level. If you want to block an entire directory (e.g., /admin/ or /staging/), use a robots.txt disallow rule instead of adding noindex tags to hundreds of individual pages.

FAQ

Frequently asked questions

A meta robots tag is an HTML element placed inside the head section of a webpage that communicates indexing and crawling instructions to search engine bots on a per-page basis. It provides page-level control over whether search engines should index the page, follow its outbound links, cache the content, show a text snippet alongside the URL, display image thumbnails, or apply any of several other display-level controls. The meta robots tag is more granular than robots.txt, which operates at the URL pattern level across the entire site rather than on individual pages, and the two mechanisms complement each other in a complete indexing management strategy. Together they cover every common scenario from blocking entire directories to fine-tuning the display of a single high-value page.

The noindex directive tells search engines not to add the page to their search index, with the practical effect that the URL will not appear in any search results regardless of how many inbound links it accumulates. The nofollow directive tells search engines not to follow the links on the page or pass ranking value through them to the destination URLs. The two directives operate completely independently and can be combined in any pattern. A page can be marked noindex with follow, where the page itself does not rank but its links still pass equity. It can be marked noindex with nofollow, where neither the page nor its links contribute anything. It can be index with nofollow, which is rare but legitimate for affiliate-heavy or sponsored content pages.

Yes, Googlebot and other compliant crawlers will continue to visit a noindex page to check for changes to the directive, because the noindex status itself can be removed in a future update and crawlers need to recheck periodically to detect the change. If you want to also prevent crawling to save crawl budget for large excluded sections of the site, add the URL pattern to robots.txt as well, but only after Google has confirmed the noindex directive has been processed and the URL has been removed from search results. Adding a robots.txt block before noindex propagates leaves the URL potentially indexed as a title-less result because the crawler never reads the noindex tag once the URL is blocked.

No, removal happens the next time Google crawls the page and processes the noindex tag, which depends entirely on how often Googlebot visits the URL in question. For a frequently crawled high-authority site, the removal may complete within a few days of the directive being added. For low-traffic pages on smaller sites with longer crawl intervals, removal could take weeks or even months as Googlebot works through its priority queue. If you need urgent removal, use Google Search Console's URL Removal tool, which temporarily removes the page from results within hours while waiting for the natural noindex crawl to permanently process the directive in the background.

Robots.txt prevents crawlers from fetching certain URLs at all, controlling crawl access at the URL pattern level before any page content is read. Meta robots tags are read from the crawled page content itself and control indexing behaviour after the page has been successfully fetched. Use robots.txt to block large sections like admin areas, staging environments, internal search results, and private directories where crawling itself is wasteful and you do not need page-level granular control. Use meta robots tags for individual pages where you want to control indexing, caching, snippets, or image previews without preventing crawl access entirely. Combining them incorrectly produces the worst outcome where pages remain indexed but with no title or description.

Use the noarchive directive when your page contains time-sensitive content that changes frequently, premium or paywalled material where the cached version would expose content you intend to gate, or any page where a cached snapshot in Google's archive would be misleading by showing outdated information that no longer matches the live page. News articles with live updates throughout the day, e-commerce pages displaying real-time pricing or inventory levels, and pages behind soft paywall metering systems are common noarchive use cases. The directive prevents users from accessing an older cached version via the Cached link in search results, which Google has been gradually deprecating but still surfaces in some contexts and through third-party caching services.

The max-snippet directive followed by a colon and an integer limits the character length of the text snippet Google displays in search results alongside your URL. For example, max-snippet:100 restricts the snippet to one hundred characters maximum, while max-snippet:0 disables text snippets entirely. This is useful for subscription content, premium articles, news sites participating in the European Copyright Directive opt-in, or any page where you want to tease content without giving away the key value in the SERP snippet itself. Google's news licence programme allows opt-out sites to use max-snippet:-1 to remove the limit entirely while opted-in sites use specific positive values to control display length per page or per directory.

Yes, you can include multiple meta robots tags inside the same head section when you need to apply different directives to different crawlers, for example to give Googlebot one rule and Bingbot a different rule on the same URL. Use a separate meta tag with the appropriate bot name for each crawler-specific rule. However, combining multiple meta robots tags targeting the same bot creates ambiguity that crawlers may resolve unpredictably, so use a single tag with comma-separated directives when you want to apply multiple directives to a single bot. Keep the implementation simple where possible because complex multi-tag configurations are difficult to audit and easy to break during template updates.

Use Google Search Console's URL Inspection tool to view exactly how Googlebot reads each page, including the meta robots directive it extracts and how it interprets that directive for indexing decisions. The Coverage report shows pages excluded by noindex tags in a dedicated section that should match your expectations of which pages are intentionally excluded from the index. Crawl your site with Screaming Frog or Sitebulb to extract the meta robots directive from every URL and audit the results in a spreadsheet, flagging any unexpected noindex tags on important content pages or missing noindex tags on pages that should be excluded. Spot-check the most critical pages manually via view-source.

The X-Robots-Tag is an HTTP response header that carries the same directives as the meta robots tag but applies at the HTTP response level rather than inside the HTML body, making it useful for non-HTML resources like PDFs, images, videos, and other files where you cannot add a meta tag because there is no HTML head section. It is also useful for applying directives at the server level across entire directories via web server configuration rather than per-page templating. Google and Bing respect both mechanisms equivalently, so use whichever is more convenient for your specific scenario. For HTML pages the meta robots tag is usually easier, while for binary files the X-Robots-Tag header is the only option.