Technical SEO Audit: 7 HVAC Crawl Tools Rank 2026

A technical SEO audit for HVAC, plumbing, and trades is a crawl that finds broken service URLs, noindex tags, redirect chains, duplicate city templates, and sitemap gaps before you spend on more copy. It is not a Content Score, it is not a GBP cleanup, and it is not a promise that requesting indexing will work this week. US Tech Automations sits above the crawler as the ticket that will not close until inspectionResult.indexStatusResult.verdict is PASS or a human accepts the exception.

TL;DR: Start with Screaming Frog if the site is small enough to crawl on a laptop and you want a public licence price. Move to Sitebulb if the owner wants illustrated issue graphs. Use Lumar, OnCrawl, or Botify when log files and crawl budget are the actual problem. Keep Semrush or Ahrefs if that seat already runs Site Audit. Paid crawl licence: £199 per year according to Screaming Frog (2026), with a free cap of 500 URLs and 300+ issue types on the paid spider.

Crawl budget on a 40-URL HVAC site

Most licensed shops do not have an enterprise crawl-budget problem. They have a 40-URL WordPress site that 404s the old /ac-repair slug after a theme change. The audit is: crawl, export 4xx/5xx, check canonicals, confirm the XML sitemap matches live money URLs, then request a recrawl only for URLs you actually fixed.

Recrawl window: days to weeks according to Google Search Central (2025) — documentation last updated 2025-12-10 says crawling after a recrawl request can take anywhere from a few days to a few weeks, and requesting a crawl does not guarantee inclusion. That is why the ticket cannot be "submitted to URL Inspection" as a close-out.

If spend is still the open question, read whether SEO is worth it for HVAC and plumbing.

Who this is for

This page is for shop owners, web developers, and agencies who ship WordPress or franchise templates for trades and need a crawler in the release checklist.

Red flags: Skip a paid spider if you have fewer than 500 URLs and the free Screaming Frog cap covers the site. Skip Botify or Lumar if you have no log files and no JS framework. Skip every cloud crawler if the site is blocked by basic auth you cannot share.

Glossary for the HVAC crawl

• Indexability: whether Google is allowed to keep the URL (no noindex, 200, canonical to self).

• Crawl depth: clicks from the homepage to a service URL; city pages buried in a footer-only loop get missed.

• Canonical: the URL you claim is the master; two city pages canonicalizing to the homepage is a common trades failure.

• Sitemap: the XML list you submit; it must not include 404s or noindex.

• Redirect chain: /old → /tmp → /new wastes crawl and leaks equity.

• JS rendering: some themes hide phone numbers until Chromium runs; Frog can render, the free cap may not.

• Log-file crawl: what Googlebot actually fetched, which desktop crawlers only guess.

• URL Inspection verdict: Search Console's inspectionResult.indexStatusResult.verdict on one URL.

How to weight technical audit tools

Weights sum to 100%. A log-file platform can be "better" and still be the wrong buy for a brochure site.

Public dollars for the crawl stack

*Screaming Frog notes the crawl ceiling depends on allocated memory and storage.

Free crawl cap: 500 URLs according to Screaming Frog (2026). A typical HVAC brochure site fits. A 2,000-URL city-page factory does not.

BEST_OF earn rate: 15.2% according to first-party mix-config (2026) on 12,514 live pages counted 2026-08-24.

Feature matrix

Screaming Frog vs Sitebulb, then the cloud

Screaming Frog

Best fit: developers and SEOs who will crawl a trades site on Windows, macOS, or Linux and export CSVs. Limitations: the free 500-URL cap hides scheduling, JS, and API connects; paid is £199/year. Implementation: crawl the production host, filter 4xx, export inlinks to the old /ac-repair slug, fix, then inspect. Primary evidence: Screaming Frog SEO Spider.

Sitebulb

Best fit: owners who need illustrated hints, not just a spreadsheet. Limitations: contact vendor for current desktop pricing; still not a GBP tool. Implementation: same crawl targets as Frog; use the hints to brief the developer. Primary evidence: Sitebulb.

Lumar

Best fit: multi-site or JS-heavy programs that need cloud scale. Limitations: contact vendor; overkill for 40 URLs. Implementation: schedule weekly, alert on indexability drops. Primary evidence: Lumar.

OnCrawl

Best fit: teams that will load server logs and compare Googlebot to the desktop crawl. Limitations: contact vendor; logs need IT. Implementation: 30 days of logs, then prove whether city pages are fetched. Primary evidence: OnCrawl.

Botify

Best fit: enterprise crawl-budget work. Limitations: contact vendor; not a shop-owner SKU. Implementation: only if a franchise template is dropping thousands of URLs. Primary evidence: Botify.

Semrush

Best fit: shops that already buy Semrush for keywords and want Site Audit in the same login. Limitations: cloud crawl caps depend on plan (contact vendor). Implementation: schedule Site Audit weekly on the production domain. Primary evidence: Semrush.

Ahrefs

Best fit: shops already in Ahrefs. Limitations: contact vendor for plan dollars. Implementation: Site Audit + the 404 report after every theme change. Primary evidence: Ahrefs.

Worked example: 42 URLs after a theme move

A plumbing shop with 42 live URLs, 11 of them 301s from a 2024 theme migration, and 6 city pages accidentally set to noindex runs Screaming Frog paid at £199/year. The crawl finds 11 chains, 6 noindex, and 3 orphan service URLs missing from the sitemap. The developer fixes templates, then calls the Search Console URL Inspection API and reads inspectionResult.indexStatusResult.verdict on those 6 city pages over 14 days. A Zapier catch of the crawl CSV can retry on 5xx and keep a run history; the shop still owns idempotency (one ticket per path), who may edit robots.txt, and the rule that "requested indexing" is not a PASS. US Tech Automations would keep the ticket open until the verdict is PASS or a human writes the exception. Trades vertical earn rate: default 10 according to homepage mix-config (2026) — not a prediction that the 6 city pages will rank.

