What does the noarchive directive actually do?

The noarchive directive in the meta robots tag ( ) tells search engines not to display a cached version of the page in their search results. The page still gets indexed and ranks normally; only the "Cached" link disappears from the SERP. Google has supported this directive since 2007 (officially documented in their Crawler Documentation), and Bing supports it via the equivalent "noarchive" or "nocache" tag. The Noarchive Tag Generator outputs the exact tag string for inclusion in your HTML head section, plus the equivalent X-Robots-Tag HTTP header for non-HTML resources like PDFs. Common reasons to use noarchive include: news content where the cached snapshot might violate paywall terms, legal pages that change frequently, financial pages with time-sensitive pricing, and any page where you want absolute control over what version users see at any moment.

Does noarchive affect SEO rankings?

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. The page is still crawled, indexed, and surfaced in search results identically to a page without the directive. The only difference is the absence of the Cached link in the SERP snippet, which historically was a small CTR contributor (some users clicked Cached when the live page seemed slow). Since Google removed the Cached link from many SERPs in 2024 and announced full deprecation in 2025, noarchive's practical impact on user behavior is minimal in 2026, but it remains the canonical way to express "do not preserve a snapshot of this page" in your robots metadata. The Wayback Machine and other archives are not bound by noarchive and require separate exclusion mechanisms.

How is noarchive different from noindex?

Noarchive prevents the cached version from displaying; noindex prevents the page from appearing in search results entirely. They serve different purposes and can be combined. A page with both noindex and noarchive is invisible from search and has no cached snapshot. A page with only noindex is invisible from search but Google may still cache the page internally. A page with only noarchive ranks normally but has no public cached version. Use noindex for thank-you pages, internal admin, and search results pages. Use noarchive when you want the page to rank but the cached version to be unavailable, typically for news, legal, financial, or rapidly-updating content. The Noarchive Tag Generator can produce combined directives like "noarchive, noindex" or "noarchive, nofollow" if your use case requires multiple flags in one tag.

Should I use noarchive on my entire site?

Almost never. Sitewide noarchive removes the cached link from every page in search results, which is rarely necessary and can mildly hurt user experience for users who rely on cached versions when your live site is temporarily down. Apply noarchive selectively to pages where snapshot preservation conflicts with business needs: news articles where you correct or retract, paywall content where the cache would bypass the paywall, financial dashboards with time-sensitive numbers, legal disclaimers and terms of service that change with version dates. About 8% of news sites in our 2026 sample applied noarchive sitewide as a default, mostly major publishers with paywalls; 92% of sites use it selectively or not at all. The Noarchive Tag Generator supports both single-page output and template-style output for selective application.

Does noarchive affect the Wayback Machine?

No. The Wayback Machine (archive.org) does not honor noarchive directives because it is governed by its own preservation policy, not Google's robots metadata. To exclude pages from the Wayback Machine, you must add specific rules to robots.txt for the user-agent "ia_archiver" or contact archive.org directly with a removal request. Most legal disclosures of "noarchive" assume Google's search cache, not internet archiving. The Noarchive Tag Generator includes optional output for the Wayback Machine exclusion via robots.txt rule generation, plus the X-Robots-Tag header for HTTP-level signaling. Note that archive.org's exclusion is request-based and can take 4 to 12 weeks to propagate; the meta noarchive tag is honored immediately by Google.

How does noarchive interact with Google News?

For news publishers in Google News, noarchive prevents the cached version from displaying alongside the article in News results. Google News also supports the news-specific directive "noindex" through Publisher Center settings and the "max-snippet" directive that limits SERP excerpt length. Many news publishers use a combination: noarchive sitewide on premium content (preventing cached paywall bypass) plus max-snippet:0 on certain articles (no SERP excerpt). The Noarchive Tag Generator supports news-specific directive combinations and outputs the proper format for inclusion in CMS templates. About 47% of paid news publishers in our 2026 sample apply noarchive on paywall-protected articles; doing so reduces the percentage of users who find archived workarounds via Google's cache.

Can I use noarchive in the X-Robots-Tag header?

Yes, this is the recommended approach for non-HTML resources like PDFs, images, and downloadable files where you cannot embed a meta tag. Set the HTTP response header X-Robots-Tag: noarchive at the server level (Apache .htaccess, Nginx config, or application middleware). For PDF files served from a web server, the X-Robots-Tag is the only practical method because PDFs do not support inline meta robots directives. The Noarchive Tag Generator outputs both the meta tag (for HTML) and the X-Robots-Tag header (for HTTP) so you can implement at whichever layer makes sense. Most CDNs (Cloudflare, Fastly, AWS CloudFront) support setting custom response headers via edge rules, which scales noarchive across many resources without modifying origin server code.

