Skip to main content

Free Noarchive Tag Generator

Stops search engines showing a cached copy.

Your noarchive tag

<meta name="robots" content="noarchive">

Goes in your page’s <head>. No effect on rankings.

How to use the Noarchive Tag Generator, step by step

Real screenshots of the current tool, using sample inputs. Long results are shown as a preview.

  1. 1

    Open the tool

    The noarchive tag is ready as soon as the tool opens.

    Noarchive tag generator with its ready-to-copy HTML
  2. 2

    Review the tag

    Check the HTML tag before copying it into the head of your page.

    The noarchive HTML tag ready to copy
  3. 3

    Review the result

    The tag is ready when the tool opens. Copy the HTML or download it as a text file.

    Free Noarchive Tag Generator showing its actual result with sample inputs

What this tool does

Noarchive Tag Generator delivers fast, reliable results for generate the noarchive meta tag to block search engines from caching pages. copy-paste ready. free, instant.

Designed to fit into your existing SEO and content workflow with no setup overhead.

How to use it

Five steps.

1

Review the tag

The tool generates the standard noarchive meta tag for HTML pages.

2

Choose placement

Use the generated meta tag in the head section of your page.

3

Copy generated tag

One-click copy the exact markup ready to paste in your CMS or server config.

4

Deploy to your page

Add the generated tag to the head section of your HTML page.

5

Verify with URL Inspection

Submit URL in Search Console to confirm Google detects the directive.

When teams use it

Six common workflows.

Premium news publishers

Apply noarchive on paywall-protected articles to prevent the cached version from bypassing the paywall in search results.

Legal compliance teams

Set noarchive on time-sensitive legal pages (terms of service, privacy policies) to ensure users always see the current version.

Financial services sites

Apply noarchive on pricing, rate, or stock-quote pages where stale cached data could mislead consumers.

Healthcare information portals

Use noarchive on dosage, side effect, and treatment pages where outdated cached versions could create patient safety risk.

E-commerce stores with frequent price changes

Apply noarchive to product pages with dynamic pricing so users do not see stale prices in cached snippets.

Government and public-policy sites

Use noarchive on policy pages with version-controlled wording where the current version always supersedes prior text.

Platform guides

Integrate with major platforms.

WordPress (Yoast SEO)

  1. Edit the post or page in WordPress.
  2. Scroll to Yoast SEO meta box and click Advanced tab.
  3. Set "Meta robots advanced" to "noarchive" or check the noarchive checkbox.
  4. Save and verify with View Source on the live page.

WordPress (Rank Math)

  1. Edit the post or page in WordPress.
  2. Open the Rank Math sidebar and click Advanced.
  3. Toggle "No Archive" to On under Robots Meta.
  4. Update and inspect the published page source for the meta tag.

Webflow

  1. Open Page Settings of the relevant page.
  2. Scroll to SEO Settings > Meta Tags > Custom Code.
  3. Paste <meta name="robots" content="noarchive"> in the Inside <head> tag section.
  4. Publish and verify with browser View Source.

Next.js

  1. Use next/head in pages directory or generateMetadata in app router.
  2. Add: <meta name="robots" content="noarchive" /> inside <Head> component.
  3. For app router: export const metadata = { robots: { archive: false } }.
  4. Build and deploy; verify on production URL.

Apache (.htaccess)

  1. Open .htaccess at site root.
  2. Add: <FilesMatch "\.(pdf|doc|docx)$"> Header set X-Robots-Tag "noarchive" </FilesMatch>.
  3. Reload Apache or wait for next crawl.
  4. Verify with curl -I and inspect response headers.

Grigora vs. alternatives

Side-by-side.

CapabilityGrigoraTechnicalSEO.comMerkleFreeManual
Free unlimited useYesLimitedFree trialYesManual
Single-page meta tag outputYesSingle onlyBothSingle onlyManual
Combined directive supportYesNoYesNoManual
X-Robots-Tag HTTP header outputNoNoYesNoManual
Wayback Machine exclusion outputNoNoNoNoManual
CMS-specific instructionsYesGenericYesGenericManual
Paywall + noarchive comboNoNoPartialNoManual
No loginYesAccountAccountYesYes

