AI Didn’t Quite Kill SEO: What Local Businesses Should Actually Do in 2025

Myth #1: You need special “AI keywords”

People try to force AI responses by sprinkling magic phrases across pages. That misses the point. AI and modern search line up with questions and intent. If someone types “How long does SEO take?” they want a straight answer in the first sentence. They do not want a lecture about search history.

Pages you make now need to get to the point ASAP - no dancing around the topic at all. Give people the answer. One, great way is with a TL;DR block at the top of pages. Boil it all down. Here's more...

What to do instead

• List the top five questions customers actually ask on calls and in emails.
• Make each question an H2. Put a one-sentence answer immediately under it.
• Follow with a short “it depends” section, then give one clear next step.

Example: A dentist in Nashville’s 12 South neighborhood writes “How soon can I get a crown?” as an H2 with a one-sentence answer first. That clean format gets saved, quoted, and read aloud by assistants more often than a wall of text.

Myth #2: Featured snippets are dead because of AI overviews

Desktop clicks on snippets can dip when an AI box shows up. That does not make snippets useless. Snippets still feed voice assistants and quick mobile answers. Those users are often closer to taking action.

What to do instead

• Use question headings followed by a standalone 40–60 word paragraph.
• Answer first. Add detail after. Write something that could be read aloud clearly.
• Where it helps, add a short list of three to five steps or pros and cons.

Example: An electrician in Madison’s Downtown area creates a “Do I need a permit to add outlets?” blog post with that question as an H1 with a crisp answer and a 3-bullet checklist. That's perfect for snippets and voice.

Myth #3: Schema markup does not matter anymore

Schema is how machines understand your page types and sections. For Q&A and step-by-step content, it is a shortcut to clarity. Not because it hacks the system, but because it labels your content properly. Your website isn't just serving one audience now, but also your audience through AI.

What to do instead

• Add FAQPage schema to your main FAQ page. Map three to eight real questions.
• Add HowTo schema to any step-by-step process like installations, maintenance, or estimate steps.
• Keep LocalBusiness details accurate: name, address, phone, hours, and service areas.

Example: An HVAC company in Rockford’s north side area publishes “How to change a 1-inch filter” with HowTo schema and a 60-second video. That page becomes the internal link target anytime filters are mentioned on the site.

Get Your Site Technically Ready for AI (Beyond Schema)

Answer-first content is the foundation, but machines also need clean, machine-readable signals. Here’s how to make your site easier for AI systems to understand and cite.

1) Clean, crawlable signals

• Canonical URLs: One preferred URL per page. Set canonicals correctly on variants (with/without params, print pages, tracking URLs).
• Indexing hygiene: Use <meta name="robots" content="index,follow"> (or noindex when needed). Avoid blocking important pages in robots.txt.
• Sitemaps: Keep XML sitemaps fresh. Include service pages, FAQs, and any critical guides. Regenerate on publish/update.
• Core Web Vitals and mobile: Fast LCP, stable CLS, quick TTFB. If a phone struggles to render your page, assistants will, too.
• Consistent NAP: Name, address, phone, hours must match across your site, schema, and major listings.

2) JSON-LD that helps machines “see” your business

Beyond FAQPage and HowTo, add the basics that describe who you are, where you operate, and what you offer.

• LocalBusiness: Include address, geo (if storefront), openingHoursSpecification, areaServed, telephone, sameAs (major profiles).
• Service (on service pages): Define what you do, typical areas served, and link back to your LocalBusiness entity with provider.
• BreadcrumbList: Helps AIs understand page position in your site structure.
• WebSite + SearchAction: Lets assistants discover your internal search endpoint.

{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Example Plumbing Co.",
"url": "https://www.exampleplumbing.com/",
"telephone": "+1-555-123-4567",
"image": "https://www.exampleplumbing.com/assets/brand.jpg",
"address": {
"@type": "PostalAddress",
"streetAddress": "1234 W Oak St",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78704",
"addressCountry": "US"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "07:30",
"closes": "18:00"
}
],
"areaServed": [
{"@type":"AdministrativeArea","name":"Zilker"},
{"@type":"AdministrativeArea","name":"Barton Hills"},
{"@type":"AdministrativeArea","name":"Travis Heights"}
],
"sameAs": [
"https://www.facebook.com/exampleplumbing",
"https://www.instagram.com/exampleplumbing"
]
}

{
"@context": "https://schema.org",
"@type": "WebSite",
"url": "https://www.exampleplumbing.com/",
"potentialAction": {
"@type": "SearchAction",
"target": "https://www.exampleplumbing.com/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}

3) Machine-readable JSON for key actions (forms, hours, locations)

In addition to JSON-LD, offer simple JSON endpoints that describe forms and business data. This helps assistants and integrations understand how to contact you or submit a lead without guessing your HTML.

• Publish lightweight JSON endpoints like /hours.json, /contact.json, and /locations.json.
• Keep them stable and versioned if you evolve the format (for example, /contact.v1.json).
• Allow CORS for GET on these endpoints so trusted clients can read them.

{
  "name": "Website Contact",
  "method": "POST",
  "action": "https://www.exampleplumbing.com/wp-json/webstix/v1/contact",
  "fields": [
    {"name":"name","type":"text","required":true,"label":"Your Name"},
    {"name":"email","type":"email","required":true,"label":"Email"},
    {"name":"phone","type":"tel","required":false,"label":"Phone"},
    {"name":"service","type":"select","required":true,"options":["Drain Cleaning","Water Heater","Burst Pipe"]},
    {"name":"message","type":"textarea","required":true,"minLength":20}
  ],
  "validation": {
    "honeypotField":"company",
    "rateLimitPerIP":"10/hour"
  },
  "success": {
    "message":"Thanks—our team will reach out shortly.",
    "redirect": "https://www.exampleplumbing.com/thank-you/"
  }
}

{
  "timezone": "America/Chicago",
  "regular": [
    {"day":"Mon-Fri","opens":"07:30","closes":"18:00"},
    {"day":"Sat","opens":"09:00","closes":"13:00"}
  ],
  "exceptions": [
    {"date":"2025-11-27","closed":true,"note":"Thanksgiving"}
  ]
}

Why this helps: Assistants can fetch your hours, know which fields your form expects, and submit or hand off leads correctly. You are reducing ambiguity and making it easier to cite or transact.

4) Action patterns for assistants

