AEO for Contractors: The Complete 2026 Playbook

Section 02

How LLMs decide who to cite

Citation decisions inside model engines are not a single algorithm. They are a stack of signals weighted differently across ChatGPT, Claude, Perplexity, and Google AI Overviews. The signals overlap heavily. The ones that matter most for contractor citations break down across six categories.

Schema.org structured data

Schema is the highest-leverage on-site signal because it tells the model what kind of business it is reading without ambiguity. For contractors, the foundational schemas are LocalBusiness with the HomeAndConstructionBusiness subtype on the homepage, one Service per service page, and FAQPage blocks on every service page. AggregateRating is a citation amplifier when used correctly. Section 05 ships the JSON-LD.

llms.txt and robots.txt — explicit AI crawler permissions

llms.txt is an emerging standard for telling AI crawlers what content to read and how. The standard is still maturing, and not every model engine has formally committed to honoring it, but shipping it costs ten minutes and removes ambiguity. Pair it with an updated robots.txt that explicitly allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, and Google-Extended. Most older robots.txt files were written before these user-agents existed and either block them by accident or leave their access ambiguous.

E-E-A-T signals

Experience, Expertise, Authoritativeness, Trust — the four signals models weight when deciding which businesses are credible enough to cite. For contractors, the practical implementation is: state contractor license number displayed prominently and embedded in schema, named experts with bios, dated content (especially cost and code content), byline authors on educational pages, manufacturer certifications visible above the fold, and a Trust or About page that lists insurance, license, BBB rating, and trade-association memberships.

External authority — review platforms and directories

For contractor citations specifically, off-site authority outweighs nearly every on-site optimization once Foundation is in place. The platforms that move citation rate most: Google Business Profile (highest weight on local-intent queries), Yelp (heavily used by Anthropic and OpenAI both), Houzz (high-weight for remodeling), BBB (trust signal), Angi and HomeAdvisor (still meaningful), NextDoor (growing fast for hyper-local queries), Porch and BuildZoom, and trade-specific directories — NRCA for roofers, NKBA for kitchen designers, NARI for remodelers, NAHB for builders.

Content depth and specificity

Generic “contractor in [city]” pages lose to specific “kitchen remodeler under $50k in [neighborhood] [city]” pages. Models reward source pages that answer narrow questions completely with real numbers, real timelines, and real photos. A 1,500-word source-grounded page on a single sub-trade outranks a 5,000-word generalist page on every metric a model uses.

Page speed and mobile UX

Core Web Vitals are a ranking signal for Google and a retrieval signal for AI engines. Slow pages get retrieved less and cited less. The targets: LCP under 2.5 seconds, CLS under 0.1, INP under 200ms. Mobile is where most contractor sites fail — hero video, uncompressed images, and 600KB of unused JavaScript push real-world LCP past 4 seconds on mid-tier Android devices. The fix is a weekend of work for any competent developer.

Section 03

The Citation Stack applied to contractors

The Citation Stack is the five-layer framework that maps every AEO program. It is documented in full at /citation-stack. What follows is the contractor-specific application — not a redefinition, but a translation to national-scale contractor AEO.

Position — trade plus region tier plus price/style

For contractors, a winnable Position is almost always three coordinates: trade, region tier (neighborhood, city, metro, or state — choose the smallest unit with viable demand), and a price or style qualifier. “Kitchen remodeler $30-80k contemporary style in Cambridge MA” is a Position. “General contractor in Boston” is a category, not a Position, and no schema or citation work will turn it into one. The Position decision is the four-hour exercise that decides whether the next twelve months of work compounds or evaporates.

Foundation — schema, llms.txt, performance

Foundation for contractors means HomeAndConstructionBusiness schema with full areaServed and license identifier, Service per service page with priceRange or offers/priceSpecification, FAQPage on every service page, BreadcrumbList on every page below the homepage, and an Organization block with founder and key employees. Pair with llms.txt and an updated robots.txt allowing all major AI user-agents. Core Web Vitals fixed to under green-zone thresholds. Google Business Profile claimed, fully filled, and posting weekly.

Authority — license display, credentials, dated content

