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

推荐订阅源

N
News and Events Feed by Topic
Malwarebytes
Malwarebytes
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
C
Cybersecurity and Infrastructure Security Agency CISA
F
Future of Privacy Forum
C
Cisco Blogs
T
The Exploit Database - CXSecurity.com
A
Arctic Wolf
S
Securelist
K
Kaspersky official blog
S
Schneier on Security
T
ThreatConnect
T
Tenable Blog
Spread Privacy
Spread Privacy
T
True Tiger Recordings
AWS News Blog
AWS News Blog
F
Fox-IT International blog
量子位
T
Threatpost
V
Vulnerabilities – Threatpost
C
CERT Recently Published Vulnerability Notes
Cisco Talos Blog
Cisco Talos Blog
GbyAI
GbyAI
宝玉的分享
宝玉的分享
腾讯CDC
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏
Cyberwarzone
Cyberwarzone
有赞技术团队
有赞技术团队
S
SegmentFault 最新的问题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
Visual Studio Blog
U
Unit 42
雷峰网
雷峰网
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Simon Willison's Weblog
Simon Willison's Weblog
O
OpenAI News
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
The Register - Security
The Register - Security
MyScale Blog
MyScale Blog
小众软件
小众软件
A
About on SuperTechFans
Last Week in AI
Last Week in AI
Y
Y Combinator Blog
博客园 - 三生石上(FineUI控件)
美团技术团队
Google Online Security Blog
Google Online Security Blog
P
Proofpoint News Feed
MongoDB | Blog
MongoDB | Blog

DEV Community

