Noindex Mistakes: How One Setting Can Hide Your Site From Google
Short answer Accidental noindex almost always comes from one switch left on: WordPress's "Discourage search engines" box, a Wix or Squarespace hide toggle, an SEO plugin setting, a test site launched as is, or a server header. Find it with URL Inspection in Search Console, turn it off, confirm the tag is gone, then request indexing.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callHow can one tag hide a whole site?
Noindex is a short instruction that tells search engines "don't list this page". It lives either in the page's code (a robots meta tag) or in the reply your server sends with the page (an `X-Robots-Tag` header). Google treats both the same. Once Google reads it, the page is gone:
"Google will drop that page entirely from Google Search results, regardless of whether other sites link to it." (Google Search Central: Block Search indexing with noindex)
Put that instruction in a shared template, and every page carries it. Most owners never typed it. A setting did. The fix is finding which one.
The usual places an accidental noindex comes from
| Where | How it got there | How to undo it |
|---|---|---|
| WordPress, Settings → Reading | The "Discourage search engines from indexing this site" box was ticked while the site was built | Untick it and save |
| SEO plugin (such as Yoast) | A whole content type, like Pages or Services, was set to stay out of search | Turn its search toggle back on |
| Wix site setting | "Let search engines index your site" is off | Switch it on in SEO Settings |
| Wix or Squarespace page setting | A page was hidden; on Squarespace, hiding a blog or shop page also hides every post or product in it | Switch the page's toggle back |
| Test site launched as the live site | The designer blocked Google during the build and the block came along | Remove it everywhere it was added |
| Server or hosting header | An `X-Robots-Tag: noindex` rule in the server setup, often meant for PDFs or a test copy | Ask your host or developer to remove the rule |
| Code pasted into the site-wide header | A noindex line added once "for now" in a header code box | Delete it from the header code |
WordPress: one checkbox
The "Discourage search engines" box under Settings → Reading puts a noindex, nofollow tag on every page of the site, according to WordPress's documentation. It's handy while a site is being built, then easy to forget. Visitors still see the site normally, so nothing looks wrong.
SEO plugins: one toggle per content type
Yoast's help center says a single setting can keep an entire content type, category or tag out of search, and on each post the Advanced tab asks whether to "Allow search engines to show this content in search results". Set to No, that adds noindex. Check the plugin's settings screen, not just one page.
Website builders: hide toggles
- Wix: a site-wide "Let search engines index your site" switch under SEO Settings, and a "Let search engines index this page" switch under each page's SEO basics (Wix Help Center).
- Squarespace: a "Hide page from search results" toggle in each page's SEO tab. Hiding a collection page, like your blog or store, also hides every item in it (Squarespace Help Center). The site-wide "Block Search engine crawlers" box under Settings → Crawlers isn't noindex; it adds a robots.txt block, with the same result.
- Shopify: a store still in private (password) mode hides all pages from visitors and search engines (Shopify Help Center). In Shopify admin, go to Online Store, click Private and select Public.
Test sites that go live
Many designers block Google while they build, which is fine. The mistake is launching without removing it. Google's own site-move checklist warns about exactly this:
"Don't forget to remove any noindex or robots.txt blocks that were only needed for the migration." (Google Search Central: Site moves with URL changes)
The header you can't see
An `X-Robots-Tag` header never shows up in the page's code, so "view source" looks clean while Google still gets told to stay away. Google's specification shows it set in server files, for example for every PDF on a site. If URL Inspection says noindex and you can't find a tag, this is usually why.
JavaScript that tries to remove it
Some sites ship noindex in the page and remove it with a script once the page loads. That doesn't reliably work:
"When Google encounters the noindex tag, it may skip rendering and JavaScript execution, which means using JavaScript to change or remove the robots meta tag from noindex may not work as expected." (Google Search Central: Understand JavaScript SEO basics)
If a page should be in Google, the original page code must not say noindex.
How to check if your site has a noindex
- Search `site:yourdomain.com` on Google. Few or no results on an older site is the first warning.
- Run URL Inspection in Search Console on your home page and one service page. Google suggests this tool to see "the HTML that Googlebot received". It names noindex if Google found it. New to Search Console? Start with the reports to read.
- Open the page source (right-click, View Page Source) and search for `noindex`. A tag reading `none` means the same as noindex plus nofollow (Google's robots meta tag specification).
- Check the header if steps 2 and 3 disagree. In a terminal, `curl -I https://yourdomain.com/` lists the headers; look for `X-Robots-Tag`.
- Open the Page indexing report to see how many pages are listed as excluded by noindex. If that list holds pages you want found, you have a mistake. What each status means: Page indexing statuses.
How to undo a noindex
- Turn it off at the source: the setting, plugin toggle, header rule or code line from the table above.
- Clear any cache your host, plugin or CDN keeps, so the old version stops being served.
- Confirm it's gone with URL Inspection's live test, not just the page source.
- Make sure robots.txt doesn't block the pages. Google must crawl a page to see the change (Google Search Central: Block Search indexing with noindex).
- Request indexing in URL Inspection for your most important pages. For many pages, submit your sitemap instead. Asking again doesn't help:
"Crawling can take anywhere from a few days to a few weeks." (Google Search Central: Ask Google to recrawl your URLs)
Google adds that "requesting a recrawl multiple times for the same URL won't get it crawled any faster" (same page).
Removing noindex lets pages back in; it doesn't promise their old rankings. Pages usually come back as Google recrawls them, a few at a time. To catch it next time, rerun URL Inspection on your home page after any redesign, new plugin or platform move.
When is noindex the right call?
Noindex is for pages that work for visitors but help no searcher: thank-you pages after a booking, your site's own search results, a test copy. Two things it isn't for:
- Privacy. Noindex hides a page from search, not from people. WordPress's documentation says plainly that its setting doesn't block access to the site; it is "up to search engines to honor your request." Use a password or login for private pages.
- Saving Google's time. Google says not to use noindex for crawl budget, because it "will still request, but then drop the page" (Google Crawling Infrastructure: Optimize your crawl budget).
Example
A plumber's new WordPress site
The site launched in March. By May, calls from Google had dried up and `site:` showed nothing. URL Inspection reported noindex on every page. The "Discourage search engines" box was still ticked from the build. Unticking it and submitting the sitemap brought pages back over the next few weeks.
A salon that hid its blog
The owner hid a seasonal promo page on Squarespace and, by mistake, switched the toggle on the blog page instead. All 40 posts dropped out of Google. Switching it off and requesting indexing for the blog page fixed it.
A law firm with clean page code
Page source showed no noindex, yet URL Inspection did. The firm's developer had added an `X-Robots-Tag: noindex` server rule for a test copy, and it applied to the live domain too. Removing the rule solved it.
FAQ
How long until my pages come back after removing noindex?
As Google recrawls them. Google says crawling takes "a few days to a few weeks", and requesting indexing for key pages helps it start.
Does noindex remove a page right away?
No. Google drops it the next time it crawls the page, which can take months for a page few sites link to (Google Search Central: Block Search indexing with noindex).
Can I put noindex in robots.txt?
No. "Specifying the noindex rule in the robots.txt file is not supported by Google" (Google Search Central: Block Search indexing with noindex). Use the page tag or the header, and don't block the page in robots.txt, or Google never sees the tag.
Is noindex the same as nofollow?
No. Noindex keeps the page out of search. Nofollow tells Google not to follow the links on the page. WordPress's checkbox adds both.
Different for you?
- Site missing from Google, cause unknown? Run the full list of checks: website not showing on Google.
- Traffic fell right after a redesign? A leftover noindex is one of several causes: traffic drop after a redesign.
- Choosing between Wix, Squarespace and WordPress? How each handles SEO settings: website platforms and SEO.
- Want someone to watch index settings for you? See /seo/.