Why is my website not showing up on Google — and how do I tell which reason is mine?

You typed your business name into Google, and your site wasn’t there.

Maybe you scrolled. Maybe you tried on your phone, in case it was something about your computer. Maybe you asked someone else to search, to be sure it wasn’t just you.

Here’s the thing that decides everything you do next: “my site isn’t on Google” is not one problem. It’s three, and they have almost nothing to do with each other.

Google might not have your site at all. Google might have it and show it to nobody. Or — if you’re a local business — your website might be perfectly fine and the thing that’s missing is your listing on the map, which isn’t your website at all.

Different causes, different fixes, different people who have to do the fixing. So before anything else, let’s work out which one is yours. The first two checks take about a minute between them, and you don’t need an account for either.

First question: the blue links, or the map?

Search for your business name plus your town — the way a customer would. “Bakery Lviv”, not “kovalweb.com”.

Look at what’s missing. Is your website absent from the ordinary list of links? Or is the list fine, and what’s missing is the box with the map, the pin, the opening hours and the reviews?

If it’s the map, this is not a website problem and nothing further down this page will fix it. That box is Google Business Profile, and it’s a separate thing you own separately. Search your business name on its own: if a panel appears on the right with your details, you have a profile — check that the address, the hours and the category are right. If no panel appears, you probably don’t have one, or it was never verified, and that’s your next hour. A perfect website will not put you on that map.

If it’s the ordinary links, keep reading.

Second question: does Google have your site at all?

Go to Google and search for this, replacing the domain with yours, with no space after the colon:

site:yourdomain.com

That asks Google a narrow question: what do you have from this website?

If you get results — even a handful, even the wrong pages — Google has your site. Skip to “Google has my site, but nobody finds it”.

If you get nothing, check the spelling before you believe it. Copy the address out of your browser’s address bar, drop the https:// and anything after the .com, and try once more. A typo looks exactly like a missing website, and people have lost a week to that.

Still nothing? One more confirmation, because this is the hinge the whole article turns on. Google’s own guidance is that site: isn’t a complete list and isn’t meant as a diagnostic tool — pages that are thin or heavily duplicated can be in Google and still not show up here. So before you act, open Google Search Console, paste your home page address into the URL Inspection box at the top, and read what it says. If it tells you the page isn’t on Google, now you know.

(If you don’t have Search Console yet, see the note below — and if that’s a wall, treat the site: result as a strong hint rather than a verdict.)

About setting up Search Console

Everything below this point is easier with it, and it’s free. But know what you’re in for, because most articles say “just set up Search Console” as though it were a two-minute job.

Google has to confirm you own the site. The usual way is adding a line to your domain settings — and if an agency built your site, that’s very likely their login, not yours. So this may be an email to them rather than a task for you. After it’s verified, the reports need a few days to fill up; a new, empty Pages report doesn’t mean you did it wrong. It’s worth doing, and it’s a this-week job, not a this-afternoon one.

Branch one: Google doesn’t have your site

Four things cause this.

Your site is simply too new. Nothing is broken. Google has to find your site, look at it, and decide to keep it, and none of that is instant. If your site went live in the last week or two, this is the most likely answer by a wide margin.

Something is telling Google to stay away. This is the most common real fault, and it’s almost never deliberate. Somewhere on your site there’s an instruction called noindex, which means “don’t put this in search results”. It gets left behind: WordPress has a checkbox called “Discourage search engines from indexing this site” that developers tick while building, a staging flag doesn’t get switched off at handover, a plugin setting was never reviewed. One forgotten checkbox and Google politely stays out.

Usually the fix is one checkbox in whatever you log into to edit your site — WordPress, Squarespace, Wix, Shopify. The fix is small. The hard part is finding which checkbox.

A file called robots.txt is blocking the door. This is the one thing on this whole list you can check yourself, right now, with no account and no waiting. Type your address followed by /robots.txt — so yourdomain.com/robots.txt — into your browser. Most of what’s in there is normal and you can ignore it. The line to look for is Disallow: / on its own. A single forward slash means “stay out of the entire site”. If you see that, you’ve found your problem.