Managing multiple docker hub accounts using docker-use System Design Interview: Decentralized Web Crawler Metric Cardinality: High or Low? 4 Steps to Making the Right Choice 로컬 LLM 셋업 가이드 (v23) Cursor Review 2026 — Honest 'Not For Me' Take From a VSCode User Hello from rikuq — a practitioner blog for solo AI SaaS founders Why DevOps Engineers Need Practical Tutorials, Not Just Theory AI Agents in CI/CD: Give Them Context, Not Production Authority Why I Track HRV Every Morning (And How It Actually Changes My Day) Now I See Why Translators Are Panicking Over AI—Should Coders Panic Too? Diffusion Language Models: How NVIDIA's Nemotron-Labs DLM Is Killing Token-by-Token Generation Chatbots GPT pour le support client : ce que les équipes françaises ont réellement besoin de savoir I Hit the 1,232-Byte Wall So You Don't Have To Google Just Rebuilt the Search Box (Again) — But This Time It's Different Aether: A local Android assistant built with Gemma 4 BoxAgnts Introduction (1) — Out of the Box mkdev: trusted HTTPS for localhost, mapped by name Just one question, one answer. Why Java Still Rules the Programming World in 2026 Four Architectures for Letting Claude Edit Elementor (and Why We Shipped Clone-and-Mutate) yard-yaml 0.1.1: safer UTF-8 handling for YAML documentation I Built a Mac App That Keeps Your Clipboard in Sync Across All Your Android Devices Stop Using UUIDs: Why B2B SaaS Needs ULIDs in Laravel 🐘 I'm a non-technical founder who built a Slack approval tool. Here's what actually broke first. Open-Sourcing Our Game AI Stack — SDKs, Templates, and CLI Tools for NPC Dialogue I Built an AI System That Makes 1,000 Decisions a Day. Here's Where I Drew the Line. Lets Encrypt DNS Challenge with Traefik and AWS Route 53 Building an agent-ready website: how to make your site readable for ChatGPT, Perplexity and autonomous agents A productivity tool with GitHub as your cloud database How We Built Dynamic NPC Dialogue with LLMs — Lessons from Early Access cmux: The Native macOS Terminal Built for Running AI Coding Agents in Parallel Deep Atlantic Storage: Rewriting in Rust How I Built a Bulk Image Optimizer with $0 Server Costs Using Vanilla JS and Canvas API Humans and Machines read differently, I think I have a fix? Claude Code Deleted 92 Images Without Asking. This Happens More Than You Think. Method Calling Stack in Java I Built Schedule Sensei & Pushed It to GitHub – Here's What's Inside (And I Need Your Help 👀) OIC: From a Working Toast Watcher to a General "Watch It for Me" Agent Memory is two-thirds of what an AI chip costs to build The XState persistence problem is five years old. Here is what we built to finally solve it. i added MCP support to my SaaS in an afternoon. here's the whole thing. Framework: Link Building ☁️ Importing existing S3 buckets into Terraform state made easy with terraform import existing s3 bucket I Built a Token System on Solana (Without Any Backend Code) 터미널 AI 에이전트 구축 (v21) I Built an AI 3D Model Generator — Here's How I Handle Meshes in the Browser 🛡️ PromptGuard: I Built a Local AI Privacy Firewall That Sanitizes Your Prompts Before They Leave Your Machine PostgreSQL WAL Bloat: Why Automatic Management Is Often Insufficient? Seven PRs Before Lunch: Parallel Claude Code Tabs Plus Audit-Before-Bump Deployment using all three Kubernetes probes Qwen 3.6 Has Four Tiers. Here's How to Route Without Burning Cash. RAG 시스템 실전 구축 (v21) How I handle my errors in PHP The Blind Spot in Treasure Hunt Engine Configuration: Long-Term Server Health Run NVIDIA NIM on Your Own GPU — Same API, Different Endpoint Webflow SEO Implementation 로컬 LLM 셋업 가이드 (v21) How Logs Travel From Your EKS Pod to Datadog 𝗦𝘁𝗼𝗽 𝗖𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗙𝗼𝗿 𝗘𝘅𝗮𝗺𝘀, 𝗦𝘁𝗮𝗿𝘁 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗥𝗲𝗮𝗹 𝗦𝗸𝗶𝗹𝗹𝘀 How to Use EXPLAIN ANALYZE in PostgreSQL: A Visual Guide gRPC Performance: tonic (Rust) vs grpc-go Benchmarked at Scale Hack The Box (HTB): Cap Machine (Full Walkthrough) Visual Search Optimization studygemma: AI study buddy for CS students Architectural Tradeoffs in Webhook Idempotency and SaaS API Versioning One Open Source Project a Day (No. 75): Understand Anything - The AI Engine That Turns Any Codebase Into an Explorable Knowledge Graph From mock-only-works to real-world-works: 48 hours of reCAPTCHA debugging I built a free music tool AI Talking Avatar Pipelines Broke Our Ad CTR by 3.7% 800G to 400G Breakout: How to Scale 400G Networks with 800G Ports 터미널 AI 에이전트 구축 (v20) Topical Authority Architecture Inside Hermes Agent's Session Memory: What X-Hermes-Session-Id Actually Does How Logs Travel From Your EKS Pod to Datadog The Hidden Journey Inside / Kubernetes Is it safe to connect my bank account to AI? No Room — The World of Aying (8/12) Fossils — The World of Aying (10/12) Familiar Stranger — The World of Aying (9/12) Being Seen — The World of Aying (7/12) [I Ran an AI Agent for 30 Days Straight — Here's the Boring Engineering That Made It Work] Gemma 4: The 128K Multimodal Powerhouse in Your Terminal How to Consolidate Your QA Toolstack: A Practical Buyer's Guide The Thank-You Email Almost Nobody Sends (And Why That's Your Edge) Schema Types 2026 Idempotency Keys: The API Safety Net You're Probably Not Using How to let Claude see my Plaid bank data Kiro Did It: Build a Simple Portfolio Website with Kiro IDE | From Prompt to HTML Prototype Islands of Commerce: What Marketplace Founders Can Learn from 60 Years of Island Biogeography React Pointer Hooks: Hover, Long-Press, Double-Click, Scratch, and Click-Outside Without the Bugs Engineering decisions for my video call tool VBScript Still Lives: How a Custom Go VM Brought Classic ASP to Linux and Mac What Happens When You Teach Old Scripting Languages New Runtime Tricks? I Tested 6 AI Coding Assistants for a Month. Here's What Actually Works. Extendscript Still Has Life Afriex Webhook Integration Guide: Signature Verification, Event Handling, and Production Best Practices The Blind Alleys of Veltrix Configuration How an ESP32 Turned a LEGO WALL-E Into a Real Working Robot The Flawed Promise of Real-Time Event Handling SSH Login Taking Forever? Check Your DNS Settings Found 897 Fake Followers on DEV.to. Here's How I Proved It.
GEO vs SEO in 2026 — What Google's May Guidance Changed
Ravi Patel · 2026-05-25 · via DEV Community

Originally published on rikuq.com. Republished here for Dev.to's readers.

Google's May 2026 AI search guidance settled one debate: for Google's surfaces, AEO and GEO are "still SEO." Same crawl, same ranking, same E-E-A-T factors. Optimizing for AI Overviews is optimizing for Google search, period.

That sentence is accurate, and it ended a year of speculation about whether Google would build a separate AI crawl or weight different signals on its AI surfaces. They didn't. They reaffirmed that strong fundamentals win everywhere they own.

But the guidance ended one debate while leaving another wide open: what about the engines Google doesn't own?

ChatGPT runs on Bing. Claude runs on Brave. Perplexity runs on its own index. Each of those engines has its own crawl behavior, ranking signals, and citation patterns. None of them issued matching guidance saying "we're also just classical SEO." Optimizing for them genuinely is a separate discipline — what I cover in the four-index reality post.

This post is the honest read on what changed in May 2026, what didn't, and what you should actually do as a content creator or solo founder in the second half of the year.

I'm Ravi. I run Citare, a platform built specifically for tracking AI search visibility across these surfaces, so I've watched this debate from inside the operational reality.

The actual content of Google's May 2026 guidance

Three substantive points worth understanding precisely:

1. AI Overviews + AI Mode + Gemini use Google's main index.

No separate AI crawl. No special "AI-friendly" schema. No llms.txt requirement specific to Google. The same E-E-A-T signals, the same backlinks, the same internal linking architecture, the same site speed considerations — everything that worked for Google search in 2024 works for Google's AI surfaces in 2026.

This is a correction of widespread bad advice from 2024-2025. Many SEO content writers spent the last 18 months selling "GEO-specific" optimizations (custom JSON-LD types, AI-optimized schema, content rewrites for "LLM consumption"). Google's guidance was effectively: stop. None of that helps. Foundational SEO discipline does.

2. E-E-A-T weight increases on AI surfaces specifically.

The model has to decide what to cite. Weak-signal sources — anonymous content, content without verifiable authorship, content from sites without authority signals — get filtered out of AI Overview citations even when they rank on regular Google search. The honest implication: investing in real author identity, real bylines, and real entity verification is no longer optional for content that wants AI Overview presence.

3. Originality and first-party data are now table stakes.

The March 2026 core update already started rewarding originality. The May guidance made it explicit: rephrased takes on existing content collapse on AI surfaces faster than they do on classical search. The model can recognize when an article is summarizing what 50 other articles already said. AI surfaces don't cite restatements; they cite the source.

For content creators this means: every post needs at least one piece of first-party data (a number you measured, a screenshot you took, a verdict you reached) that no competitor can copy. If your post is rewritable from publicly available sources, AI engines will cite the publicly available sources, not you.

What Google specifically did NOT cover

The guidance was Google-shaped. They covered Google's surfaces and what works there. They didn't address:

  • ChatGPT/Bing behavior. Microsoft hasn't issued matching guidance.
  • Claude/Brave behavior. Anthropic hasn't published optimization guidance.
  • Perplexity behavior. Perplexity has issued some guidance but it's narrower than Google's.
  • Citation behavior across surfaces — Google's guidance was about ranking, not about how AI engines surface citations to users. Citation UX varies dramatically (Perplexity shows inline citations, ChatGPT shows linked sources at the bottom, Claude shows sources in a side panel, AI Overview shows a few cards).

The half of the AI search world Google doesn't own is still a genuinely different discipline. Anyone telling you "GEO is dead, just do classical SEO" is half-right and half-wrong — right about Google, wrong about the other ~40 percent of AI-mediated discovery.

The "GEO is still SEO" framing — when it's true vs not

True when:

  • You're optimizing for Google search (any surface — regular results, AI Overview, Gemini, knowledge panels)
  • Your audience primarily discovers content via Google
  • You're investing in fundamentals (E-E-A-T, backlinks, structured data, originality)

False when:

  • You need visibility in ChatGPT, Claude, or Perplexity specifically
  • Your brand is cited differently across AI engines (which it is, almost always)
  • You're trying to win citation slots in AI engine responses, not just ranking on classical search results
  • You're tracking AI search visibility, not just Google rankings

The honest one-line summary: GEO is still SEO inside Google's universe. Outside it, real multi-engine GEO is a distinct discipline.

What's genuinely changed in the optimization playbook

Five concrete shifts since 2024:

1. Padding for word count is dead.

AI extraction punishes filler. Articles bloated to "rank for length" now lose to tighter articles that say more in fewer words. Editorial discipline > length.

2. First-party data went from nice-to-have to table stakes.

Every serious post needs at least one number, screenshot, dataset, or experiment that no competitor has. AI engines cite the source of facts; if you're not the source, you're not the citation.

3. Real author identity matters more.

Bylines with photos, bios linking to verified social profiles, Person schema with sameAs entries to other owned properties (the entity graph). AI engines weight this heavily for citation trust.

4. FAQ schema is now extraction infrastructure.

Not just a Google SERP feature — AI engines extract FAQ Q&A pairs directly into responses. Articles with well-structured FAQs get cited more across AI surfaces, regardless of underlying engine.

5. "Last updated" dates became a citation factor.

Recency signals weight heavier in AI surfaces than they ever did in classical SEO. Articles with visible "Last updated [date]" and actual updates get cited; stale articles get filtered out even when they rank.

What did NOT change (and won't)

Classical SEO fundamentals still drive most of the work:

  • Backlinks still matter — especially on Bing (ChatGPT's index)
  • Schema markup still matters — especially Article, FAQPage, BreadcrumbList, Person
  • Site speed still matters — Core Web Vitals are a Google signal still
  • Internal linking still matters — for both classical SEO and AI engine context understanding
  • E-E-A-T still matters — now more than ever
  • Content quality still matters — and is more measurable now via AI extraction patterns

If you've been doing SEO right, 80 percent of your existing work still applies. The 20 percent shift is what this post is about.

The practical playbook — what to do as of May 2026

Universal (do these regardless of engine):

  1. Real author identity on every post. Photo, bio, Person schema with sameAs to your other properties.
  2. At least one first-party data point per post. Number, screenshot, dataset, verdict.
  3. FAQ schema with FAQPage JSON-LD on every post where Q&A pairs are natural.
  4. Visible "Last updated [date]" prominent at the top of every post. Update quarterly.
  5. Tight, decisive writing. No hedging. No filler for word count.
  6. Clean technical foundation. Site speed, structured data, internal linking, mobile-friendly. The basics.

Google-specific (works for AI Overview + Gemini + classical):

  1. Heavy investment in E-E-A-T — author credentials, demonstrated expertise.
  2. Backlinks from authoritative domains in your topical neighborhood.
  3. Topical cluster building — comprehensive coverage of related questions, internal linking between them.

Multi-engine GEO (works for ChatGPT/Claude/Perplexity beyond Google):

  1. Bing-specific: invest in backlinks (Bing weights them heavier than Google does today).
  2. Brave-specific: invest in freshness and independent sources (less domain-authority bias than Google).
  3. Perplexity-specific: invest in citable inline facts — specific numbers, named entities, extractable claims.
  4. Track per-engine visibility — single-engine rank tracking misses 40-60 percent of where your brand appears. Use a tool that watches all four indexes.

Skip these (they don't help):

  1. Custom "AI-optimized" schema beyond the standard types — no evidence any engine rewards it.
  2. Content rewrites specifically "for LLM consumption" — wasted effort; quality content works everywhere.
  3. Heavy llms.txt investment beyond shipping a basic one — uncertain ROI.
  4. "AEO-specific" agencies promising 10x AI search visibility — nothing structurally separates this from good SEO + multi-engine awareness.

The honest summary

Google was right about Google. Their AI surfaces use the same ranking as classical search, and the optimization is the same discipline. The 2024-2025 "GEO is a totally separate field" advice was largely wrong, and Google's May guidance correctly buried it.

Google was incomplete about the non-Google engines. ChatGPT (Bing), Claude (Brave), and Perplexity all behave differently, have different optimization profiles, and require separate attention if you want presence on those surfaces.

The practical work in 2026 is: nail classical SEO fundamentals (they're now table stakes), invest in first-party data and real author identity (the post-March-2026 differentiation), and track per-engine visibility across all four indexes if you care about the half of AI search Google doesn't own.

Anyone selling you a more complicated story than that is selling you something. The discipline is straightforward; the execution requires consistency.

Related reading


Last updated 2026-05-24. AI search guidance changes frequently — I refresh this when any major engine issues new direction. If your data points in a different direction from this advice, tell me on Twitter/X.