Every agency has published an "AI is changing SEO" thinkpiece by now. Most of them are speculation wearing a suit. This one is configuration: what actually runs on this website to stay visible to AI search, why each piece is there, and what I'd honestly tell a Tampa business to do about all of it this quarter.
What Actually Changed
A growing slice of your customers no longer type "estate planning lawyer tampa" into a search box and compare ten blue links. They ask ChatGPT, Perplexity or Google's AI Overviews a whole question – "who's a good estate planning lawyer in South Tampa and what should it cost?" – and get back one assembled answer with three or four names in it.
You want to be one of the names. The assembly draws on what these systems can crawl and corroborate: your website, your Google Business Profile, your reviews, your structured data. Which means AI visibility isn't a new discipline. It's local SEO with the volume turned up on a few specific dials.
Decision One: Let the AI Crawlers In
The first fork in the road is whether AI systems may crawl your site at all. Here is the actual crawler policy in this site's robots.txt file – you can view it yourself at connorcedro.com/robots.txt:
User-agent: GPTBot → Allow: /
User-agent: ClaudeBot → Allow: /
User-agent: PerplexityBot → Allow: /
User-agent: Google-Extended → Allow: /
…plus anthropic-ai and cohere-ai. Every major AI crawler, explicitly welcomed.
For a publisher whose content is the product, blocking these bots is a defensible business decision. For a local service business it isn't. Your website exists so people can find and choose you – and if the systems answering your customers' questions can't read your site, you simply don't exist to them. Blocking AI crawlers doesn't protect a local business; it just means the answer engines describe your competitors instead.
Decision Two: llms.txt
This site also serves an llms.txt file, plus a fuller llms-full.txt – an emerging convention that gives AI systems a plain-text map of what the site is, who runs it, and where the important pages live. Think of it as a sitemap written for a reader instead of a crawler.
Is it a proven factor in AI answers? No, and I won't pretend otherwise – it's early. The calculation is simpler than that: it costs twenty minutes, it can't hurt, and if the convention sticks, the sites that adopted it early get described accurately. That's the entire bet.
What AI Answers Actually Cite for Local Queries
Spend an evening asking AI tools about local services and the patterns surface fast:
- Sites that answer questions in plain language. Language models assemble answers from text that already reads like an answer. There are 1,651 marked-up questions and answers in this site's FAQ schema, and every one of them is a candidate sentence for an AI response about SEO in Tampa. That's not an accident.
- Review volume with substance. When an AI answer calls a business "highly rated," that traces back to Google reviews. Twenty detailed reviews that mention the service and the neighborhood beat fifty five-star drive-bys.
- A complete, consistent Google Business Profile. Category, services, hours, photos – answer engines lean heavily on profile data for anything "near me."
- Consistency across the web. The same name, address and phone number everywhere, and mentions on the directories and local sites these systems crawl and were trained on.
What Doesn't Work
- Keyword stuffing for language models. Same failure mode as stuffing for Google, new audience. Text written for machines reads badly to both machines and humans now.
- Hidden instructions to AI buried in your pages. Systems increasingly discard them, and it's a terrible look when a customer – or a journalist – finds them.
- Waiting for the dust to settle. The inputs above are identical to what already wins the map pack. There is no fork in the road yet where "AI optimization" and local SEO diverge – doing the work once covers both audiences.
Can You Measure Any of This?
Imperfectly, and it's worth being honest about that. In GA4, referral traffic from chatgpt.com and perplexity.ai is visible and worth a simple report. AI Overview appearances mostly hide inside ordinary Google impressions in Search Console, so you can't cleanly separate them. My honest read: treat AI referrals as an early-signal dashboard, not a KPI. The KPI is what it always was – calls, form fills and booked work.
What I'd Do This Quarter
- Check your robots.txt. Make sure you're not blocking GPTBot, ClaudeBot, PerplexityBot or Google-Extended by accident – some security plugins and CDN "bot protection" settings do exactly that by default.
- Add FAQ schema with real questions customers actually ask, each answered in two or three plain sentences. This is the highest-leverage hour on the list.
- Complete your Google Business Profile and respond to every review from here forward.
- Run your own audit from the outside: ask ChatGPT and Perplexity your money questions – "best [your service] in [your city]" – and note who gets named and what gets cited. That's your competitive read, free.
If the answer engines are already naming your competitors and not you, that's fixable – it's the same work as local SEO done properly, aimed at one more audience.
Want to Know What AI
Says About Your Business?
Ask the answer engines your own money questions and you'll see who they recommend – and who's missing. If you're missing, the fix is measurable, ordinary work. I can show you exactly where to start.
Book a Free SEO Audit