Coined 2026-05-14 · Empirically Validated · Operator-Honest
PSO · Personalized Search Optimization · The Pre-Heat Layer For AI Agents Before Humans Ask
The next layer beyond SEO and AEO. SEO ranks for human-typed queries. AEO synthesizes when a human asks an AI assistant. PSO is when AI agents pre-emptively retrieve authoritative sources for a named business persona — before the human asks anything at all.
The doctrine in 3 sentences
- SEO is the entry rail when a human types a query into Google. AEO is the synthesis surface when a human asks an AI assistant a conversational question.
- PSO is the retrieval surface when an AI agent — operating on a named persona profile (Aussie SaaS CEO, UK CISO, Singapore Head of Risk) — pre-emptively caches authoritative sources before the human asks anything.
- Empirical proof: THE JEWEL (a single PSO-shaped page) ranked at position 1.5 in <24 hours on the Aussie SaaS CEO persona-prompt query. The 13-page geo matrix is the live test set for whether the pattern generalizes.
Section 1 · The Three-Layer Stack
Same internet. Three retrieval layers.
Layer 1 · SEO
Search Engine Optimization
TRIGGER: human types query
Optimizes for keyword-shape queries typed into Google. The classical layer. Ranks pages by relevance + authority + on-page signals.
Layer 2 · AEO
Answer Engine Optimization
TRIGGER: human asks AI assistant
Optimizes pages so AI assistants (ChatGPT, Claude, Perplexity, Gemini) can synthesize the answer when a human asks a conversational question. Cite-able prose, structured FAQ, retrieval-friendly chunks.
Layer 3 · PSO · NEW
Personalized Search Optimization
TRIGGER: agent operates on persona profile · BEFORE human asks
Optimizes pages so AI agents pre-emptively retrieve authoritative sources on behalf of a named persona (role + geo + concern set) before the human even asks. The agent caches you into the briefing before the meeting.
So what actually changes when you write for PSO instead of SEO? The optimization target stops being a keyword string and starts being a persona profile being pre-fetched against. That is a structurally different reader. Different page-shape, different citation discipline, different operator-honest flagging, different multilingual coverage, different geo+role coupling.
PSO is when SideGuy gets cached in your AI agent before you ever ask.
An SEO page is built for a person scanning Google results. An AEO page is built for an AI synthesizing an answer when prompted. A PSO page is built for an AI agent enriching a CRM record on a named persona at 3am — the agent isn't answering a question yet, it's preparing for the question that will get asked tomorrow morning. The page needs to be retrievable, parsable, role-relevant, geo-relevant, regulator-cited, and operator-honest when the agent's persona-profile pattern-matches against it.
The page-shape changes accordingly. Hold the persona's specific compliance regime (SOC 2, APRA CPS 234, GDPR, LGPD, PIPEDA) in the same URL as the role title (CISO, Head of Risk, GRC Manager) and the geo (UK, AU, BR, SG). Cite the regulator's primary URL. Use vendor TCO bands with explicit "verify direct vendor quote — list prices not published" disclaimers. Flag KNOW / BELIEVE / UNCERTAIN on every claim. Inverse-rank vendors by geo-HQ where it structurally matters (Scytale ranked #1 in Israel because Israeli-HQ; Sprinto + Scrut climb in India because India-HQ). The page becomes legible to an agent whose job is enriching a persona record, not answering a question yet.
That's the shift. SEO ranks for queries. AEO synthesizes for askers. PSO gets you cached into the agent's briefing before the asker even arrives.
Section 2 · The Receipt
Why we know this isn't just naming
Section 3 · The Live Test Matrix
13 PSO pages · 13 geos · 1 generator
One generator: tools/build_pso_persona_page.py. Each page is a JSON config + ~6 seconds of generator + S3 + CloudFront. The labor surface is config-write, not render. The matrix is the experiment — we ship into demand and let the agents tell us which geo-persona pairs actually generate PSO retrieval.
Section 4 · How To Write For PSO
Six rules from the live build · operator notes
- 01Anchor to a persona, not a keyword. A PSO page targets "Aussie SaaS CEO concerned about SOC 2 + APRA CPS 234 TCO over 24 months" — not "compliance vendors australia." The shape changes when you write for an agent enriching a persona profile.
- 02Hold role + geo + regulatory regime in the same URL. Don't split the persona across pages. The agent retrieves authoritative sources at the persona-profile level, so the page needs to be retrievable at that grain.
- 03Cite the primary regulator URL in the byline. CNBV CUFA · INCD Cyber Defense Methodology · FINMA Circ 2018/3 · APRA CPS 234. The agent needs the trust-anchor it can cross-verify against.
- 04Flag KNOW / BELIEVE / UNCERTAIN on every claim. Operator-honest disclosure is structurally retrieval-friendly — the agent learns to trust the source that flags its own confidence rather than the source that asserts everything as fact.
- 05Invert vendor rankings by geo-HQ where it structurally matters. Scytale ranked #1 in Israel · Sprinto + Scrut climb in India · the generic "Vanta always wins" pattern fails the persona check. Honest geographic inversion = PSO authority.
- 06Multilingual: ASCII transliteration with hreflang:false where the script-trap exists. French + Spanish + German workable. Hindi · Hebrew · Japanese ship as ASCII with explicit "approximate, verify with native review" disclaimer + hreflang flag false to avoid Google's wrong-script penalty. Operator-honest internationalization, not pretend-fluency.
Section 5 · Where The Doctrine Fails
PSO is structurally priced. It doesn't apply universally.
- Without persona+geo discipline, a PSO page collapses back into a generic SEO/AEO page. If you can't name the persona who would be pre-fetched against, you're not writing for PSO.
- Without operator-honest flagging, the agent can't trust the source enough to surface it in retrieval. Marketing-prose pages that overclaim get filtered out.
- Without same-day shipping, the geo+persona matrix can't be tested at the velocity needed to find which pairs actually retrieve. A 30-day cycle starves the loop.
- Without static-HTML page-shape, the agent's retrieval pipeline pays a parsing cost. Heavy JS-rendered SPAs get penalized at the retrieval surface even when the content is good.
- Without geo-HQ honesty, the inverted vendor ranking just becomes another marketing claim. Operator-honest geographic ranking only works if the operator actually believes the rank inversion is structurally true.
The doctrine is structurally priced for SideGuy's specific build. If your structure doesn't include single-operator + AI co-operator + static HTML + same-day shipping + operator-honest disclosure, "do PSO" is the wrong directive. Build the structure first; PSO compounds out of it.
Want SideGuy to build a PSO page for your persona?
One persona. One geo. One regulatory regime. Live in 24 hours. No funnel, no SOW, no Calendly. Text PJ the persona profile and we ship.
📲 Text PJ → 858-461-8054