Technical SEO for Tradies

Most tradies pour effort into Google Business Profile, reviews and writing suburb pages, then wonder why they are still not ranking. Often the problem is not the content, it is the technical foundation underneath it. Google Search Central is explicit: a page that cannot be crawled, loads slowly on mobile or is marked insecure can be deprioritised before its content is ever read.

For a residential electrician in Parramatta with 12 suburb pages, or a plumber in Brisbane targeting 20 drain-clearing keywords, one bad technical decision, such as accidentally setting the whole site to noindex after a WordPress plugin update, can wipe months of ranking progress overnight. These are fixable problems, but you have to know to look for them.

Google switched to mobile-first indexing in 2023. That means Google crawls your site as a mobile user. The desktop version is secondary. If your mobile site is missing content, shows a different menu or strips out suburb pages, Google sees a worse version of your site than a desktop visitor does.

What Mobile-First Indexing Actually Means

Your mobile site must have exactly the same content as your desktop site. A common mistake for tradies using page builders like Elementor or Divi is hiding certain sections on mobile to make the layout cleaner. If Google cannot see that content on mobile, it may as well not exist for ranking purposes.

• All text content, headings and suburb mentions must be visible on mobile, not hidden with CSS display:none
• The same internal links that appear on desktop must appear on mobile navigation
• Phone numbers and click-to-call buttons should be prominent above the fold on mobile
• Images must be the right size for small screens, not just scaled-down desktop images that bloat load times
• Tap targets (buttons and links) need to be at least 48px tall so thumbs can hit them accurately

A roofing company in Penrith recently discovered that their 'Areas We Serve' section, which listed 18 suburb pages, was hidden on mobile using their theme's responsive settings. All 18 internal links were invisible to Google. Once restored, the suburb pages began picking up impressions within six weeks.

Core Web Vitals are a set of real-user experience metrics that Google uses as a ranking signal. They were introduced as a ranking factor in 2021 and remain in place today. Search Engine Journal's ranking factors research confirms they form part of the Page Experience signal. There are three metrics tradies need to care about.

LCP: The Most Common Failure for Tradie Sites

LCP is almost always the metric tradie sites fail. The main cause is a large hero image, usually a photo of a work van or a job site, that is served at full resolution instead of a compressed, correctly sized version. A 4MB JPEG hero loaded on a 4G connection will score a 6-8 second LCP. The fix is to convert images to WebP format, compress them properly and use responsive image sizing.

CLS: The Layout Jump Problem

CLS happens when elements load in after the page structure is established and push other content out of the way. For tradie sites this commonly happens with Google reviews widgets, map embeds and banner ads that load asynchronously. The fix is to reserve space for those elements with explicit width and height attributes before they load.

1. 1

   Run PageSpeed Insights

   Go to pagespeed.web.dev and enter your homepage and one service page URL. Look at the Field Data section first (real user data), then the Lab Data. Note every metric showing amber or red.

2. 2

   Fix LCP first

   Compress your hero image to WebP, serve it at the correct width for mobile (around 800px wide), and add the 'fetchpriority=high' attribute to the hero img tag. This single fix often moves LCP from 4-6 seconds to under 2.5 seconds.

3. 3

   Address CLS sources

   Add explicit width and height attributes to every image so the browser reserves space before the image loads. Reserve space for reviews widgets and map embeds using a min-height CSS rule.

4. 4

   Reduce INP

   Remove or defer heavy JavaScript that runs on page load. Google Tag Manager with multiple tags firing on load is a common culprit. Only load what you actually need.

5. 5

   Verify in Search Console

   Open Search Console, go to Experience then Core Web Vitals. Check the mobile report. It can take 4-6 weeks for real-user data to update after a fix.

HTTPS has been a Google ranking signal since 2014. More practically, any site still running on HTTP is flagged as 'Not Secure' in Chrome's address bar. For a pest control company in Adelaide asking visitors to fill in a contact form, that warning kills conversions before SEO even gets a chance to work.

Checking Your SSL Certificate

