How to index a page on Google and what to check if it fails

To index a page on Google you need two things: Google has to find it, and after reading it, Google has to decide to keep it in its index. You can push the first part from Google Search Console in two minutes. The second depends on the page and the site, and that's where almost all the time goes.

The scene is familiar. You publish a page, search for it the next day, it isn't there, and someone on the team says "just request indexing". That works pretty well for one URL. When it's twenty, fifty or ten thousand, requesting them one by one becomes a chore and doesn't pay off much.

We saw it on this very blog. Using the inspection tool, we checked the 49 Spanish-language articles published between August 24 and October 5, 2026: on October 9, 29 were indexed and 17 were still "Discovered - currently not indexed", meaning Google knew they existed and hadn't gone to fetch them yet. My read: if you have more than a handful of pages, the useful work is understanding why Google didn't want them and fixing the pattern, with internal links from pages Google already visits.

In this guide I cover what it means for a page to be indexed, how to check it, how to request indexing step by step, how long it takes, why Google sometimes doesn't index, and what changes when the site is large.

What does it mean to index a page on Google?

Indexing a page means Google crawled it, understood what its content is about and stored it in its index, the database it uses to build search results. If the page isn't in the index, it can't appear on Google, however good it is (the only way to reach it is by typing the URL or following a link).

The process has three stages, and it's worth separating them because each one fails for different reasons:

1. Crawling: Googlebot, Google's robot, discovers the URL by following links or reading your sitemap, and downloads it.

2. Indexing: Google processes the content, decides whether it's worth keeping and picks the canonical version if there are duplicates.

3. Ranking: when someone searches, Google orders the indexed pages by how well they answer.

The library analogy works: crawling is the librarian receiving your book, indexing is cataloguing it and putting it on a shelf, and ranking is which shelf it ends up on and how easy it is to reach. A book can arrive at the library and sit in a box in the storeroom for weeks. That's what the "Discovered - currently not indexed" status shows.

One clarification that saves arguments: being indexed only gets you in the door. An indexed page can get zero clicks, because ranking is a separate SEO job.

How do you check if a page is indexed on Google?

There are three ways, from fastest to most reliable.

The site operator in the search bar. Type site:yourdomain.com/your-page into Google. If the page shows up in the search results, Google has it. The site operator is useful to check quickly whether something is indexed, but it's imprecise: it sometimes leaves out pages that are in the index, and the total it gives for a whole domain is an estimate.

The URL Inspection tool in Google Search Console. You paste the address in the bar at the top and Google tells you whether "URL is on Google" or not, when it was last crawled, whether it found it in the sitemap, which page links to it and which one it chose as canonical. It's the official answer for a specific page.

The Pages report (Indexing > Pages). It shows how many URLs in your property are indexed and how many aren't, grouped by reason. For a large site, this is the starting point, because it lets you see the problem by status instead of checking one address after another. Google's help page for the report says you shouldn't expect everything to be indexed, and that what matters is that the important pages are.

How do you index a page on Google step by step?

If the page isn't indexed and nothing is blocking it, this is the standard path. It's free and takes a few minutes:

1. Verify your site in Google Search Console. Sign in, add a Domain property (it covers every subdomain and protocol) or a URL-prefix property, and prove you own it with a TXT record in your domain's DNS, an HTML file or a tag in the head. Without a verified property you can't do any of the steps that follow.

2. Submit your sitemap. In Search Console, go to Indexing > Sitemaps, paste the address of your XML file (for example, yourdomain.com/sitemap_index.xml or whatever your CMS generates) and click Submit. That list tells Google which URLs you want it to know about. Include only canonical addresses that return 200, with no redirects and no content marked noindex.

3. Inspect the URL. Paste the full address into the URL Inspection bar in Google Search Console and wait for the result.

4. Click "Request indexing". If the page isn't on Google, or if you changed the content significantly, this button puts it in a priority queue.

5. Check the result a few days later. Inspect it again or review the Pages report. If it's still not indexed, the reason Search Console shows tells you what to check (there's a table further down).

A note on step 2: if your site runs on a platform like WordPress or Shopify, the file most likely already exists and updates itself. Check it anyway, because it often includes addresses that shouldn't be there (empty tags, test drafts).

How many times can you request indexing?

A few per day. Google has a quota for requesting indexing of specific URLs and doesn't publish the exact number. And its guide to asking Google to recrawl is clear on two points: requesting the same URL several times won't get it crawled faster, and requesting it doesn't guarantee the page gets into the index.

For many URLs, the channel is the sitemap. And if you're thinking about the Indexing API: Google only allows it for pages with job posting (JobPosting) or livestream (BroadcastEvent) structured data, according to its Indexing API documentation. Using it for articles or product pages is breaking the rules.

How long does Google take to index a page?

