Why is my website not showing up on Google?

There are two completely different versions of “not showing up,” and the wrong diagnosis can waste a week.

Your page may be absent from Google’s index, which is a discovery, crawl, or indexing problem. Or the page may already be indexed and simply appear lower than the search results you checked, which is a ranking problem. Submitting the same indexed URL again will not make it rank first. Rewriting a page that Google cannot crawl will not get it indexed.

Start with the guided Google ranking diagnosis. Paste the exact page URL, not just the domain. The tool does not fetch the page or pretend to know Google’s cause. It asks one question at a time and opens the specific Google checks needed to separate indexing, ranking, and local Maps results.

If you would rather work directly in Search Console, the same decision begins below.

First, inspect the exact URL

Open Google Search Console, select the property containing the page, and paste the complete URL into the inspection bar at the top. Include the protocol, hostname, path, and trailing slash exactly as the page uses them.

Google’s URL Inspection documentation draws an important line between two views:

• The indexed URL is the version Google last stored. Its crawl date and result can be older than the page you see today.
• The live test fetches the current page and checks whether it appears indexable now. A successful live test does not guarantee that Google will index or rank it.

Read the large verdict first, then expand Page indexing. The useful fields are page fetch, whether crawling and indexing are allowed, the referring page or sitemap through which Google found the URL, the last crawl, and Google’s selected canonical.

The verdict now sends you down one of four paths.

If Search Console says “URL is on Google”

Stop troubleshooting indexing. The page is eligible to appear, even if your own search did not surface it. URL Inspection does not promise that a page will appear for every query, location, device, or person, and it does not promise a particular position.

Open Performance → Search results and filter the report to the exact page. Use a date range long enough to contain real impressions. Then separate three cases:

1. The page has impressions for relevant queries. It is showing up. The problem is position, click-through rate, or a mismatch between the queries Google associates with the page and the searches you expected.
2. The page has impressions, but only for irrelevant queries. Re-check what the page actually promises in its title, heading, copy, links, and surrounding site context. Do not add a pile of loosely related keywords; decide which user job the page should own.
3. The page is indexed but has no impressions in the selected period. Confirm that the date, search type, country, and device filters are not hiding data. A newly indexed page may also need time before it earns impressions.

For a repeatable review, export the Pages and Queries tables and run them through the Search Console report analyzer. It keeps impressions, clicks, CTR, and average position visible and turns only documented rules into actions. A standard Pages file and a standard Queries file cannot prove keyword cannibalization, because neither contains the relationship between page and query; that check requires an export grouped by both dimensions.

If Search Console says “URL is unknown to Google”

Google has not discovered the exact URL yet. Check the address before changing the content. A different protocol, www hostname, trailing slash, uppercase letter, or redirected path can be a different URL to a crawler even when a browser makes the difference feel invisible.

Then give Google ordinary, durable discovery paths:

• Link to the page with a normal HTML link from another page Google already knows. Important pages should not depend on a menu that appears only after a click or on an internal search box.
• Include the canonical URL in the site’s XML sitemap and submit that sitemap in Search Console.
• Make sure the page is not behind a login and that the public URL returns the intended content.
• Run Test live URL. If it succeeds, use Request indexing once.

Google’s own guide to a page missing from Search recommends allowing at least a week after a sitemap submission or indexing request before assuming that something is broken. Repeating the request every hour does not turn a queue into a guarantee.

If crawling or indexing is blocked

URL Inspection normally names the blocking layer. Fix that layer, not every SEO setting at once.

Crawl allowed: No

A robots.txt rule prevents Googlebot from fetching the page. Inspect the rule that matched the URL. Broad patterns are the usual trap: a line intended for a staging folder can cover the live path too.

Removing the robots rule only permits a crawl. It does not itself request indexing, select a canonical, or make the page rank. After the file is corrected, run the live test again.

Do not use robots.txt as the method for removing an already indexed page. Google may retain the URL without being able to fetch the page and see a noindex instruction.

