Noindex: Your Site Is Telling Crawlers Not to Index It
What a site-wide noindex signal is, the three places it comes from, and how to remove it.
What This Warning Means
AIO Radar checks what your site actually sends back to a crawler, not just what a setting
says it should send. When that check finds a site-wide instruction not to index anything,
it shows a warning — on the Overview tab as the first action item, and on the
Crawlers tab — before it does anything else, including before your first sync.
Why This Matters
Your site can tell crawlers not to index it three ways: WordPress's own privacy setting, an
X-Robots-Tag header from your host or CDN, or a meta robots tag from an SEO plugin or
theme. Any one of them hides every page from search and AI until it's removed — normal on
staging, usually a mistake in production.
The Three Origins
AIO Radar reports which of these it found, so you know where to look:
| Origin | What it is | Where to check |
|---|---|---|
| WordPress setting | "Discourage search engines from indexing this site" is checked. | Settings → Reading |
| Response header | Your host or CDN sends X-Robots-Tag: noindex on every response. | Your host's or CDN's dashboard/config |
| Meta tag | A <meta name="robots" content="noindex"> (or googlebot) tag is in the page <head>. | Usually an SEO plugin or your theme |
Only one of these needs to be present to block indexing entirely — they aren't additive,
and fixing one while another is still active leaves the site just as invisible.
Why It Matters More Than It Looks
A noindex signal doesn't slow down AI visibility — it removes it. Every AI crawler
(training, search-index, and on-demand fetchers alike) that respects noindex will treat
your entire site as off-limits until the signal is gone, regardless of how good your
llms.txt, summaries, or schema are underneath it.
Staging Sites
Staging and development sites often have this on purpose — it's the correct default there.
AIO Radar's warning fires the same way on staging as on production; the point isn't to tell
you it's wrong, only that it's present, so a real launch doesn't inherit a staging default
by accident.
What AIO Radar Does — and Doesn't Do
AIO Radar detects and reports the signal and its origin. Per
ADR 0005, it never removes a noindex header, tag, or setting
on your behalf — that decision, and the fix, stays with you.
Fixing It
X-Robots-Tag rule from your host's or CDN's configuration —this is not a WordPress setting, so a plugin cannot undo it.
theme's <head> output if you don't run one.
After fixing the source, run Sync now or wait for the next hourly check — the warning
clears as soon as AIO Radar confirms the signal is gone.
Troubleshooting
The Warning Won't Clear After I Fixed It
I Can't Find Where the Header Is Set
X-Robots-Tag headers are usually added by a CDN rule, a security plugin, or server
config (.htaccess, nginx config) rather than WordPress itself — check your host's
dashboard for a "security" or "staging protection" feature first.