SEO / Indexing

Your page is live, but Google isn't showing it: what to check before changing everything

PuntoStackSeptember 23, 2026

You published a page. It opens correctly. It has text, images, buttons and even appears in your sitemap.

Several days pass, you search on Google, and you can't find it.

It's natural to assume something is broken.

Then the changes begin: the sitemap gets resubmitted, the title gets changed, plugins get installed, indexing is requested several times, robots.txt gets edited, and someone eventually says you need more keywords.

The problem is that we still don't know what's going wrong.

Before changing anything, it helps to separate four things that often get bundled into one statement: Google can't find my page.

A published page hasn't necessarily been discovered by Google yet. Being discovered doesn't mean it has been visited. Being visited doesn't mean it has been indexed. And being indexed doesn't mean it will appear near the top when someone searches.

First: what does appearing on Google actually mean?

A simple way to understand it is to imagine five steps.

1. The page exists

You can open it in your browser. That only confirms it is published.

2. Google discovers the URL

Google learns that the address exists. It may discover it by following a link from another page or reading a sitemap.

3. Google crawls it

Googlebot visits the page and tries to read what's there.

4. Google decides whether to index it

If Google adds it to its index, it can then consider it for search results.

5. Google decides when to show it

When someone searches, Google compares many pages and decides which ones it considers most relevant and useful for that query.

That's why a page can be published correctly and still be held up at any of the following steps.

And each situation needs a different kind of investigation.

Before worrying: confirm whether the page really isn't indexed

Many people search for their service, don't see their page near the top, and conclude that Google hasn't indexed it.

That may not be true.

The page could be indexed and simply rank much lower for that search.

You can also try a search using site:yourdomain.com, but don't treat it as an exact count. Google explains that the site: operator does not necessarily return every indexed URL.

For checking a specific URL, the most useful tool is URL Inspection in Google Search Console.

WHAT TO CHECK

whether Google knows the URL;
whether crawling is allowed;
whether Google could fetch the page;
whether indexing is allowed;
which URL Google considers canonical;
when the page was last crawled.

This stops you from trying to fix things that may not be broken.

Case 1: the page is new

This is probably the least exciting explanation, but it is also one of the most common.

Publishing a page doesn't send Google an instant alert.

On new sites or sites with little activity, Google may take days to discover and process a URL. Some pages may take longer.

If you just published it, don't turn a few hours of waiting into an SEO emergency.

WHAT I WOULD DO

confirm that another actual page on the site links to it;
confirm that it appears in the sitemap if it should be indexed;
check that it returns a normal response and anyone can open it;
inspect it in Search Console;
if everything looks right and it's an important URL, request indexing once.

WHAT I WOULDN'T DO

request indexing ten times in the same day;
repeatedly upload and delete the sitemap;
rewrite the entire page every few hours;
install random tools hoping they will force Google to act.

Requesting indexing is a request, not an order.

Case 2: Google can't even find the page

Here, the problem comes before quality, keywords or rankings.

Google needs a way to reach the URL.

Imagine a service page you can only open because you saved the link. It isn't in the menu, no article links to it, no category points to it, and it isn't in the sitemap either.

For someone who already knows the address, the page exists. For a crawler, it may be practically hidden.

Google recommends that important pages have at least one link from another page on the site.

CHECK THESE POINTS

Can you reach the page by navigating normally from other parts of the site?
Is the link an actual link that a browser and Google can follow?
Is the page included in the sitemap when appropriate?
Was it left orphaned after a redesign or menu change?
Does it only appear after clicking filters, dropdowns or other interactions that generate the URL in an unclear way?

A sitemap helps, but it shouldn't be the only place an important page can be found.

Case 3: Google can see it, but something says not to index it

This does involve technical settings, but you don't need to understand code to grasp the idea.

A website can send signals that essentially say:

You can visit this page, but don't keep it in the index.

The best-known signal is noindex.

It is intentionally used on pages that shouldn't appear on Google: for example, certain dashboards, internal search results, temporary pages or areas that have no value as search results.