When the URLs are indexable, send them toward AI citations on how HVAC shops get cited in Google AI and keep jobs in HVAC software so the phone number on the page is real.

Citation Builder: $2 per citation according to BrightLocal (2026) does not fix a noindex city template. Finish the crawl before you buy listings.

A second pass after the theme hotfix should compare crawls, not start a new tool eval. Frog's paid licence includes crawl comparison; use it. If 11 chains remain, the developer is not done. If the 6 city pages still return noindex in the rendered HTML, the SEO blog post you planned to commission is wasted. Technical debt is cheaper than another content retainer when the URLs cannot enter the index.

Step-by-step crawl recipe for a trades WordPress site

1. Confirm the production host, not staging, unless you are comparing with URL mapping.

2. Crawl with the paid spider if you need JS rendering; otherwise the 500-URL free cap is enough for a brochure site.

3. Filter Internal > 4xx and 5xx. Export source inlinks. Those are the old service slugs still in the blog.

4. Filter Indexability > Non-Indexable. City pages with noindex are the usual theme-migration scar.

5. Check canonicals that point at the homepage. That pattern kills every city URL at once.

6. Crawl the XML sitemap as a source and diff against the internal URL list. Orphans are money pages with no inlinks.

7. Connect Search Console on the paid licence if you have it, then inspect the six URLs you actually fixed.

8. Save the crawl. Next week, compare. If issue counts did not drop, the developer did not ship.

Surfer Standard: $99/mo yearly according to Surfer (2026) is the wrong next purchase while 6 city pages are noindex. Finish the crawl.

Common mistakes: crawling staging and celebrating a clean report; requesting indexing on URLs that still 404; blocking /service/ in robots.txt because a plugin defaulted that way; shipping two trailing-slash variants; putting the phone number in a JS widget the free spider never rendered. Sitebulb's graphs help owners see crawl depth; Frog's CSVs help developers fix it. Use both only if someone will read both.

Recrawl reality and DIY crawls

You can schedule Frog via command line, or ping a cloud audit from Make, with retries and audit logs. A Slack ping on crawl finish is useful; auto-submitting every 404 to URL Inspection is not. Zapier, Make, and n8n support run histories, retries, error branches, and audit evidence when you configure them. The buyer still owns observability, idempotency (one ticket per path), escalation (developer owns 5xx), access controls on production credentials, retention of crawl CSVs, and maintenance when Google changes Inspection. US Tech Automations would wrap the crawl export as a ticket with a human review before anyone hits Request indexing.

When NOT to use US Tech Automations

Use free Screaming Frog alone if the site is under 500 URLs and one developer already exports 404s after every deploy. Use Semrush Site Audit alone if that seat is paid and the only job is a weekly email. Skip the ticket layer if you do not publish new URLs and the sitemap has been stable for a year.

What “done” looks like after two crawls

A technical audit is not a PDF in a Drive folder. Done means the second crawl shows fewer 4xx, fewer noindex money URLs, and a sitemap that matches the live service folder. If the second crawl is identical to the first, the developer did not ship, or you crawled staging again. Print the delta: 11 chains last week, 2 this week. That is a number an owner can buy.

Keep the crawl files. Paid Frog lets you save and compare. Cloud crawlers schedule. Either way, the ticket is the delta, not the first screenshot. If the shop also runs Semrush Site Audit, pick one crawler as source of truth so two tools do not argue about the same 301.

When the crawl is clean, stop buying crawlers. The next dollar is unique facts and GBP, not Botify. A 40-URL HVAC site that is indexable is finished with this chapter until the next theme change.

Key Takeaways

• A technical SEO audit for trades is indexability, 4xx, canonicals, and sitemaps — not a content grade.

• Screaming Frog prints £199/year paid and 500 URLs free as of 2026-09-07; that covers most brochure shops.

• Sitebulb, Lumar, OnCrawl, Botify, Semrush, and Ahrefs stay in the shortlist; cloud dollars were not fetched this wave.

• Google says recrawl after a request can take days to weeks and may never include the URL.

• "Requested indexing" is not a ticket close-out.

• Do not buy Botify to fix 11 leftover 301s.

Technical audit FAQs

What is a technical SEO audit for HVAC, plumbing, and trades?

A technical SEO audit for HVAC, plumbing, and trades is a crawl of status codes, indexability, canonicals, redirects, and sitemaps on the shop's service URLs. It is not a GBP audit and it is not a blog outline.

Is Screaming Frog or Sitebulb better for a trades shop SEO audit?

Screaming Frog is better if you want a public £199/year licence and CSV exports. Sitebulb is better if the owner needs illustrated issue hints. Both beat a cloud enterprise crawler on a 40-URL site.

How long after a fix will Google recrawl HVAC pages?

Google Search Central says a recrawl request can take a few days to a few weeks and does not guarantee inclusion. Plan the ticket around the verdict, not the request timestamp.

Can the free Screaming Frog crawl replace a paid licence?

Yes if you stay under 500 URLs and do not need JS rendering, scheduling, or API connects. No if city pages are client-rendered or you must save crawls.

Do we still need content tools after a technical audit?

Yes. A 200 OK on a thin city page still will not rank. Fix indexation first, then unique facts.

Should we buy Lumar for a single-location HVAC site?

Usually no. Lumar and Botify fit log-file and crawl-budget programs. A single shop should start with Frog or the Semrush/Ahrefs audit already in the stack.

Fix the crawl, then write. When the inspection verdict needs to live on a ticket next to the deploy, review pricing.