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

推荐订阅源

T
Tenable Blog
D
DataBreaches.Net
S
Secure Thoughts
B
Blog
S
Schneier on Security
Y
Y Combinator Blog
P
Proofpoint News Feed
C
Cybersecurity and Infrastructure Security Agency CISA
C
Cyber Attacks, Cyber Crime and Cyber Security
D
Darknet – Hacking Tools, Hacker News & Cyber Security
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
F
Full Disclosure
Engineering at Meta
Engineering at Meta
L
LangChain Blog
T
Threatpost
阮一峰的网络日志
阮一峰的网络日志
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The Hacker News
The Hacker News
月光博客
月光博客
大猫的无限游戏
大猫的无限游戏
Cyberwarzone
Cyberwarzone
T
The Exploit Database - CXSecurity.com
雷峰网
雷峰网
博客园 - 司徒正美
Help Net Security
Help Net Security
www.infosecurity-magazine.com
www.infosecurity-magazine.com
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
Application and Cybersecurity Blog
Application and Cybersecurity Blog
P
Privacy International News Feed
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
Vulnerabilities – Threatpost
Cisco Talos Blog
Cisco Talos Blog
L
LINUX DO - 热门话题
酷 壳 – CoolShell
酷 壳 – CoolShell
T
Threat Research - Cisco Blogs
Recent Announcements
Recent Announcements
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
H
Heimdal Security Blog
Jina AI
Jina AI
C
Cisco Blogs
Attack and Defense Labs
Attack and Defense Labs
Microsoft Security Blog
Microsoft Security Blog
L
Lohrmann on Cybersecurity
aimingoo的专栏
aimingoo的专栏
D
Docker
I
Intezer
C
Check Point Blog
Cloudbric
Cloudbric
小众软件
小众软件
V2EX - 技术
V2EX - 技术

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
From SEO to SEO + AEO + GEO — Web marketing as Context Ops in the AI search era
OKIKUSAN-PUB · 2026-05-29 · via DEV Community

📌 The full version (with 4 SVG figures and a related-article network) lives on my blog:

👉 https://okikusan-public.dev/seo-aeo-geo-context-ops.en

This dev.to post is the condensed version. The visualisations live on the canonical page.

Introduction

Marketers are sitting in the middle of the quietest, most destructive tectonic shift in twenty years.

The "type a keyword, click one of the ten blue links" routine is collapsing fast. Google's AI Overviews, Perplexity, ChatGPT Search — these AI search engines crawl the web on the fly and present "a single answer" in response to whatever complex question the user typed in.

The short version: "You don't need to throw SEO out. But on its own, it no longer works." From here on, AEO and GEO have to be stacked on top of SEO.

Five prerequisite terms

This article assumes the following background. Skim here if any are unfamiliar.

  • SEO (Search Engine Optimization) — getting found in the first place. Crawlability, semantic markup, speed.
  • AEO (Answer Engine Optimization) — getting picked as the direct answer by summarising AIs. TL;DR / answer-first / FAQ / comparison tables.
  • GEO (Generative Engine Optimization) — getting cited as the source for generative AI answers. First-hand experience, proof data, author attribution.
  • AI Overviews / Perplexity / ChatGPT Search — examples of AI search engines that crawl the web and summarise it into a single answer. They always attribute citations.
  • Context Ops — a concept growing out of LLMOps. Output quality is decided more by "what context you hand the model" than by "which model."

TL;DR

  • With AI search (Google AIO / Perplexity / ChatGPT Search) on the rise, the "ten blue links" SEO era is over.
  • The new paradigm is a three-layer stack: SEO (entrance) + AEO (the answer) + GEO (the citation). SEO is the foundation, AEO is the pick, GEO is the real battlefield.
  • AI crawlers measure cosine similarity in vector space. Commodity round-ups score zero information gain and get filtered out. Only first-hand experience and proof data survive as "unique nodes."
  • The essence of web marketing shifts to Context Ops — handing the right context to AI agents. Humans produce the tacit; AI cleans it into the explicit.

Chapter 1 — The Three-Layer Stack: SEO / AEO / GEO

Layer In one line Target Key optimisation
SEO Get found Search engines (the index) Crawlability, semantic markup, speed
AEO Get picked as the answer Answer engines (summarising AI) TL;DR, FAQ structure, answer-first, comparison tables
GEO Get cited in AI answers Generative AI (RAG / citations) First-hand data, proof logs, author attribution

The stack looks like this:

┌──────────────────────────────────────────────────────────┐
│  GEO (Generative Engine Optimization)                    │
│    cited as the source by generative AI answers          │
├──────────────────────────────────────────────────────────┤
│  AEO (Answer Engine Optimization)                        │
│    picked as the direct answer by summarising AIs        │
├──────────────────────────────────────────────────────────┤
│  SEO (Search Engine Optimization)                        │
│    the entrance — get found at all                       │
└──────────────────────────────────────────────────────────┘

Enter fullscreen mode Exit fullscreen mode