The problem is when a commercial page ends up with noindex by mistake.

OTHER POSSIBILITIES INCLUDE

a page that requires a login;
a server error when Google tries to access it;
a 404 or similar status code;
a setting that blocks crawling;
important content that doesn't load correctly in the version Google processes.

Search Console often provides quite specific clues here. It's better to read that evidence than to guess.

Robots.txt and noindex are not the same thing

This causes a lot of confusion.

The robots.txt file is mainly used to indicate which URLs a robot may crawl. It isn't the recommended way to ensure a page disappears from search results.

noindex, on the other hand, is an instruction not to include a page in the index.

And there's a catch: if you completely block a page with robots.txt, Google may never see the noindex you put inside it.

That's why editing robots.txt just to see if it fixes things is a bad idea when you don't know what the problem is.

Case 4: Google thinks the page is essentially another page

Sometimes Google finds several URLs that seem to represent the same thing.

For example:

the same page on HTTP and HTTPS;
the same page with and without www;
URLs with parameters that don't actually change the content;
two service pages with almost identical text;
duplicate versions created during a migration;
a new page that is too similar to one that already exists.

Google tries to choose a representative version, called the canonical URL.

That means a URL may not appear separately because Google considers another URL a better representative of that content.

This isn't always an error. In many cases, it is exactly what should happen.

WHEN TO INVESTIGATE

If you expected two pages to be different but Google treats them as duplicates, ask whether they genuinely offer something different to a person.

Changing only the title or replacing a few words usually doesn't turn two nearly identical pages into two different resources.

Case 5: Google crawled the page but didn't index it

This status often causes more anxiety because everything seems to work.

Search Console may show:

Crawled - currently not indexed

In simple terms, Google visited the URL but didn't add it to the index at that time.

It doesn't automatically mean you have a penalty.

There is no technical button that can force Google to change its mind, either.

Google also says the page may be indexed later.

If this affects a single URL you just published, it may be too early to draw conclusions.

If it keeps happening to many important pages, it is worth looking at the overall pattern.

QUESTIONS WORTH ASKING

Do these pages say essentially the same thing as other pages on the site?
Is their content thin or unhelpful to someone looking for that answer?
Were they created in bulk by changing only the city, service or a few words?
Do they genuinely address a different need?
Are they well connected to the rest of the site?
Are some of these pages perhaps not worth trying to index at all?

Google recommends creating helpful, reliable content for people first. There is no magic word count that guarantees indexing.

A 3,000-word page that repeats what twenty other pages say may offer less value than a short page that solves exactly what the person needed.

Case 6: the status is Discovered - currently not indexed

This status is different.

Google already knows the URL exists, but it hasn't crawled it yet.

Search Console's documentation explains that Google may postpone crawling, for example, to avoid overloading a site.

The important thing is not to confuse this with Crawled - currently not indexed.

In one case, Google hasn't visited the page yet. In the other, it already has.

If you have thousands of discovered URLs and very few that really matter, the issue may be broader than a single page: structure, URL volume, duplicates, filters, overall quality or crawl priorities.

If it's just a few new pages, the context is completely different.

Case 7: the page is indexed, but nobody finds it

This is no longer an indexing problem.

It is a ranking, relevance or demand problem.

A page can be in the index and still appear in position 70, 90 or 120 for the search you're making.

It may also be relevant to searches different from the ones you imagined.

The questions change here:

Does the page actually answer what the person is searching for?
Do the title and content make the topic clear?
Do other pages offer a more useful or complete answer?
Does your site have enough context and authority around that topic?
Are there internal and external links that help explain the page's importance?
Are you searching for a phrase your customers actually use, or an internal business term?

Continuing to tweak the sitemap won't fix a page that is already indexed but isn't competitive.

A 10-minute check before changing anything

If a page isn't appearing as expected, I would follow this order:

