How to Index Your Website on Google, Step by Step

To index your website on Google, verify the property in Search Console, submit your XML sitemap, fix anything blocking the crawl, then use URL Inspection to request indexing on your most important pages. Most new sites see their homepage indexed within days and the rest within a few weeks, once the blockers are cleared.

I maintain this site by hand, no CMS, and every one of its 200+ guides has gone through this exact indexing sequence at least once. That includes a recent batch of thin posts I rewrote and resubmitted this year. This guide is the procedure I actually follow: what to check first, what to submit, when to click Request Indexing, and how long to realistically wait before you assume something is broken.

What it means for a page to be "indexed" on Google

A page is indexed when Google has crawled it, processed its content, and added it to the index, the enormous database Google's search results are drawn from. An indexed page is eligible to appear in results. It is not guaranteed to rank well, or even to appear on the first ten pages, but it is in the running. A page that is not indexed cannot appear for any query at all, no matter how well it is written.

Indexing sits between two other stages. Crawling comes first: Googlebot has to fetch the page before anything else can happen, which my guide to what crawling is in SEO covers in full. Ranking comes after: once a page is indexed, Google decides where it appears for a given search, based on relevance, quality and authority. Confusing these three stages wastes time, because the fix for "not crawled" is different from the fix for "crawled but not indexed," which is different again from "indexed but not ranking."

This guide is about the middle step: getting a page from existing to indexed, as fast as that step can reasonably go. If you already know your site is indexed and the real problem is that it does not show up for the searches you care about, this is not the guide you need. Read why your website is not showing on Google instead, which starts with the full diagnosis and only points you here once indexing is confirmed as the actual cause.

Why a new page does not index itself

Google does not know a page exists until something tells it. On an established site with a healthy crawl rate, Googlebot often finds new pages within a day or two just by revisiting the homepage and following the link to it. On a brand new site, or a page nothing links to, there is no such signal, and the page can sit unindexed indefinitely. Not because anything is wrong with it, but because nobody invited Google to look.

New sites carry an extra disadvantage. They have no history and no authority yet. Google indexes selectively, and a domain with zero backlinks and a handful of pages does not get the benefit of the doubt an established site does. This is normal, not a penalty, and it is exactly why the manual steps in this guide matter more for a new site than an old one. The gap closes as the site earns links and history.

Three groups of causes keep a page out of the index, and it helps to know which one you are dealing with. First, discovery problems: Google simply does not know the URL exists. Second, access problems: Google knows about the URL, but a noindex tag, a robots.txt rule or a broken canonical is stopping it. Third, quality problems: Google crawled the page and chose not to index it because the content did not justify a place in the index. The seven steps below handle the first two directly and give you the tools to catch the third.

What you need before you start

Everything here is free, and most of it takes minutes to set up if you have not already.

• Google Search Console, verified for your domain. Every step in this guide happens here. My Search Console guide for beginners covers verification if you have not done it yet.
• Your XML sitemap URL, usually yoursite.com/sitemap.xml. If you are not sure whether yours exists or is correct, the XML sitemap guide covers how to generate and check one.
• Access to your site's code, CMS or hosting dashboard, so you can check or remove a noindex tag, edit robots.txt, or confirm a canonical tag.
• Website SEO Checker, to scan a URL for noindex tags, robots.txt blocks and canonical issues in one pass instead of digging through source code by hand.

How to get a new page indexed on Google: the 7-step procedure

Do these in order. Steps 1 to 3 remove anything stopping Google from indexing the page at all. Steps 4 to 6 actively invite Google to look. Step 7 confirms it worked.

Step 1: Verify your site in Google Search Console

If your property is not verified yet, go to search.google.com/search-console and add it, either as a Domain property, verified through a DNS record, which covers http, https, www and non-www together, or a URL-prefix property, verified with an HTML tag, file upload, or Google Analytics. A Domain property is the better choice for most small sites because it shows everything in one place. Once verified, open Indexing, then Pages, and note the current indexed count as a baseline.

