惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
人人都是产品经理
人人都是产品经理
IT之家
IT之家
T
The Blog of Author Tim Ferriss
V
V2EX
博客园 - 聂微东
The Cloudflare Blog
Blog — PlanetScale
Blog — PlanetScale
A
About on SuperTechFans
U
Unit 42
Vercel News
Vercel News
L
LangChain Blog
博客园 - 司徒正美
H
Help Net Security
Recent Announcements
Recent Announcements
Recorded Future
Recorded Future
V
Visual Studio Blog
Jina AI
Jina AI
Microsoft Azure Blog
Microsoft Azure Blog
GbyAI
GbyAI
Y
Y Combinator Blog
C
Check Point Blog
博客园 - 三生石上(FineUI控件)
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
J
Java Code Geeks
The Register - Security
The Register - Security
The GitHub Blog
The GitHub Blog
B
Blog RSS Feed
F
Fortinet All Blogs
B
Blog
G
Google Developers Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
云风的 BLOG
云风的 BLOG
爱范儿
爱范儿
MongoDB | Blog
MongoDB | Blog
F
Full Disclosure
有赞技术团队
有赞技术团队
罗磊的独立博客
博客园_首页
MyScale Blog
MyScale Blog
aimingoo的专栏
aimingoo的专栏
Google DeepMind News
Google DeepMind News
M
MIT News - Artificial intelligence
N
Netflix TechBlog - Medium
Engineering at Meta
Engineering at Meta
量子位
I
InfoQ
小众软件
小众软件
P
Proofpoint News Feed

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Why AI Search (GEO/AEO) Is Eating Traditional SEO — And What Agencies Must Do Now
WebCoreLab · 2026-05-15 · via DEV Community

Why AI Search (GEO/AEO) Is Eating Traditional SEO, and What Agencies Must Do Now

If you're still measuring SEO success by ranking positions, you're measuring the wrong thing.

I'll be honest: that sentence used to feel a little dramatic. It doesn't anymore. In 2024, Google's AI Overviews appeared on more than half of search queries in some categories. Perplexity went from niche to mainstream. ChatGPT became the first stop for millions of people who used to Google things. And a growing chunk of that traffic just stopped clicking through to any website at all.

Old-school SEO assumed one behavior. Person types query. Ten blue links appear. Somebody clicks.

That model is breaking in plain sight. Not everywhere, not overnight, but fast enough that agencies are seeing odd client dashboards: rankings steady, impressions weird, clicks down, conversions harder to explain. Why does this matter? Because the old reporting story no longer matches how people actually search.

Here's what's happening, why it matters, and three tactics we've found useful.


What GEO and AEO actually mean (and why the distinction matters)

Generative Engine Optimization (GEO) is writing and structuring content so AI systems (ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini) will surface, cite, or summarize it when answering a query. Unlike traditional SEO, GEO isn't really about links or domain authority. It's about whether your content is usable by an AI as a source.

Answer Engine Optimization (AEO) is the older sibling. It focuses on getting content into featured snippets, voice search results, and structured answer boxes. Those were the precursors to today's AI answers. AEO taught one useful lesson: format matters. Questions help. Direct answers help. Lists help, but not every answer needs to be chopped into a neat little list.

Most guides blur GEO and AEO together. That's only half right. AEO was about winning answer surfaces inside search engines. GEO is about becoming source material for systems that may never show a classic search results page at all.

Why the distinction matters: you can rank #1 organically and still get zero visibility in AI answers. We've seen it. A client sits at position one for a moderately competitive keyword, but when users ask ChatGPT or Perplexity the same thing, our client's site doesn't show up at all. A competitor with weaker backlinks but better-structured content does.

That stings.


What the data is actually showing

I want to be careful here and not invent numbers. What we see across client accounts is directional but real. In categories where AI Overviews appear often (health, finance, how-to, product comparisons), organic CTR has dropped 15–35% compared to 2022 baselines for the same rankings. Some queries that used to drive 400 clicks a month now drive 80.

A 2024 BrightEdge study found AI Overviews appeared on over 50% of queries across several verticals. Semrush data from late 2024 showed that position-one results in AI-heavy SERPs were getting less than 2% CTR in some categories.

The shift isn't uniform. Transactional queries with local intent are still relatively safe for traditional SEO. So are branded queries. Queries with strong visual intent have held up better too. The damage is concentrated on informational queries, especially the "what is," "how to," and product-comparison pages content teams have been publishing for years.

Counter to the usual panic, this does not mean every blog is dead. It means lazy informational content is a weaker asset than it used to be.

That's a lot of content investment quietly losing force.


Three tactics that actually work for GEO

I'll skip the vague advice. Here's what we've actually tested.

1. Write definitions AI systems can quote verbatim

AI systems want dense, self-contained answers. If your page defines a concept, that definition should work as a standalone 30–50 word block that answers the question without any surrounding context. Not "as we discussed above, this approach is effective because..." but a clean, quote-ready statement.

We rewrote several FAQ sections to follow this pattern. State the term. Define it in one tight sentence. Add one specific supporting fact or number when you have one. Pages that went through this treatment started appearing in Perplexity answers within 6–8 weeks.

Correlation, not proven causation. My take: that caveat matters, but it doesn't make the pattern useless. We've seen it often enough now to keep doing it.

2. Answer before you explain

Traditional content structure often buries the answer. Introduction, context, background, then answer. AI systems scrape for the direct response, and if it's on page three of your long-form article, they might find it or they might not.

