A complete technical SEO audit checklist for service businesses: crawlability, Core Web Vitals, mobile, HTTPS, schema, internal links and JS rendering.
A technical SEO audit checklist is the step-by-step list you work through to confirm search engines can crawl, render, index and rank every important page on your website. For a service business, that means checking your robots.txt, sitemap and canonicals, passing Core Web Vitals on mobile, serving everything over HTTPS, adding the right structured data, and making sure your internal links and JavaScript do not block Google. This guide gives you the full checklist, grouped so you can tick each item off in order.
Work through it top to bottom. Each section below is a checklist group, and every ### heading is a single item you can mark done. If you would rather have this run for you, our free website audit covers the same ground in a single report.
Crawlability and Indexing
If Google cannot crawl and index a page, nothing else on this checklist matters. Start here every time.
Check your robots.txt
Open yourdomain.com.au/robots.txt and read it line by line. Confirm you are not accidentally blocking important directories, CSS or JavaScript files. A stray Disallow: / left over from a staging build is one of the most common, and most damaging, technical SEO mistakes. Make sure the file also points to your XML sitemap.
Validate your XML sitemap
Your sitemap should list only canonical, indexable, status-200 URLs. Remove redirects, 404s, noindex pages and parameter duplicates. Submit it in Google Search Console and check the coverage report for "Discovered – currently not indexed" or "Crawled – currently not indexed" warnings, which signal crawl-budget or quality problems.
Audit canonical tags
Every page needs a self-referencing canonical tag unless it deliberately points elsewhere. Confirm canonicals are absolute URLs (with https:// and your real domain), consistent with the version in your sitemap, and not pointing to redirected or broken pages. Conflicting canonicals quietly strip pages out of the index.
Review noindex and meta robots
Search your codebase or crawl the site for noindex directives. Confirm every page carrying one is meant to be hidden (thank-you pages, internal search results, faceted filters) and that no money page, service page or suburb page has slipped a noindex in by mistake. Check both the meta robots tag and the X-Robots-Tag HTTP header.
Confirm key pages are actually indexed
Use the URL Inspection tool in Search Console on your homepage, top service pages and location pages. "URL is on Google" is the only confirmation that counts. A page that ranks nowhere is often simply not indexed.
Site Architecture and URLs
A clean, shallow structure helps both crawlers and customers find what they need. This group is about how your pages are organised and named.
Keep important pages within three clicks
Map your structure from the homepage down. Every page that should rank ought to be reachable within about three clicks of the homepage. Pages buried deeper are crawled less often and seen as less important.
Use a logical, flat URL structure
Group URLs by intent, for example /services/, /locations/ and /blog/. Avoid deep nesting like /services/category/sub/page/. A predictable hierarchy makes the whole site easier to crawl and easier to expand later.
Write clean, readable URLs
Use lowercase, hyphen-separated, descriptive slugs (/plumbing-services-brisbane, not /page?id=482). Drop stop words, session IDs and tracking parameters from canonical URLs. Keep them short and human-readable.
Fix broken links and redirect chains
Crawl the site and list every 404 and every redirect. Repair or redirect broken internal links to a relevant live page. Collapse redirect chains (A to B to C) into a single hop (A to C). Every chain wastes crawl budget and slows the page for users.
Standardise on one domain version
Pick one canonical version (https + www, or https + non-www) and 301-redirect every other variant to it. Test the http, https, www and non-www combinations to confirm they all resolve to the same single URL.
Core Web Vitals and Page Speed
Core Web Vitals are part of Google's page experience signals, and slow pages lose both rankings and customers. In 2026 the three metrics are LCP, INP and CLS, with INP having replaced FID in 2024.
Pass Largest Contentful Paint (LCP)
LCP measures how long the largest visible element (usually your hero image or headline) takes to render. Aim for 2.5 seconds or less on mobile. Improve it by compressing and correctly sizing hero images, serving modern formats like AVIF or WebP, preloading the LCP image, and removing render-blocking CSS and JavaScript.
Pass Interaction to Next Paint (INP)
INP replaced First Input Delay as a Core Web Vital. It measures how quickly your page responds to user interactions across the whole visit, not just the first one. Aim for 200 milliseconds or less. Reduce it by trimming heavy JavaScript, breaking up long tasks, and removing unnecessary third-party scripts that block the main thread.
Pass Cumulative Layout Shift (CLS)
CLS measures unexpected movement as the page loads. Aim for 0.1 or less. Prevent shifts by setting explicit width and height (or aspect-ratio) on images and embeds, reserving space for ads and banners, and avoiding content injected above existing content.
Measure with field data, not just lab data
Check the Core Web Vitals report in Search Console, which uses real Chrome user data (CrUX). Use Lighthouse and PageSpeed Insights for diagnosis, but trust field data for whether you are actually passing. Test on a mid-range mobile connection, not your office fibre.
Tighten general performance
Enable compression (Gzip or Brotli), leverage browser caching, serve assets through a CDN, lazy-load below-the-fold images, and minify CSS and JavaScript. Reducing total page weight lifts every Core Web Vitals metric at once.
Mobile Optimisation
Google indexes the mobile version of your site, and most "near me" service searches happen on phones. Audit your site as a mobile user would experience it.
Confirm the site is responsive
Your layout should adapt to every screen width without a separate mobile URL. Resize your browser and test on a real phone. Content, navigation and forms should all work without horizontal scrolling or pinch-zoom.
Check tap targets and font sizes
Buttons and links need enough size and spacing to tap accurately. Body text should be readable without zooming (roughly 16px or larger). Cramped, tiny tap targets frustrate mobile users and hurt conversions.
Verify mobile and desktop parity
Because of mobile-first indexing, your mobile version must contain the same important content, headings, links and structured data as your desktop version. Hiding content behind mobile accordions is fine; removing it entirely from the mobile DOM is not.
HTTPS and Security
Security is a ranking signal and a basic trust requirement. These checks protect both your rankings and your customers.
Serve the entire site over HTTPS
Confirm a valid, current SSL certificate covers your domain and that it has not expired. Every page, including images, scripts and stylesheets, should load over HTTPS.
Eliminate mixed content
A page served over HTTPS that loads any asset over HTTP triggers mixed-content warnings and can break the secure padlock. Crawl for http:// references in your HTML and update them to https://.
Force HTTPS with redirects
Set a 301 redirect from every HTTP URL to its HTTPS equivalent so neither users nor crawlers land on an insecure version. Consider adding an HSTS header to enforce HTTPS at the browser level.
Review basic security headers
Check for sensible security headers such as Strict-Transport-Security, X-Content-Type-Options and a content security policy. They are not direct ranking factors, but they signal a well-maintained, trustworthy site.
Structured Data and Schema Markup
Structured data helps search engines understand your content and can earn rich results that lift click-through. For service businesses it is one of the highest-value, lowest-effort wins.
Add the right schema types
At a minimum, mark up your business with LocalBusiness (or the most specific subtype, such as Plumber, Dentist or Electrician), your articles with Article, and any FAQ content with FAQPage. Use Service, BreadcrumbList and Organization where relevant. Always pick the most specific type available.
Use JSON-LD format
Google recommends JSON-LD over Microdata or RDFa. Place it in a <script type="application/ld+json"> block, ideally in the page head. Keep one consistent organisation reference across the site.
Validate every schema block
Run your markup through Google's Rich Results Test and the Schema.org validator. Fix every error and review the warnings. Make sure the structured data matches the visible content on the page, mismatches can trigger manual penalties.
Keep schema consistent with your NAP
For local schema, your name, address and phone number must match your Google Business Profile and your citations exactly. Inconsistent NAP data inside schema undermines the trust signal it is meant to provide.
Internal Linking
Internal links spread authority through your site and tell Google which pages matter. This group is easy to overlook and easy to improve.
Link from high-authority pages to priority pages
Your homepage and most-linked pages carry the most authority. Make sure they link to the service and location pages you most want to rank. Orphan pages with no internal links rarely rank.
Use descriptive anchor text
Anchor text should describe the destination, for example "emergency plumbing in Brisbane" rather than "click here". Descriptive anchors give Google context about the target page without keyword stuffing.
Build topic clusters
Link related content together: a pillar page linking out to supporting articles, and each supporting article linking back. This shows topical depth and keeps users (and crawlers) moving through related pages.
Find and fix orphan pages
Crawl your site and list pages with zero internal links pointing to them. Add contextual links from relevant pages so every important URL has at least a few internal links.
Duplicate and Thin Content
Duplicate and thin content split ranking signals and can suppress whole sections of a site. This is especially important for service businesses running many similar location pages.
Identify duplicate content
Look for the same or near-identical content on multiple URLs: print versions, parameter variations, http/https duplicates, and trailing-slash inconsistencies. Resolve each with a canonical tag or a redirect to a single preferred URL.
Audit location and service pages for uniqueness
Template-driven suburb pages with only the place name swapped in are treated as doorway pages and can be suppressed. Confirm each location page has genuinely unique, useful content about serving that area. If it does not, rewrite it or remove it.
Remove or improve thin pages
Find pages with little original value, auto-generated tag archives, near-empty service stubs, scraped content, and either expand them into something genuinely useful or noindex and consolidate them.
JavaScript Rendering
If your site relies on JavaScript to build content, you need to confirm Google can actually see it. Rendering issues silently hide content and links from search engines.
Check what Google renders
Use the URL Inspection tool's "View crawled page" and rendered HTML in Search Console to see what Googlebot actually receives. If your main content, headings or links only appear after JavaScript runs and are missing from the rendered HTML, you have a rendering problem.
Make critical content available without client-side JS
Server-side rendering (SSR) or static generation makes your most important content and links present in the initial HTML. For service businesses, your core copy, headings, structured data and internal links should not depend on client-side JavaScript to exist.
Avoid JavaScript-only links
Google follows standard <a href> links. Links built only with onclick handlers or buttons may not be crawled. Make sure every important navigational and internal link uses a real anchor with an href.
Test with JavaScript disabled
Load your key pages with JavaScript turned off in the browser. If the main content and navigation vanish, search engines may struggle with them too. This is a quick, revealing sanity check.
Frequently Asked Questions
What is a technical SEO audit?
A technical SEO audit is a systematic review of the back-end and infrastructure factors that affect how search engines crawl, render, index and rank your site. It covers crawlability, indexing, site architecture, Core Web Vitals and speed, mobile usability, HTTPS and security, structured data, internal linking, duplicate content and JavaScript rendering, the exact groups in the checklist above.
How often should I run a technical SEO audit?
Run a full technical SEO audit at least once or twice a year, and after any major change, a redesign, a migration, a platform switch or a big content release. Beyond that, monitor Search Console weekly for new coverage errors, Core Web Vitals drops and manual actions so you catch problems between full audits.
What are the most important technical SEO factors in 2026?
The highest-impact items are making sure important pages are crawlable and indexed, passing Core Web Vitals on mobile (LCP, INP and CLS, with INP having replaced FID), serving the whole site over HTTPS, ensuring mobile-first parity, and adding valid structured data. For service businesses, clean internal linking and genuinely unique location pages also carry a lot of weight.
Conclusion
Technical SEO is not about chasing a perfect score, it is about removing the barriers that stop search engines and customers from reaching your pages. Work through this technical SEO audit checklist group by group: confirm crawlability and indexing first, then site architecture, speed and Core Web Vitals, mobile, security, structured data, internal linking, duplicate content and finally JavaScript rendering. Fix the issues you find, then re-check.
For service businesses, getting these fundamentals right is what makes your content and SEO services actually pay off, and it pairs naturally with the location-level work in our local SEO audit checklist.
If you would rather see exactly where your site stands without running every check by hand, start with a free, no-obligation review.