A common mistake here is verifying the wrong version of the domain, say www, while the site actually serves the bare domain. If Search Console shows almost no data for a site you know gets traffic, this mismatch is usually why. Confirm the property matches the URL your canonical tags and redirects actually resolve to.

Step 2: Submit your XML sitemap

Under Indexing, then Sitemaps, submit your sitemap URL. A sitemap does not force Google to index anything, but it hands over a complete, direct list of the URLs you consider worth indexing, which is more efficient than making Google discover them one link at a time. Most CMS platforms generate one automatically. WordPress needs a plugin like Yoast or Rank Math; Shopify and Wix generate theirs by default. My guide to XML sitemaps covers the format and the common mistakes in full.

Check that the sitemap actually lists the page you are trying to get indexed, in its canonical form, not a version that redirects or carries a noindex tag. A sitemap full of URLs that immediately redirect elsewhere sends a confusing signal, and Search Console flags the mismatch in the sitemap report within a day or two of submission.

Step 3: Fix anything blocking the page from being indexed

This is the step people skip and regret. Open the page's source and search for noindex. A meta robots noindex tag anywhere in the head tells Google not to index the page, full stop, and no sitemap submission or Request Indexing click overrides it. On WordPress, check Settings, then Reading, for the "Discourage search engines from indexing this site" box, which developers tick during a staging build and routinely forget to untick at launch.

Next, open yoursite.com/robots.txt and read every Disallow line. A stray rule blocking everything under the general user agent blocks the entire site from being crawled, which means it can never be indexed regardless of anything else you do. My robots.txt guide explains the syntax if any of it is unfamiliar. Here is what both blockers look like in raw form, so you know exactly what to search for:

<!-- Blocks indexing even if everything else is correct -->
<meta name="robots" content="noindex">

# Blocks the entire site from being crawled
User-agent: *
Disallow: /

Finally, check the canonical tag. If the page you want indexed carries a rel="canonical" pointing at a different URL, you are telling Google this page is a copy and the other one is the original. My canonical URL guide covers how this gets set wrong. The fastest way to check all three at once is to run the URL through the free SEO checker, which flags noindex tags, robots.txt blocks and canonical mismatches in a single scan.

Step 4: Use URL Inspection and click Request Indexing

Paste the exact URL into the search bar at the top of Search Console. The result tells you whether the URL is currently on Google, when it was last crawled, and whether indexing is allowed. If it is not yet indexed and you have confirmed there is no blocker, click Request Indexing. This puts the URL into a priority crawl queue, and in my experience it genuinely is the fastest way to get a specific page looked at, often within a day or two rather than the days-to-weeks a page might otherwise wait.

Request Indexing has a daily quota. Google does not publish the exact number, and it can vary by account, but at the time of writing (September 2026) it typically holds to somewhere around ten to twelve individual URL submissions a day per property before the button greys out for 24 hours. Treat that figure as a rough, changeable guide rather than a fixed rule, and check your own account if it matters for a launch. That covers a handful of important pages, not fifty pages at once, which is what the sitemap in step 2 is for. Google's own guidance on asking Google to recrawl URLs also says clicking Request Indexing repeatedly on the same URL will not get it crawled any faster, and recommends a sitemap for larger batches.

Step 5: Link to the new page from pages Google already indexes

Internal links are the single most underused lever in this list. When Googlebot crawls your homepage or another indexed page and finds a link to the new URL, that link is both a discovery signal and a vote that the page matters enough to be reachable. A page linked from your homepage or a well-trafficked guide tends to get crawled faster than one that only exists in the sitemap.

Add the link from a real, relevant page, using a normal anchor tag, not a button that loads the destination with JavaScript, which Googlebot may not follow on the first pass. My internal linking strategy guide covers how to do this across a whole site rather than one page at a time.

Step 6: Earn one or two real external mentions

