Skip to content
Sitequiry

Why Is My Website Not Showing Up on Google?

A site that does not show up on Google has one of three problems: Google has not indexed the page, it indexed a different URL instead, or the page is indexed and does not appear for the words you type. Each has a different fix, so the first job is to find out which one it is. In Google Search Console that takes a few minutes.

Updated 6 min read Written by the GE-KO team

Which of the three problems do you have?

Open Google Search Console and paste the full address into URL Inspection at the top. If the site is not verified there yet, do that first: no outside tool can see Google's index. The answer is one of three:

  • URL is not on Google: the page is not indexed. The report names the reason, and the table below explains each one.
  • URL is on Google, but the Google-selected canonical is a different address: Google has filed your page as a copy of another URL and shows that one.
  • URL is on Google with your own address as canonical: the page is indexed. What you have is a ranking question, covered near the end.

A site:yourdomain.com search is a quick first look, but Google says it does not necessarily return every indexed URL and points to URL Inspection when a page seems to be missing. Treat an empty site: result as a reason to check, not as proof.

What the reason in Search Console means

For a page that is not indexed, URL Inspection and the Page indexing report give the reason in a fixed wording. The main ones:

Page indexing reasons and the next step
Reason shown What it means What to do
URL marked ‘noindex’ The page tells search engines not to index it, in a robots meta tag or in an X-Robots-Tag HTTP header. Remove the directive, which is often a setting in the CMS, then request indexing.
URL blocked by robots.txt robots.txt forbids Googlebot to fetch the page. Remove the Disallow rule that matches the address.
Page with redirect The address redirects, so only the destination can be indexed. Nothing, if the destination is the page you want. Otherwise correct the redirect.
Not found (404) or Soft 404 The server says the page does not exist, or shows a "not found" message with a success status. Restore the page or redirect the old address. A real page needs real content.
Server error (5xx), Blocked due to access forbidden (403), Blocked due to unauthorized request (401) Google could not fetch the page. Googlebot never logs in. Check the server, the firewall and any password protection.
Alternate page with proper canonical tag, Duplicate without user-selected canonical, Duplicate, Google chose different canonical than user Google treats the page as a copy and indexes another URL. Make the signals agree, as described under "One page is missing".
Discovered - currently not indexed Google knows the address but has not crawled it yet. Usually wait. Link to the page from pages that are already indexed.
Crawled - currently not indexed Google fetched the page and has not indexed it. Work on the page, not on the settings.

The first two rows interact. If robots.txt blocks a page, Google cannot read a noindex on it, and URL Inspection then reports indexing as allowed. Google describes robots.txt as not a mechanism for keeping a page out of Google: a blocked address can still appear in results, without a description.

A new site or a new page

Google says finding and indexing a new page can take from a day or two to a few weeks, and advises waiting at least a week after submitting a sitemap or an indexing request before assuming a fault. Three things help in the meantime:

  • Submit an XML sitemap in Search Console. Google lists new sites with few links from other sites among the cases where a sitemap helps most. It makes discovery easier and does not oblige Google to index every URL in it.
  • Link to the new page from pages that are already indexed, starting with the homepage and the navigation.
  • Use Request indexing in URL Inspection once. There is a quota, and Google states that asking again for the same URL does not get it crawled any faster.

Nobody can sell a shortcut: Google does not accept payment to crawl a site more often or to rank it higher.

The site vanished after a launch, a redesign or a move

When a site that used to appear drops out soon after a release, look first at what was carried over from the development version:

  • A noindex meant for the staging site. In WordPress it is the checkbox Discourage search engines from indexing this site under Settings → Reading. It can also arrive as an X-Robots-Tag: noindex header set on the server, which the page source does not show.
  • Disallow: / in robots.txt, copied from the test server.
  • Canonical tags, redirects or sitemap entries that still point to the old domain, to http:// or to the staging address.
  • Old addresses without redirects. For a move Google asks for permanent (301) redirects from the old addresses to the new ones.
  • A login wall or an IP restriction left on the live site. Google treats 401 and 403 answers like missing pages and removes such URLs from the index if they were indexed before.

If you bought or inherited the site, add two checks from Google's own troubleshooting page: the history in the Manual Actions and Security Issues reports, and old requests in the Removals tool, which hide a URL for about six months.

One page is missing while the rest of the site is indexed

