Bottom line: Homeowners ask AI for HVAC, roofing, and plumbing the same way they once asked neighbors and Google: who does this job in my city, for this constraint, without drama. If your company only has a thin homepage, inconsistent NAP, and a booking form that is the real risk surface, you lose silent demand — people who never call because a model never named you.
For US trade operators. Checklist first; products second.
Primary path: GEO audit — $900 · Secondary: security work from $1,500 if forms/admin are exposed.
Why service businesses lose silent demand
Classic failure mode:
- Ads and brand-name SEO look “fine.”
- Category + city prompts in ChatGPT (or Perplexity / Gemini) name competitors.
- Your public evidence is slogans (“#1 trusted,” “family owned”) without service × city pages a model can quote.
- Proof lives only in review stars or Facebook, not as indexable process/FAQ text.
AI does not owe you a referral. It synthesizes from named entities + quotable pages + corroboration. Trades with clear service menus, service areas, and FAQs get cited more often than sites that are mostly a phone number and a hero image.
This is GEO (Generative Engine Optimization) — adjacent to SEO, focused on being citable, not on a fake “AI rank score.”
Checklist: entity, service pages, proof pages, schema
Use as a pass/fail pass. No points theater.
Entity hygiene
- Legal/brand name matches domain and Google Business Profile (or differences are explained consistently)
- Primary phone and address (or service-area model) match across site and major profiles
- Cities/counties you actually serve are stated in text, not only a vague “greater metro”
- Multi-location brands have distinct, non-duplicate location facts
Service pages (not one dump)
- Each revenue service has a dedicated URL (e.g. AC repair, heat pump install, roof replacement, drain cleaning)
- Service pages name the city/region in title/H1/body when true
- Scope boundaries are clear (residential vs commercial, emergency vs scheduled)
- Thin “Services” bullet list alone is not your only coverage
Proof and trust as text
- Process or “what to expect” page (inspection → quote → work → cleanup)
- FAQ covering licensing, warranties, financing mentions only if true, emergency response, brands you service
- Project or case-style writeups with place + job type (indexable HTML)
- Reviews may support trust; they are not a substitute for service pages
Technical / machine-readable
- Key pages crawlable (not blocked, not accidental noindex)
- LocalBusiness / HomeAndConstructionBusiness-style schema as appropriate; not junk copy-paste
- Forms work; thank-you and policy pages exist
- No public staging/admin links in footers or sitemaps
External corroboration
- Same name/phone/service area on major directories you actually use
- No abandoned duplicate profiles with old NAP
If most boxes fail, you have a structure problem. More Facebook posts will not fix citation.
Queries by trade + city
Write five buyer questions per primary trade. Examples — replace with your cities and specialties:
HVAC
- “heat pump installation [City]”
- “AC repair near [neighborhood] same day”
- “furnace replacement cost guidance [City]” (informational → still tests entity presence)
- “HVAC company that services [brand] in [City]”
- “alternatives to [competitor] HVAC [City]”
Roofing
- “roof replacement [City] asphalt shingle”
- “emergency roof leak repair [City]”
- “roof inspection [City] insurance claim”
- “metal roofing installer [City]”
- “roofing company [City] residential”
Plumbing
- “water heater replacement [City]”
- “drain cleaning near [City]”
- “repipe [City] galvanized”
- “plumber for slab leak [City]”
- “emergency plumber [City]”
How to run the test
- New chat / clean session — no brand priming.
- Same five queries in ChatGPT + one other surface (and note Google AI Overview if it appears).
- Log: named yes/no; fact used; competitors; URL or name-only.
Pass/fail: Absent where weaker or similar firms are named → prioritize entity + service pages over more ad spend alone.
Security note: public booking forms & exposed admin
Home-service sites often bolt on:
- Online booking or “request service” forms
- Customer portals
/wp-admin,/login, staging subdomains, phpMyAdmin leftovers- Chat widgets and third-party scripts
GEO is about visibility. Exposure is different: anyone can probe headers, TLS, open admin paths, and form endpoints from the outside without logging in as a customer.
If you collect addresses, access instructions, or payment intent through a form, treat that surface as security-relevant. Visibility work that drives more traffic to a weak form is not free risk.
OMEN separates products on purpose:
| Need | Public path | Price floor |
|---|---|---|
| AI / answer visibility | GEO audit | $900 |
| External exposure (headers, TLS, admin, forms) | Security audit / hardening path | from $1,500 |
| Implementation of site fixes | Build | from $5,000 |
Related checklist for SaaS-style header hygiene: Small SaaS Security Headers Checklist. Trades can use the same external view even if you are not “SaaS.”
Two fixed-price paths (visibility vs. exposure)
Path A — GEO audit ($900)
Use when AI answers omit you or misstate services/cities.
Deliverables in plain language: agreed queries, observed visibility snapshot, entity/site gaps, prioritized fixes, decision-ready report. No placement guarantee. No retainer. Details: What a GEO audit includes.
Path B — Security (from $1,500)
Use when booking, admin, TLS, or headers are the worry — or when a GEO push would send more strangers into a soft form.
External-focused findings; fixed-price path without a mandatory retainer. Combine with GEO only if both problems are real ($900 + from $1,500), separate reports.
Do not buy either product for invented metrics or “guaranteed ChatGPT #1.”
FAQ
Is this only for companies with huge sites?
No. Small trade sites benefit most from a few strong service × city pages and clean NAP. Complexity is optional; clarity is not.
We rank in the map pack — why care about AI?
Map pack and AI answers are different surfaces. Some buyers never open the pack; they start in chat. Test category + city queries yourself.
Who implements the checklist fixes?
Your team, your web vendor, or OMEN under a separate build. The $900 audit diagnoses and prioritizes; it does not silently rewrite the site.
Can we do GEO and security together?
Yes. Different methods and deliverables. Book both only when both problems exist.
Next step
If the checklist fails and cold AI queries name competitors:
GEO audit — $900 · describe case or chat → omen-it.tech/us
If forms or admin worry you more than citations:
Security path — from $1,500 · same hub → omen-it.tech/us
Cold, fixed scope. No retainer required to start.
Related reading
- Why Your Business Does Not Show Up in ChatGPT — core diagnosis
- Small SaaS Security Headers Checklist — external header / TLS view
- What a GEO Audit Includes — $900 scope
- Google AI Overviews for Local Services — Google AI-shaped results
- Hub: omen-it.tech/us