• ContactAction: In JSON-LD, describe how to contact you with a target EntryPoint. Keep it accurate with your real contact URL.
• Book an estimate: If you offer bookings, describe the flow with an Action type that points to your booking page or API.

{
"@context":"https://schema.org",
"@type":"LocalBusiness",
"name":"Example Plumbing Co.",
"url":"https://www.exampleplumbing.com/",
"potentialAction":{
"@type":"ContactAction",
"target":{
"@type":"EntryPoint",
"urlTemplate":"https://www.exampleplumbing.com/contact/",
httpMethod":"POST
}
}
}

5) Practical extras that reduce friction

• Accessible markup: Labels tied to inputs, descriptive alt text, clear focus states. If screen readers can parse it, AIs generally can, too.
• Server responses: Return proper HTTP codes on forms and APIs. 200 for success, 4xx for validation errors with a concise JSON error body.
• Security and trust: Valid TLS, HSTS, and visible contact options. Don’t gate essential info behind heavy JS.
• Consistent CTAs: Phone numbers in tel: links, emails in mailto:, and addresses with geo in JSON-LD.

Bottom line: Keep your human content clear, and give machines predictable, structured hooks. That combo is what gets surfaced and cited.

Shift #1: Hyper-local content clusters beat generic city pages

Citywide pages like “Madison Roofing” still help, but they lose to pages built for specific neighborhoods and micro areas. Think landmarks, subdivisions, campus zones, and real problems locals face.

How to build a hyper-local cluster

1. Pick four to six micro areas you truly serve. For Denver, that could be Cherry Creek, Washington Park, Green Valley Ranch, Sloan’s Lake.
2. Create a dedicated page for each with details that prove you know the area:
   • Common jobs in that area like flat roofs, alley access, older brick chimneys.
   • Local constraints like HOA quirks, permit rules, parking, or narrow streets.
   • Response times and seasonal notes like hail cycles or freeze and thaw.
3. Interlink these pages from your main service page and an “Areas We Serve” footer block.

Example: A plumber in Eau Claire’s west side mentions older multi-family buildings, UW-Eau Claire's move-in weeks, and common winter pipe bursts. That level of detail wins “near me” and campus searches a generic “Eau Claire plumber” page will not reach.

Shift #2: Continuous micro A/B testing, every week

Search changes fast. Quarterly tests are too slow. You do not need giant experiments. One controlled tweak per week is enough if you track it.

A 30-minute weekly testing loop

1. Pick one micro test: headline variant, a tighter first sentence, bullets vs paragraph, a mini-FAQ add, or a different hero CTA.
2. Ship one change on one page. Do not bundle five changes at once.
3. Track impressions, clicks, snippet pickup, and conversions for two to three weeks.
4. Roll out the winner to similar pages.

Example micro tests: “How long does a heat pump last?” Try a one-sentence answer vs a three-sentence answer. “Sump pump failure signs” Try bullets first vs a paragraph first. “Emergency roofer near McFarland” Try a phone-first CTA vs a form-first CTA.

Implementation checklist

• Refresh five Q&A sections with the answer in sentence one.
• Add HowTo schema to one process page and FAQPage schema to your main FAQ.
• Publish three to five hyper-local pages with real, unique details.
• Start a simple weekly test log. One change, one page, one metric.
• Link new local pages from your main services and your footer.

Real-world ideas you can borrow

• Ann Arbor near South Quad: “Same-day drain clearing near campus” with map, campus hours, and a phone CTA during move-in weeks.
• Columbus Short North: “Small storefront signage permits” with a 5-step HowTo and links to city forms.
• Austin Zilker: “Mini-split installs in older bungalows” that covers attic access, power constraints, and typical timelines.

FAQs About AI and SEO for Small Businesses

Are AI overviews replacing websites?

No. They shift where attention goes. Pages that answer questions cleanly, use schema, and cover specific neighborhoods still win traffic and leads.

Do I need a separate page for every suburb?

No. Start with three to five you truly serve and can write about in a useful way. Add more only if you have real details.

What should I test first?

Test the first sentence on your most searched question page. Make it a direct, quotable answer. That single change often moves the needle.

Next steps

Pick one: publish a hyper-local page this week, add FAQPage schema to your FAQ, or run your first micro test. Do one of those every week for a month and you will feel the difference in both visibility and lead quality.

Do you... need help with that? We'd be happy to help you get started and get your website more in tune with AI. Contact Webstix today to get going.

{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Are AI overviews replacing websites?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. They shift where attention goes. Pages that answer questions cleanly, use schema, and cover specific neighborhoods still win traffic and leads."
}
},
{
"@type": "Question",
"name": "Do I need a separate page for every suburb?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. Start with three to five you truly serve and can write about in a useful way. Add more only if you have real details."
}
},
{
"@type": "Question",
"name": "What should I test first?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Test the first sentence on your most searched question page. Make it a direct, quotable answer. That single change often moves the needle."
}
}
]
}