Indexing allowed: No

The page returned a noindex directive in a meta tag or HTTP response header. Remove it only if the page is genuinely meant for public search. Search results, account screens, duplicate print views, and temporary campaign variants may be excluded deliberately.

Check the rendered response that Google receives, not only the template in your editor. A plugin, deployment setting, or response header can add the directive after the source file you inspected.

Page fetch failed

A timeout, server error, redirect loop, DNS failure, or access challenge prevented the fetch. Open the live test details and compare Google’s HTTP result with an ordinary private browser window. A page that works only because your browser holds a login cookie is not publicly crawlable.

Fix availability first. Titles, schema, and keyword edits cannot compensate for a response that never delivers the page.

If Google selected another canonical

Search Console may call your URL a duplicate and show a different Google-selected canonical. That means Google chose another URL as the representative version, so the submitted duplicate is not the address expected in results.

Decide whether the choice is correct.

If both URLs contain the same thing, make the signals agree: link internally to the preferred URL, put that URL in the sitemap, redirect obsolete variants where appropriate, and use a self-referencing canonical on the preferred page. Do not alternate between both versions across navigation, hreflang, feeds, and structured data.

If the pages serve different intentions, make that difference real and visible. A canonical tag is a consolidation signal, not a command that lets two interchangeable pages compete forever. Inspect both URLs after the next crawl to confirm which one Google selected.

If one page vanished after a migration or redesign

Check the old URL and the new URL separately. The old address should return a direct permanent redirect to the closest replacement, not the homepage and not a chain through several historical versions. The new page should be internally linked, indexable, and named in the sitemap.

Also compare what survived the move: the main content, title, headings, canonical, language signals, and links from important pages. A visually identical redesign can still remove the plain HTML links or server-rendered text that made the old page discoverable.

Do not measure a migration from a single search you remember. Compare Search Console periods for the affected page group, keeping search type and filters equal.

If the whole site is missing

A site-wide disappearance calls for site-wide reports before page edits.

Check Search Console’s Manual actions, Security issues, and Removals reports. Google states that a manual action can lower or omit some or all of a site, while a security issue may place warnings between the search result and the visitor. An approved temporary removal can hide a URL even when the underlying page remains indexable.

Then inspect the homepage and one representative inner page. If both fail in the same way, look for a shared cause: an expired domain, broken DNS, a site-wide noindex, an overbroad robots rule, an authentication wall, or a deployment that serves errors to crawlers.

If only the homepage is indexed, the problem is more likely discovery and internal navigation. Google’s missing-page guidance recommends link paths that reach every important page from the homepage and a sitemap that names the URLs you want crawled.

What a site: search can and cannot tell you

A search such as site:example.com is a useful public clue when you do not own the Search Console property. Searching site:example.com/exact-page or the quoted full URL can also reveal an obvious indexed result or an unexpected hostname.

It is not an index inventory. Do not treat the displayed result count as a database total, and do not conclude that a page is definitely absent because one restricted search omitted it. Search Console’s URL Inspection report is the diagnostic source for a property you control.

The guided diagnosis prepares exact-page, domain, and www versus non-www searches when Search Console is unavailable, while labeling every one as a clue rather than proof.

The shortest correct order

1. Inspect the exact URL in Search Console.
2. If it is indexed, move to the Performance report and diagnose ranking rather than indexing.
3. If it is unknown, add a real internal link and sitemap entry, test live, and request indexing.
4. If it is blocked, fix the named crawl, noindex, fetch, or canonical condition and test again.
5. If the site disappeared broadly, check manual actions, security issues, and removals.
6. Wait for a new crawl, then inspect the same URL again and record what changed.

The last step matters. “I changed several things and the page returned” proves almost nothing. Keep the original verdict, the change, the request date, and the next indexed result together. That turns a frightening disappearance into a reproducible diagnosis — and gives you a way to recognize the same failure before the next page goes missing.