Skip to main content
design_services
Initializing Protocols...
0%
arrow_back Back to Codex
Getting Found July 3, 2026 4 min read

Why Is My New Website Not Showing Up on Google?

A new site can be missing from Google for two completely different reasons, and the fix for one does nothing for the other. Here is the fifteen minute check I run on every freshly launched client site to tell which problem it actually has, before anyone panics.

MIN_READ 4
WORDS 838
YEAR 2026
Jul 03, 2026 — DISPATCH_016
Abstract dark editorial image of a search index grid with a single node glowing in indigo and cyan

There are two very different reasons a new website goes missing from Google, and treating one like the other can waste you a month.

Before you panic or blame whoever built the site, you can find out which problem you actually have in about fifteen minutes, using tools that are already free. The single most useful thing I can tell you is this: "not indexed" and "not ranking" are separate diseases with separate cures. Fix the wrong one and nothing moves.

The one search that splits the whole problem

Abstract lens of light over a field of dots with one dot dimmed, indexing concept

Open Google and type site:yourdomain.com (your real domain after the colon, no space). Google shows you every page it has stored from your site.

If you get zero results, your site is not indexed. Google does not have your pages yet, so it cannot show them to anyone, for any search. If you get results but your business never appears when you search for what you actually do, you are indexed but not ranking. Same symptom on the surface, completely different cause underneath.

Not indexed: the four checks I run first

When a freshly launched client site shows nothing under site:, I do not guess. I run the same four checks in the same order, because the cheap, embarrassing causes are also the most common.

First, the noindex tag. Half the "we are invisible" emergencies I have seen came down to one setting a previous builder left switched on. In WordPress it lives under Settings, then Reading, as a checkbox that discourages search engines. Staging sites ship with it on by default, and it quietly travels to the live site if nobody unticks it. Two clicks and you are done.

Second, robots.txt. Visit yourdomain.com/robots.txt in the browser. If you see Disallow: / sitting there, the whole site is being waved away from crawlers. That line belongs on a staging site, never on the one you want customers to find.

Third, the sitemap. In Google Search Console, open the Sitemaps report and confirm your sitemap was actually fetched, with a status of Success and a recent read date. Submitting a sitemap and Google reading it are not the same event, and people assume the first automatically means the second.

Fourth, request indexing. Paste a real page URL into the URL Inspection tool at the top of Search Console, and if it reports the page is not on Google, press Request Indexing. This does not force a ranking. It just moves your page into the queue to be looked at.

Reading the Search Console coverage states

Two diverging glowing paths splitting from one point, indexing versus ranking concept

Once you are inside Search Console, the Pages report tells you exactly what Google decided, if you know how to read the labels. These are the ones that actually matter.

"Discovered, currently not indexed" means Google knows your URL exists but has not crawled it yet. On a new domain this is normal and mostly a waiting game, helped along by internal links and a little authority coming in.

"Crawled, currently not indexed" is a sharper signal. Google visited the page and chose not to keep it. That usually points at thin, duplicate, or near-empty content, not a technical bug. The cure is a better page, not another indexing request.

"Excluded by noindex tag" means the page is telling Google to stay away, so go back to check number one. "Alternate page with proper canonical tag" is usually fine and means Google folded that URL into another version on purpose.

Indexed but not ranking is a different disease

If site: does return your pages, stop running indexing fixes. They will do nothing, because indexing was never the problem. Ranking is not permission to appear, it is competition for position, and a brand new domain starts with almost no trust built up.

For the first few months a new site can be fully indexed and still sit far down the results while Google works out whether to take it seriously. That is expected, not a defect. This is also where a genuine, well-built site earns its place over time, through real content, clean structure, and other sites eventually pointing back to it. If you want a second pair of eyes on where your site actually stands, a plain-language free website audit will tell you which of the two diseases you are dealing with before you spend money treating the wrong one.

The reason this matters is money and calm. Owners who confuse the two problems either wait patiently for rankings on a site Google literally cannot see, or they frantically resubmit sitemaps for a site that is already indexed and simply young. When I take on a new website build, the technical side of getting found is handled from day one, and the ongoing climb is something a steady care plan keeps pushing. The fifteen minute check above is not a substitute for that work. It is how you stop guessing, so the next decision you make is the right one.

Run the site: search first. Everything you do next depends on that single answer.

arrow_back Previous
What You Get for €390: Landing Page or Portfolio Site, Both With AI
// NEXT_STEP

Want this built for you?

Fixed scope. Fixed price. Fixed deadline.

// SUMMON_AGENT arrow_forward