Step	What to do	What you're trying to find out
1	Open the URL	Does it load for anyone without a login or errors?
2	Inspect it in Search Console	Does Google know it? Is it indexed? What reason does it show?
3	Check the HTTP status and access	Does it respond correctly? Could Google fetch it?
4	Check indexing	Is there a noindex directive or another signal preventing indexing?
5	Check the canonical URL	Does Google consider another URL to represent this page?
6	Check internal links	Does an actual page on the site link to it?
7	Check the sitemap	Is it included if it really should be indexed?
8	Review the content	Does it offer something of its own, or does it look like another version of something that already exists?
9	Separate indexing from ranking	Is it really not indexed, or does it simply rank very low?
10	Fix only what you found	After an important fix, test the URL and request indexing if it makes sense.

Three mistakes that waste a lot of time

1. THINKING A SITEMAP FORCES GOOGLE TO ACT

A sitemap is a very useful way to tell Google which URLs you consider important, especially on new or large sites.

But submitting it doesn't guarantee that a page will be crawled immediately, indexed or ranked.

2. REQUESTING INDEXING OVER AND OVER

If the issue is a noindex directive, an incorrect canonical URL, duplicate content or a page that offers nothing different, clicking Request indexing again won't fix the cause.

Fix it first. Then request another review when it makes sense.

3. CHANGING EVERYTHING AT ONCE

If you change the title, URL, sitemap, text, canonical URL, menu and settings on the same day, it becomes much harder to understand what was wrong.

A good diagnosis isn't about changing lots of things. It's about finding the most likely cause and testing it.

Not every page needs to be on Google

This matters because many audits treat every unindexed URL as a problem.

It doesn't make sense for Google to index absolutely everything.

Thank-you pages, private areas, duplicate versions, certain filters, internal search results or steps in a process can exist for users without having any reason to appear as search results.

The goal shouldn't be:

I want Google to index 100% of my URLs.

A more useful question is:

Can Google find, understand and index the pages that actually matter to my business and my users?

A simple example

Imagine a company that has just published a new page called Office air conditioning maintenance.

The owner searches for the service on Google the next day and doesn't see it.

Any of these things could be happening:

Google doesn't know the URL yet;
it knows the URL but hasn't crawled it;
it crawled it but found a noindex directive left over from development;
it considers it almost identical to another page about residential maintenance;
it indexed the page, but it still ranks very low;
the content is so generic that it's unclear why the page deserves to exist separately;
the page is isolated, with no other content on the site linking to it.

From the outside, all these situations feel the same: I'm not showing up on Google.

Behind the scenes, they are completely different problems.

That's exactly why it's worth diagnosing the issue before you start changing things.

When does it make sense to ask for help?

You don't need an SEO audit every time a new page takes a few days.

But a deeper review is worthwhile when:

important commercial pages have gone weeks without being indexed;
many URLs switch to Crawled - currently not indexed;
Google is choosing canonical URLs you didn't expect;
a migration or redesign coincided with a sharp drop in indexed pages;
Search Console shows blocks or errors you don't understand;
the sitemap contains URLs that shouldn't be there;
filters, parameters or templates have created hundreds or thousands of URLs;
the site is indexed, but its important pages receive almost no impressions.

In those situations, the work shouldn't start with a list of SEO tricks.

It should start by understanding where each type of page is getting stuck in the process.

The main takeaway

When a page doesn't appear on Google, don't start by asking:

What do I need to do to make Google index it right now?

Start by asking:

Has Google discovered it, crawled it, indexed it, or does it simply not rank where I expected yet?

That distinction completely changes what you need to check.

Sometimes the answer is to wait.

Sometimes it's to correct a technical signal.

Sometimes it's to improve the site's structure.

And sometimes the problem is less comfortable: the page works technically, but it doesn't yet offer enough value to compete.

The important thing is not to treat all these situations as the same problem.

Next step

If you have important pages that Google can't find, doesn't index or doesn't show as expected, we can first look into where the problem is before starting to change things.

Find out what's happening with my site

Sources consulted for this resource

We primarily used official Google sources to check how Google currently describes discovery, crawling, indexing, canonicalization and diagnosis in Search Console. The explanations, structure and examples in this resource are PuntoStack's own.