Your Site Isn’t Showing on Google: How to Tell Indexing from Ranking

“The site can’t be found on Google” describes two problems that have nothing in common. In the first case, Google doesn’t know the page: it’s not in its archive, and it won’t show up for any search. In the second, Google knows it perfectly well, but shows it below other results it considers more suitable. The causes are different, the fixes are different, and mixing them up leads to rewriting text for a technical problem, or touching the server for a content problem.

Telling the two cases apart takes a few minutes and should be done before any other action.

The test that separates the two cases

Search Google for an exact phrase taken from the page — a long, uncommon one — enclosed in quotation marks. It’s the fastest check, and it requires no logins.

• If the page shows up, Google knows it. The problem is ranking: the page exists in the archive but isn’t being surfaced for the searches you care about.
• If it doesn’t show up, Google most likely doesn’t have it archived. The problem is indexing, and no amount of content work will fix it.
• The same check can be done from the Search Console panel by pasting the page’s exact address: the result is more reliable and also says why.

A note on method: don’t use your own everyday searches as proof. Results are affected by history and location, and seeing your own site near the top from your office doesn’t mean everyone else sees it there.

If Google doesn’t know the page

The causes are technical and almost always unintentional: something is blocking access, or explicitly telling Google not to archive it. Check them in this order, from the most common to the rarest.

1. Does the page actually respond, to any random visitor, without being logged in and without browser cache? An address that returns an error or a blank page won’t be archived.
2. There’s a block on access: a system file that forbids reading that part of the site, a password protection left over from development, a block that responds badly to automated requests.
3. There’s an instruction asking not to index, often turned on while the site was being built and never removed at launch. It’s by far the most frequent cause after a redesign.
4. Can the page be reached by browsing? A page that’s not linked from any menu and doesn’t appear in any list is hard to find, even when it’s technically open.
5. There’s a signal designating another page as the main version, or a redirect leading elsewhere. In this case the page is deliberately excluded, and the question becomes whether that’s the right call.

A diagnostic path with illustrative outcomes

Search Console classifies the status of every page. Here’s how to read the most common outcomes, with illustrative wording: the point isn’t the exact labels, which change, but the reasoning each one involves.

The two middle rows are the ones most often misread. “Discovered but not indexed” isn’t a malfunction, and it doesn’t get fixed by requesting indexing a second time: it’s a judgment call, and it only changes if the content changes.

If the page is indexed but brings no one

Here the problem shifts from technical to content, and the questions are different.

• Which searches would you like to appear for, and does anyone actually search with those exact words? Many pages are written in the company’s language, not the searcher’s.
• Do results already exist that answer that question better? If the page says less than the ones above it, the ranking won’t change for technical reasons.
• Does the page answer one question or five? A page that covers all your services together competes poorly on each one.
• Do you have several pages that say almost the same thing? They compete with each other, and Google picks one — often not the one you would have picked.

Assign the fixes and watch without setting deadlines

Fixes split into two separate lists, with different owners: technical ones go to whoever maintains the site, content ones to whoever writes. Mixing them into a single document is the surest way to get neither one done.

What this guide doesn’t cover

This covers diagnosing your search presence: understanding whether a page is known and why it isn’t shown. The specific case of a drop after a site redesign — what to plan before the switch and how to recover — is covered in a dedicated guide, because it has its own causes and calls for a different order of checks. Reading Search Console data to make decisions has its own guide too.