Technical SEO for a home service site means five things are true: Google can crawl every page you want indexed, each page has one clear canonical version instead of competing with a near-duplicate, the mobile version of the page (the one Google actually indexes first) matches the desktop version, redirects from any past site rebuild still resolve, and your service-area or city pages add real, specific detail instead of the same template with a name swapped in. None of this replaces good content or a strong Business Profile. It's what decides whether the content and profile work you've already done ever reaches the index in the first place.
By the numbers
- Google indexes the mobile version of your site first. Since mobile-first indexing rolled out to the whole web, Google predominantly uses the mobile version of a page's content for indexing and ranking, crawled with a smartphone user agent, not a desktop one. GOOGLE DOCUMENTED
- Without an explicit canonical signal, Google guesses for you. Google's own guidance on duplicate URLs says that if you don't tell Google which URL is canonical, "Google will make the choice for you, or might consider them both of equal weight," which can split ranking signal across near-duplicate pages instead of consolidating it on one. GOOGLE DOCUMENTED
- Pages built mainly to rank, not to help a reader, are a named policy violation. Google's scaled content abuse policy applies to "many pages... generated for the primary purpose of manipulating Search rankings and not helping users," regardless of whether a human, automation, or both produced them. A template with the city name swapped and nothing else changed is the exact shape this policy describes. GOOGLE DOCUMENTED
- Crawl budget usually isn't a small-site problem, with one exception worth checking. Google's guidance is that crawl budget "is not something most publishers have to worry about" under a few thousand URLs, but its large-site crawl budget guide also applies when a large share of a site's URLs sit in Search Console's "Discovered - currently not indexed" state. GOOGLE DOCUMENTED
- HTTPS has been a baseline expectation since 2018, not just a minor ranking nudge. Google called HTTPS "a very lightweight" ranking signal when it first counted in 2014. Since Chrome 68 in July 2018, Chrome marks any page loaded over plain HTTP as "Not secure," directly in front of the visitor, before Google ever ranks it. GOOGLE DOCUMENTED
Where a home service site's technical SEO actually breaks
Most of these sites carry more pages than a typical small business site: one per service, one per city, sometimes one per service-per-city. That volume is exactly where each of these five issues does the most damage.
| Technical issue | Why it costs you | The real fix |
|---|---|---|
| Templated city pages, name swapped, nothing else changed | Reads as scaled content abuse: many pages built to rank, not to help a specific reader | Real, unique detail per page: named neighbourhoods, actual service specifics, not a mail-merge |
| Missing or wrong redirects after a site rebuild | An old, already-ranked URL 404s, and its ranking history doesn't transfer to the new page | Map every old URL to its new home before launch, and check none redirect through more than one hop |
| No canonical tag on near-duplicate pages | Google may split ranking signal across duplicates instead of consolidating it on one | A self-referencing canonical on every real page, and a canonical pointing true duplicates at the one you want ranked |
| Mobile content that doesn't match desktop | Google indexes the mobile version; content missing there is content Google may never see | Confirm the same headings, text, and internal links exist on both versions before assuming parity |
| A sitemap that's stale or missing after a platform change | Real pages sit undiscovered, or discovered and never crawled | Keep the XML sitemap current, resubmit it, and link to the page internally, not just from the sitemap |
The order to actually work through this in
- Check Search Console's Page Indexing report first. It names the exact reason a page is excluded. Guessing which of the five issues above applies wastes the one report built to just tell you.
- Fix redirects and canonicals before touching content. A page Google can't correctly resolve to one URL won't rank regardless of how good the copy on it is.
- Differentiate templated pages before publishing more of them. Adding a sixth near-identical city page to five that already exist adds more of the same problem, not more coverage.
- Confirm mobile parity by hand. Load the mobile version yourself and check the same content, headings, and links are actually there, not just that the layout looks fine on a phone.
- Resubmit the sitemap, then wait. Recrawling and reindexing takes real time, often weeks, not a same-day fix once the underlying issue is corrected.
Three assumptions worth checking, not trusting
That's a claim, not a checked fact. Search Console's Page Indexing report shows exactly which pages Google indexed and why the rest were excluded, for free, in a few minutes. A site can look polished and still be mishandling canonicals or redirects underneath.
Only if each one earns its place. Google's own scaled content abuse policy names pages "generated for the primary purpose of manipulating Search rankings" as the problem, not the count. Forty pages that each name real neighbourhoods and real job detail are coverage. Forty with a swapped city name over the same paragraph are the risk the policy describes.
Mobile-first indexing means Google crawls and indexes what its own smartphone crawler can see, not what looks right to a human eye on a phone screen. A menu, a block of text, or a set of internal links hidden behind a script that only loads on interaction can look complete visually and still be invisible to the crawler.
Questions we get
Frequently asked questions
What does "technical SEO" actually mean, in plain terms?
Whether Google can crawl your pages, pick one clear version of each as canonical, and index the same content a visitor sees, especially on mobile. It's separate from the content itself. A page can be well written and still fail to rank if the technical layer underneath it is broken.
Does having more city or service pages always help my ranking?
No. Google's own scaled content abuse policy targets pages built mainly to rank rather than to help a specific reader, which is exactly what a template with only the city name changed looks like. More pages only help when each one adds real, specific detail.
What is mobile-first indexing?
Google predominantly uses the mobile version of a page, crawled by a smartphone user agent, to index and rank it. If your mobile site is missing content, links, or headings that exist on desktop, that missing content is effectively invisible to Google, not just to mobile visitors.
Do I actually need HTTPS for SEO reasons?
Google's own 2014 announcement called HTTPS a lightweight ranking signal on its own. The stronger reason now is that Chrome has marked plain HTTP pages "Not secure" directly to visitors since 2018, which affects whether someone trusts and stays on the page long before any ranking factor does.
How do I know if Google is actually indexing my pages?
Search Console's Page Indexing report is the direct answer: it lists indexed pages and names the specific reason for every excluded one. Checking that report is faster and more reliable than judging by how the site looks or loads for you.
What is a canonical tag, and do I need one?
It's the signal that tells Google which URL is the "real" version when duplicate or near-duplicate pages exist. Without it, Google decides on its own, which can split ranking signal across pages instead of putting it all behind the one you want to rank.
Sources
- Google Search Central, Mobile-first indexing best practices: Google predominantly using the mobile version of a page's content for indexing and ranking.
- Google Search Central, Consolidate duplicate URLs: what happens when a canonical URL isn't explicitly specified.
- Google Search Central, Spam policies for Google web search: the scaled content abuse policy definition.
- Google Search Central, Large site owner's guide to managing crawl budget: which sites this guidance actually applies to, including the "Discovered - currently not indexed" condition.
- Google Search Central Blog, HTTPS as a ranking signal (2014).
- Google Chrome Blog, A milestone for Chrome security: marking HTTP as "not secure" (2018).
The 2014 HTTPS ranking-signal figures are Google's own dated statement from that announcement, not a current published weighting; they're included to show the direction and history of the signal, not its current strength.