How to get a new site indexed by Google
Verify the site in Search Console, submit a sitemap, then request indexing on your most important pages — crawling itself can take days to weeks.
To get a new site indexed, verify it in Search Console, submit an XML sitemap, and use the URL Inspection tool to request indexing on your most important pages. Crawling can then take a few days to a few weeks. Most sites that stay invisible are not penalized — they simply have not been found yet.
This is the step-by-step version of one piece of the small business SEO guide. If the site has other launch tasks still outstanding, the website launch SEO checklist covers the wider list this post is one item from.
On this page
What actually gets a new site indexed?
Three steps, done in order, each one unlocking the next. Verification proves you own the site and gives you access to real data about it. A sitemap tells Google what pages exist instead of waiting for them to be discovered by chance. Requesting indexing on the pages that matter most nudges the crawler toward them specifically rather than waiting for a routine crawl to find them on its own schedule.
None of this is complicated, and none of it needs a developer. The whole sequence takes about half an hour for a small site, and it is the single highest-return half hour available to a site that has just launched — far more valuable than an equivalent half hour spent on content, because content that cannot be found does nothing at all.
Verify the site in Search Console
Free, and required before anything else on this list works. Google offers several verification methods — a DNS record, an HTML file, or your existing analytics tag — and any one of them is enough.
Build and submit an XML sitemap
List every real page you want found and submit the sitemap URL through Search Console's sitemap report. This is the single fastest way to tell Google what your site actually contains.
Use URL Inspection to request indexing on key pages
For your homepage and your most important service pages, paste the URL into Search Console's inspection tool and request indexing directly, rather than waiting for the sitemap crawl alone to reach them.
Fix anything the inspection tool flags
The same tool tells you if a page is blocked, redirected, or already indexed. Read what it says before requesting again — it is usually more informative than guessing.
Google's own guidance on this is direct: requesting a crawl does not guarantee instant inclusion, and crawling itself can take anywhere from a few days to a few weeks [2]. That range is normal, not a sign something has gone wrong.
Verification specifically is worth doing carefully rather than quickly, because it is the one step that unlocks everything else. Google offers a handful of methods — adding a DNS record, uploading an HTML file, or confirming through an existing Google Analytics or Tag Manager account already on the site [1]. Pick whichever one you can complete without waiting on someone else, since a DNS change routed through a third-party registrar can itself take a day to propagate before verification succeeds.
How long does indexing actually take?
Days to weeks for crawling, and that is only the first hurdle. Being crawled means Google has read the page; being indexed means it has been stored as a candidate to show in results; being ranked well enough to be seen is a third, slower step still. Google's own documentation on requesting a recrawl states this plainly and adds that asking a second time does not move a URL up any queue [2].
What's actually stopping a page from being indexed?
Usually one of a short list of technical blockers, roughly in order of how often we see them. All four are worth checking even if you are confident none apply, because each one is invisible from the front end — the site looks completely normal to a visitor while quietly being invisible to the crawler.
| Blocker | What it looks like | Fix |
|---|---|---|
| A leftover noindex tag | Page loads fine, but a meta tag tells Google to skip it | Remove the tag; it is often left from a staging build [5] |
| Robots.txt disallowing the path | The page is never even fetched | Check robots.txt directly at yourdomain.com/robots.txt [4] |
| No internal links pointing to the page | The page exists but nothing on the site links to it | Link to it from your navigation or a relevant page |
| Thin or duplicate content | Crawled but judged not worth indexing | Add real, specific detail a reader would actually want |
Robots.txt deserves a specific warning here, because people misuse it in both directions. It is meant to manage how heavily a site gets crawled, not to hide pages from search results — Google is explicit that it is "not a mechanism for keeping a web page out of Google," and a disallowed page can still be indexed if other sites link to it [4]. If you actually want a page excluded, use a noindex tag instead; if you want a page included, make sure robots.txt is not accidentally blocking the whole site.
The internal-links blocker is the one people least expect, because it is not really about the page itself. A page that exists, loads fine and has no technical block can still sit unindexed for weeks simply because nothing else on the site points to it — no menu item, no related-content link, nothing a crawler could follow to find it. Sitemap submission helps here, but a page that also has a real link from your own navigation or another relevant page tends to get discovered and trusted faster than one that only ever appears in the sitemap file.
Are there limits on what a sitemap can include?
Yes, and hitting them is a real problem for a larger site.
50,000 URLs per sitemap file
Most small business sites never come close to this limit, but it matters the moment a site has a large catalog or many location pages. If that applies to you, split the sitemap into several files and list them in a sitemap index file, which Search Console can also read directly.
A more common sitemap mistake for a small site has nothing to do with size: listing pages that redirect, return an error, or carry a noindex tag. Submitting a clean sitemap that matches exactly what should be indexed is worth more than submitting a large one, because a sitemap full of dead or blocked URLs signals a poorly maintained site rather than speeding anything up.
What about search engines other than Google?
Worth doing, and it takes ten extra minutes once you have already done the Google steps. Bing Webmaster Tools offers the same verification and sitemap submission, and its index also feeds some AI assistants that answer buying questions, which Google's index alone does not reach. There is no reason to skip it once the harder technical work is already done.
Bing also imports a verified Search Console property directly in many cases, which shortens the second setup considerably. Even without that shortcut, the sitemap file you already built for Google works for Bing without changes, so the marginal cost really is the ten minutes it takes to click through verification a second time.
What if indexing is fine but nothing is ranking?
That is a different, slower problem, and a good sign in one sense: it means the technical work above worked. Indexed pages that do not rank are usually competing against sites with more history, more links and more proven trust, which is the subject the SEO on a small budget guide covers for exactly this stage — what to do once the pages are found and the wait for trust begins.
Resist the urge to treat this as the same problem as not being indexed at all, because the fix is different. An indexing problem is solved by removing a technical block. A ranking problem is solved by time, links, reviews and pages that keep answering their question well — none of which a second indexing request touches. Confusing the two is the most common way people waste a month chasing the wrong fix.
The number of times we've been asked to 'fix the SEO' on a site that was simply never indexed is higher than you'd expect. Always check indexing status before touching a single word of the content — it is a five-minute look in Search Console, and it rules out the most common real cause first.
If checking and fixing all of this feels like more than you have time for, that is one of the clearer signals it might be time to bring in help; when to hire an SEO lists the other signals alongside this one.
Questions people also ask
How do I get my new website indexed by Google?
Verify the site in Search Console, submit an XML sitemap, then use the URL Inspection tool to request indexing on your most important pages. Crawling itself can take a few days to a few weeks after that.
Why is my site not showing up on Google at all?
Usually because it has not been crawled yet, not because of a penalty. Check for a leftover noindex tag or a robots.txt file blocking everything, then verify, submit a sitemap, and request indexing on the pages that matter most.
Does requesting indexing again speed things up?
No. Asking twice does not move a URL up any queue. If a page has not appeared after a few weeks, check for a technical block before requesting again.
Does a sitemap guarantee my pages get indexed?
No. A sitemap tells Google what exists and helps it find pages faster; it does not force indexing. Google still decides whether a page is worth indexing based on whether it is reachable and appears to have real value.
Do I need to do anything for Bing separately?
Yes. Bing has its own webmaster tools and its own index, which also feeds some AI assistants, so verifying and submitting a sitemap there too is worth the extra ten minutes on top of Google.
Sources
- Search Console: get started — Google Search Central (checked 23 September 2026)
- Ask Google to recrawl your URLs — Google Search Central (checked 23 September 2026)
- Build and submit a sitemap — Google Search Central (checked 23 September 2026)
- Robots.txt introduction — Google Search Central (checked 23 September 2026)
- Tell Google not to index a page with noindex — Google Search Central (checked 23 September 2026)
Find out why your new site isn't indexed yet
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- Small business SEO: the complete 2026 guideSmall business SEO explained: what to fix first, what it costs, how long it takes, when to hire help, and how it compares with ads, social and email.
- SEO for a new website: the first 90 daysA new website's SEO starts with crawlability and a sitemap, then a handful of real pages, then patience while Google decides the domain can be trusted.
- How to do SEO on a small budgetA small SEO budget means spending time where money would normally go: the free basics done properly beat a cheap package almost every time.
- When to hire an SEOThe signal that it's time to hire isn't a revenue number or a date on a calendar. Here's what actually tells you, and what to hire first.