Skip to main content

ElectrifyAtlas

Heat-pump rebate explorer; organic-first content play with AEO discipline.

Experiments·Alpha·Rev. 2026·Next.js · SST

What is ElectrifyAtlas?

ElectrifyAtlas is a heat pump rebate explorer built on the same iSM site stack as the client network: Next.js with SST v3, AEO-optimized content, and the full schema and atomic answer treatment. It is a bet that the heat pump adoption curve will produce years of high-intent organic search volume across state-specific rebate queries that are underserved by generic energy efficiency content.

Abstract

ElectrifyAtlas is a heat pump rebate explorer built on the same iSM site stack as the client network: Next.js + SST v3, AEO-optimized content, and the full schema + atomic answer treatment. It is a bet that the heat pump adoption curve will produce years of high-intent organic search volume across state-specific rebate queries.

Problem

Federal and state heat pump incentives are genuinely complex: HEEHRA income limits, 25C vs HEEHRA stacking, rebate timing by state, mini-split sizing for cold climates, and contractor eligibility requirements all produce distinct high-intent queries that are underserved by generic energy efficiency content.

A thin-shell launch with placeholder content fails at this type of organic play. Paid search can't compensate for shallow content at low budgets; the organic compound only starts when there's a real content floor in place.

Approach

Content floor

The launch posture is organic-must-carry from day one. Content floor: 8+ long-form posts at ≥1,500 words each, covering high-intent buyer queries rather than generic category content.

State pages carry per-state FAQs, priority-state narrative, and page-specific metadata — not a template with the state name swapped in.

AEO requirements

Every page hits AEO 100: H1, SEO title, meta description, AtomicAnswer component as an h2, FAQAccordion (3–7 questions), FAQ schema (JSON-LD), Breadcrumb schema, and page-specific schema (Article, HowTo, Service as appropriate). The pipeline integration feeds 2–3 new posts per week post-launch to sustain the long-tail compound.

Status

  • In development. Launch posture locked: organic-first, no "add content later" concession.
  • Content strategy defined around high-intent buyer queries (HEEHRA income limits, rebate stacking order, cold-climate sizing, state-level incentive guides).
  • Site infrastructure follows the standard iSM SST v3 + GitHub Actions + CloudFront pattern.

Frequently asked

Apex Architecture

Every site we build runs on Apex — sub-500ms, AI-native, zero maintenance.

Explore Apex Architecture

Stay Ahead of the Curve

AI strategies, case studies & industry insights — delivered monthly.

K