Why your service pages aren't indexing, and how to fix it
Most service pages that stay out of Google aren't broken. Google has looked at them and decided they aren't worth a place yet. The fix is usually the page, not the index button.
What "not indexed" actually means
A page that isn't indexed has either not been crawled yet, or been crawled and left out on purpose. Search Console tells you which, and the fix is different for each.
A new page for plumbing in Casper that never shows up is rarely a bug. More often, the site is sending mixed signals about whether that page matters.
Start with the exact status
Paste the page's address into the URL Inspection tool in Search Console. It shows whether Google can index the page, which canonical it picked, and the page's current status.
Write that status down word for word. Each one points to a different problem, and Google's Page indexing help explains every one of them.
| Status | What it means | What to do next |
|---|---|---|
| Discovered, currently not indexed | Google found the URL but hasn't crawled it. Google says it often reschedules to avoid overloading the site. | Link to it from strong pages, keep it in the sitemap, check the site is fast. |
| Crawled, currently not indexed | Google read the page and left it out for now. Google says there's no need to resubmit. | Make the page more useful and less like your other pages, then link to it. |
| Duplicate, Google chose different canonical | Google picked another URL as the main version. | Fix canonicals and redirects so only one version exists. |
| Excluded by noindex | The page itself tells Google to stay out. | Remove the noindex from the page, plugin or server header. |
Send us one URL. We'll read it in Search Console and tell you which of these it is.
The usual causes on service sites
On the small local sites we work on, the same seven causes come up again and again. Most stuck pages have more than one.
- Near-duplicate pages. The same layout and paragraphs, with the service or town swapped.
- Weak internal links. The page exists, but nothing important points to it.
- Canonical conflicts. Google treats a different URL as the real one.
- An accidental noindex. Set by a plugin, a theme option or a server header.
- A robots.txt block on the folder the page sits in.
- Index bloat. Hundreds of thin tag, search or filter pages competing for attention.
- Thin local detail. The town name is the only local thing on the page.
How to fix it, in order
Clear the quiet blockers
Check the page isn't set to noindex and that robots.txt doesn't block it. The URL should resolve in one step, with no redirect chain, and its canonical should point to itself.
One trap catches a lot of sites. If robots.txt blocks a page, Google never sees its noindex rule, so the page can still appear in results.
Make the page worth indexing
Google doesn't need another copy of a page it already has. Give this one what only you can: what you do and don't do, the areas you really cover, real photos, and answers to the questions customers ask on the phone.
If two pages say the same thing, merge them into one stronger page and redirect the other.
Link to it from pages that matter
On a small site, internal links carry more weight than almost anything else. Link to the page from your homepage or a services hub, and from related pages, inside sentences with clear anchor text. A footer link alone says very little.
Trim the clutter
When most of a site's URLs are thin, Google spends its time on them. Noindex or remove tag archives, internal search results and old duplicates, and keep the XML sitemap to pages you actually want in Google.
Then request indexing, once
When the changes are live, use Request Indexing in URL Inspection. Asking again doesn't help: Google says repeat requests won't get a URL crawled any faster, and crawling can take a few days to a few weeks.
Are town pages risky?
They can be. Google treats pages made only to catch a place name as doorway pages, and those rarely get indexed for long.
A town page is fine when it has something real for that town: the work you do there, how people there search, and a reason to exist beyond the name.
Indexing questions
The ones owners ask us most.
How long does indexing take after publishing a service page?
Google says crawling can take a few days to a few weeks. A unique page with strong internal links usually goes in sooner. A thin or isolated page can sit outside the index indefinitely.
Should I press Request Indexing more than once?
No. Google says repeat requests for the same URL won't speed anything up. Request once after a real change, then work on the page and its internal links.
Can robots.txt cause indexing problems even when the page is live?
Yes. If Google can't crawl the page, it can't judge it, and it can't see a noindex rule on it either. That mix of signals is a common reason pages behave strangely.
What's the fastest win when several service pages aren't indexed?
Build one strong services hub, link from it to each service page with descriptive anchor text, make each page clearly different, and noindex or remove the thin pages around them.
Get your pages into Google
If a page still won't index after these fixes, the cause is usually site-wide: speed, crawl time wasted on thin URLs, or how the site is built. That's what our technical SEO service sorts out.
Nobody can guarantee indexing. Google decides what goes in, and these steps give it every reason to say yes.
Read next
Send us the pages that won't index. We'll tell you what Search Console says and what to fix first.