ubricHelp

Does noarchive stop Copilot using my page?

Rubric check: noarchive or nocache tag that limits Copilot (check id ne_bing_noarchive_nocache_copilot)

Yes, for now. Bing's Webmaster Guidelines say NOARCHIVE keeps a page out of Copilot answers, and NOCACHE lets Copilot use only its URL, title and snippet. Rubric flags pages that send either one.

Free, no card. Your report opens with this check first.

Why it matters for SEO

Neither tag removes a page from normal Bing or Google results. Google stopped showing cached pages, so noarchive does little there today.

They're often left in a theme or a security plugin from years ago, when people used them to hide the cached copy. Check whether yours is deliberate.

Does this matter for ChatGPT and AI Overviews?

This one matters for Copilot. A page with NOARCHIVE can't be quoted or linked in Copilot answers, and NOCACHE leaves it only a title and snippet to work with.

Bing has said it will stop reading these two tags for AI use on 1 March 2027 and read a new ai-grounding setting instead. Rubric stops this check on that date.

How Rubric scores it

StandardStandard checks are the baseline every other tier is measured against.

Why this tier: Stops Copilot using the page.

It is judged on every page Rubric scores.

Every Rubric score starts at 100. When this check fails, it takes up to 12 points off. Even one failing page costs at least 6 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.

This check doesn't cap your score. It only takes off its own points.

From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).

How common it is

Found on 3 of 299 sites where Rubric could judge it (1.0%). That is 3 of 286 judged sites in Rubric's 313-site test set and 0 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.

1.0% of the sites Rubric could judge have this problem. Check yours.

Free, no card. Your report opens with this check first.

How accurate the check is

Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)

Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.

How to fix it

WordPress

  1. View the page source and search for noarchive and nocache.
  2. In Rank Math, open the post's Advanced tab and untick No Archive under Robots Meta. Also check Rank Math > Titles & Meta for a site-wide default.
  3. In Yoast, check the post's Advanced settings for No Archive under the advanced meta robots options, where your version offers it.
  4. If it's in the response header, look for an X-Robots-Tag rule in your security plugin, .htaccess or host settings.

Shopify

  1. Shopify doesn't add noarchive or nocache by default.
  2. View the page source. If you find the tag, go to Online Store > Themes > Edit code, search theme.liquid and your snippets for noarchive, and remove the tag.
  3. If an SEO app added it, turn the setting off in that app.

Webflow

  1. Webflow doesn't add these tags by default.
  2. Check Site settings > Custom code > Head code and each page's Custom code in page settings for a robots meta tag with noarchive or nocache.
  3. Remove those words (keep any other rule you meant to set), then publish.

Custom code

Remove noarchive and nocache from the robots meta tag and any X-Robots-Tag header:

html
<meta name="robots" content="index, follow">

If you want to keep a page out of Copilot on purpose, leave the tag in place. From 2027 use Bing's ai-grounding setting for that instead.

More bot access checks · The full AI SEO glossary

Free, no card. Your report opens with this check first.