Noindex & Nosnippet: The Tags Hiding You From AI

If ScoutRival’s Site Audit flagged “No noindex or snippet-suppression directives,” it means one of your pages is carrying a tag that tells search and AI engines either not to index it at all, or not to quote from it — and since AI answers are built by retrieving and quoting indexed pages, that tag can make you invisible in AI results even while everything else looks healthy. This guide explains the difference between the two problems and walks you through removing them on every major platform. Most cases are a single checkbox; the header-level ones need a hand from a developer.

Two different problems that look the same

There are two families of directive here, and it’s worth understanding the difference, because they fail in slightly different ways.

1. noindex — the total block. This tag tells engines: don’t put this page in your index at all. Every AI engine retrieves and cites from a search index (Google’s, Bing’s). If your page isn’t in the index, there’s nothing for ChatGPT, Perplexity, Gemini or Claude to find or quote. noindex is the bluntest way to disappear.

2. Snippet suppression — the quiet muzzle. These are subtler and, frankly, sneakier:

• nosnippet — don’t show any text snippet from this page.
• max-snippet:0 — allow zero characters of snippet.
• data-nosnippet — a page-level HTML attribute marking a specific block as “don’t quote this.”
• noarchive — don’t keep a cached copy.

Here’s why these matter for AI: Google’s AI surfaces (AI Overviews and Gemini’s grounded answers) honour these snippet directives. So your page can still be indexed, still rank normally in classic search — and yet be excluded from being quoted in an AI answer, because you’ve told Google it may not show an excerpt. Classic ranking looks completely fine, which is exactly why this hides.

Why it’s almost always an accident

Very few businesses set these on purpose. The usual sources:

• A page-builder or theme default that ships new pages as noindex.
• A “hide from search engines” toggle left on after a page was in draft.
• The WordPress “Discourage search engines” checkbox (which applies noindex sitewide).
• A per-post SEO-plugin setting clicked by mistake — Yoast’s “Allow search engines to show this page?” set to No, or a Rank Math “No Index” box ticked.
• A server or CDN rule emitting an X-Robots-Tag: noindex header — the hardest to spot, because it’s invisible in your page’s HTML.

Let’s clear them in order, sitewide first, then per-page, then the header case.

Step 1 — Rule out the sitewide block (WordPress)

Go to Settings → Reading and confirm “Discourage search engines from indexing this site” is unchecked. When ticked, WordPress adds a noindex to your entire site — the fastest way to be invisible everywhere at once, including in Google and Bing’s indexes that AI engines borrow. This one box is the most common cause of “the whole site disappeared.”

Step 2 — Fix it per page

WordPress (Yoast)

1. Edit the page or post.
2. Open the Yoast SEO panel → Advanced tab.
3. Set “Allow search engines to show this page in search results?” to Yes.
4. Set “Should search engines follow links on this page?” to Yes.
5. Below that, check the “Meta robots advanced” field and make sure No Snippet, No Image Index and any max-snippet limit are not selected.
6. Update the page.

WordPress (Rank Math)

1. Edit the page → open the Rank Math panel → Advanced tab.
2. Under Robots Meta, uncheck No Index, No Snippet and No Archive.
3. Update.

Wix

Open the page → SEO settings (the Marketing & SEO → SEO Tools panel or the page’s own SEO tab) → make sure “Let search engines index this page” is on and no snippet restriction is enabled. Save and publish.

Squarespace

Squarespace controls this per page, not via robots.txt. Open the page’s Settings → SEO and turn off “Hide this page from search engines.” For a whole site, check Settings → Marketing → SEO / Site availability isn’t set to hidden or password-protected.

Webflow

1. Open the page’s Settings (gear icon) → SEO settings.
2. Turn off “Sitemap indexing” exclusions and make sure “Disable indexing” is unchecked for that page.
3. Check Project Settings → SEO for any global noindex in the custom robots.txt or head code.
4. Save and Publish.

Shopify

Shopify pages are indexable by default, but a theme or app can inject a noindex. Check any SEO app’s per-page settings, and search your theme’s theme.liquid <head> for a hand-added <meta name="robots" content="noindex">. Remove it and save.

Any other site (custom or unlisted CMS)

Open the page and View Source (Ctrl-U). Search for noindex, nosnippet, max-snippet and data-nosnippet. Remove the offending directive in your CMS’s SEO settings, or from the template’s <head> if it’s hand-coded.

Step 3 — Check the header-level case (X-Robots-Tag)

This is the one that fools people. A noindex can be delivered as an HTTP response header instead of a meta tag — so it’s completely invisible when you View Source, but engines still obey it. It’s usually set at the server or CDN level.

To find it:

1. Open your browser’s DevTools → Network tab, reload the page, click the main document request, and read the Response Headers.
2. Look for a line like X-Robots-Tag: noindex (or nosnippet).
3. If it’s there, it’s coming from your server config, a CDN rule, or a plugin adding headers — a developer or your host must remove it. A per-page SEO toggle won’t touch it, because it isn’t in the page’s HTML.

Step 4 — Verify it worked

• View Source (Ctrl-U): no noindex, no nosnippet, no max-snippet:0, no data-nosnippet.
• DevTools → Network → Response Headers: no X-Robots-Tag: noindex.
• Google Search Console → URL Inspection: the page should report “Indexing allowed? Yes.”
• Re-run your ScoutRival Site Audit — the AC4 check should turn green.

Common mistakes to avoid

• Only checking the meta tag. A noindex in the X-Robots-Tag header is invisible in View Source. Always check the response headers too.
• Fixing one page and missing the sitewide toggle. The WordPress “Discourage search engines” box overrides every page. Clear it first.
• Assuming healthy Google rankings mean you’re fine. A nosnippet or max-snippet:0 can leave you ranking normally while quietly excluding you from AI answer excerpts.
• Leaving data-nosnippet on the block AI most wants to quote. People sometimes wrap pricing or key answers in data-nosnippet to “protect” them — which tells AI not to cite exactly that.
• Confusing noindex with a robots.txt block. They’re different tools. robots.txt controls crawling; noindex controls indexing. If a page is blocked in robots.txt, engines may never even see the noindex — see How to Let ChatGPT, Perplexity & Claude Crawl Your Site.
• Forgetting to re-publish. On Wix, Webflow and Shopify, a settings change only goes live after you publish.

The bottom line

noindex takes you out of the indexes AI engines quote from; nosnippet and its cousins let you rank but forbid the excerpt an AI answer would lift. Both are usually accidental, and both are easy to clear — flip the Yoast or Rank Math toggles, uncheck the sitewide “discourage” box, and check the response headers for a hidden X-Robots-Tag. Then confirm “Indexing allowed? Yes” in Search Console.

Not sure which of your pages carries one of these tags — or whether it’s in the HTML or the headers? Run a free Site Audit with ScoutRival — it checks both the meta robots tag and the X-Robots-Tag header across your site and gives you a plain-English fix for each page it flags.