Open your site in Chrome and click the padlock icon (or the 'i' icon) next to your URL. If it says 'Connection is secure' and shows a valid certificate, you are fine. If it says anything about the certificate being expired, mismatched or missing, you need to renew or install an SSL certificate through your hosting provider. Most hosts do this for free through Let's Encrypt.

• Check that all pages redirect from http:// to https:// automatically
• Confirm that www.yourdomain.com and yourdomain.com both resolve to the same canonical URL
• Check for mixed content warnings: HTTPS pages loading images or scripts over HTTP
• Verify the SSL certificate is not expired and covers your domain correctly

Ranking requires indexation. Indexation requires crawlability. A page that Google cannot crawl cannot be indexed. A page that is indexed but has a noindex tag set will not rank. These sound basic but they are among the most common technical issues on tradie sites, especially sites that have been through multiple rounds of DIY edits.

The robots.txt File

Your robots.txt file tells Google which parts of your site it is allowed to crawl. You can view it by typing yourdomain.com.au/robots.txt in your browser. The most dangerous line you can have is 'Disallow: /' which blocks Google from crawling everything. This happens more often than you would think, usually left over from a development period when the site was set to private.

XML Sitemaps

A sitemap is a list of your pages that you submit to Google. It does not guarantee indexation but it tells Google where your pages are and how frequently they are updated. For a landscaper in Perth with 15 suburb pages, a sitemap ensures every single one of those pages is known to Google, even if none of them have inbound links yet.

Submit your sitemap in Google Search Console under the Sitemaps section. Enter the URL (usually yourdomain.com.au/sitemap.xml or yourdomain.com.au/sitemap_index.xml) and click Submit. Check back after a few days to confirm the pages listed are being discovered.

Noindex Tags: The Silent Ranking Killer

A noindex meta tag tells Google not to include that page in search results. Every page you want to rank must not have this tag. Check for it in Search Console under URL Inspection, or search for 'meta name=robots content=noindex' in your theme or plugin settings. Yoast SEO, Rank Math and similar plugins can set this accidentally if the 'Search Engine Visibility' setting is toggled incorrectly.

Redirect Chains and Broken Links

Every time a URL permanently changes, a 301 redirect should be in place pointing the old URL to the new one. Problems occur when redirects are chained together (A redirects to B which redirects to C) or when old redirects point to pages that no longer exist, creating 404 errors. Redirect chains slow down crawling and dilute link equity. Check for them using the free Screaming Frog SEO Spider tool or by reviewing the Crawl section of Search Console.

A logical site structure helps both Google and visitors understand what your business covers and how your pages relate to each other. For most tradie businesses, a flat, simple structure works best: homepage, then service pages, then suburb pages under each service.

The Right URL Structure for Tradie Sites

URLs should be short, descriptive and use hyphens between words. Avoid dynamic parameters, session IDs and auto-generated strings. For a HVAC contractor in Sydney, a URL like sydneyaircon.com.au/services/ducted-air-conditioning/ is clean and readable. A URL like sydneyaircon.com.au/?p=847 or sydneyaircon.com.au/services/category/2/ducted is not.

Crawl Budget: Why It Matters for Larger Sites

Google allocates a crawl budget to each site, meaning it does not crawl every page on every visit. For a tradie site with 30-50 pages, this rarely causes problems. But a builder in Melbourne who has let their old CMS generate hundreds of tag pages, date archives and duplicate category pages is wasting crawl budget on pages that should never exist. Use robots.txt to block those junk pages so Google's crawlers spend time on your real service and suburb content.

Structured data is code you add to your pages that gives Google explicit information about your business, services and content. It uses a standard vocabulary from Schema.org and is written in a format called JSON-LD. For trade businesses, the right schema markup can generate rich results in search, including star ratings, business hours and FAQ dropdowns, which increase click-through rates even before you change your ranking position.

LocalBusiness Schema

LocalBusiness schema tells Google exactly what your business is: its name, address, phone number, opening hours and the area it serves. For a locksmith in Fitzroy, this schema reinforces the same NAP (name, address, phone) information in your Google Business Profile, which builds consistency signals that support map pack rankings. It belongs on your homepage and contact page.

