Commercial HVAC · Technical SEO + Schema

The Challenge

The content was genuinely good and the reputation backed it up, but the site just sat there in search. Pages were slow to get indexed, and rankings lagged competitors who had thinner material. Leadership could not work out why quality writing was not translating into visibility.

A technical audit found several barriers that affected efficient crawling, canonicalization, indexation, and page experience:

• Crawl errors were blocking pages from being read properly
• Duplicate content created competing canonical and indexation signals
• Orphaned pages had no internal links pointing to them
• Schema markup was missing, so search engines had no structured context
• Internal linking was weak and left pages isolated
• Core Web Vitals were slow and dragged mobile performance down

Let Google actually crawl the site

Important pages need to be crawlable, internally discoverable, canonicalized, and eligible for indexation before their content can compete. We cleared the technical barriers affecting those page groups.

• Fixed crawl errors: we worked through Search Console and a full crawl to resolve the errors that were stopping pages from being read, so nothing important stayed invisible.
• Rescued orphaned pages: pages with no links pointing to them were effectively hidden, so we wired them back into the internal linking so both users and Google could find them.
• Cut duplicate content: duplicates split ranking signals and confused Google about which page to show, so we consolidated them and set canonicals to point at the right one.
• Rebuilt internal linking: relevant links connected orphaned commercial pages and clarified the site hierarchy. Later ranking movement was assessed as an observed outcome, not proof from internal links alone.

Give search engines the context with schema

Structured data provided explicit, machine-readable context that matched the visible organization and service information. It supported interpretation and eligible search features without promising rankings, rich results, or AI citations.

• Organization schema: we described the company as a clear entity, with name, location, and contact details, so search engines knew exactly who they were dealing with.
• Service schema: core services were described in structured data where the page visibly supported them. Google does not document Service as a guaranteed rich-result type.
• Eligibility, not display: supported markup can enable eligible search features, but search engines decide whether and how a result appears.
• AI search context: accurate markup can support entity clarity, but Google says no special structured data is required for its generative AI features.