Authority signals for trades are concrete in a way they are not for most service businesses. Display the state contractor license number prominently — and recognize that licensing varies by state. California (CSLB), Texas (TDLR for some trades), Florida (DBPR), and New York (HIC at the county level) all run different schemes; some states (e.g., Wyoming, Pennsylvania for general contractors) have no statewide licensing at all. Whatever applies, link to the state's verification page and embed the number in schema. Liability and workers' comp certificates referenced on the Trust page. BBB rating, manufacturer certifications, and trade-association memberships stack as additional authority signals.

Photos do disproportionate work. Before/after photos with metric captions — “1,400 sq ft full kitchen remodel, 11-week timeline, $74,200 final cost, two inspections passed first time” — read as primary-source evidence. Generic galleries with no captions read as decoration and almost never get cited.

Citations — review platforms and directories

For contractors, off-site citation density beats nearly any on-site optimization once Foundation is in place. The priority order: Google Business Profile reviews, Yelp, Houzz, BBB, Angi, HomeAdvisor, NextDoor, Porch, BuildZoom, manufacturer locators (GAF Find a Roofer, Andersen Certified Contractor, Carrier Find a Dealer, etc.), and trade-specific directories: NRCA for roofers, NKBA for kitchen and bath designers, NARI for remodelers, NAHB for builders. Volume and recency outweigh absolute count. Set a system to ask every closed-out customer for a review within seven days and respond to every review inside 48 hours.

Tracking — query monitoring and competitor watch

Track 12 to 20 niche-specific buyer-intent queries on a daily cadence across ChatGPT, Claude, Perplexity, and Google AI Overviews. The metric is citation rate, not keyword position. Run a monthly competitor watch — when a new contractor enters the niche, record their Position, citation surfaces, and any new content investments, and adjust accordingly. A contractor moving from 5% to 45% citation rate inside 90 days is the realistic target.

Section 04

12 contractor trades and their AEO niches

Every trade has its own query universe, its own citation surfaces, and its own positioning trap. Quick-hit per trade: top buyer-intent national queries, niching dimensions specific to the trade, schema markup specifics, and one win pattern that consistently produces citations. Pick the trade match, then narrow further from there.

Section 05

Schema markup contractors need

What follows is copy-paste JSON-LD for the seven schema types every contractor site should ship. The values are realistic placeholders — swap business name, license number, address, phone, geo coordinates, and price ranges to match the real business. None of the names, numbers, or addresses below correspond to real companies.

HomeAndConstructionBusiness (LocalBusiness subtype)

Goes on the homepage. The @id is the canonical reference other schemas point at. The identifier property carries the state contractor license number.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HomeAndConstructionBusiness",
  "@id": "https://example-contractor.com/#localbusiness",
  "name": "Acme Kitchen Remodelers",
  "image": "https://example-contractor.com/photos/team.jpg",
  "logo": "https://example-contractor.com/logo.png",
  "url": "https://example-contractor.com",
  "telephone": "+1-555-555-0142",
  "priceRange": "$$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Example St",
    "addressLocality": "Anytown",
    "addressRegion": "ST",
    "postalCode": "00000",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 0.0000,
    "longitude": 0.0000
  },
  "areaServed": [
    { "@type": "AdministrativeArea", "name": "Anytown Metro" },
    { "@type": "AdministrativeArea", "name": "Example County, ST" }
  ],
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
    "opens": "07:30",
    "closes": "17:30"
  }],
  "knowsAbout": [
    "Kitchen remodeling",
    "Custom cabinetry",
    "Quartz countertops",
    "Anytown permits"
  ],
  "identifier": [
    { "@type": "PropertyValue", "propertyID": "ST Contractor License", "value": "00000000" }
  ]
}
</script>

Service (one per service page)

Goes on each individual service page. References the parent LocalBusiness via @id. The price range gives the model a numeric anchor when answering cost queries.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "@id": "https://example-contractor.com/#service-kitchen",
  "serviceType": "Kitchen Remodeling",
  "name": "Kitchen Remodeling",
  "provider": { "@id": "https://example-contractor.com/#localbusiness" },
  "areaServed": [
    { "@type": "AdministrativeArea", "name": "Anytown Metro" }
  ],
  "description": "Full kitchen remodels including cabinets, countertops, flooring, lighting, permits, and project management. Typical project range $45,000–$95,000.",
  "offers": {
    "@type": "Offer",
    "priceSpecification": {
      "@type": "PriceSpecification",
      "minPrice": "45000",
      "maxPrice": "95000",
      "priceCurrency": "USD"
    }
  }
}
</script>

