Is your site accidentally hidden?
noindex, explained — with the check and the fix.
One invisible instruction in your site's code can switch the whole thing off in Google — no warning, and every page still looks perfectly normal in a browser. Check in 60 seconds: open any page, right-click, choose View page source, and search for noindex. If it's there, this guide takes you from alarm to fixed. If it isn't, two hiding places are still worth three more minutes.
The meta tag, the response header, the template setting — the audit scans every hiding place in this guide, page by page.
First, the 60-second check
noindex. The word alone isn't a verdict — it only counts inside a robots tag, like <meta name="robots" content="noindex">. If you see content="index,follow", that's the opposite: an explicit all-clear. Nothing found at all? Your pages are probably clean — but read hiding place 2 below before you relax: one form of noindex is invisible in view-source.
The three-check noindex diagnosis
View-source finds the common form. Search Console tells you Google's side of the story. The site: search shows the damage. Run all three and you'll know whether noindex is your problem — and exactly which pages it's eating.
1 · View page source
Right-click any page, choose View page source, search noindex. You're looking for a <meta name="robots"> line in the head with noindex in its content. Run it on your homepage and one page you actually care about — a service, a product, a post.
index,follow = explicit all-clear. The word noindex appearing only in visible text or scripts = harmless.2 · Search Console's confession
Google Search Console is free and verifies in minutes. Its "Page indexing" report lists every page Google has decided not to index — with the reason, by name. It's Google showing you its own homework.
3 · The site: search
Search site:yourdomain.com on Google. It shows everything Google has filed under your domain — the closest thing to seeing the index with your own eyes.
Three places a noindex hides
The same instruction can live in three different places — and the second is completely invisible unless you know where to look. Find which one yours is in, and the fix is usually a single setting.
The meta tag, on the page itself
A single line in the page's HTML head — <meta name="robots" content="noindex"> — is the classic form. It's what WordPress's famous checkbox writes, what SEO plugins write, what staging setups write. And it travels with the page wherever the page goes.
noindex (diagnosis check 1).The fix: untick the setting that wrote it — accidents 1–4 below are the usual suspects — or delete the tag from the template. Every page carrying it needs the fix, not just the homepage.
The X-Robots-Tag response header
The server can send the same instruction as a header — X-Robots-Tag: noindex — before the page even loads. It never appears in view-page-source, it can cover the entire site in one line, and it's usually set by hosting config, a CDN rule, or an .htaccess file: places owners never look.
The fix: find the rule — server config, .htaccess, nginx, CDN setting, "coming soon" plugin — and remove the header. Usually needs the person with server access.
Only on some pages — the template pattern
Site-wide noindex is dramatic but rare. Far more common: a whole page-type noindexed by one template setting — every product, every blog post, every tag page — while the homepage checks clean and the owner swears the site is fine.
The fix: the setting usually lives in an SEO plugin's titles-and-meta area or the platform's per-content-type visibility. Flip it once and the whole page-type returns.
Six ways it happens by accident
Nobody types noindex by hand. It arrives through a checkbox, a default, or a migration — and it's almost always someone doing something sensible at the time. Ranked by how often each turns out to be the culprit.
The launch checkbox
WordPress ships a box under Settings → Reading: "Discourage search engines from indexing this site." One tick writes noindex to every page. It's meant for private test sites — but it gets ticked on day one and forgotten on launch day more than any other noindex in the world.
The fix: untick it, save, then request indexing on your homepage.
The staging site that went live
Developers deliberately noindex staging copies so Google never finds the unfinished version. Then the staging site becomes the live site — migrations and plugins happily carry the setting across — and launch day is the day the site goes invisible.
The fix: turn off the staging/development mode or plugin writing the tag, then re-run the view-source check on several pages.
The SEO plugin setting wider than intended
Yoast, Rank Math and their peers can noindex by content type, archive, category, even pagination — genuinely useful options, individually. One toggle set during setup ("hide tag archives") and hundreds of pages quietly leave the index while the pages you check daily stay put.
The fix: set each content type you sell from to index — and let pages you truly want hidden stay noindexed on purpose.
Trial, private, or "coming soon" mode
Site builders and coming-soon plugins noindex the site until you explicitly flip visibility to public — sensible for an unfinished site. The trap: paying for the plan or launching the design doesn't always flip that switch. The site is live, beautiful, and hidden.
The fix: switch visibility to public. Builders usually drop the noindex within a day of the change.
A theme or plugin default
Some themes and plugins ship noindex on certain views — internal search results, tag archives, landing-page packs — by design. An update, a theme switch, or a newly installed plugin can turn it on for more than you ever agreed to, with no notice and nothing changed on screen.
The fix: the theme's or plugin's own visibility options. If it can't be turned off, that's a reason to change the tool, not the site.
A server, host, or CDN rule
The X-Robots-Tag header from hiding place 2 gets set in hosting config, .htaccess or nginx rules, or a CDN setting — sometimes years ago, sometimes by a security feature or an old maintenance mode that never fully ended. One line nobody remembers writing hides the whole site.
The fix: your host or developer removes the header at its source. This one usually needs the person with server access.
Removed it — now what?
Fixing the tag doesn't fix the index. Google has to come back, re-read each page, and change its mind — on Google's calendar, not yours. The honest timeline, how to speed it up, and the traps still left.
Google re-crawls on its own schedule
Pages return as Google re-visits them. The homepage usually comes back within days; pages deep in the site can take one to four weeks, longer on large sites. Nothing is broken during this window — the fix is already in, the index just hasn't caught up.
Watch the count drain
Search Console's Page indexing report is your recovery dashboard: the "Excluded by 'noindex' tag" count should fall toward zero over the following weeks. That's the moment the fix becomes visible from outside.
Some noindex is correct — leave it
Cart and checkout pages, internal search results, thank-you pages, admin screens: noindex is the right setting for these, and removing it would be a mistake. The goal was never "zero noindex" — it's noindex on purpose, never by accident.
If the traffic doesn't come back
Pages returning to the index and pages ranking where they used to are different recoveries. If listings reappear but positions disappoint, the noindex was hiding a second problem — usually authority or competition. That's not bad news; it's a diagnosis.
Checklist: what you see → what it means
The whole guide, compressed. Run these in order; each result tells you which hiding place or accident to jump to.
| Check | If you see… | It points to |
|---|---|---|
View source → search noindex |
It inside <meta name="robots"> |
Hiding place 1 — the page asks not to be listed; accident 1, 2 or 3 wrote it |
View source → search noindex |
Nothing, or only index,follow |
Pages probably clean — but hiding place 2 is invisible in view-source |
| DevTools → Network → response headers | x-robots-tag: noindex |
Hiding place 2 — server- or CDN-level; usually accident 6 |
| Search Console → Page indexing | "Excluded by 'noindex' tag" rows | Google naming the pages for you — the count is your to-do list |
site:yourdomain.com on Google |
Nothing, or a shrinking handful | Consistent with noindex, but not proof — fifteen other causes exist (the 16-cause guide) |
yourdomain.com/robots.txt |
"Disallow: /" | A different problem that looks identical from outside — it blocks crawling; the 16-cause guide covers it |
Every check above is free and takes under a minute. All six clean and the site still doesn't show? The problem probably isn't noindex — work through the diagnosis in Website not showing up on Google — 16 causes, ranked instead.
What the £7.99 report checks — and what it can't
Everything in this guide that can be checked from outside your site is mechanical, and mechanical is checkable. Full disclosure: some of it isn't, and we say which. The report is the full 21-category audit — what it costs and how it compares to doing it yourself are on their own pages.
The mechanical hiding places
Checked page by page across up to 25 pages, with every hidden page named and the exact tag or header that's hiding it.
- meta robots noindex tags, on every page audited (hiding place 1)
- X-Robots-Tag response headers (hiding place 2)
- robots.txt directives and what they actually block (checklist row 6)
- whole page-types hidden by template settings (hiding place 3)
- Sitemap presence and reachability — recovery's delivery route
- Canonical tags quietly pointing pages elsewhere (a look-alike)
— Not ours to claim
What no report sold from outside your accounts can do:
- See inside Search Console — your indexing status and recovery history live behind your Google login (diagnosis check 2); the report names the exact screen to open
- Untick the box for you — the settings that write the tag sit inside your platform's admin, not on your public pages; the report tells you precisely which one to open
- Make Google re-crawl faster — nobody can pay for that; removing the tag removes the blocker, the crawl does the rest
Also honest: a noindex on a cart, checkout or internal-search page is often the right setting — anything intentional you simply leave alone. The report's job is to show you exactly what's hidden and how, so the accidents get fixed and the deliberate ones stay.
Fair questions, straight answers
How do I remove a noindex tag?
Find where it lives first — the meta tag, the X-Robots-Tag response header, or a per-template setting — because removing the symptom doesn't stop the setting from writing it again. WordPress: untick Settings → Reading → "Discourage search engines". SEO plugin: its index-settings screen. Header: the hosting or CDN rule that sends it. Then verify with view-source on several pages, not just the homepage.
How long until my pages come back on Google?
Google has to re-crawl each page before it returns. The homepage usually reappears within days; deeper pages can take one to four weeks, longer on large sites. Request indexing in Search Console speeds up the pages that matter most, and the "Excluded by 'noindex' tag" count falling toward zero is your progress bar.
Will the £7.99 report find my noindex?
For the forms that live on the site itself — yes: meta noindex tags and X-Robots-Tag response headers are checked page by page across up to 25 pages, alongside robots.txt, the sitemap, and canonical look-alikes. What it can't see is inside your Google account (Search Console's indexing report, your request-indexing history); for that, the report names exactly which screen to open. Judge the sample report before you buy.
Is noindex ever the right setting?
Yes — deliberately. Cart and checkout pages, internal search results, thank-you pages, admin screens and staging copies should stay out of the index. The problem this guide solves is noindex by accident: site-wide, or on the pages that earn your money. A page a customer would search for belongs in the index; a page that exists only after a click often doesn't.
Find out if yours is hidden.
Enter your URL and pay securely — your report PDF lands in your inbox in ~30 minutes,
with every noindex hiding place from this guide checked page by page.