Technical
SEO in 2026: What AI Search Actually Changed About Discovery
A year of daily publishing plus a year of AI search reshaping discovery gave me a field report that most SEO content cannot. Here is what actually changed for my site.
Traffic Source Shift
Early 2025 my traffic was 80 percent Google, 15 percent direct, 5 percent other. By March 2026 it is 52 percent Google, 18 percent direct, 14 percent ChatGPT referrals, 10 percent Claude referrals, 6 percent other. AI referrers are real and growing.
They behave differently than Google traffic. Higher intent. Longer sessions. Different conversion profile.
What Still Works
Clear titles. Good URLs. Real information. Article structure with headers. Internal links. Author bylines. Dates. None of this changed.
What Changed
AI engines reward articles that answer a specific question directly in the first paragraph. Google rewards articles that lead with context. Writing for both means leading with an answer and following with context.
Schema markup matters more. Not for Google. For AI engines. They parse it. Articles with clear structured data show up in AI answers more often than articles without.
The Format That Wins Both
Question-driven title. One-paragraph direct answer. Then context, nuance, code examples, and links. This format performs well in Google featured snippets and in AI citations. A format that did not exist as strongly in 2024 is now necessary.
What Stopped Working
Thin listicles built for keyword stuffing. Content mills. Generic AI-generated posts with no voice. Each of these got punished by Googles updates and ignored by AI engines at the same time.
The Measurement Shift
I now track AI referrer traffic as a first-class metric. Google Analytics and Plausible both surface it. Ignoring it in a 2026 reporting stack is professional malpractice.
Sources I now report monthly
- Google organic
- ChatGPT and Claude referrers
- Direct
- Newsletter clicks
- Social referrers (declining every month)Reading
Google Search Central and Schema.org are still the references. Adjust your output. The platforms changed.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read