SEO is not dead. Even an AI search crawler has to discover and index your page before anything else can happen. Technically clean, semantic markup, fast loading — these remain the foundation layer on which AEO and GEO are built.

Chapter 2 — Vector search and the cosine trap

Why are the round-up sites and curation articles that used to dominate SEO getting wiped out of AI search citations?

Because of a cold algorithmic fact: AI search engines run on vector search and cosine similarity.

[ AI crawler's decision flow ]
   Web content
      ↓
   project into a multi-dimensional vector space
      ↓
   measure cosine similarity vs pre-trained data & other pages
      ↓
   ┌────────────────────────┐    ┌────────────────────────┐
   │ HIGH similarity (~99%) │    │ LOW similarity         │
   │ "already known"        │    │ "unique node"          │
   │ info gain ≈ 0          │    │ worth citing           │
   │ → DROPPED              │    │ → CITED                │
   └────────────────────────┘    └────────────────────────┘

Enter fullscreen mode Exit fullscreen mode

A round-up of stuff that lives on the internet gets scored at "99% similarity (= the AI already knows this perfectly)." No reason to load it as RAG context. Information gain is zero.

By contrast, content like the following sits far from the existing learned data in vector space, recognised as a "unique node":

  • Raw before/after logs from actually using your own product
  • The failure in a specific project, and the judgement you arrived at because of it
  • The tacit knowledge you scraped together on the ground, finally put into words

💡 This lines up perfectly with Google adding Experience to "E-A-T" in its search quality guidelines. In an era when AIs with no experience mass-produce commodity round-ups, content with "lived, first-hand proof data from someone who actually did it" gets prioritised. That's the official signal.

Chapter 3 — Marketing shifts to Context Ops

Getting your information "accurately understood by AI search and autonomous agents, and chosen as the basis for the user's decision" — at its core, that is Context Ops against the AI system.

Old web marketing:
└ hacks for the things humans see (display / traffic)

New web marketing (Context Ops):
└ hand the right context to AI agents and shape their reasoning

Enter fullscreen mode Exit fullscreen mode

The role-confusion trap with reasoning models

Here's the trap many companies and marketers fall into: "have the big reasoning model write the long blog post or the rambling explainer." It's a confusion of roles.

No matter how huge or clever the LLM, the documents it produces are statistically the average of its training data — "polite round-ups (commodity)." Outsourcing the actual creation lands you with both a hallucination risk and immediate removal from the AI search index by the cosine trap. Two collapse risks in one move.

The human-AI standardisation boundary

┌─────────────────────────────┐       ┌─────────────────────────────┐
│ Human (primary author)      │  →    │ AI (assistant)              │
│ Creating tacit knowledge    │       │ Cleaning into explicit form │
│  · raw field experience     │       │  · structuring & whiteboard │
│  · messy struggle           │       │  · semantic organisation    │
│  · unique judgement         │       │  · parser-friendly shaping  │
│  · measured evidence        │       │  · AEO/GEO optimisation     │
└──────────────┬──────────────┘       └──────────────┬──────────────┘
               │                                     │
               └──────────────┬──────────────────────┘
                              ↓
              ┌──────────────────────────────┐
              │ Clean knowledge on the web   │
              │ cited by AI / chosen by you  │
              └──────────────────────────────┘

Enter fullscreen mode Exit fullscreen mode

Ask the reasoning model to do the upstream work — brainstorming, structuring complex information, breaking tacit knowledge apart. For the final step of putting it into words, let the human (or a fast lightweight LLM) inject lived experience and emotional heat.

Chapter 4 — A template for the next-gen page

The rule for content design that wins AEO/GEO is one page, one point — narrow and deep, not wide and shallow.

# Layer Block What goes in Which AI eye reads it
01 SEO TITLE one-point title the indexed entrance
02 AEO TL;DR three lines / answer-first used for summarisation
03 AEO DIRECT ANSWER plain answer to the query picked by the answer engine
04 AEO DEFINITION clear terms & premises matches question terms
05 GEO PROOF DATA first-hand data / proof logs evidence the AI cites
06 GEO COMPARISON TABLE old vs new, side-by-side structured info gain
07 AEO FAQ explicit Q/A shape wired into answer engines
08 GEO UNIQUE TAKE author's judgement & hypothesis breaks the cosine trap

Stack these blocks top-down and you get a skeleton that catches SEO, AEO, and GEO all at once.

Closing

SEO is the entrance. AEO is the answer. GEO is the citation. And your unique perspective is the biggest citation asset of the AI Mode era.

Web marketing from here on is not a side-show of tactics for hacking search slots. It's a deeply intelligent, creative practice: extract the living tacit knowledge you earned on the ground, structure it into explicit context both AI and humans can read at a glance, and plug it into the global knowledge graph called the internet.


📌 The full version with 4 SVG figures and the related-article network is on the original:

👉 https://okikusan-public.dev/seo-aeo-geo-context-ops.en

Related (the author's adjacent threads)

Sources (official references)

How is the cosine trap showing up in your stack? Would love to hear which "unique node" you're trying to publish next. 🦄 💬