This and noindex sound the same but aren’t. One says “don’t look”, the other says “look, but don’t list”. And they don’t cancel out the way you’d expect: if robots.txt blocks a page, Google never fetches it, so it never sees the noindex sitting on it. Google’s own instruction is to remove the robots.txt block so that it can read the noindex.

One wrinkle worth knowing, because it can send you down the wrong path: if other sites link to a blocked page, Google can still list the bare address with no description underneath, because it never read the page to write one. So if your site: results are naked URLs with nothing beneath them, check robots.txt even though Google technically “has” your site.

Google doesn’t know your site exists. Google finds sites mostly by following links from other sites. A brand-new site that nobody links to, and that hasn’t handed Google a sitemap — a list of your pages in a format Google reads — is genuinely hard to stumble across.

Most website systems generate a sitemap for you automatically, usually at yourdomain.com/sitemap.xml. Type that into your browser: if you see a list of your pages, you already have one, and all that’s left is telling Google where it is.

What Search Console will actually say to you

If you haven’t got Search Console yet, don’t read this section now — skip ahead to “How long should it take”. Bookmark this page and come back when the report has your own site in it. It will make far more sense with your data in front of you.

In Search Console, go to Indexing → Pages. Under the chart there’s a table titled “Why pages aren’t indexed”, and it names a reason for every page. Find the row with the highest page count — that’s the one to start with.

Those names are written for people who already work in this field. Here’s what they mean in ordinary words. These are the ones you’re most likely to see; Google has more, and if yours isn’t here it’s in Google’s own list on that page.

“Excluded by ‘noindex’ tag” — the leftover instruction from above. A page is telling Google not to list it. If this is on your home page, it explains everything. This is your answer. Stop here and go find the checkbox.

“Blocked by robots.txt” — the file at the root of your web address is telling Google it may not read these pages. This is your answer too — and you can confirm it in ten seconds with the browser check above.

“Not found (404)” — Google is asking for pages that don’t exist. Usually harmless leftovers from an old site structure. Only worth acting on if the missing pages are ones you expect to exist.

“Page with redirect” — the address Google tried sends it somewhere else. Not a problem. If you moved from http to https, or dropped the www., every old address redirects to a new one and Google files them here. A number next to this row is not a task.

“Alternate page with proper canonical tag” — read that carefully. The word “proper” is in Google’s own message. It means the page duplicates another one and you’ve correctly told Google which is the original. Nothing is wrong. It’s filed under “not indexed” because the page isn’t listed separately, and people lose entire evenings fixing something that was already right.

“Duplicate without user-selected canonical” — same situation as above, except you haven’t told Google which version is the original, so it picked one for you. Worth sorting out if it’s affecting pages that matter.

“Crawled — currently not indexed” — Google read the page and decided not to add it. No error, no fault, just a judgement. This one is genuinely frustrating because there’s no instruction to follow. It usually means the page didn’t seem worth listing: very little content, nearly identical to another page, or nothing links to it.

“Discovered — currently not indexed” — Google knows the page exists but hasn’t looked yet. Usually a matter of waiting.

“Server error (5xx)” — your site failed to answer when Google asked. If this one has a real number next to it, tell whoever hosts your site today.

Notice something: three of those — “Page with redirect”, “Alternate page with proper canonical tag”, and usually “Not found (404)” — aren’t problems at all. Two of them are Google telling you that you got it right. Which is why “how many warnings do I have” is the wrong question, and “what is this one, and does it apply to a page I care about” is the right one.

How long should it take?

This is what clients ask me about a week after a site goes live, and the answer is unsatisfying: days to weeks, with no guarantee.

Google’s guidance is to allow at least a week before worrying. What speeds it up is short and boring: submit your sitemap in Search Console (Sitemaps → paste sitemap.xml → Submit), use URL Inspection to request indexing for your most important pages, and get at least one real link pointing at your site from somewhere that already exists.

What you can’t do is buy your way to the front of the queue, and anyone offering to is selling you something else.

Google has my site, but nobody finds it

