Is Your Site Blocking Google Without Knowing It?

Every few weeks I get a call from someone whose traffic fell off a cliff and never came back. The site looks fine. Nothing seems broken. But somewhere along the way, usually during a redesign or a hosting move, the site started telling Google to stay away. And Google, being polite, listened.

The good news is that blocks like these leave fingerprints. Here are the ones I check first, and how you can check them yourself.

The noindex tag left on after launch

While a new site is being built, developers often set it to "noindex," which tells search engines not to list it. That is the right move during construction. The problem is forgetting to turn it off at launch. I have seen businesses run for months after an expensive redesign with that switch still flipped, wondering why the new site performs worse than the old one.

To check, open Search Console and look at the Pages report. If your important pages show up as "Excluded by noindex tag," you found it. On WordPress, the setting lives under Settings, then Reading, and it is one checkbox labeled "Discourage search engines from indexing this site." One unchecked box can change everything.

A robots file blocking the wrong folder

Your robots.txt file is a short list of instructions telling crawlers where they may and may not go. It only takes one bad line, something like blocking the folder where your page templates or images live, to keep Google from rendering your pages properly. Google may still list the page, but it cannot see it the way a visitor does, and rankings suffer quietly.

You can read your own file right now by typing your domain followed by /robots.txt into a browser. If you see a line that blocks everything, or blocks folders with names like /wp-content/ or /assets/, that is worth a closer look before you change anything.

Security tools that block Google too

Bot protection, firewalls, and security plugins exist to keep bad traffic out. Sometimes they cannot tell the difference between a scraper and Google's crawler, especially when the crawler visits often. The result is a site that loads fine for you but returns errors or challenge pages to Google.

Search Console will hint at this under the Pages report as server errors or "Blocked due to access forbidden" entries. If those started right after you installed a security tool or changed hosts, that timing is your clue.

The staging copy that outranks the real site

Redesigns are often built on a temporary address, something like yoursite.tempdomain.com or a dev subdomain. If that copy is left public and unprotected, Google can find it, index it, and sometimes rank it above the real site. Customers land on an unfinished copy with placeholder text and the wrong phone number. I have watched this exact thing drain calls from a business for weeks.

Search your own business name plus a word from your homepage and see what comes up. Anything you do not recognize, especially addresses that are not your real domain, deserves a look.

Errors that only happen when Google visits

A site can run fine all day and still fail at crawl time. Cheap or overloaded hosting sometimes returns errors when several pages are requested at once, which is exactly what a crawler does. You never see it, because you visit one page at a time. Search Console keeps a record under Settings, in the crawl stats, and a wall of server errors there explains a lot of mysterious ranking drops.

How this fits the bigger picture

Blocking problems are one family in a larger set of issues. My overview of the technical problems that hide sites from Google covers the rest, and its close cousin, duplicate pages competing with each other, often shows up in the same audits.

If you want a hand sorting out which of these is yours, my technical SEO help page explains how the sessions work. A fix session is $99 for the first hour, and there is a free 15-minute Marketing Check if you just want a first look.

This is the kind of thing I untangle live on a screen share. We pull up Search Console together, find the block, remove it, and you watch your pages become visible to Google again in real time.