The second half of 2026 belongs to businesses that AI assistants can actually read. Most still can't be.

Two numbers frame the second half of 2026 for every local business in the nine Bay Area counties — Sonoma, Napa, Marin, Solano, San Francisco, San Mateo, Santa Clara, Alameda, and Contra Costa.

First: AI search visits grew 42.8% year over year — from 15.6 billion to 27.4 billion between Q1 2025 and Q1 2026. Your customers are asking ChatGPT, Perplexity, Claude, and Google's AI Overviews the questions they used to type into a search box.

Second: the crawlers feeding those assistants — GPTBot, ClaudeBot, PerplexityBot — do not execute JavaScript. If your site renders its content client-side, those systems see a mostly empty page. In a region full of businesses running on modern JavaScript-heavy site builders, that's not a footnote. That's the whole game.

Here's the playbook we're running for the back half of the year.

1. Your entity graph belongs in raw HTML

An AI assistant deciding whether to recommend you is assembling an entity: who you are, what you do, where you do it, why you're credible. Everything that feeds that entity needs to exist in the initial HTML response — not injected by a script after the page loads.

• Name, address, phone, hours, service area — as plain text in the served HTML, on every page, matching everywhere else you appear online.
• What you do, stated flatly. "Bonsai Marketing is a Santa Rosa agency doing local SEO, Google Business Profile management, paid ads, AI visibility, content authority, and websites." One sentence a machine can lift verbatim. Write yours.
• Credentials and provenance. Licenses, founding date, owner's name. Ours: founded 2021 by Bryan Fikes, who's spent 27 years in search and built his first agency, Zenergy Internet Marketing, back in 2007. That history is on our site in plain text because provenance is exactly what these systems weigh.
• Schema markup that agrees with the visible text. LocalBusiness, Organization, Person. Schema that contradicts the page — or exists only in JavaScript — hurts more than it helps.

Quick self-test: view your site's page source (not the rendered inspector — the source) and search for your phone number and services. If they're not there, an AI crawler can't see them either.

2. Ship an llms.txt

llms.txt is a plain-text file at your site root that gives AI systems a curated map: what your business is, and where your most important pages live, in markdown a language model can digest in one pass. It's an emerging convention, not a guarantee — think of it the way robots.txt and sitemaps started. It costs an hour, it can't hurt, and it puts your best self-description in the exact format these systems prefer. Every site we manage gets one this quarter.

3. Optimize to be the cited answer, not the ranked link

When someone asks Perplexity "who's a good deck contractor in Sonoma County?", the answer is a couple of sentences with two or three citations. There is no page two. There's barely a page one. Being the citation is the new ranking, and it favors different work:

• Answer real questions completely on one page. Assistants cite pages that resolve the query, not pages that tease it. Cost factors, timelines, process, tradeoffs — the stuff you explain on every sales call belongs in your content.
• Be specific and checkable. Vague marketing copy never gets cited. Concrete, verifiable statements do.
• Third-party corroboration. Local press, directories, chamber listings, reviews. Assistants triangulate; a business that exists in only one place on the internet looks like a business that might not exist.
• Freshness. Stale content loses citations to a competitor's newer page answering the same question. A quarterly refresh pass on your key pages is now table stakes — it's a standing part of our content authority retainers.

4. What Google killing FAQ rich results actually means

In May 2026, Google removed FAQ rich results from search entirely. The expandable Q&A boxes under listings — gone. Cue the panic posts about FAQ schema being dead.

Read it more carefully: FAQPage markup is still parsed for understanding. The visual reward disappeared; the comprehension value didn't. And that's the real lesson of the change. For years, local businesses spent effort chasing rich-result decorations — the visible trinkets in the results page. Google keeps taking the trinkets away. What it never takes away is the value of being clearly understood.

So the effort shifts: from rich-result chasing to entity clarity. Keep FAQ markup where it genuinely describes the page. Stop bolting it onto everything for a cosmetic payoff that no longer exists. Redirect those hours into the entity work in section one — which pays in Google, ChatGPT, Perplexity, Claude, and AI Overviews simultaneously.

The 90-day action list

Days 1–30: Make yourself readable.

• View-source audit: confirm NAP, services, and key content exist in raw HTML on every important page.
• Fix or server-render anything that only exists in JavaScript.
• Verify GPTBot, ClaudeBot, and PerplexityBot aren't blocked in robots.txt.
• Publish llms.txt.

Days 31–60: Make yourself unambiguous.

• Write the one-sentence machine-liftable description; put it on your homepage and about page.
• Align schema with visible text; add Person markup for the owner.
• Reconcile your name, address, and phone across every listing you can find.

Days 61–90: Make yourself citable.

• Pick the five questions prospects always ask; publish a definitive page for each.
• Ask the assistants your own money questions — "best [your trade] in [your city]" — and log who gets cited. That's your baseline.
• Pursue two or three local citations: press, chamber, community organizations.

None of this requires a big budget. It requires doing unglamorous work in the right order. If you'd rather see exactly where you stand first, our AI visibility audit shows how the assistants currently see you — or don't.

The businesses that win H2 2026 won't be the ones with the cleverest prompts or the shiniest schema. They'll be the ones an AI can read, verify, and confidently repeat.