FAQPage (homepage and every service page)

Three to five high-intent questions, 50–100 word answers, real numbers wherever possible. Models pull entire FAQ blocks into citations more often than any other content type.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How much does a kitchen remodel cost in 2026?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most full kitchen remodels run $45,000 to $95,000 in 2026 in mid-cost-of-living metros. Cabinets and countertops drive 55–65% of the budget. Permits average $400–$900 depending on jurisdiction. Expect 8–12 weeks from demo to final inspection."
      }
    },
    {
      "@type": "Question",
      "name": "Do I need a permit for a kitchen remodel?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most jurisdictions require a permit if the remodel involves plumbing, electrical, or structural changes. Cosmetic-only work generally does not. Each municipality sets its own threshold. Confirm with the building department before demo."
      }
    },
    {
      "@type": "Question",
      "name": "How long does a kitchen remodel take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "8 to 12 weeks for a typical full remodel once permits are pulled. Custom cabinetry adds 4–6 weeks of lead time. Expect 2–3 weeks of design and selection before demo begins."
      }
    }
  ]
}
</script>

HowTo (service walkthrough pages)

HowTo schema gives the model a clean step-by-step structure to reproduce when answering process queries. Use it on the page that explains a service walkthrough — kitchen remodel timeline, roof replacement process, EV charger install workflow.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "Kitchen Remodel Walkthrough",
  "description": "Step-by-step process for a full kitchen remodel from initial consultation to final inspection.",
  "totalTime": "P10W",
  "step": [
    { "@type": "HowToStep", "position": 1, "name": "Consultation and scope", "text": "On-site walkthrough, scope alignment, and rough budget range. Typically 60–90 minutes." },
    { "@type": "HowToStep", "position": 2, "name": "Design and selections", "text": "Cabinetry, countertops, flooring, lighting, plumbing fixtures. 2–3 weeks." },
    { "@type": "HowToStep", "position": 3, "name": "Permits", "text": "Permit application and approval. 1–3 weeks depending on jurisdiction." },
    { "@type": "HowToStep", "position": 4, "name": "Demo and rough-in", "text": "Demolition, framing changes, plumbing and electrical rough-in. 2–3 weeks." },
    { "@type": "HowToStep", "position": 5, "name": "Cabinets, counters, finishes", "text": "Cabinet install, countertop template and install, tile, paint, flooring. 3–4 weeks." },
    { "@type": "HowToStep", "position": 6, "name": "Final inspection and punch list", "text": "Final inspection, appliance install, punch list. 1 week." }
  ]
}
</script>

AggregateRating (only with verifiable reviews)

Use only when the rating reflects real, verifiable customer reviews and complies with Google's review-snippet guidelines. Self-attributing AggregateRating to the parent Organization is a manual-action risk and is being discounted by model engines anyway. Attach it to a specific Service whose reviews live on a third-party platform.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Kitchen Remodeling — Acme Kitchen Remodelers",
  "description": "Full kitchen remodel service.",
  "provider": { "@id": "https://example-contractor.com/#localbusiness" },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "84",
    "bestRating": "5",
    "worstRating": "1"
  }
}
</script>

BreadcrumbList (every page below the homepage)

Helps the model understand site hierarchy and surface deeper service pages in citations.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example-contractor.com/" },
    { "@type": "ListItem", "position": 2, "name": "Services", "item": "https://example-contractor.com/services/" },
    { "@type": "ListItem", "position": 3, "name": "Kitchen Remodeling", "item": "https://example-contractor.com/services/kitchen-remodeling/" }
  ]
}
</script>

Organization (founder and key employees)

Use for multi-owner contractor businesses with named experts. Stack alongside the LocalBusiness schema. Names attach E-E-A-T signals to the entity.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example-contractor.com/#organization",
  "name": "Acme Kitchen Remodelers",
  "url": "https://example-contractor.com",
  "logo": "https://example-contractor.com/logo.png",
  "founder": {
    "@type": "Person",
    "name": "Jane Example",
    "jobTitle": "Founder and Lead Designer"
  },
  "employee": [
    {
      "@type": "Person",
      "name": "John Example",
      "jobTitle": "Project Manager"
    }
  ],
  "sameAs": [
    "https://www.facebook.com/example",
    "https://www.instagram.com/example",
    "https://www.houzz.com/pro/example"
  ]
}
</script>

