Skip to content

Home services SEO

Technical SEO for Home Services Sites: Weight, Sprawl and Scripts Fixed

Trades sites are rarely large, but they break in predictable ways: page builders loading megabytes before the phone number appears, galleries of uncompressed photos, quote calculators that render nothing for search engines and plugins that generate hundreds of near-identical town pages. I fix those in the order they cost you jobs.

years in SEO
6+
client websites worked on
60+
person doing the work
1

Free review

Get a free Technical SEO review

I look at your site before we talk and tell you what I would fix first.

Free and without obligation. I read every request myself.

Technical SEO for home services begins with how trades sites get built

Technical SEO for home services makes sure a contractor's site loads fast on a phone, shows search engines every service, cost and project page, and stops plugins and templates from creating pages nobody wants indexed. Most of the problems trace back to where the site came from.

Most contractor websites come from one of three places: a local web designer using a page builder, a trade-focused agency with its own templated platform, or a website bundled with a directory or lead-generation subscription. Each brings its own technical baggage. Page builders add layers of scripts and styles. Agency platforms often share templates and code across hundreds of client sites, which can mean thin, near-duplicate pages and limited control over redirects. Bundled sites are sometimes not portable at all.

The intent behind trades searches makes those problems more expensive than they would be elsewhere. A homeowner searching "emergency electrician near me" on a phone will give a page a few seconds before going back to the map pack. A homeowner researching "conservatory roof replacement cost" on a laptop will read for longer, but only if the price section is visible and the calculator works. Technical SEO for contractors is about making sure each type of visitor, and each type of crawler, can get to what they came for.

Key takeaways

  • Emergency searches happen on phones, often on weak signal, so mobile load time and a visible call button are technical priorities for any trade that does urgent work.
  • Quote calculators, booking widgets and finance tools built in client-side JavaScript or iframes often hide their content from search engines and should be backed by crawlable text.
  • Plugin-generated location pages create crawl waste and doorway-page risk; most contractor sites need fewer, stronger location URLs.
  • Project galleries are usually the heaviest part of a trades site. Proper image sizing, modern formats and lazy loading fix most of it.
  • Rebrands, domain merges and moving off an agency-hosted platform are the biggest technical risks contractors take, and they need a redirect map before anything goes live.

What's included in my technical SEO for home services

Each tab is one part of the audit and the fixes that follow it. Everything ends up in a prioritised ticket list written for your web designer or developer, so nothing depends on me having access to your hosting.

Crawl and render checks on the templates contractor sites run on

A full crawl of the site, with the raw HTML compared against the rendered page on every key template: service, cost, location, project and gallery. This is where quote calculators, review carousels and tabbed service content that only exist after JavaScript runs show up, along with sitemaps still listing plugin leftovers.

  • Raw versus rendered comparison on each template
  • Sitemap and robots rules checked against real pages
  • Content trapped behind forms, tabs or scripts listed
Talk to me about crawl and render

Mobile speed fixes for trades pages that take emergency calls

I review Core Web Vitals from field data rather than a lab test on a fast connection, and name the element behind each problem: the slider driving a slow paint, the chat widget blocking taps, the late call bar shifting the layout. Fixes are ordered by which pages take the most calls.

  • Field data per template from Search Console
  • The specific element causing each slow or shifting page
  • Click-to-call placed in the HTML, not injected late
Talk to me about mobile speed

Image weight fixes for roofing, landscaping and renovation galleries

Project galleries are usually the heaviest part of a trades site, often full of photos straight off a phone at several megabytes each. The report lists every oversized image with a resizing and format action, and sets lazy loading for anything below the first screen.

  • Oversized images listed with target dimensions
  • Modern formats and lazy loading below the fold
  • Originals kept off public pages
Talk to me about images and galleries

Index coverage review for service, project and town URLs

Search Console shows which pages Google has chosen to crawl but not index. On contractor sites the list usually holds template town pages, tag archives, image attachment pages and expired promotions, sometimes alongside a service page that should be ranking. I sort what needs fixing from what should be removed.

  • Excluded pages grouped by reason
  • Valuable pages that are being skipped, with the cause
  • Staging copies and old domains found and closed off
Talk to me about index coverage

Consolidating plugin-built town pages for a service-area business