Service Schema

Service schema describes individual services your business provides. An electrician with separate pages for switchboard upgrades, safety inspections and EV charger installation can add Service schema to each page, naming the service type, the area served and the provider. This helps Google match those pages to specific search queries more confidently.

FAQPage Schema

FAQPage schema on pages that contain genuine question-and-answer sections can generate an expanded FAQ dropdown directly in Google's search results. A plumber's blocked-drains page with a proper FAQ section and FAQPage schema can take up significantly more visual space in the SERP, pushing competitors down even without ranking higher.

Thin content is not just a writing problem. It is a technical one too. When a tradie site creates 20 suburb pages that are near-identical except for the suburb name, Google may index two or three and largely ignore the rest. This is a technical crawlability and content architecture issue as much as it is a writing problem.

Spotting Duplicate Content in Search Console

In Google Search Console, go to Pages and look for pages marked 'Duplicate without user-selected canonical' or 'Duplicate, Google chose different canonical than user'. These are pages Google thinks are too similar to other pages on your site. They will not rank well until they are differentiated or the duplication is resolved with canonical tags.

Thin Page Thresholds

There is no official minimum word count from Google, but in practice, a suburb page for a painter in Richmond with 120 words of templated copy and nothing unique about Richmond will rarely rank for 'painter Richmond Melbourne'. Each suburb page needs location-specific content: real references to local landmarks, specific services offered in that area, or genuine job examples from that suburb.

Common Technical Duplicate Content Sources

• www and non-www versions of your site both resolving with no canonical tag
• HTTP and HTTPS versions both accessible without a redirect
• URLs with and without trailing slashes serving the same content
• Printer-friendly page versions or category archive pages with duplicate post excerpts
• Suburb pages generated from a template with only the suburb name changed
• Pagination pages that repeat the same meta title as the first page

A technical audit does not require expensive software. Google gives you two free tools, Search Console and PageSpeed Insights, that together surface the majority of issues on a tradie site. The following process takes about 90 minutes and should be repeated quarterly.

1. 1

   Set up and verify Search Console

   Go to search.google.com/search-console. Add your property and verify ownership using the HTML tag method or your DNS records. If you are already set up, make sure you have both the www and non-www versions verified.

2. 2

   Check the Coverage report

   In Search Console, go to Pages (previously Coverage). Look at the Valid tab to see how many pages are indexed. Look at the Error and Excluded tabs to identify pages with problems: noindex tags, 404 errors, redirect issues and soft 404s.

3. 3

   Review Core Web Vitals

   Go to Experience then Core Web Vitals. Open the mobile report. Any URLs in amber or red need attention. Click through to the grouped issue view to see which pages are affected and what the specific problem is.

4. 4

   Run PageSpeed Insights

   Go to pagespeed.web.dev and test your homepage and your most important service page. Read the Opportunities and Diagnostics sections. These give specific, actionable fixes with an estimate of how much time each one would save.

5. 5

   Check your robots.txt and sitemap

   Visit yourdomain.com.au/robots.txt and confirm there is no Disallow: / line. Visit Search Console under Sitemaps and confirm your sitemap is submitted and the last fetch was successful with no errors.

6. 6

   Audit your top pages with URL Inspection

   In Search Console, use URL Inspection on your five most important pages: homepage, top service page, two suburb pages and your contact page. Check that each one shows as indexed, is being crawled by Googlebot-Mobile and has no manual actions against it.

7. 7

   Check schema with the Rich Results Test

   Go to search.google.com/test/rich-results and enter your homepage URL. Verify that your LocalBusiness schema is detected and has no errors. Repeat for service pages to check Service and FAQPage schema.

Most technical SEO problems on tradie sites were introduced by the site owner themselves, either through a plugin update, a theme change or a setting toggled without understanding what it did. A quarterly audit catches these before they cost you months of ranking progress.

Common finding across tradie site audits