The shift is simple: lead every section with the answer. One sentence, direct, no hedging. Then follow with explanation, examples, caveats, source context. This is sometimes called BLUF structure (Bottom Line Up Front), borrowed from military writing.

Is this overkill? For a 50-page site, no. It makes content more likely to be lifted into AI answers, and it also just makes for better writing.

3. Use named experts and specific sources, not "industry experts say"

Vague attribution ("experts believe," "studies show") is almost invisible to AI citation algorithms. Named sources with dates and publication context are not. When you write "according to a 2024 BrightEdge survey of 1,700 enterprise marketers," you're giving AI systems something to verify and attribute. When you write "experts agree," you're giving them nothing.

This is more work. No way around it. It means actually citing sources instead of gesturing at them.

Yes, this contradicts some old SEO advice about keeping pages clean and frictionless. Bear with me. For GEO, attribution is not clutter; it's a parsing aid. In our experience, pages with specific attributions consistently outperform vague ones in AI citation surfaces.


What definitely doesn't work anymore

Keyword density. If you're still manually targeting a keyword 12 times per 1,000 words, you're doing something that no longer correlates with AI visibility. AI systems understand topic coverage, not keyword repetition.

Skip this step.

Thin "pillar pages" with no original insight. A 3,000-word page that summarizes what five other pages already say is not a GEO asset. AI systems tend to prefer sources that add something: a specific dataset, a case study, a defined methodology, an original opinion. Generic overviews are easy to skip when there are thousands of them.

Ignoring structured data for Q&A content. FAQ schema, how-to schema, and article schema don't guarantee AI citation, but they help AI systems parse your content structure. Skipping them when you have FAQ content is leaving a low-effort signal off the table.

One more thing has started to matter, in ways most agencies are only beginning to measure: brand entity recognition. If your brand isn't a recognizable entity to AI systems (no Wikipedia presence, no Wikidata entry, inconsistent NAP across the web), you're harder to cite with confidence. Building entity recognition is slow. Annoyingly slow, sometimes. But the benefits compound across both GEO and traditional SEO.


What agencies specifically need to do differently

If you're running an SEO agency, the challenge isn't only technical. It's how you explain this to clients.

Clients who hired you to improve rankings need to understand that rankings are now one of several visibility metrics, not THE metric. You need to start tracking AI visibility separately. How often does the client's brand appear in ChatGPT or Perplexity responses for target queries? There are emerging tools for this. AI Rank Tracker, Search Response, and Profound are early-stage but getting more useful. Manual spot-checking is also just honest work.

The agency value proposition has to shift too. "We'll get you to page one" is a weaker promise when page one increasingly means an AI answer box that doesn't send clicks. The new pitch sounds more like "we'll make you the source AI systems cite, and the brand users recognize when they search for themselves."

That's harder to sell. I don't love that, but it's the accurate pitch.

Agencies that figure out how to audit for AI visibility, measure it consistently, and charge for that work will have a service that's genuinely different for the next few years. The ones that don't will keep selling something that's quietly losing power.


What I think is actually going to happen

My read: traditional SEO doesn't disappear. Local SEO, product SEO, and branded search stay relevant. But informational content (the "what is," "how to," "best of" content that's been the backbone of most content marketing programs for a decade), that's going through a real shift.

The volume of AI-answered queries will keep climbing. CTR to organic results for those queries will keep dropping. The content that does get surfaced in AI answers will increasingly belong to sources that figured out early how AI systems pick and cite content.

Here is the uncomfortable part: being "good at content" may not be enough. You can write a useful page, rank it, and still lose the AI answer to a page that is easier to quote, easier to verify, and clearer about who is making the claim.

There's also the flip side. Brands that get cited consistently by AI systems build a different kind of trust. When ChatGPT recommends your methodology or Perplexity cites your research, that's a signal that compounds. Harder to build than a backlink, but harder for someone else to replicate too.

It works.


FAQ

What's the difference between GEO and traditional SEO?

Traditional SEO optimizes content to rank in search engine results pages (SERPs) based on factors like backlinks, domain authority, and keyword relevance. GEO (Generative Engine Optimization) optimizes content to be cited, summarized, or recommended by AI-powered answer engines like ChatGPT, Perplexity, and Google AI Overviews. These are systems that synthesize answers instead of returning a list of links.

Does GEO replace SEO, or do they coexist?

They coexist, at least for now. GEO and SEO share foundational principles (quality content, E-E-A-T signals, structured data), but GEO adds requirements around quotable content structure, named sources, and entity clarity. Most agencies need to run both in parallel instead of treating them as alternatives.

Which AI tools matter most for GEO visibility right now?

In 2025–2026, the most consequential surfaces are Google AI Overviews (highest volume), Perplexity (high engagement among technical audiences), and ChatGPT browse mode. Claude's web search is growing. For most brands, Google AI Overviews should be the first priority simply because of search volume. Perplexity is disproportionately influential with developer, researcher, and SaaS buyer audiences.

How do I know if my content is being cited by AI systems?

Manual testing is the most accessible starting point. Run your target queries in Perplexity, ChatGPT, and Google AI Overviews and note which sources get cited. Tools like Profound and Search Response offer more systematic monitoring.

This is still an emerging area. There's no mature GA4 equivalent for AI visibility yet, which is part of why it's worth tracking now, before it gets crowded. My take: the teams that start logging this manually now will understand the market before the dashboards get polished.


We run GEO audits for clients at webcorelab.com.