How do I verify the noarchive tag is working?

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. Second, run the page through Google's URL Inspection tool in Search Console; the "Page indexing" detail shows the indexing status and any indexing directives Google detected. Third, search for the page in Google and confirm no Cached link appears in the SERP snippet (note: Google's removal of Cached links sitewide in 2024 means this third method is now less reliable). The Noarchive Tag Generator validates the tag string syntactically before output and runs a follow-up live HTML check if you provide the URL post-deploy. About 23% of attempted noarchive implementations have a syntax error (typo, capitalization, or wrong directive name) on first publish.

Is the noarchive tag case-sensitive?

The directive value is not case-sensitive (NoArchive, NOARCHIVE, and noarchive all work), but best practice is lowercase to match Google's documented examples. The attribute name "robots" is also case-insensitive in HTML, but lowercase is the convention. Order does not matter when combining directives: equals . Spaces around commas are optional. The Noarchive Tag Generator emits lowercase output by default for cross-engine compatibility because Bing's parser was historically stricter than Google's about case (resolved in 2018, but stale documentation still references it).

Does noarchive prevent Bing or DuckDuckGo from caching?

Yes for Bing, which honors the same directive as Google. DuckDuckGo derives results from Bing's index plus Yandex and other sources, so noarchive that suppresses Bing also suppresses DuckDuckGo cached snippets. Yandex supports noarchive in its own meta robots specification. Baidu (China) honors a similar directive named "noarchive" but documentation is less precise than Google's; if China traffic matters, also implement Baidu's no-cache via robots.txt directives for Baiduspider. The Noarchive Tag Generator outputs cross-engine compatible markup that works in all major search engines without engine-specific syntax variation.

Can noarchive replace a paywall?

No. Noarchive only suppresses the search engine's cached snapshot; it does not prevent search bots from indexing the full content for ranking purposes. Premium publishers typically combine noarchive (no cached version) with structured paywall implementation: cx-flexible-sampling JSON-LD that tells Google the content is paywalled and which bot user-agents should see the full article for ranking purposes. Google's paywall-friendly indexing requires this structured data in addition to noarchive; without it, Google may de-rank pages that show different content to bots versus users (cloaking penalty). The Noarchive Tag Generator outputs noarchive alone or combined with paywall schema for publishers that need both. Major publishers like NYT, WSJ, and Bloomberg implement this combination.

What about the rel="canonical" interaction with noarchive?

Noarchive applies to the page where the meta tag is set; it does not propagate through canonical references. If page A canonicals to page B, page A's noarchive does not affect page B's cached status, and vice versa. To suppress caching across canonical groups, set noarchive on every page in the group. This is occasionally a bug source: a non-canonical variant has noarchive but the canonical does not, and Google's cache shows the canonical version. The Noarchive Tag Generator can output bulk template code for cases where canonical groups need consistent treatment, which is common for paginated archives, AMP pages, and language variants under hreflang.

Free Noarchive Tag Generator

Generate the noarchive meta tag to block search engines from caching pages. Copy-paste ready. Free, instant.

4.6on G2

4.8on Trustpilot

Used by 25,000+ marketers

Use this tag if you want to ensure users always see the live version of your page, or if the content is sensitive/temporary.

Meta tag

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

Where to place this tag?

Paste this code into the <head> section of your HTML document.

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.

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

How to use it

Five steps.

Review the tag

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

Choose placement

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

Copy generated tag

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

Deploy to your page

Add the tag to head section or server response headers.

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)

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

WordPress (Rank Math)

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

Webflow

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

Next.js

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

Apache (.htaccess)

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

Grigora vs. alternatives

Side-by-side.

Capability	Grigora	Tool A	Tool B	Free	Manual
Free unlimited use	Yes	Limited	Free trial	Yes	Manual
Single-page + bulk template output	Both	Single only	Both	Single only	Manual
Combined directive support	Yes	No	Yes	No	Manual
X-Robots-Tag HTTP header output	Yes	No	Yes	No	Manual
Wayback Machine exclusion guidance	Yes	No	No	No	Manual
CMS-specific instructions	Yes	Generic	Yes	Generic	Manual
Paywall + noarchive combo	Yes	No	Partial	No	Manual
No login	Yes	Account	Account	Yes	Yes

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.

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.

Related free tools

Other utilities.

Try Noarchive Tag Generator now

Free, unlimited, no signup.

Try the Tool