A link from another website is a stronger discovery and trust signal than anything you can do on your own site, because it tells Google someone outside your control thought the page was worth pointing at. You do not need many. A mention on a relevant local directory, a guest post on an industry blog, or a supplier or partner linking back is enough to help a new page or a new domain get noticed and crawled faster.

This is a slower lever than the first five steps. Treat it as something you build over the following weeks, not something you finish today.

Step 7: Check the Pages report and confirm it worked

Give it a few days, then return to Indexing, then Pages, and check whether the URL has moved into the indexed count. You can also run a site search for the exact page in an incognito window; if it appears, it is indexed. If a week has passed and nothing has changed, go back to step 3.

In almost every case I have diagnosed, a page that will not index after a genuine Request Indexing attempt still has a blocker somewhere, most often a noindex tag re-added by a plugin update or a canonical pointing at the wrong URL. It is rarely a case of Google simply refusing a clean page.

How long indexing actually takes, realistically

For a single page on an established, healthy site, expect anywhere from a few hours to a few days after a Request Indexing submission. For a brand new domain with no history, expect a few days to a few weeks for the first pages, even after doing everything in this guide correctly, because Google is still deciding how much attention the domain deserves.

Google's own documentation is honest about this: crawling after a recrawl request can take anywhere from a few days to a few weeks, and a request does not guarantee indexing will happen at all if the page does not clear the quality bar once it is fetched. The table below is a rough guide, not a promise, useful for judging whether you are on a normal timeline or actually stuck.

Why content quality decides this more than any button does

Request Indexing feels like the whole solution because it is the one action with a visible click and an immediate confirmation message. It is not the whole solution. Google's crawlers will fetch a requested page quickly in most cases, but fetching is not the same as indexing, and Google is openly selective about what it stores once it has looked. A technically clean page with thin, generic content can sit in "Crawled, currently not indexed" indefinitely, requested or not.

I saw this directly on this site. A batch of older guides, each around 1,300 words and covering their topic at a surface level, sat in "Crawled, currently not indexed" in the Page indexing report for months. They had sitemaps, internal links, no noindex tags and no robots.txt blocks. Clicking Request Indexing on them did nothing, because there was nothing wrong with their access, only with how much the content justified a place in the index next to more thorough pages already covering the same ground.

Rewriting each one to go deeper, with real examples and more complete coverage, moved them into the index within weeks, without touching a single technical setting. If you have fixed every blocker in steps 1 to 3, submitted the sitemap, requested indexing and linked to the page internally, and it still will not index after a few weeks, stop checking technical settings and read the page as a stranger would. Indexing is Google's way of saying a page earned a place in a very large, very selective library, and a button cannot substitute for that.

Does IndexNow help you index faster on Google?

No, and this catches people out because IndexNow is real, useful, and easy to confuse with a Google feature. IndexNow is a protocol, originally from Microsoft and Yandex, that lets a website ping a search engine the moment a page is published or changed, instead of waiting to be crawled. Bing, Yandex and a handful of smaller engines support it. Google has publicly declined to join IndexNow and does not use it as an indexing signal.

If your site already pings IndexNow, there is no harm in leaving it running. It genuinely speeds up indexing on Bing, and Bing's index feeds several AI answer engines, so the effort is not wasted. It simply does nothing for Google, which means it cannot substitute for the sitemap, Request Indexing and internal linking steps above. If a plugin or a vendor tells you IndexNow will get your site indexed instantly on Google, that claim is not accurate, and Search Console remains the only channel that actually reports what Google has done with your pages.

Common mistakes that slow indexing down

• Requesting indexing on the same URL repeatedly. Clicking Request Indexing five times in a day does not speed anything up and burns through your daily quota.
• Submitting the sitemap without fixing blockers first. A sitemap tells Google a URL exists; it does not override a noindex tag or a robots.txt disallow on that same URL.
• Leaving the WordPress "discourage indexing" box ticked after launch. The single most common accidental block on new sites, and a thirty-second fix once you know to look for it.
• Treating a redirected or canonicalised URL as the target. If the URL you are requesting indexing on immediately redirects, index the destination instead. My 301 redirect guide covers how to check where a URL actually resolves to.
• Assuming Request Indexing helps with AI search too. It only affects Google's own index. Getting cited by AI answer engines is a related but separate problem with its own signals.