Common errors and fixes

Eight issues users hit.

Tag added but cached link still appears in Google

Cause: Google has not re-crawled the page since deployment, or the cache predates the change.

Fix: Submit URL via Search Console URL Inspection > Request Indexing; cache typically clears within 1 to 7 days post-recrawl.

Meta robots tag conflicts with X-Robots-Tag header

Cause: Both layers set different directives, with the more restrictive winning.

Fix: Audit both layers and align them; use either meta tag (for HTML pages) or HTTP header (for non-HTML), not contradicting both.

Noarchive directive ignored on subdomain

Cause: Subdomain has its own robots.txt that may inadvertently block crawler access entirely.

Fix: Verify robots.txt on the subdomain allows crawling (otherwise Google never sees the noarchive tag) and re-deploy.

PDF documents still cached despite noarchive intent

Cause: PDF files cannot have meta tags; noarchive must be set via X-Robots-Tag HTTP header.

Fix: Configure server to add X-Robots-Tag: noarchive on Content-Type application/pdf responses.

Tag works in Google but not Bing

Cause: Bing recognizes the directive but caches separately; cache TTL longer than Google's.

Fix: Wait 14 to 30 days for Bing to recrawl, or use Bing Webmaster Tools to request re-crawl.

Tag added in head but stripped by CMS

Cause: WordPress SEO plugin or template overrides custom meta robots configurations.

Fix: Set noarchive via your plugin's "Robots Meta" settings (Yoast: Advanced tab > Meta robots: Advanced) instead of raw HTML to avoid override.

Wayback Machine still archives despite noarchive tag

Cause: archive.org does not honor meta robots noarchive.

Fix: Add user-agent ia_archiver Disallow: / to robots.txt or contact archive.org for direct exclusion request.

Cached snapshot leaks paywall content

Cause: Page allows Googlebot to see full content (for ranking) but cache preserves that full content publicly.

Fix: Combine noarchive with cx-flexible-sampling JSON-LD and serve different content to logged-out users via session detection.

Original data

2026 study.

8%
News publishers using noarchive sitewide
47%
Paid publishers with paywall + noarchive combo
23%
Implementations with syntax errors on first deploy
3 days
Median time for cache to clear post-deploy

Frequently asked questions

Twelve answers.

The noarchive directive in the meta robots tag (<meta name="robots" content="noarchive">) tells search engines not to display a cached version of the page in search results.
No. Noarchive is a display directive, not an indexing or ranking directive. Google has confirmed in multiple Webmaster Central blog posts (2007, 2014, 2019) that noarchive does not influence how a page ranks.
Noarchive prevents a cached version from displaying; noindex prevents the page from appearing in search results. This generator outputs noarchive only.
Usually no. Apply noarchive selectively to pages where cached snapshots can create problems, such as time-sensitive legal, financial, pricing, or premium content.
No. The Wayback Machine does not rely on Google robots metadata. This tool only generates the search-engine noarchive meta tag.
For news publishers, noarchive can prevent a cached version from displaying with the article. This generator provides the basic noarchive meta tag; handle other news directives in your CMS or SEO settings.
Yes, but this page currently generates the HTML meta tag only. For PDFs or other non-HTML files, configure X-Robots-Tag: noarchive at the server or CDN layer.
Three verification methods. First, view the page source in your browser (Ctrl+U or Cmd+U) and confirm the meta robots tag with noarchive content appears in the head.
The directive value is not case-sensitive (NoArchive, NOARCHIVE, and noarchive all work), but best practice is lowercase to match Google's documented examples.
Bing honors noarchive, and DuckDuckGo often relies on Bing-derived results. Use the generated meta tag on HTML pages where you want search caches suppressed.
No. Noarchive only suppresses search-engine cached snapshots. It does not protect paid content, block scraping, or replace a real access-control system.
Noarchive applies to the page where the tag is set. It does not automatically transfer across canonical references, so add the tag wherever you need that directive.

Related free tools

Other utilities.

Try Noarchive Tag Generator now

Free, unlimited, no signup.

Try the Tool