Here the site-wide settings are usually fine and the page itself is the question.

  • Google chose another canonical. When two addresses show the same or nearly the same content, Google indexes one. Redirects and a rel="canonical" link are strong signals, a sitemap entry is a weak one, and Google may still pick a different URL from the one you declared. Use one address in internal links, in the canonical tag and in the sitemap.
  • The page was crawled and not indexed. Google states that not every page it processes is indexed and names low quality of the content on the page among the common reasons. The fix is on the page: say something the other pages of the site do not.
  • No links lead to it. Google asks for a chain of ordinary links from the homepage to every page; a page that exists only in the sitemap does not meet that.
  • The content exists only after a click or a scroll. Google renders JavaScript in a step of its own and does not interact with the page, so content that loads on a user action may never be seen. Run the live test in URL Inspection and read the rendered HTML.

The page is indexed, but you cannot find it

If URL Inspection reports the URL as on Google with your address as canonical, indexing is done. Being indexed means the page can appear, not that it will appear for a given search. Three checks before you treat it as a ranking question:

  • Search for the exact title of the page in quotation marks. If the page comes up, Google serves it; it does not yet compete for the broader words.
  • Open Security & Manual Actions in Search Console. A manual action can lower pages or leave some or all of a site out of the results, and Google sends a message when it applies one.
  • Look in the Removals report for a request somebody filed earlier.

After that the answer is in the Performance report: the queries the page gets impressions for, and at what position. That is a different job from fixing indexing, and SEO score vs rankings explains why a technically clean page can still sit on page four.

How often the outright blocks occur: our own numbers

Two sets of our own data show how rare the outright blocks are on sites that are already live:

  • In our September 2026 crawl of 90 websites, 1 homepage carried noindex and none blocked Googlebot in robots.txt. Sitemaps were less tidy: on 6 of the 75 sites that had one, at least one sitemap URL we analysed was noindex, and on 15 of 75 at least one redirected or answered with an error.
  • Among the pages people analysed with Sitequiry between 24 August and 9 November 2026, counting the latest result for each of 106 different sites and leaving out our own, none had a noindex in the page or in the HTTP header, none of the 98 with a readable robots.txt blocked Googlebot, and 12 declared no canonical URL.

Neither is a sample of sites with indexing trouble, so they do not say how often a block is the cause of a missing page. They do suggest an order of work: rule out noindex and robots.txt first because that check is quick, then move on to the sitemap, the canonical and the page itself, where our crawl found more loose ends.

What you can check without Search Console, and what you cannot

A check from outside reads what the page and the server declare. A free Sitequiry analysis of the address shows:

  • whether the page carries a noindex signal, in the robots meta tag or in the X-Robots-Tag header;
  • whether robots.txt blocks Googlebot;
  • the canonical URL the page declares;
  • whether the address could be fetched at all, and the reason when it could not: a firewall, an invalid certificate or a server error.

It cannot see Google's side: whether the URL is indexed, which canonical Google selected, manual actions or removal requests. Those exist only in Search Console, and Google Search Console vs a website SEO audit sets the two side by side. For conflicts between the canonical and hreflang tags of language versions there is the hreflang and canonical checker.

Frequently asked questions

How long does it take for a new website to show up on Google?

Google gives a range of a day or two to a few weeks for a new page and suggests waiting at least a week after submitting a sitemap or an indexing request before looking for a fault. It does not promise that every page will be indexed.

Does submitting a sitemap make Google index my pages?

It helps Google discover them, most of all on a new site with few links from elsewhere and on large sites. Google states that listing a URL in a sitemap does not mean it will be crawled and indexed.

My page shows up for a site: search but not for normal searches. Why?

Then it is indexed, and the question is ranking for the words you typed, not indexing. Confirm it in URL Inspection, then look at the queries and positions in the Performance report.

Can robots.txt remove a page from Google?

No. robots.txt controls crawling. A blocked address can still be indexed, without a description, when other pages link to it. To keep a page out, use noindex and leave the page crawlable so that Google can read the directive, or protect the page with a password.

I requested indexing several times. Why is nothing happening?

Repeating the request does not speed anything up, and there is a quota. Read the reason URL Inspection gives for the page and fix that; one request afterwards is enough.

Check your own site in about a minute

The free analysis measures the points from this guide on your URL and shows what to fix first.