New website not showing on Google: what to check in Search Console

A new website not showing on Google is usually not a penalty or a hidden bug: Google simply has little to show. Before touching anything technical, check what the search engine actually sees in Search Console: impressions, pages, queries and sitemaps. This guide covers what to look at, how to read small numbers and which plan to follow during the first weeks.

There is no standard timeline for Google to rank a new site, and nobody serious can promise one. What you do control is what you diagnose, in what order, and when you measure again.

A new website not showing on Google: what to check first

The performance report in Search Console is the starting point. Review it in this order: clicks, impressions, CTR and average position; the pages with impressions; the queries; the breakdown by country and device; and the sitemaps you submitted. Then cross-check against your analytics: how many sessions come from organic search, and how many from social networks, direct visits or referrals.

The pattern that repeats most often in a new site is simple: minimal presence in search, with traffic concentrated among people who already know the project. When you see it, the problem is rarely ranking. It is surface, meaning how much indexable content Google has to answer with.

The page indexing report adds a second layer. Labels such as "Discovered: currently not indexed" and "Crawled: currently not indexed" mean different things. The first usually means Google knows the URL but has not crawled it yet: wait, and make sure other pages on the site link to it. The second means Google fetched the page and chose not to index it, which often points to thin or duplicate content. Each label asks for a different action, so do not treat them as one problem.

A sitemap does not force indexing, but it helps Google discover URLs. Check that it is processed without errors, that every URL in it answers with a 200 status and that none is blocked by robots.txt.

There is one more reading mistake worth avoiding: seeing only one query, or very few. Search Console anonymizes very-low-volume queries to protect privacy, so on small sites it is normal to see few of them. A single visible query does not mean nobody searches for other topics; it means volume never cleared the threshold for display. It is another symptom of the same condition: little surface.

How to read small numbers: what they say and what they don't

With a handful of impressions there is no ranking to judge, only anecdote. An average position can look reasonable and still mean nothing, because it is calculated over very few appearances. The same goes for CTR: if it rests on one or two clicks, a single extra click doubles it or erases it.

That is why you should read the numbers as a trend, not as a snapshot. Compare equivalent periods, note the date of every change you make, and look first at whether more URLs gain presence, then at impressions, and only last at clicks. Clicks depend on having something to show, so they arrive last.

The usual causes of a new website with no presence

Four causes come up again and again, and each one has a concrete check.

The first is scarce indexable text. If pages depend on JavaScript that builds everything in the browser, or if the content lives in images and canvases without text, Google sees an almost empty page. The URL Inspection tool in Search Console shows how the search engine processes it. A typical case of this problem, and how to address it, is covered in the article on 3D website SEO.

The second is the lack of pages that answer queries. A home page, a services page and a contact form are useful to someone who already knows you, but they give Google no reason to show you to a person searching for a topic.

The third is an empty content section. A blog with zero posts, or with two URLs in its sitemap, cannot generate impressions consistently. It is a promise, not a channel. This is the easiest cause to tackle, which is why it usually comes first in the plan.

The fourth is relying only on your own channels. If visits come from social networks and earlier contacts, nobody new is finding you by searching. That is not wrong in itself, but the site will not be discovered on its own.

What is usually not the problem

Ruling things out is diagnosis too. Nothing points to a penalty if your URLs already appear with impressions: that means Google finds, processes and shows the site. If the numbers are low, the most likely reason is how much surface you have, not a punishment.

Nor should you spend hours tweaking titles and descriptions on a site with four pages. Fighting for positions makes sense once you have pages that answer queries; before that, any polishing moves very little. A striking design does not replace text either. The framework for deciding how bold a design should be is in the article on disruptive web design.

Language and market are not default faults. Country and device data describe the audience you already have; they do not tell you whether the site should be showing.

When this is not a problem: if your business sells through another channel and search contributes nothing, there is no need to chase impressions. The diagnosis depends on the goal; without one, any number can look alarming.

A reference case with real numbers

For reference, sergioja.com recorded, over 90 days from July 16 to October 11, 2026, 38 impressions and 1 click in Search Console: a 2.6% CTR and an average position of 6.9. Only one query was visible and 3 URLs had impressions. In GA4, none of the 79 sessions came from organic search: 33 arrived from Instagram and 23 were direct. The audience was mostly in Colombia (around 67%) and on mobile (around 79%). When the analysis was run, on October 14, 2026, the blog had zero posts and its sitemap listed two URLs: the Spanish and English home pages.

What these figures show is a small indexable surface, not a ranking problem. The samples are small, so any strong conclusion would be an overreach. The response being tested is to publish useful content, link it from the surfaces that already get traffic and review the same views at 4 to 6 weeks, whatever the result. The architecture behind that setup is described in the reference implementation.

A plan of action for your website

This is the order I would follow before touching anything technical:

1. Write the numbers down as they are: impressions, clicks, CTR, position, visible queries and URLs with presence over 90 days. Then note sessions by channel, country and device in your analytics. Without that snapshot, everything else is guesswork.
2. Decide whether the problem is ranking or surface. If you have few URLs with indexable text and nearly all your traffic is social or direct, you lack material to show, not positions to fight for.
3. Build surface that answers real questions: articles, guides or case notes with indexable text, clear headings and internal links. If your site runs in several languages, check the signal between versions too, as the article on hreflang in Next.js explains. Publishing for the sake of it has a cost: thin content dilutes the rest of the site, so every page should earn its place.
4. Connect that surface to the rest of the site, submit the sitemaps and link from the pages that already receive traffic.
5. Set a review at four to six weeks and compare the same views. If impressions have not moved, the hypothesis has failed, and that is useful information too. Do not change everything every week.

No plan guarantees results or timelines. What you do control is your publishing pace and the quality of your measurement.

And if you want a second pair of eyes on your case, write to me through the contact page: send me your numbers as they are and I will tell you frankly whether I see a surface problem, a ranking problem or a goal problem.