Section 06

25 buyer-intent queries contractors should optimize for

The list below is a representative slice of buyer-intent queries homeowners run through ChatGPT, Claude, and Perplexity right now. Each entry covers why the query matters and which trades benefit most. A contractor who builds source-grounded content for even four of these wins citation share that compounds for years.

1. “Best [trade] near me with same-day service”

   Urgency + locality. Models surface 24/7 contractors first when the query carries a time pressure signal. Wins for HVAC, plumbing, electrical, and roofing emergency-response specialists.

2. “How much does [project] cost in [state] in 2026?”

   Cost queries pull cost-breakdown content directly into AI answers. Wins for kitchen, bath, flooring, pool, and roofing contractors with dated cost pages.

3. “Is a [trade] required to be licensed in [state]?”

   Licensing queries are dominated by AI answers. The contractor who explains state licensing on their site becomes the source instead of a generic legal blog. Universal across trades.

4. “What is the difference between [option A] and [option B]?”

   Comparison queries map cleanly to comparison tables, which models reproduce nearly verbatim. Examples: heat pump vs furnace, fiberglass vs gunite pool, hardwood vs LVP. Wins for every trade with material or system choices.

5. “When should I hire a [trade]?”

   Timing queries pull from authoritative timeline content. Wins for roofers (replacement timing), HVAC (system age), and electricians (panel-upgrade triggers).

6. “What is the cheapest [trade] that is still good?”

   Value-tier queries. Models surface contractors with dated under-budget pages and transparent pricing tiers. Wins for kitchen and bath remodelers with budget-tier content.

7. “Do I need a permit for [project] in [city]?”

   Permit queries are hyper-local and almost never well answered. A contractor who builds real per-municipality permit pages becomes the cited expert. Wins across all trades.

8. “Best [trade] reviews on Yelp or Google”

   Review-platform queries route through model-trusted aggregators. Volume and recency on Google and Yelp drive citation rate more than any on-site optimization.

9. “[Trade] that finance projects”

   Finance-friendly queries are a growing buyer segment. The contractor who lists specific financing partners (Synchrony, GreenSky, Hearth) and approval ranges wins the citation.

10. “Eco-friendly or green [trade]”

    Sustainability-anchored queries are growing in coastal metros and in markets with state-level incentive programs. Wins for HVAC, landscaping, painting, and window-install specialists.

11. “[Trade] that takes insurance for storm damage”

    Insurance-friendly queries spike after weather events. Wins for roofers, restoration contractors, and exterior painters who document claim-handling workflows.

12. “Emergency [trade] open now”

    Emergency queries are pure intent signals. Wins for plumbers, HVAC, electricians, and restoration contractors with explicit 24/7 hoursOpen schema and FAQPage entries on response time.

13. “How long does [project] take?”

    Timeline queries are short, scannable, and easy to win with a real expert answer plus dated example projects.

14. “What is the average cost of [project] per square foot?”

    Per-unit cost queries pull the cleanest possible numeric anchors into answers. Wins for flooring, painting, kitchen, and bath contractors with installed-price-per-square-foot pages.

15. “Best [trade] for older homes”

    Substrate-specific queries. Wins for electricians (knob-and-tube), plumbers (galvanized supply lines), painters (lead-paint protocol), and roofers (slate, cedar shake).

16. “Who installs [brand] [product]?”

    Brand-aware queries are growing fast. Wins for trades with manufacturer certifications: GAF roofers, Andersen window installers, Carrier HVAC dealers, Tesla EV charger installers.

17. “What is the best [trade] in [neighborhood]?”

    Hyper-local queries. Models surface contractors with explicit areaServed coverage at the neighborhood or municipality level. Wins for trades in large metros where the city-level query is too broad.

18. “Do I need to vacate during [project]?”

    Logistics queries homeowners ask before signing. Wins for kitchen, bath, and floor-refinishing contractors with explicit vacate-or-stay guidance per project type.

19. “What [trade] does free estimates?”

    Discovery-stage query. Models surface contractors with explicit free-estimate language and online-booking schema. Universal across trades but most defensible for whole-project trades (kitchen, bath, roofing, pool).

