The whole-home HVAC contractor with 30 years in business, 800-plus five-star Google reviews, and a Trane Comfort Specialist designation runs into the same wall every time. The site is on Scorpion. Or Surefire Local. Or Hibu. Or Astound. Or it’s on something the marketing manager calls “our Yodle site” because Yodle was the brand five rebrands ago. Underneath, in most cases, is WordPress. On top is a home-services niche template that does not let the contractor edit JSON-LD, canonical tags, or robots.txt. The 87% of HVAC and plumbing contractors that the Plumbing & Mechanical / Metricus joint study found invisible to AI in May 2026 are not invisible because they don’t have content. They are invisible because the wrapper above their content gates the layer AI engines actually read.
What home-services platforms ship for HVAC contractors in 2026
HVAC contractor sites in 2026 cluster on home-services niche platforms — Scorpion, Surefire Local, Hibu, Astound — and on legacy Yodle-style templates that have been re-skinned through three or four owners. Research/03 confirms the category: WordPress plus niche themes underneath, with high GEO-blocker incidence likely because the wrappers ship AI-blocking JavaScript that pre-dates AI bots becoming material. The pattern matches the dental ProSites/Sesame trap and the CPA template lock-in exactly.
The category-level diagnosis is in research/03’s CMS distribution note: no 2026 HVAC-vertical CMS breakdown has surfaced, but the industry pattern is clear — WordPress with niche themes (Astound, Scorpion, Hibu), some Wix/Squarespace, many on legacy Yodle-style template platforms with AI-blocking JS. The same research file flags it as a wedge opportunity. The 87% invisibility number sits next to that pattern and is not a coincidence.
Each of the four named home-services platforms sells a slightly different deck. Scorpion positions on lead-volume guarantees and a managed-service bundle that includes the website, the paid search, and the call-tracking. Surefire Local sells a marketing-platform layer that wraps the website, the local listings, and the review feed. Hibu’s pitch is end-to-end small-business marketing with the contractor site as a deliverable. Astound is a long-tenured home-services agency with template sites bundled into the service contract. The four sell different stories. The closed-CMS pattern they share at the back end is what lands the contractor at zero AI citation share.
The Yodle legacy: AI-blocking JS that wasn’t there in 2023
Yodle was acquired by Web.com in 2016 and has been re-bundled, re-rebranded, and re-sold through three corporate owners since. The sites Yodle built circa 2014 to 2018 are still live across the HVAC vertical in 2026 — re-skinned, re-themed, but running the same template chassis. The chassis was designed for a pre-AI-bot internet, where Googlebot rendered JavaScript and that was the only crawler that mattered.
The AI crawler reality, documented in research/01 Stream 6, is structurally different. GPTBot, ClaudeBot, and PerplexityBot do not execute JavaScript. They fetch raw HTML and move on. The legacy Yodle-style template, with its tracking JS, its lead-capture overlay, its click-to-call float, and its content-loading-after-DOMContentLoaded pattern, was built around a model where the browser would run all of that and the search crawler would render it. AI bots don’t render. They see the initial HTML response and decide on the citation candidate from there.
That is what “AI-blocking JS” means in the research/03 context. It is not malicious. It is not configured. It is the side effect of a template chassis built before the failure mode existed. The contractor on a re-skinned 2017 Yodle template, paying a monthly fee to a successor owner, ships HTML where the headline, the service list, the location pages, and the schema layer all arrive after JavaScript runs. The AI bot sees an empty shell.
Why does legacy template JS block AI citation specifically
AI crawlers including GPTBot, ClaudeBot, and PerplexityBot do not execute JavaScript — research/01 confirms this is structural and unlikely to change. Templates built before AI bots became material, including the Yodle-era chassis still re-skinned across HVAC sites in 2026, render their schema, content blocks, and entity layer client-side. AI bots fetch the raw HTML, see an empty shell, and move on. Googlebot still renders fine. The AI engines driving the new traffic share do not.
The same client-side-render failure mode is what the 12-platform 2026 leaderboard documents on Wix Studio, where JSON-LD is injected on the client and 200 to 400 kilobytes of platform JavaScript push mobile LCP past four seconds. The HVAC home-services-platform variant of that failure is not the same vendor — but it is the same diagnosis: the schema is technically on the page, but it is not in the response the AI bot reads.
Scorpion vs Surefire Local vs Hibu — feature lock comparison
The vendor-specific feature audit is where research stops and inference begins. Scorpion, Surefire Local, Hibu, and Astound do not publish per-tier feature matrices documenting which subscription level exposes JSON-LD editing, robots.txt access, or canonical control. That documentation is not in the public 2026 record. The category-level diagnosis is, and it is consistent across analogous niche-template providers in adjacent verticals.
Research/04 documents the closed-CMS pattern in detail on Wix, Squarespace, GoDaddy, and HubSpot. The pattern travels: schema is plugin- or platform-driven, not user-driven; locked editors do not expose the head; canonical edits land behind upgrade tiers or are absent entirely. Research/03 identifies the dental analog (ProSites, Sesame Communications, PBHS, Smile Marketing) and the CPA analog (CPASite Solutions, GetNetSet, CountingWorks PRO) as following the same pattern. The HVAC home-services platforms — Scorpion, Surefire Local, Hibu, Astound — appear in the same research/03 entry as the home-services equivalent of those niche-template categories.
The honest 2026 statement is this: the category diagnosis is well-supported by the research file. The vendor-specific tier audit — which exact Scorpion package unlocks JSON-LD, whether Surefire Local exposes robots.txt on its top tier, whether Hibu lets the contractor edit canonical URLs — is what the analogous niche-template trap on cosmetic dentistry and the analogous niche-template trap on accounting firms describe in their own verticals: an audit the contractor needs to commission, not a lookup. (Inferred from the closed-CMS pattern; vendor-specific tier feature matrices for Scorpion, Surefire Local, Hibu, and Astound are not publicly published in 2026.)
The same closed-box pattern is what the GoDaddy AI citation black box cluster maps for the most extreme version of the failure: a platform where research/04 documents you literally cannot edit your robots.txt and cannot add custom JSON-LD. The home-services niche platforms in HVAC are not GoDaddy — but they are the same closed-box pattern across home-services builders, applied to a different sales motion.
The HVAC platform-lock pattern matches dental and CPA exactly
WordPress sits underneath most home-services niche platforms in 2026, the same way it sits underneath most ProSites and CPASite installs. The wrapper is what gates the schema, canonical, robots.txt, and head-tag access. The fix path is not “upgrade your Scorpion tier.” The fix path is the wrapper off, with the WordPress install — or a static rebuild on Astro — exposing the layer the AI bot reads. The analogous niche-template trap on real estate Luxury Presence and Real Geeks covers the same diagnostic with a different sales deck above the engine.
WordPress itself is not the failure mode. Research/04 ranks WordPress with Bricks Builder plus Yoast or Rank Math at position 4 on the 12-platform 2026 leaderboard, with sub-2.0s LCP achievable, native llms.txt support since 2025/2026, FAQPage schema as a first-class feature, editable canonical per page, editable robots.txt via the Yoast/Rank Math Tools panel, and the Yoast Schema Aggregation feature shipped in March 2026 that builds a site-wide schema map AI agents can read. The same WordPress install behind a Scorpion or Hibu home-services template surfaces none of those switches in the editor the contractor ever sees.
The Trane-Comfort-Specialist site migration audit
The premium HVAC contractor with the Trane Comfort Specialist or Lennox Premier Dealer designation has the most to gain from the migration and the most to think through during it. The dealer-program designation is a credential, not a website feature, and it ports cleanly. The schema layer that tells AI engines the credential exists is what the wrapper hides.
The keep list on a Trane Comfort Specialist or Lennox Premier Dealer migration is straightforward. The credential itself — awarded by the manufacturer to the dealer, valid through whatever certification cycle is in place — survives the move untouched. The badge images and brand-use rights survive under each manufacturer’s dealer program guidelines. The link to the Trane dealer locator or the Lennox Premier Dealer directory survives as an outbound href. The customer review history, the install gallery, the financing-partner listings (Synchrony, Wells Fargo, GreenSky), and the Google Business Profile all port: research/03 names Google Business Profile as the primary citation surface for HVAC, owned by the contractor and re-verified through Google in a 10-minute task on the Google side.
The rebuild list is where the citation work happens. Organization schema with memberOf the Trane Comfort Specialist program (or Lennox Premier Dealer) plus sameAs pointing to the manufacturer’s dealer-locator URL is the entity-graph block the AI engine needs to resolve “Trane Comfort Specialist near me” or “Best Lennox Premier Dealer Phoenix” — both of which appear in the research/03 sample 2026 buyer prompts. FAQPage schema on the high-intent service pages (variable-speed AC install, heat pump retrofit, ductless mini-split, geothermal, IAQ + air purification, zoned HVAC) maps cleanly to the buyer-prompt list research/03 documents. Person schema with hasCredential for any NATE-certified or factory-trained installer the contractor wants to surface adds a layer the closed wrapper has no UI for.
The 7-14 day HVAC migration playbook
Days 1-2: content extraction including install-gallery image library, financing-partner blocks, and dealer-program badges. Days 3-5: rebuild on WordPress + Bricks + Yoast or static Astro, including Organization with memberOf the Trane Comfort Specialist or Lennox Premier Dealer program, FAQPage on every service landing page, sameAs to the manufacturer dealer-locator URL. Days 6-9: redirect map plus Google Business Profile re-verification plus Trane or Lennox dealer-locator listing update if the URL changes. Days 10-14: AI-engine resolution check on the metro-level buyer prompts.
The 7-14 day window is consistent with the dental ProSites/Sesame migration the analogous niche-template trap cluster describes and with the Wix migrations the Pillar-1 hub maps. The HVAC-specific work concentrates in days 3-5, where the dealer-program entity graph gets built page-by-page. A whole-home contractor with the Trane Comfort Specialist designation, ten core service categories, and a multi-location service area needs roughly a dozen FAQPage blocks and three to five entity blocks at minimum.
The vertical playbook the platform-wedge serves — the premium HVAC citations cluster — covers what the schema layer points at after migration: the metro-level citation graph for $20K-plus install tickets, the Trane Comfort Specialist and Lennox Premier Dealer directory weight, and the per-metro arbitrage that 87% invisibility creates.
When the rebuild beats the upgrade tier
The contractor on Scorpion or Hibu paying a monthly fee through a multi-year contract has one more decision to think through: whether to renegotiate the platform contract for an upgrade tier that might, possibly, expose JSON-LD editing or robots.txt access — versus migrating to a stack where those switches are first-class features.
The math leans toward the migration in 2026. The niche platforms exist because they bundle the parts a generalist agency would charge to build from scratch — the HVAC-specific landing pages, the financing-partner widgets, the metro-level service-area pages, the click-to-call infrastructure, the call-tracking integration. That bundle is real. It is also rebuildable on a clean WordPress install in days 3-5 of the migration window, and the rebuild ships with the AI-citation features the bundle does not.
The lateral cluster on the WordPress underneath, locked by the niche template ranking pattern frames the engine choice: WordPress + Bricks Builder + Yoast or Rank Math sits at rank 4 on the 2026 leaderboard. The same WordPress wrapped in a Scorpion or Hibu template is invisible to AI engines because the wrapper hides what makes the engine work. The fix is not to negotiate harder with the wrapper vendor. The fix is to leave.
The March 2026 HVAC price-fixing class action — the ACCA-tracked Bosch, Carrier, Daikin, Lennox, Rheem, Trane, AAON case — is the consumer-facing news event that pushes more HVAC buyers to AI engines for “is this contractor trustworthy” prompts in the May-June 2026 window. The contractors with the schema layer that resolves the trust question — credentials, dealer program memberships, NATE certifications, BBB listing, AACA member status — get cited. The 87% on the wrong side of the wrapper do not.
The overarching cluster context — how 8 verticals get cited in 2026 — frames why the platform-wedge approach lands harder in HVAC than in most. A $12K-to-$20K-plus install ticket on premium variable-speed whole-home systems, a 87% invisibility floor for the field, a manufacturer dealer-program credential the engines can resolve when the schema layer is in place, and a wrapper the contractor can leave in 7-14 days. The ceiling is the wrapper. The fix is the migration.
