Why Is My Website Not Showing on Google

This is the call I get most weeks, and it usually arrives the day after a new site goes live or at the end of a quiet month. The owner has searched their own business name, seen three competitors and a directory listing, and wants to know whether the site is broken, penalised, or simply too new to matter yet.

My first answer is always the same. Do not touch anything yet. Most of these panics turn out to be one of six causes, and the wrong fix makes things worse. Blocking a page in robots.txt, redirecting a URL that did not need redirecting, or requesting indexing every morning can each turn a small problem into a real one.

After 13 years of this work, I can tell you where the time goes. It goes into working out which cause you actually have before changing a single setting. What follows is the order I work in, the evidence to look for at each step, and a 30 minute version you can run yourself before you pay anyone.

First Check Whether the Page Is Really Missing

The site: search and what it proves

Start with a site: query. Search site:yourdomain.com.au in Google and read whether your pages come back. If they do, Google knows about them and you have a ranking problem rather than a crawling one. If nothing comes back, either nothing is indexed or the results are being filtered in that particular view.

Search Console's own guidance on missing pages is blunt about how often the first impression is wrong: "Many people assume that they are not on Google, when in fact their page simply appears low in Search results, or might be omitted because the specifics of your search". That one sentence explains a large share of the calls I take. The detail sits on the Search Console help page on missing pages.

Why your own search can mislead you

Search results are shaped by location, device, language and your recent history. If you have been opening your own site all week, what you see is influenced by that behaviour, and the position you see is not the position a customer in another suburb sees. Use a private window, check once from a phone on mobile data, and treat any single result as one data point rather than a verdict. The reports inside Search Console are the better instrument, because they show what people actually searched for and what Google actually served.

The Four Stages Where a Page Can Fall Out

Crawling, indexing, ranking and being replaced

Every visibility problem sits at one of four stages. Google has to find the URL, decide to store it, choose it for a query, and then the page has to hold the slot against everything else competing for the same intent. Each stage fails for different reasons and shows up in different reports.

The discipline that saves the most money is refusing to fix stage three before confirming stage one. Ask the questions in order. Has Google seen the URL? Has Google kept it? Is it being chosen for the query? Is it losing that slot to another page of yours? Three of those four questions are answered by the same two reports, and none of them are answered by searching your own business name repeatedly.

New Pages: Not Crawled Yet

How long Google usually takes

Newness is the most common cause of all, and it is the easiest to accept once you see the numbers. Google's help page on missing pages is specific: "It can take time for Google to index your page; allow at least a week after submitting a sitemap or a submit to index request before assuming a problem." The same page continues: "The total time can be anywhere from a day or two to a few weeks, typically, depending on many factors."

Google's crawling and indexing FAQ says the same thing more directly: "In general, the most common reason that a site is not indexed is because it's just too new; be patient and ask Google to crawl and index it." That second clause is the part owners skip, and it matters. Asking Google to fetch the page is a real step, and waiting afterwards is the next one. The full explanation is on the crawling and indexing FAQ. A sitemap helps discovery but is not a submission queue, and a sitemap file can help Google learn about your site, but it does not guarantee indexing or increase your site's ranking.

What to do while you wait

Spend the waiting week strengthening the page rather than refreshing the report. Add internal links from pages Google already crawls, confirm the page is not orphaned, check that it appears in your sitemap, and make sure the content answers the query you expect it to rank for. Then request indexing once, and leave it alone.

Blocking: Something Is Stopping Google

robots.txt, noindex and the clash between them

This cause costs the most time when it is misdiagnosed, because the two mechanisms work in opposite directions. A noindex instruction tells Google to keep the page out of results: "Google will drop that page entirely from Google Search results, regardless of whether other sites link to it." A robots.txt block stops the crawler reading anything on the page at all, including that instruction. Google states the trap in full: "If the page is blocked by a robots.txt file or the crawler can't access the page, the crawler will never see the noindex rule, and the page can still appear in search results, for example if other pages link to it." Both quotations are from Google's page on blocking search indexing with noindex.

So when a URL is blocked from crawling and you want it gone from search, the answer is not a stronger block. It is allowing the crawl and adding the instruction, or removing the internal links that point at the page.

Password protection, firewalls and old staging copies

Staging sites left on a live domain, password protected directories and firewall rules that reject known crawler addresses all produce the same symptom. So do forgotten copies of an old site that still resolve on a subdomain. Check whether the domain you are searching serves the same content as the domain you built on, and whether that content sits behind a login.

Indexed but Invisible: A Ranking and Intent Problem

The wrong page winning the query

If the URL is indexed and still does not appear for the phrase you care about, you have moved into ranking territory, and the usual cause is intent. Either the page is not about what the searcher wants, or a different page of yours sits closer to it. Compare your page with the three results Google currently shows for that query. Read what they cover, what format they use, and what they answer in the first hundred words.

Pages competing with each other