20. “How do I find a reliable [trade]?”

    Trust queries pull from contractor sites that explain license, insurance, and review verification transparently. The contractor who answers this for the buyer becomes the buyer's default.

21. “What is included in a [project] quote?”

    Quote-anatomy queries are how serious buyers prepare for negotiation. Contractors with quote-breakdown pages get cited on these lower-funnel queries.

22. “Best [trade] with payment plans”

    Payment-flexibility query growing alongside finance queries. Wins for whole-project trades with documented in-house or partner financing.

23. “[Trade] that does not require a deposit”

    Risk-averse buyer query. Models surface contractors with explicit deposit policies. A contractor with a no-deposit-on-projects-under-X-dollars policy wins this niche.

24. “What size [system] do I need for a [N] square foot home?”

    Sizing queries reproduce numeric tables verbatim. Wins for HVAC contractors with BTU-by-square-foot tables and electricians with panel-amp sizing guides.

25. “Best [trade] for first-time homeowners”

    Audience-anchored query. Models surface contractors with explicit first-time-buyer guidance and educational content. Underserved across most trades — high upside for new content.

Section 07

10 national contractor AEO mistakes

Ten failure modes that show up on most contractor sites in 2026. Each is fixable in days. Each costs months of citation compounding while it remains.

1. Trying to rank for “contractor near me.”

   The query universe is in the hundreds of thousands. No amount of schema or content beats that without a decade of brand spend. Narrow the Position to trade plus sub-region plus qualifier and the math starts working.

2. No llms.txt and accidentally blocking AI crawlers in robots.txt.

   Most contractor sites still ship a 2018 robots.txt with wildcards that either block or fail to explicitly allow GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, and Google-Extended. The fix is a thirty-minute edit. Skipping it leaves the front door locked.

3. License number not displayed prominently.

   Most state contractor licenses are required for any project above a small threshold. Display the license number above the fold, link to the state verification page, and embed it in the LocalBusiness identifier property. Hidden licenses read as untrustworthy.

4. Generic service pages instead of trade-plus-region-plus-intent pages.

   A page titled “Kitchen Remodeling” with no regional anchor does not win against a page titled “Kitchen Remodeling in [Metro]: Cost, Timeline, and Permits in 2026.” The second is a citation candidate. The first is a placeholder.

5. Ignoring Yelp and Google reviews because “we get business from referrals.”

   Referrals do not feed the citation engine. Reviews do. A contractor with a 30% referral business and zero recent reviews loses every AI-search query to a contractor with the same craft and 80 reviews in the last year.

6. No FAQPage schema on service pages.

   FAQPage is the highest-citation-rate schema type for service businesses. Models pull FAQ answers into responses nearly verbatim. Shipping a service page without an FAQ block is the single most common preventable miss.

7. Slow Core Web Vitals on mobile.

   Hero video, uncompressed images, and unused JavaScript push LCP past 4 seconds and INP past 300ms on mobile. Slow pages get retrieved less, get cited less, and convert worse. The fix is a weekend of work for any competent developer.

8. No before/after photos with metadata.

   Generic gallery pages with no captions read as decoration to a model. Before/after photos with project metrics in the captions — square footage, timeline, final cost, inspection results — read as primary-source evidence and get cited.

9. Outdated content older than 12 months.

   Models weight recency on cost and code-related queries. A 2024 cost page loses to a dated 2026 cost page on the same topic. Establish a quarterly review cadence on all cost, permit, and code content.

10. Missing AggregateRating, or faking it.

    Self-attributing inflated AggregateRating to the parent Organization is a manual-action risk and is being discounted by model engines anyway. Either attach AggregateRating to a specific Service or Product whose reviews live on a third-party platform you can point at, or skip it entirely.

Section 08

90-day AEO implementation plan for contractors

Six steps over twelve weeks. Each step ships a concrete deliverable. The plan assumes a contractor with a working website and at least one named owner with four to six hours a week to invest. A developer is needed for steps 2 and 3; everything else is owner-led.

