Why Can't I Find My Website on Google?

"I type my company name into Google and find nothing." It is one of the most common opening lines after a site launch. And in most cases the problem behind it is not the one the sentence suggests.

Because there are two entirely different situations that feel identical:

Your site is not in the index. Google either does not know about it or has decided not to include it. It appears for no search at all, not even your company name.

Your site is in the index but does not rank. Google knows it, but does not show it on page one for the term you tried.

Different problems, different fixes. The first step is always to establish which of the two you are in.

First: diagnose properly

The widely shared trick is to type site:yourdomain.com into Google. It gives a rough impression, but it is not a reliable diagnostic — the results of that query are known to be incomplete and to fluctuate between runs.

The dependable source is Google Search Console. It is free, and if you have not set it up, that is the actual first step — not any optimisation measure.

Two places in it matter:

URL Inspection, the bar at the top. Enter a specific address and get the answer for exactly that page: indexed or not, and if not, why.

Indexing → Pages. How many pages are indexed, how many are not, and for what reasons.

If it says your pages are indexed, you do not have an indexing problem — you have a ranking question. Skip to the second-to-last section.

The three stages Google goes through

To read the status messages, it helps to know the pipeline. Google does three separate things:

Discovery. Google learns that a URL exists — via your sitemap, an internal link, or a link from elsewhere.

Crawling. Googlebot actually fetches the page and reads the content.

Indexing. Google evaluates the content and decides whether it belongs in the search index.

A page can get stuck at any of these three, and Search Console tells you which. That is the single most useful piece of information, because the remedies differ completely.

"Discovered – currently not indexed"

This means Google knows the URL exists but has not visited it yet. The page is sitting in a queue.

It is primarily not a quality issue but a priority one. Google allocates crawl resources based on demand and a domain's standing. For a new site with no history, that priority is naturally low.

A handful of affected URLs on a new site is a normal queue state. It becomes worth investigating when important pages are affected, when the count is rising, or when the affected URLs follow a recognisable pattern.

What helps: internal linking. If Google only knows a page from your sitemap and no other page on your site points to it, there is no signal that it matters. Three to five contextually relevant links from already-indexed pages shift that assessment more than any technical measure.

"Crawled – currently not indexed"

This is the other message, and it means something fundamentally different: Google visited, read the page, and decided against including it.

That is no longer a technical problem but a judgement. Google does not publish the exact criteria, but the recurring patterns are well documented: very thin content, text that closely resembles other pages either on your own site or elsewhere, and pages with no discernible standalone purpose.

For some page types this status is normal and needs no action: login pages, carts, account pages, paginated listings, RSS feeds. Those do not belong in the index anyway.

For content pages it is a signal. And the important part: leaving the page unchanged guarantees the same outcome next time. Hitting "request indexing" without changing anything changes nothing.

The word "currently" is meant sincerely, though — the state is not permanent.

How long is normal?

The most common mistake on new sites is impatience, followed by hurried changes in the wrong places.

A new domain has no history. Google does not know whether things appear there regularly, whether frequent visits are worthwhile, whether the content persists. That assessment builds over weeks, not days.

An example from my own practice, as of mid-September 2026: this site is new. A sitemap of roughly seventy addresses was submitted and processed within days — status "Success", all URLs discovered. The number of pages actually indexed lags well behind that and is climbing gradually.

That is not a flaw in how the site is built; it is the normal course. I am putting it in writing here deliberately, because most articles on this topic tell a success story in hindsight. From inside the process it looks different, and someone who does not know that starts rebuilding a site that has nothing wrong with it.

What genuinely helps in this phase: submit your three to five most important pages individually via URL Inspection. That puts them in a prioritised queue. You cannot do this for every page — there is a quota, and it is not necessary anyway.

When something is genuinely blocking

Before settling in to wait, rule out the technical causes. They are uncommon, but where they exist, no amount of patience helps.

A forgotten noindex. The most frequent real cause. Sites are blocked from search engines during development, and at launch someone forgets to lift it. URL Inspection reports this unambiguously.

A block in robots.txt. Prevents crawling of entire sections. Also visible in Search Console.

The site is unreachable or too slow. If Googlebot hits timeouts, crawling is throttled. How to measure and improve load time is covered in the article on Core Web Vitals.

Content that only exists via JavaScript. Google can execute JavaScript, but it takes longer and fails more often. If the substantive content only appears after load, it may be picked up late or incompletely. If that cannot be fixed with targeted corrections, a relaunch is eventually the more honest answer than further repairs.

A security warning. If Google classifies the site as compromised, it drops out of results. That shows under Security Issues in Search Console — and what to do about it is its own subject.

On multilingual sites: incorrect hreflang. If language versions do not reference each other properly, Google serves the wrong one or treats them as duplicates. Details in the article on multilingual websites.

The other case: indexed, but not on page one

If Search Console says your pages are indexed, the original question was framed wrongly. You are being found — just not for the term you tried.

Two things clarify the picture:

Search for your exact company name. If you appear, you are in the index, and everything beyond that is a question of competition.

Look at Performance in Search Console. It lists the queries you are actually being shown for. That is nearly always illuminating, because they are rarely the terms you would have guessed.

Behind this sits a common misreading. Someone searches for "electrician", finds nothing, and concludes the site is broken. But a generic trade term puts you in competition with the entire country. "Emergency electrician Braunschweig weekend" is a different picture entirely — and that is where the enquiries actually come from.

One more thing worth knowing: local searches usually put a map block with three listings at the top. That is not driven by your website but by your Google Business Profile. Anyone wanting to be found locally has to deal with it — and reviews there carry more weight than the best copy on your own site. How the profile and the site work together for a trade business is covered in the article on that.

Frequently asked questions

How long before a new website shows up on Google? Days to weeks, and for a new domain more likely weeks. A domain with no history starts with low crawl priority, and that assessment builds gradually. Full indexing of a new site with several dozen pages frequently stretches across months.

Can I check whether I'm indexed with site:mydomain.com? Only very roughly. Results from that query are incomplete and unstable. URL Inspection in Search Console is reliable because it answers for a specific address straight from Google's own data.

What's the difference between "Discovered" and "Crawled – currently not indexed"? "Discovered" means Google knows the URL but has not fetched it — a queueing and priority matter. "Crawled" means Google fetched it and decided against inclusion — an evaluation matter. The remedies differ entirely: internal linking in the first case, the content itself in the second.

Does repeatedly requesting indexing help? For "Discovered", a single request can shorten the wait. For "Crawled – currently not indexed" with no content change, no: Google has already evaluated the page and will reach the same conclusion next time. There is also a quota on these requests.

Do I have to submit a sitemap? It helps with discovery but guarantees nothing about indexing. A sitemap tells Google that URLs exist; whether they are included is decided afterwards. A "Success" status means the file was read, not that the pages are in the index.

I show up for my company name but nothing else. Is that a fault? No, that is the normal starting state. Your own name is the easiest possible query because nobody else competes for it. Everything else is competition, and it starts with specific, longer queries rather than broad industry terms.

My site was indexed and has disappeared. What now? Start with URL Inspection: is there a noindex, a robots block, or a fetch error? Then check Security Issues. And if there has been a recent relaunch, the most common cause is a changed URL structure without redirects.

In short

Diagnose before acting. Search Console tells you which of the three stages is the sticking point, and without that you are optimising blind.

For a new site, waiting is not a failure but the normal course. What actually works during that time is internal linking — and content that has its own reason to exist.