If site:yourdomain.com returned pages, you’re in a different situation, and the good news is that the technical part is already working.

Three checks, in order:

Search a full sentence copied from your own page, in quotation marks. If your page comes up, that page is genuinely in Google and can be shown. If it doesn’t, that specific page may not be indexed even though others are — back to branch one for that page.

Search your business name in quotation marks. If you appear, you’re findable by people who already know you. If you don’t, and the sentence check passed, something odd is going on with how your site describes itself — start with whether your home page title actually contains your business name and your town.

Open Search Console → Performance. If you see impressions but almost no clicks, you are being shown to people and they’re choosing someone else — that’s about what your title and description say. If you see almost no impressions at all, you’re barely being shown for anything, which is a longer piece of work: what your pages actually say, what questions they answer, and who links to you.

That last one is competition rather than a fault, and I’m not going to pretend a checklist fixes it. But knowing you’re in it saves you from spending three weekends on technical settings that were never broken.

If someone else built your site

Most of the fixes above take two minutes for whoever built your site, and are impossible for you if you don’t have the logins. That’s not a failing on your part.

Send them this, word for word:

Our site isn’t appearing in Google. Search Console says: [paste the exact reason]. Can you check whether a noindex tag is set on the home page, and whether robots.txt is blocking anything? Also, can you add me to Search Console for our site?

That last sentence matters more than the rest of the message. It’s your site, and you should be able to see what Google says about it.

You changed something. How do you know it worked?

Here’s where most of the wasted time goes, and it’s the part almost nobody writes about.

You found the checkbox. You unticked it. Now what?

There is one free check that genuinely works, and you should use it first. Paste the page’s address into URL Inspection in Search Console and press “Test live URL”. That fetches the page as it is right now and tells you whether indexing is allowed on it. If it still says the page is blocked, your change didn’t land, and you’ve learned that in thirty seconds instead of three weeks.

What that won’t tell you is whether anything actually changed compared to before, because it has no memory of what the page said last week. And it answers about one page at a time.

The other instinct — going back to the Pages report to see whether the warning is gone — is where it gets slippery. A warning disappearing is not proof the problem was solved. It can disappear because Google hasn’t looked again yet. It can disappear because the page moved into a different category — still not indexed, different label, and now it looks like progress.

Search Console has a “Validate fix” button that asks Google to check properly. It ends in passed or failed, and Google says validation “typically takes up to about two weeks, but in some cases can take much longer”. Most site owners never press it at all, because nothing explains what it does.

And read how Google defines passed, because it’s the whole point:

All known instances of the issue are gone (or the affected URL is no longer available).

Google Search Console Help

A page that stopped existing counts as fixed. Deleted the page instead of correcting it? Passed. That’s not Google being careless — it’s an honest description of what it can actually observe. But it means “the warning went away” and “the thing is fixed” are two different statements, and the report can only ever tell you the first one.

This is the thing I built Koval SEO Console for. You paste your web address in, it reads your pages and shows you what it found, with the actual line it read from your page next to each problem so you can check it yourself. You fix something, run it again, and it answers one of exactly three ways: fixed, not fixed, or couldn’t confirm. I built that third answer in deliberately — it refuses to call a problem solved just because the warning stopped appearing. Nothing to install, and you don’t need an account for the first one.

What to do this week

1. Search your business name plus your town. Missing from the map, or missing from the links? Everything else follows from this.
2. If it’s the links: run site:yourdomain.com, check the spelling twice, and note which branch you’re in.
3. Check yourdomain.com/robots.txt yourself. Looking for Disallow: /. Two minutes, no account.
4. Start Search Console if you haven’t. Expect it to take a few days, not an afternoon, and expect to need whoever holds your domain settings.
5. If your site is under two weeks old and nothing above applies: submit the sitemap and wait. That is the correct action, even though it doesn’t feel like one.
6. After you change anything, test the live URL. Don’t accept a warning disappearing as evidence.

And if you work through that and still can’t tell what’s wrong, write to me. Send your web address and the exact reason Search Console gave you — that’s usually enough for me to tell you which of the three problems you’ve got.