Where a plugin or agency template has generated a page for every town, often multiplied by every service, I produce a consolidation plan: which locations have real work and local content to justify a page, which merge into a stronger one, and a redirect map so nothing that earns visits is lost.

  • Keep, merge or remove decision per location URL
  • Redirect map to the strongest relevant page
  • Removed URLs taken out of sitemaps and internal links
Talk to me about location consolidation

Schema and business details kept consistent for plumbers, electricians and builders

I check the business subtype, Service and BreadcrumbList markup, and that the name, phone number and service area match across the site, the schema and the Business Profile. Call tracking is reviewed at the same time, because number swaps done badly are the usual source of mismatched details.

  • Correct subtype such as Plumber, Electrician or RoofingContractor
  • One main number in source, schema and footer
  • Dynamic number insertion limited to what visitors see
Talk to me about schema and nap

Migration safeguards for contractor rebrands, redesigns and platform exits

Rebrands after a merger, leaving an agency platform you cannot export from, redesigns that quietly drop location or cost pages, and builder or protocol changes are where trades businesses lose rankings built over years. Each needs a page list, a redirect map and a staging crawl before launch. Larger moves are covered under SEO migration services.

  • Domain and content ownership confirmed before you give notice
  • Old and new page lists compared before launch
  • Profile, directories and schema updated together
Talk to me about migrations

Experience

Technical SEO from someone who has done it many times

You work with me from the first call to the last report. No account managers, no hand-offs to a junior team.

Book a free call
years in SEO
6+
client websites worked on
60+
documented case studies
35

Technical problems I find on contractor sites

The recurring issues, roughly in the order I check them. Impact is relative to a typical trades site, and every audit re-ranks them against your own data.

IssueSymptomFixImpact
Page-builder bloatSlow mobile loads, phone number appears late, poor Core Web VitalsStrip unused widgets and plugins, remove sliders and background video, load only what each page uses, or rebuild key templates leanHigh for emergency trades
Uncompressed project galleriesGallery and project pages take seconds to load; huge image requestsResize to display size, serve modern formats, lazy-load below the fold, keep originals off the pageHigh
Quote or price calculator in client-side JavaScriptCost page looks empty or thin in rendered HTML; price content never ranksPut the ranges and pricing factors in server-rendered text; let the calculator add to itHigh for cost queries
Booking, finance or review widget in an iframeContent counted as someone else's page; layout shift as it loadsKeep key information in the page itself; reserve space for the widget; load after main contentMedium
Plugin-generated location pagesHundreds of near-identical town URLs, many crawled but not indexedConsolidate to genuine locations, redirect the rest, remove from sitemapsHigh
Multiple domains or town micrositesSplit authority, duplicate content, confused brand signalsMerge onto one domain with page-level redirectsMedium to high
Tracking-number swaps breaking NAPDifferent phone numbers in HTML, schema and Business ProfileUse dynamic number insertion on display only; keep the main number in schema and footer sourceMedium
Orphaned project and blog pagesPages exist but are not linked from services or locationsLink projects to services and locations; add to sitemap; prune what has no valueMedium
Staging or old sites still indexedDuplicate copies of the site in search resultsPassword-protect or noindex staging; redirect old domainsMedium

Crawl, render, index, understand - applied to a trades site

I work through the same four questions on every audit, in order, because a problem early in the chain makes later fixes pointless.

  1. 1

    Can it be crawled?

    Robots rules, sitemaps that list real pages and not plugin leftovers, internal links that reach every service and project page, and no important content trapped behind forms, filters or search boxes.

  2. 2

    Can it be rendered?

    I compare the raw HTML with the rendered page. Quote tools, review carousels, gallery pages and service tabs built in JavaScript often show far less to a crawler than to a homeowner.

  3. 3

    Is it indexed - and should it be?

    Search Console's indexing reports show which service, location and project pages Google has chosen to skip. Template town pages, tag archives, thin gallery attachments and old promotion pages are common entries.

  4. 4

    Is it understood?

    Clear titles and headings per service, the right schema subtype such as Plumber, RoofingContractor or HVACBusiness, a consistent business name, phone and service area, and internal links that tell search engines which page owns which job.

Free review

Get a free Technical SEO review

Send me your site. Before the call I look at your rankings and pages, then tell you what I would fix first and what it is likely worth.

