Why Is Google Ignoring My Entire Website? The noindex Tag Explained
If your audit flagged a page as "blocked from Google," the site itself looks completely fine - it loads, it works, a customer who already has the link sees no problem at all. That's exactly what makes this one so dangerous: there's no error, no broken layout, no warning. The site is simply invisible to every Google search that could have found it, and has been the entire time.
What noindex actually is
noindex is an instruction that lives in a page's own code - most often a meta tag in the <head>, occasionally an HTTP header sent by the server - that tells Google and every other well-behaved search engine one specific thing: "you're welcome to visit and read this page, just don't ever show it in search results." Google can crawl it, index its content internally, follow its links - it just will not list the page for any search, no matter how well it would otherwise rank.
That single line, sitting anywhere in the page's <head>, is enough. It requires no error, no broken code, nothing a visitor would ever notice by looking at the page.
How a live, working website ends up with this turned on
This is almost never intentional on a real business site. It happens because most CMS platforms build in a legitimate, useful version of this switch - and it gets flipped at the wrong time.
The "discourage search engines" checkbox never got unchecked
WordPress and several other platforms ship a single setting, usually worded something like "discourage search engines from indexing this site," meant to keep a site under construction out of Google while it's being built. It's flipped on during development, the site launches, and the checkbox is never revisited - so the finished, live site keeps behaving like an unfinished one as far as Google is concerned.
A staging environment got cloned straight to production
Staging and development copies of a site are deliberately noindexed so search engines never see duplicate or half-finished content. When that staging copy is cloned or migrated to become the live site - a common shortcut during a redesign or a host migration - its noindex setting comes along for the ride unless someone remembers to remove it.
A maintenance-mode plugin or security tool never fully reverted
Maintenance-mode tools often add a temporary noindex tag automatically while a site is down for updates, then remove it once maintenance mode is switched off. If that toggle fails partway, or a plugin update changes how it cleans up after itself, the tag can outlive the maintenance window by months.
noindex vs. robots.txt - the confusion that makes it worse
These two get mixed up constantly, and mixing them up can backfire instead of fixing anything. noindex lets Google visit and fully read a page, then tells it not to list that page in results. robots.txt tells crawlers not to visit a page at all, full stop. A page blocked by robots.txt can't have its noindex tag seen by Google in the first place, because Google never gets far enough to read it - so a site owner who "fixed" a visibility problem by blocking a page in robots.txt while a stray noindex tag still sits on it may still see a bare, title-less URL show up in search, the worst of both outcomes.
The real-world cost
A single noindexed homepage means the entire domain effectively doesn't exist in Google search, no matter how good the content, the design, or the SEO on every other page. Existing rankings can vanish within days of Google recrawling and honoring the tag. Worse, because nothing about the page itself changes for a visitor, the business often has no idea anything is wrong until organic traffic quietly dries up - or until a free audit like this one flags it directly.
How to check your own site in under a minute
Open your homepage, then view its source code: right-click and choose "View Page Source," or press Ctrl+U on Windows/Linux, Cmd+Option+U on a Mac. Search the page (Ctrl+F / Cmd+F) for the word "noindex." If you find content="noindex" anywhere inside a <meta name="robots"> tag in the <head>, that page is invisible to Google right now, no matter how it looks in the browser. Check your most important pages individually - a noindex tag can be set per-page as easily as site-wide.
How the free audit catches this
A blocked-from-indexing page is one of the checks in our free audit, run alongside robots.txt, speed, and the rest of our website audit checklist. It's flagged as a high-impact finding the moment the live Lighthouse check confirms the page cannot be indexed - not a guess, an actual read of the page's own code.
Frequently asked questions
What does the noindex tag do?
noindex is an instruction, usually a meta tag in a page's <head> (or an X-Robots-Tag HTTP header), that tells Google and other search engines "you can visit this page, just don't show it in search results." A page with noindex still loads perfectly fine for a visitor who has the link - it simply cannot appear in a Google search, ever, no matter how relevant it is.
How does a live website end up with noindex turned on?
Almost always by accident, not on purpose. The most common cause is a "discourage search engines from indexing this site" checkbox (WordPress and several other CMS platforms ship one) that gets checked during development to keep a staging or in-progress site out of Google, and never gets unchecked when the site actually launches. A staging environment cloned straight to production, or a maintenance-mode plugin that never fully reverted, cause the same result.
Is noindex the same thing as a broken robots.txt file?
No. robots.txt tells crawlers not to visit a page at all. noindex lets Google visit and fully read the page, then tells it not to list that page in search results. They can also interact badly: a page blocked in robots.txt cannot have its noindex tag seen at all, because Google never gets far enough to read it - so relying on both at once, expecting either to work, can backfire.
How do I check if my site has noindex turned on?
View your homepage's source code (right-click, View Page Source, or Ctrl+U / Cmd+Option+U) and search for the word "noindex." If you see <meta name="robots" content="noindex"> anywhere in the <head>, that page is blocked from every search engine that respects the tag, even though it loads fine in a browser.
Will my rankings come back once I remove noindex?
Usually, yes, once Google recrawls the page and sees the tag is gone - which can take anywhere from a few days to a few weeks depending on how often Google visits the site. Submitting the page in Google Search Console's URL Inspection tool after removing the tag can speed up the recrawl.
The cheapest way to find out
Run the free audit below. We check indexability along with speed, SEO, accessibility, and security, using the same tooling Google itself uses, and email you a plain-English report the moment something's wrong. If something needs fixing, it's a flat $149 for your fixable speed/image/SEO/broken-link issue, or $299 for everything, with before-and-after proof once it's done.