Two pages on the same subject compete for the same slot and Google picks one, which is why a page can look healthy in a report and still be invisible in practice. That is a consolidation question rather than a content one, and it belongs with the rest of the diagnosis work covered in the other diagnosis guides on the blog.

Duplicate URLs Taking the Credit

Canonical tags and what Google chooses

Duplicates are normal on almost every site. The secured and unsecured versions, the www and non www versions, trailing slash variants, tracking parameters, filtered category pages and print styles all produce near identical content. Google groups them and chooses the one it judges most complete and useful, and it treats your canonical tag as a hint rather than an instruction. When the hint and the other signals disagree, the signals normally win.

Parameters, trailing slashes and old domains

The practical check is to compare the URL Google reports as indexed against the URL you would have chosen. If they differ, look for the conflicting signal. A canonical pointing at a URL that redirects, an old domain still linked from somewhere, or internal links pointing at the parameter version of a page will all send Google a mixed message.

Technical Faults the Reports Will Show You

Server errors, soft 404s and redirect chains

Server errors, soft 404s and redirect chains each appear in the Page Indexing report with their own label. A soft 404 is the one worth understanding: the page returns a success code, but it looks empty or broken enough that Google treats it as missing. Redirect chains matter for a different reason, because every extra hop spends crawl time and every hop is a chance for a signal to be lost on the way.

Reading the Page Indexing report states

The report groups URLs by state: indexed, crawled but not indexed, discovered but not indexed, excluded by a noindex tag, alternate page with a proper canonical, and several more. Read the group names literally and in order, because discovery problems sit at the top of that list, decisions in the middle and confirmations at the bottom. The technical SEO checklist I work through walks the same states in the same order.

Manual Actions and Security Problems

Both are rare, and both are quick to rule out. The Manual Actions report tells you whether Google has applied a penalty to your site or to a section of it, and the Security Issues report flags hacked content, malicious redirects and unwanted software. If those two reports are clean and traffic has still fallen, the cause is competitive or intent related rather than punitive, and no number of indexing requests will change it.

Test a Fix Properly Before You Change More

URL Inspection, live test and requesting indexing

Use the URL Inspection tool to see what Google holds for a specific URL, then run the live test after a change so you are comparing against the current version rather than a cached one. Request indexing once. Then wait a week before drawing a conclusion, because the reports lag what happened on the site.

What to expect in the days after

Expect the inspection result to update before the index does. Expect impressions to appear before clicks. Expect a newly indexed page to rank poorly for a fortnight while Google works out where it belongs. None of that is evidence of failure, and none of it is a reason to change the page again in the same week.

A 30 Minute Diagnosis You Can Run Yourself

Minutes one to five: run the site: search and note whether the page appears at all. Minutes five to ten: open the Page Indexing report and find the state of the URL you care about. Minutes ten to fifteen: inspect that URL and read the coverage section for a canonical mismatch or a block. Minutes fifteen to twenty: check robots.txt and the page source for a noindex instruction. Minutes twenty to twenty-five: confirm the page is linked internally and present in your sitemap. Minutes twenty-five to thirty: if all of that is clean, wait a week and check again.

Everything after that is either patience or a technical fault worth fixing properly. If you would rather have it found for you, a proper SEO audit that checks crawling and indexing should name the specific blocking or duplication issue in plain English rather than hand you a score out of a hundred. And if the diagnosis still does not line up, the questions I get asked about indexing cover the cases that come up most.

Google Indexing FAQ

How long should I wait before worrying?

Longer than most owners do. Google's own guidance is to allow at least a week after submitting a sitemap or an indexing request before assuming a problem, and that the total time can run from a day or two to a few weeks. If the page is brand new, check again next week before you change anything.

Google removed my page. Did I get penalised?

Usually not. Duplicate content is normal and is not a spam policy violation, and Google itself notes that most pages that look missing are simply ranking low or being filtered by the specifics of the search. A real manual action appears in the Manual Actions report, and that report is the only place to confirm it.

Does adding my site to Search Console get it indexed?

No. Search Console is a reporting and diagnostic tool, not a submission queue. It shows you what Google found and why a URL was not indexed, and it lets you inspect a page and request indexing, but the crawl and index decisions stay with Google.

My page is blocked in robots.txt. Will that remove it?

No, and this is the mistake that costs the most time. If a URL is blocked by robots.txt, the crawler never sees a noindex instruction on that page, so the page can still appear in results when other pages link to it. To remove a page from search properly, either allow crawling and use noindex, or stop linking to the page.

The page is indexed but will not rank. Is that the same problem?

No, it is the next problem. Indexation is about whether Google holds the page. Ranking is about whether it is chosen for a query, and the usual causes are intent mismatch, weak internal linking, a duplicate URL winning the slot or a stronger competitor. Fixing indexation will not fix ranking, and the two should be diagnosed separately.

Should I ask Google to recrawl the page every day?

No. One request after a real fix is enough. Repeated requests do not move a page up the queue, and they distract from the actual cause. Change the thing that is blocking or confusing Google, confirm the change is live, then request indexing once.