Most of these mistakes cost a week or two, not months, but a week or two matters when a launch date is waiting on visibility. Checking the Pages report before assuming a step failed saves more time than any single fix on this list.

When this guide is not what you need

If a site search for your own domain already returns your pages, indexing is not your problem, and nothing in this guide will move the needle, because Google already has the page. What you are looking at instead is a ranking problem: the page is indexed but not competitive for the searches you want it to appear for. That is a content, intent-matching and authority question, covered in how to rank on the first page of Google.

If you have worked through every step here and pages are still not indexed after several weeks, the honest next move is the fuller diagnosis in why your website is not showing on Google, which walks through the less common causes: manual actions, a redirect chain eating the request, or a hosting setup serving different content to Googlebot than to visitors. Realistic expectations matter here too. My guide to how long SEO actually takes covers the timeline for the ranking work that follows indexing, once a page is safely in Google's library. And if a page's address is about to change as part of any of this, set the move up correctly the first time with my 301 redirect guide, since a badly configured redirect can undo an indexing fix within days.

Frequently asked questions

How long does it take to index a website on Google?

For a page on an established site, expect a few hours to a few days after you submit a Request Indexing request in Search Console. For a brand new domain, expect a few days to a few weeks for the first pages, since Google has no history with the site yet. If nothing has moved after four weeks, the cause is almost always a leftover noindex tag, a robots.txt block, or content Google judged too thin to store, not a queue you simply have to wait out.

Why is my new website still not indexed after I submitted the sitemap?

A sitemap only tells Google a URL exists, it does not override a block. If the page carries a noindex tag, is disallowed in robots.txt, or has a canonical tag pointing at a different URL, Google will not index it no matter how many times it appears in your sitemap. Open the page's source and check all three before assuming the sitemap submission failed. A free SEO checker tool can flag all three in one scan, which is faster than reading raw HTML by hand.

Does clicking Request Indexing guarantee my page will be indexed?

No. Request Indexing puts a URL into a priority crawl queue and usually gets it fetched faster than waiting for normal discovery, but Google is explicit that a request does not guarantee inclusion in search results or that it will happen instantly. If Google fetches the page and judges the content too thin or too similar to something already indexed, it can still leave the page out. Requesting indexing gets a page a fair look. Whether it earns a place still depends on the content.

How many pages can I request indexing for in a day?

Google does not publish an exact number, but in practice the Request Indexing button in URL Inspection allows roughly ten to twelve individual submissions per property per day before it stops working for 24 hours. That covers your most important new or fixed pages, not dozens of URLs at once. For anything beyond a handful of pages, submit or resubmit your XML sitemap instead, which Google explicitly recommends for larger batches of URLs.

Does IndexNow get my pages indexed on Google faster?

No. IndexNow is a protocol supported by Bing, Yandex and a few smaller search engines, and Google has publicly declined to support it. Pinging IndexNow can speed up indexing on Bing, which also feeds some AI answer tools, but it has no effect on Google's crawling, indexing or ranking. For Google specifically, the only levers that work are a correct sitemap, an unblocked page, internal links, and the Request Indexing button in Search Console.

Related guides

• 301 redirects: meaning, setup and SEO impact
• Why your website is not showing on Google
• What crawling is in SEO
• XML sitemaps: what they are and how to submit one
• Google Search Console for beginners
• What canonical URLs are
• Internal linking strategy guide
• How long SEO actually takes

Your next step

Open Search Console today, submit your sitemap, and request indexing on your two most important pages. Then run the free SEO checker to confirm nothing else is silently blocking the crawl.