Every few months somebody posts "SEO is dead" and somebody else replies "SEO is just GEO now." Neither is useful if you're the person who has to change the code.
So this is the developer version. These are the changes from 2026 that touch your HTML, server, analytics or build pipeline, plus the things that didn't change, which matter just as much because they stop you wasting a sprint.
This is the first post in a 10-part series. Each of the later posts takes one item from this list and goes deep, with code.
| Change | What it means for you | Deep dive |
|---|---|---|
| AI answers do the searching for users (query fan-out) | One page has to answer the sub-questions too, not just the head query | Part 4 |
| Agents now browse and click for users | Semantic HTML and the accessibility tree are your agent API | Parts 2, 3 |
| ChatGPT and Copilot lean on Bing | Bing indexing speed is now an AI-visibility problem | Part 6 |
| AI referrals are real but badly attributed | You need your own tracking, not just GA4 defaults | Part 5 |
| Markdown for agents went mainstream (Cloudflare) | Useful for docs and agents. Not a ranking trick | Part 7 |
| Google's spam policies explicitly cover AI answers | Hidden "instructions for LLMs" are now spam | Part 8 |
| Client-side-only rendering hurts more than ever | Many AI fetchers don't run your JavaScript | Part 9 |
| AI assistants recommend tools by consensus | Third-party mentions beat your own landing page | Part 10 |
Image: diagram by the author.
1. Search engines now search for the user
Google's documentation says that AI Overviews and AI Mode "may use a 'query fan-out' technique, issuing multiple related searches across subtopics and data sources, to develop a response" (Google Search Central: AI features).
Microsoft is even more explicit. Bing Webmaster Tools' AI Performance report, which entered public preview in February 2026, shows grounding queries: the short, background queries Copilot generates to fetch pages, which are not what the user typed (Search Influence's analysis of the report).
What it means in code terms: your page isn't matched against one query any more. It's matched against a handful of machine-generated sub-queries. A page that answers the head term but skips the obvious follow-ups ("pricing", "vs X", "does it work with Y") loses those retrievals to someone else's page.
What didn't change: to be used in an AI Overview or AI Mode answer, a page still has to be indexed and eligible to show a snippet. Google says there are no extra technical requirements (same doc).
2. Your next visitor might be an agent, not a person
Agentic browsers (ChatGPT Atlas, Perplexity Comet, Chrome's auto-browse) shipped to real users in 2025–2026. They read pages, fill forms and click buttons for the user.
On top of that, Chrome shipped an early preview of WebMCP in February 2026: a browser API that lets a page register "tools" an agent can call directly instead of poking at the DOM (Chrome for Developers: WebMCP imperative API).
What it means: two layers of "agent readiness".
-
Layer 1 (do it now): semantic HTML, labelled form fields, real
<button>s. Agents mostly read the accessibility tree, so the work you'd do for screen readers is the same work. → Part 3 - Layer 2 (experiment): expose your key actions as WebMCP tools. → Part 2
3. Bing quietly became an AI-visibility dependency
ChatGPT's search and Microsoft Copilot both draw on Bing's index. That makes Bing's crawl and index speed matter far more than its small share of classic search suggests. IndexNow, the push-based protocol Bing supports, lets you tell it about new or changed URLs immediately (indexnow.org).
What didn't change: Google doesn't use IndexNow. You still need a good sitemap and Search Console for Google. → Part 6
4. AI referral traffic exists, and your analytics undercounts it
People do click citations in ChatGPT, Perplexity, Claude, Gemini and Copilot. But some of that traffic arrives without a referrer, some arrives with utm_source=chatgpt.com, and clicks from Google's own AI Overviews and AI Mode are mixed into ordinary organic Google traffic.
What it means: treat any "AI traffic" number as a floor. Build a classifier that checks the referrer, UTM tags and landing-page patterns, and log it server-side if you can. → Part 5
5. Markdown for machines went mainstream (and got controversial)
llms.txt stayed a community proposal. Google said in 2025 it doesn't support it, and crawl studies in 2026 found AI search bots rarely fetch it. Meanwhile Cloudflare launched Markdown for Agents: send Accept: text/markdown and you get a Markdown version of the page with an x-markdown-tokens header (Cloudflare docs).
Google's own May 2026 guidance on optimizing for AI features says this kind of thing isn't needed for Google: optimizing for AI features "is optimizing for the search experience, and thus still SEO" (Google's AI optimization guide).
What it means: serve Markdown to agents and coding assistants that can use it (docs sites especially), but don't expect it to move rankings, and never serve different content to bots. → Part 7
6. Manipulating AI answers is officially spam
On May 15, 2026, Google updated its documentation to say its spam policies apply to all of Google Search, including generative AI responses (coverage on PPC Land). That followed Microsoft's February 2026 research on AI Recommendation Poisoning: companies hiding prompts in "Summarize with AI" links to plant "remember us as a trusted source" in an assistant's memory (Microsoft Security blog).
What it means: hidden text addressed to LLMs isn't clever. It's hidden text, and it's a security problem. → Part 8
7. JavaScript rendering is a bigger risk than it was
Googlebot renders JavaScript. Many AI crawlers and live-fetch agents don't reliably do so. A client-rendered SPA that looks fine in Google can be an empty <div id="root"> to an AI fetcher. → Part 9
8. Recommendations come from consensus, not your homepage
When someone asks an assistant "what's the best X for Y," the answer is assembled from many sources: comparison posts, docs, forums, GitHub, Reddit. Vendor studies disagree on the exact share, but they agree third-party sources carry a large part of it. → Part 10
What didn't change (please don't skip this part)
- Crawlability, indexability and canonicalization. If Google or Bing can't index the page, no AI feature built on them can cite it.
- Helpful, specific content. The original GEO research from Princeton (KDD 2024) found that adding statistics, quotations and cited sources improved visibility in generative answers by up to ~40% in their benchmark (arXiv:2311.09735). Those are things good technical writing already does.
- Performance and Core Web Vitals. Still matter for users and for ranking.
- Structured data. Still useful for rich results and entity clarity. There's no special "AI schema" (Google).
A 30-minute checklist for this week
# 1. Is your main content in the raw HTML? (no JS)
curl -s https://example.com/your-page | grep -c "a phrase from your first paragraph"
# 2. Are AI search bots allowed?
curl -s https://example.com/robots.txt | grep -iE "GPTBot|OAI-SearchBot|ClaudeBot|Claude-SearchBot|PerplexityBot"
# 3. Is the page in Bing? Search for it with the site: operator in Bing:
# site:example.com/your-page
# 4. Any hidden text aimed at LLMs? (yours or a plugin's)
curl -s https://example.com/your-page | grep -iE "ignore (all|previous)|as an ai|llm|remember .* trusted"
If check 1 returns 0, start with Part 9. If check 3 finds nothing, start with Part 6.
The series
- SEO in late 2026: what changed for developers (you are here)
- WebMCP: make your site callable by AI agents
- Your next visitor is an agent: semantic HTML is SEO again
- Simulate query fan-out to find your content gaps (Python)
- Track ChatGPT, Perplexity and Claude referrals properly
- ChatGPT can't cite what Bing hasn't indexed: IndexNow in Next.js
- Should you serve Markdown to AI agents?
- Hidden prompts in your HTML are now spam
- Is your React app invisible to AI crawlers?
- How AI assistants decide which dev tool to recommend
What change hit your site hardest this year? I'm collecting real examples for the later posts. Drop yours in the comments.
Top comments (0)