Google says crawling can take anywhere from a few days to a few weeks. There's no guaranteed timeline, and it depends on how much it trusts your site, how easy it is to reach the page and how interested it is in the content.

On this blog, timing was all over the place. Articles published on October 1 and 2 were already indexed a week later. Meanwhile, 5 of the 12 published between August 24 and 31 were still "Discovered - currently not indexed" more than five weeks later, without the inspection recording a single Googlebot visit.

So if an important page still isn't showing up after two weeks, I wouldn't keep waiting with my arms crossed: I'd check its status in the report, its content and how Google gets to it.

Why doesn't Google index a page?

Because of a technical block, because it hasn't crawled it yet, or because it crawled it and decided not to keep it. The Pages report in Google Search Console tells you which of the three it is, with the exact name of the status. This is the practical translation of the most common ones, based on the official help page:

Blocks are the easiest to fix and the most common after a launch or a migration: a robots.txt with Disallow: / left over from the staging environment, or a noindex nobody unchecked (in WordPress, the "Discourage search engines" box under Settings > Reading). If you're about to change platforms, I explain how to size the SEO risk beforehand in this article on migrations (in Spanish).

The other two statuses call for something else. When a page shows as Crawled, Google already read it and decided not to index it, and it's almost always a content conversation: thin, duplicated or mass-produced text nobody reviewed (I wrote about that in what Google says about AI-generated content). When it shows as Discovered, Google hasn't crawled it yet, and that's more of an architecture conversation, the one you see most on sites that publish a lot.

What happened with the 49 articles on this blog?

To keep it concrete, this is the indexing status of the blog's Spanish-language articles, inspected one by one with the Search Console URL Inspection API on October 9, 2026:

Three things caught my attention.

First: the 17 "Discovered" articles were in the sitemap, and Google had downloaded it on October 6. So that list did its job (Google knew they existed) and Google still didn't go fetch them. I wrote about something similar in the article on why Google sometimes doesn't use your sitemap: that file tells Google what exists, and Google still decides when to go.

Second, it has to do with links. The inspection shows which pages Google knows about link to each article. Of the 31 that had at least one link of that kind, 24 were indexed (77%). Of the 18 without one, only 5 (28%). That's 49 articles on a small site and it's a correlation, so I take it as a clue. It does fit with how Google says it discovers pages: by following links.

Third: we published fast. There were days with seven and even nine new articles, and for a site with little authority that's probably more new content than Google feels like crawling in one go.

How do you get Google to index a large site faster?

On a site with thousands of URLs nobody is going to go page by page, so the technical SEO work happens at the template level. This is what I'd check, in this order:

1. Group the Pages report by page type. Export what isn't indexed and split it by pattern (product pages, categories, articles, filters). If 40% of product pages are "Discovered" and articles are fine (an illustrative example), the first thing I'd check is how product pages are linked.

2. Measure click depth by template. When we crawl an enterprise site for the first time, the pattern repeats: pages the business needs in order to sell end up 5, 6 or 7 clicks from the homepage. The rule we use is easy to audit: everything commercial at 3 clicks or fewer. You fix it with internal link modules in the template (related items, topic hubs, full breadcrumbs), because in a catalog of thousands of products linking by hand is impossible. If you're interested in the architecture side, it's in the article on silo structure.

3. Link new pages from pages Google already visits. A new page linked from a category or an article with traffic gets discovered the next time Google crawls that page. One that only lives in the sitemap waits its turn.

4. Look at the server logs. Server logs show where Googlebot actually went. On large sites it's common for a significant share of Googlebot's visits to go to filters, parameters and internal searches you don't want indexed, while new content waits. In the crawl budget guide I explain when that's a real problem and when it isn't.

5. Clean up the sitemap and robots.txt. Only canonical addresses that return 200, with a real last-modified date. In robots.txt, block what you don't want crawled (filter combinations, internal search) and make sure it isn't hiding anything that sells.

6. Review template quality. If thousands of pages share the same text with one detail changed, Google can crawl them and leave them out, and in that case requesting indexing doesn't change the outcome either.

Google's guide to crawl budget says this applies mainly to domains with more than a million unique URLs, or more than ten thousand that change daily, and also to those with a large share of their addresses in "Discovered". This blog is in the third group, with only a few hundred pages, so the status shows up on small sites too.

What should you check this week?

If you have one or two pages that aren't showing up, inspect them, request indexing and come back in a few days, which is usually enough.

If you have many, here's what I'd do with a free hour and zero budget: open Indexing > Pages in Google Search Console, note how many important URLs are in "Discovered" and "Crawled", and pick ten. For each one, check which pages link to it and how many clicks it is from the homepage. If the answer is "none" or "six", you know where to start (and you get to skip hitting the indexing button for the eleventh time).