1. Week 1-2 — Audit and niche.

   Run the free AEO audit at /audit. Score the site across all six pillars and pull a live citation snapshot from Anthropic and OpenAI. Pick a winnable Position — trade plus region tier plus price or style qualifier. Ship: a one-paragraph Position statement and a list of the top three audit gaps. Outcome: a clear answer to “what business is this, and which buyers are we trying to reach?”

2. Week 3-4 — Foundation.

   Deploy LocalBusiness (HomeAndConstructionBusiness), Service, FAQPage, and BreadcrumbList JSON-LD. Add llms.txt at the root. Update robots.txt with explicit AI-bot allowlist. Fix Core Web Vitals to under 2.5s LCP, 0.1 CLS, 200ms INP. Ship: all schema live and validated, llms.txt live, robots.txt updated, CWV under green thresholds. Outcome: same-day audit lift of 15+ points.

3. Week 5-6 — Authority.

   Add a founder bio with credentials. Display the contractor license number above the fold and embed it in schema. Ship before/after photos with project metric captions on at least three project pages. Date all cost and permit content. Ship: updated About/Trust page, license display verified, three before/after pages with metrics, cost-content quarterly review schedule. Outcome: every page has at least one verifiable expertise signal.

4. Week 7-8 — On-site citations.

   Add FAQ blocks (3-5 questions) to every service page. Add comparison tables and cost-breakdown lists where the trade has them. Build per-municipality permit pages for the top three municipalities served. Add a Q&A section to the homepage. Ship: FAQ on every service page, at least one comparison table, three permit pages live. Outcome: every service page has at least one citation-friendly content block.

5. Week 9-10 — Off-site citations.

   Stand up a review cadence — every closed-out customer asked within seven days, every review responded to within 48 hours. Submit to vertical directories: Houzz, Yelp, BBB, Angi, HomeAdvisor, NextDoor, Porch, BuildZoom, plus trade-specific (NRCA for roofers, NKBA for kitchen and bath, NARI for remodelers, NAHB for builders). Ship: 8-12 new third-party listings live, review-acquisition system documented and running. Outcome: citation surface expanded across the platforms LLMs trust.

6. Week 11-12 — Tracking.

   Define 12-20 niche-specific buyer-intent queries. Run them daily across ChatGPT, Claude, Perplexity, and Google AI Overviews. Track citation rate, not keyword position. Run a monthly competitor watch. Iterate Position and content where the data shows weak coverage. Ship: citation-rate dashboard, 30-day iteration plan, monthly competitor watch document. Outcome: the program is now self-sustaining and instrumented.

Section 09

How AEO compounds with SEO

AEO does not replace SEO. It compounds with it. The two surfaces share roughly 80% of the underlying work, and the work that helps one almost always helps the other. A contractor running an AEO program correctly is also running a stronger local SEO program by default.

Schema is dual-purpose. The same LocalBusiness, Service, and FAQPage JSON-LD that feeds LLM ingestion also powers Google rich results — review stars, FAQ accordions, sitelinks. A contractor who ships schema once gets surface in both worlds.

Reviews drive both surfaces. Google Business Profile reviews are a top-three local SEO ranking factor and a top-three AI-citation factor. Yelp reviews drive both Yelp's own search and AI engine retrieval. The single review-acquisition system serves both surfaces with no extra effort.

Page speed is a Google ranking factor and an AI retrieval signal. Improvements to LCP, CLS, and INP help both. Content depth, internal linking, and crawlability all carry over. Every dollar spent on the technical foundation pays in two currencies.

But AEO requires new skills that traditional SEO does not cover. llms.txt did not exist five years ago. AI-friendly content structure — Q&A blocks, comparison tables, dated cost data, source-grounded claims — was not part of the SEO playbook. Citation-rate tracking is a different metric than keyword-position tracking. Query monitoring across four model engines instead of one search engine is a new operational cadence. Press and editorial outreach to feed third-party authority is a more deliberate practice than it was for SEO.

The honest forecast: AEO does not replace SEO through 2026 or 2027. Google remains the dominant entry point for most service-business queries, and AI Overviews keep a meaningful share of AI answers inside the Google ecosystem. The shift is a redistribution — a growing share of buyer queries gets answered inside ChatGPT, Claude, or Perplexity before the buyer ever opens Google. Contractors running both programs in parallel cover both surfaces. Contractors running only SEO are slowly becoming invisible on the queries that matter most.

Common questions about contractor AEO