Book the review

Core Web Vitals when the visitor is standing in a flooded kitchen

Core Web Vitals are not a ranking cheat code, but on trades sites they track something that really matters: how fast a stressed person on a phone can see what you do and tap to call. Largest Contentful Paint on most contractor sites is a hero image or slider that weighs more than the rest of the page together. Interaction to Next Paint suffers from chat widgets, review carousels and tracking scripts competing for the main thread. Cumulative Layout Shift comes from cookie banners, late-loading call bars and embedded widgets pushing the content around just as someone tries to tap the phone number.

The fixes are usually unglamorous. Replace the slider with one compressed image or none. Load chat and review widgets after the main content, or only on pages where they earn their place. Reserve space for anything that loads late. Put the click-to-call button in the HTML rather than injecting it with a script. Check the result in the field data in Search Console, not just a lab test on a fast office connection.

Where SEO meets CRO

Speed and call tracking are both conversion problems

Every technical fix on a trades site should be checked against what the visitor does next. A faster page that hides the phone number has not helped. Call-tracking scripts that swap numbers late can cause layout shift and NAP inconsistency if set up badly, but without them nobody knows which pages produce jobs. I set them up so tracking, speed and consistency work together. Speed and measurement get checked together, on the same pages, in the same audit.

Site architecture and location page sprawl

A contractor site's architecture should mirror how the business sells: services at the top level, cost guides and sub-services under them, a locations section for genuine service areas, and a projects section that links across both. Flat, shallow and obvious beats clever.

The most common structural mistake is location sprawl. A plugin or an agency template generates a page for every town within a radius, sometimes multiplied by every service - "boiler repair in X", "boiler installation in X", "plumber in X". The result is hundreds of URLs with the same copy, crawled and mostly ignored, and at real risk under Google's doorway-page rules. Pruning those down to the areas where you have real work and real local content, with redirects to the strongest page, usually improves how the remaining pages perform. The thinking behind which locations deserve pages is in local SEO for home services.

The other structural issue is microsites: a separate domain for each trade or each town, often bought because an exact-match domain seemed like a shortcut. They split links and reviews, confuse brand searches and multiply maintenance. Merging them onto one domain is usually the right call, done carefully.

Where technical SEO connects to the rest

Technical fixes make the rest of the work count. The page set they protect comes from keyword research for contractors and the templates in on-page SEO for trades. Cost pages and project galleries that render properly are what content strategy for home services depends on. For the wider plan, see home services SEO.

FAQs

Technical SEO for Home Services FAQs

Does technical SEO for home services mean rebuilding my website?

Often not. Many page-builder sites can be made much faster by removing unused plugins, sliders and widgets and compressing images. A rebuild makes sense when the platform cannot be fixed, when you do not own it, or when the templates are so heavy that patching costs more than replacing. I make that call after the audit, not before.

Will call tracking hurt our local SEO?

Not if it is set up properly. Use dynamic number insertion so tracking numbers appear only to visitors, keep your main number in the page source, schema and footer, and in Google Business Profile use the tracking number as primary with your main number listed as an additional phone. The risk comes from inconsistent numbers scattered across directories.

Should we delete our town pages?

Not all of them blindly. Keep and improve pages for areas where you do real work and can add local projects and detail. Merge or redirect the rest to the strongest relevant page. Removing near-duplicate pages usually helps the remaining location and service pages.

Are online quote calculators bad for SEO?

No, they are often very good for conversion. The problem is when the calculator is the only content on the page and it renders in JavaScript or an iframe. Put the price ranges and factors in normal text on the page, then add the calculator as an interactive tool on top.

How heavy should a project gallery be?

As light as possible while still looking good on a phone. Serve images at the size they display, use modern formats, lazy-load images below the first screen and avoid loading full-resolution originals. A gallery page should not take longer to load than any other page on the site.

We have separate websites for each trade. Should we merge them?

Usually yes, unless the businesses are genuinely separate with different brands and customers. One domain concentrates links, reviews and brand signals. The merge needs a URL-by-URL redirect map, updated Business Profiles and directory listings, and monitoring for several weeks afterwards.

See what technical SEO for home services would fix on your site

Send me your website address. On a free 30-minute call I will show you what loads before your phone number on a mobile, which pages Google is ignoring and what I would fix first.