GEO for Energy and Utilities

TL;DR

Four query categories drive almost all AI traffic to utility sites: outage status, rates and bills, service requests, and energy-efficiency programs. Optimize each with a stable URL, clear answer-first copy, schema.org structured data (GovernmentService, Service, Offer), and explicit timestamps. Stay aligned with regulator-required disclosures so AI engines treat your pages as authoritative.

Why GEO Matters for Utilities

Utility customer service is uniquely AI-amenable. The questions are repetitive ("is my power out?", "why is my bill higher?", "how do I switch to budget billing?"), the answers are factual, and the source of truth is the utility's own website. AI assistants like ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews are well-suited to answer these questions on the utility's behalf — if the utility's web content is structured for retrieval.

Three forces concentrate value in this vertical:

• Regulated authority is rewarded. Utilities are typically the only entity legally allowed to publish official rate schedules, outage data, and program eligibility. AI engines preferentially cite primary sources, which means a well-structured utility page outranks third-party explainers.
• Self-service deflection compounds. Every billing or outage question answered by an AI assistant is a call avoided. Utilities that win citation share for these queries see measurable contact-center reductions.
• Time sensitivity matters. Outage and rate-change content is the rare case where freshness directly affects citation eligibility. Pages with explicit dateModified and live status indicators outrank stale alternatives.

Utilities that treat their websites as customer-service infrastructure — not just marketing brochures — capture this AI-mediated demand.

The GEO-for-Utilities Playbook

1. Outage status as a first-class citizen

The single highest-volume utility query is "is my power out?" Build a public outage page that:

• Lives at a stable URL (e.g., /outages or /storm-center).
• Loads with server-rendered HTML, not a client-side-only map widget. AI crawlers retrieve the static page, not the JavaScript-hydrated map.
• Includes a current-as-of timestamp () updated at least every 15 minutes during events.
• Provides text summaries of outage counts by region for the screen-reader and AI-crawler paths, in addition to the visual map.
• Links to a "how to report an outage" page with a phone number, SMS code, and report-online link.

Mark up the page with Service schema (or a customized GovernmentService for cooperatives and municipal utilities), and add a dateModified to the JSON-LD so retrievers see the freshness signal.

2. Rate transparency pages

Rate-related queries ("what is my rate?", "how much does electricity cost in my city?", "is my rate going up?") are extremely common and command high commercial intent. For each rate schedule and tariff:

• Publish a per-rate URL (e.g., /rates/residential-standard).
• Lead with a one-sentence summary including the rate name, who it applies to, and the current price per kWh.
• Include a clean table with effective date, summer/winter or time-of-use bands, and per-component charges.
• Link to the full PDF tariff for regulator-aligned authority, but never make the PDF the only source.
• Use Offer and PriceSpecification schema where appropriate to make pricing structured.

This structure is also the foundation of AEO for pricing queries.

3. Bill explainer and FAQ pages

"How do I read my bill?" is a perennial AI-assistant question. A canonical bill explainer page should:

• Walk through each line item (service charge, energy charge, distribution, taxes) in clearly labelled H3 sub-sections.
• Use an FAQ structure for each question users actually ask: "Why is my bill higher?", "How is my meter read?", "What is the budget billing program?".
• Include FAQPage JSON-LD covering each question.
• Cross-link to rate schedules, payment-assistance programs, and energy-efficiency rebates.

4. Service-request and program pages

For every customer-initiated process (start service, stop service, transfer, payment plan, low-income assistance), create a dedicated page:

• Title as the canonical question ("How do I start electric service?").
• Step-by-step list with prerequisites, expected timing, and the exact URL or phone number to act on.
• Eligibility criteria as bullet points, not buried in prose.
• Service or GovernmentService schema with provider, audience, and availableChannel.

5. Regulated-content workflow

Utilities operate under state PUC, FERC, or municipal regulator oversight. Every customer-facing rate, tariff, or program disclosure typically requires regulator approval. GEO content must respect that:

• Treat the regulator-approved disclosure as the source of truth. Web copy paraphrases for clarity but never contradicts the filing.
• Add a footer note linking to the regulator filing reference number and effective date.
• Maintain a versioning history so AI engines can see which pages were updated when (this also satisfies regulator audit trails).
• Coordinate marketing and regulatory affairs review on every customer-facing page change.

This discipline doubles as a citation-quality signal: pages with explicit regulatory references and version history are interpreted as authoritative.

6. Energy-efficiency and rebate content

"What rebates are available for a heat pump in [state]?" is a top AI-assistant query in 2026, especially in markets with utility-administered Inflation Reduction Act programs. For each rebate or incentive:

• Stable URL per program (e.g., /rebates/heat-pump).
• Lead with eligibility, rebate amount, and deadline in the first three sentences.
• Link to the application form and any required pre-qualification.
• Use Offer schema with validFrom, validThrough, and eligibleRegion.

7. Authoritative external citations

AI engines weight third-party authority. Utilities benefit from being cited or referenced by:

• The U.S. Energy Information Administration (EIA), state energy offices, and regulators.
• Local journalism on rates, outages, and customer programs.
• Industry associations (Edison Electric Institute, American Public Power Association, NRECA).

Publishing transparent, citable data — reliability statistics, customer satisfaction surveys, environmental metrics — in a structured, linkable format earns these mentions over time.

Common Mistakes

• Outage map as the only outage surface. A JS-hydrated map alone is invisible to most AI crawlers. Always pair with a server-rendered text summary.
• PDF-only rate disclosures. PDFs are heavy and rarely cited by AI engines. Mirror the rate as HTML with structured data; keep the PDF for the regulator.
• Marketing copy that contradicts the filed tariff. Creates ambiguity for AI engines and regulator risk for the utility.
• No timestamp on time-sensitive pages. Outage and rate pages without dateModified are treated as stale.
• Burying eligibility behind a calculator. AI engines cannot run the calculator. State eligibility in plain text first, calculator as a supplement.
• Brand-only optimization. Branded queries are easy. The high-leverage opportunity is non-branded category queries ("natural gas rate Atlanta", "power outage Phoenix").

FAQ

Q: Do AI assistants actually answer outage questions from utility sites?

Yes. ChatGPT, Perplexity, AI Overviews, and Gemini frequently surface utility outage status when users ask, provided the outage page is server-rendered with a clear text summary and timestamp. JS-only outage maps are typically skipped.

Q: Should we publish a public API for outage and rate data?

It helps. Structured JSON endpoints with permissive CORS and Cache-Control headers are sometimes consumed directly by AI clients and by third-party aggregators that AI engines cite. Treat the API as a citation surface, not just an integration channel.

Q: How do we handle regulated language without making pages unreadable?

Use a two-layer pattern: a plain-English summary at the top of each page, then the regulator-aligned exact language below. Add a footer reference linking to the filed tariff. AI engines extract the summary; regulators see the precise language preserved.

Q: Does GEO conflict with privacy and security obligations?

No. GEO improves the discoverability of public, customer-facing content only. Internal customer data, account specifics, and sensitive operational details should remain behind authentication. Public marketing of programs and rates is the GEO surface.

Q: What metrics indicate GEO is working for a utility?

Reduced contact-center volume on routine queries (outage, billing, rates), measured citation share across AI assistants on a fixed 30-query set, and increased web traffic from AI referrers landing on outage and rate pages.

Q: Should a co-op or municipal utility approach GEO differently than an investor-owned utility?

The technical playbook is identical. Cooperatives and municipal utilities benefit additionally from GovernmentService schema in some cases and from local-search structured data tied to service territory boundaries.