You publish a new location page or service page, refresh Google Search Console for three days straight, and nothing happens. New pages don't get indexed by accident - they get indexed because you gave Google clear, easy signals to find and trust them. None of what follows is a trick or a loophole; it's the same handful of technical steps that separate a page that gets crawled same-day from one that sits invisible for a month. Work through this checklist in order every time you publish a new page, and indexing stops being a mystery.
Google doesn't index pages it can't find, doesn't trust, or can't render. Fix those three things and speed takes care of itself.
1. Ask Google directly: URL Inspection + Request Indexing
The single most reliable lever you have is also the most overlooked. Open Google Search Console, paste the new page's exact URL into the URL Inspection tool, wait for it to check the live version, then click Request Indexing.
This puts your page into a priority crawl queue instead of waiting for Googlebot to stumble onto it naturally. It's not a guarantee, but for a legitimate, well-built page it's usually the fastest single action you can take.
2. Confirm it's actually in your sitemap
Google re-checks submitted sitemaps periodically, not constantly, and a page that's missing from the sitemap can sit unnoticed for a long time even if the rest of your site is healthy.
Open your sitemap.xml directly in a browser and search for the new URL. If it's not there, fix your sitemap generation (most CMS and static site setups do this automatically, but custom builds can miss new routes). Then confirm the sitemap itself is submitted under Sitemaps in Search Console, not just sitting on your server unreferenced.
- Open yourdomain.com/sitemap.xml and Ctrl+F for the new page's slug
- If missing, check your CMS/build process for why new pages aren't being added automatically
- Confirm the sitemap is listed and reads 'Success' under Search Console > Sitemaps
3. Link to it from a page Google already trusts
Google discovers new pages mostly by following links from pages it already knows and crawls regularly. A brand-new page with zero internal links is an island - Search Console submission helps, but a real link from an established page is what keeps a page getting re-crawled long-term.
Add a link to your new location or service page from your main services page, your navigation, or your blog index - somewhere Google already visits often. A single relevant, contextual internal link does more for discovery than any technical trick.
4. Rule out accidental blockers
Before you assume Google is just slow, check that you're not accidentally telling it to stay away. This is the step people skip and then wait three weeks for nothing.
Check all three of these on the live page, not a cached version or your CMS preview.
- robots.txt isn't disallowing the page's path
- There's no stray noindex meta tag left over from a staging template
- The canonical tag on the page points to itself, not to a different (older or similar) URL
Not sure if something on your site is blocking indexing?
A free audit checks your robots.txt, canonical tags, sitemap, and page speed in one pass, so you're not guessing which of the seven steps above actually applies to you.
Audit your site's health free →Book a free call →5. Keep it fast and mobile-friendly
Page experience signals - load speed, mobile rendering, layout stability - factor into how Googlebot prioritizes and processes a page. A page that loads slowly or renders broken on mobile can get crawled but deprioritized or delayed in the index.
Run the new page through Google's PageSpeed Insights and check it on an actual phone. Fix anything that blocks rendering (render-blocking scripts, oversized images, layout shift) before you spend more time chasing indexing directly.
6. For multi-location sites: ping IndexNow too
If you're publishing several location or service pages - the common case for a multi-location local business - an IndexNow-compatible ping can notify participating search engines the moment a page goes live or changes, on top of your normal Search Console submission.
It's a legitimate open protocol, not a workaround, and it's most useful as a supplement to steps 1-3, not a replacement for them.
7. Make sure the page is actually worth indexing
This is the one that quietly sinks most multi-location SEO efforts. If your "new" page is a near-duplicate of nine other city pages with only the city name swapped, Google's quality systems are specifically built to recognize and deprioritize that pattern - sometimes it gets crawled and then dropped from the index days later.
Every location or service page needs genuinely distinct content: real local detail, different examples, different photos or proof points, not a find-and-replace template. Thin, templated pages are the most common reason indexing looks "slow" when the real problem is that Google decided the page isn't worth keeping.
Even doing everything above correctly, give it time. New pages typically take anywhere from a few hours to two weeks to be crawled and indexed - this checklist shortens that window, it doesn't override it.
FAQ
How long does it normally take Google to index a new page?
Anywhere from a few hours to about two weeks, depending on how established your site is and how strong its crawl signals are. Doing the steps in this checklist shortens that window; it doesn't guarantee same-day indexing.
Does clicking 'Request Indexing' in Search Console actually work?
Yes, for legitimate pages it's usually the fastest single step you can take, since it puts the URL into a priority crawl queue rather than waiting for normal discovery. It's not a guarantee, and Google can still decline to index a page it judges low-value.
Why is my page in the sitemap but still not indexed?
Being in the sitemap gets it noticed, but sitemaps are only checked periodically. If the page also lacks internal links, is slow on mobile, or reads as thin/duplicate content, Google may crawl it and still choose not to index it.
Is IndexNow necessary, or is Search Console enough?
Search Console submission is the essential step for any site. IndexNow is a useful add-on if you're regularly publishing multiple location or service pages and want faster discovery beyond Google's normal crawl schedule, not a replacement for the core checklist.
Why do some of my location pages get indexed and others don't?
This is almost always a content-quality issue. Pages that are genuinely unique tend to get indexed and stay indexed; pages that are templated with only the city name changed are exactly what Google's quality systems are tuned to filter out.