Technical Search Everywhere Optimization (SEOx):The Engineering Guide
Search Everywhere Optimization (SEOx) means making your brand findable, readable and citable on every search surface — classic Google, answer engines (ChatGPT, Perplexity, Gemini), social search (TikTok, YouTube) and communities (Reddit). Most guides stop at theory. This one is the engineering implementation guide: llms.txt, HTTP content negotiation for AI agents, and @graph entity architecture — with live, verifiable examples.
What is Search Everywhere Optimization?
The citable definition: SEOx is the discipline of structuring your digital presence so your brand is found, understood and cited on any search interface — classic or generative. The term names a change in habits: people now put their questions to TikTok, YouTube and AI assistants as well, not to Google alone.
The strategy layer is well covered by the big publishers. What almost nobody covers is the technical layer: the work that makes your pages easy for machines to fetch, parse and quote correctly. That's this guide.
The three technical pillars of SEOx
llms.txt — a clean table of contents for AI tools
llms.txt is a Markdown file in your site root that offers AI tools a curated, noise-free map of who you are and what your content covers. Source note: the file is a proposal↗, not a standard, and Google Search ignores it explicitly, so whatever value it has lies outside Google Search (coding agents, for example). It should include: a one-paragraph brand definition, your core services with absolute URLs, and the exact phrasing you want quoted back.
Ours is live: verdantmindset.com/llms.txt. Note the structure — definition first, services as annotated links, an explicit "Authoritative phrases for citation" section.
HTTP content negotiation — serve Markdown to AI agents
AI agents waste tokens parsing your CSS, scripts and layout markup. Content negotiation fixes that at the protocol level: when a request arrives with Accept: text/markdown, the server returns the page as pure Markdown instead of HTML.
Try it against our live site:
curl -H "Accept: text/markdown" https://verdantmindset.com/en/services/sustainable-seo-growth/seo
You get clean Markdown — exactly what an agent that asks for this format receives. Implementation sketch on Next.js: a middleware that detects the Accept header on page routes and rewrites internally to a converter endpoint (HTML → Markdown via Turndown, scripts and styles stripped, Vary: Accept set so caches keep both representations apart). For Google Search none of this is a requirement: its guide to generative AI features in Search↗ says you need no Markdown versions, AI-specific files or special markup to appear there. It is a courtesy to agents, not a ranking lever.
@graph entity architecture — how AI knows who you are
The more explicit your entity graph, the less a machine has to guess who you are. A single JSON-LD @graph should connect: Organization (with taxID, address, sameAs), Person (founder, with consistent naming everywhere), Service nodes, and per-page WebPage/Article/FAQPage nodes referencing those identities via @id. An engine can then read how the pieces connect instead of inferring it, though nothing guarantees it takes the graph as written.
Two rules that decide citations: consistency (the same entity name and IDs across every page and platform) and verifiability (claims an AI can cross-check — published pricing, registered company data, measurable performance).
The editorial layer:Answer-first content
Every page should answer its core question in the first 40-60 words — definitively — then elaborate. A question written on the page, with its answer right below it, is easy to lift; FAQPage markup can describe the pair, but Google does not ask for it in AI Overviews. Write facts with sources, not adjectives.
Measuring SEOx:Share of Voice in AI answers
Rankings alone no longer describe your visibility. Track: how often AI assistants cite you on your niche questions (we use a 5-tries-average methodology — the same question, five separate sessions, because generative answers vary), brand mentions with and without links, direct brand searches, and the classic fundamentals (indexation, Core Web Vitals).
Implementation checklist
-
llms.txtin the site root — definition, annotated service links, authoritative phrases for citation - Content negotiation:
Accept: text/markdown→ Markdown response withVary: Accept - One
@graphJSON-LD connecting Organization, Person, Services, pages - Static HTML (SSG) — no content hidden behind client-side JavaScript
- Answer-first intros and visible Q&A on knowledge pages (
FAQPageoptional) - AI Share of Voice tracking with a repeatable methodology
We practice every item on this list — verifiably, on this very site. If you want your brand engineered the same way, start with a technical audit or explore our sustainable SEO service.
FAQ.PROTOCOL
Frequently Asked Questions
Corrections and updates
- October 31, 2026. The llms.txt section now calls the file what its author calls it, a proposal, and describes it as a map for AI tools rather than for crawlers. It no longer contrasts the file with robots.txt as if every crawler obeyed robots.txt: Google writes that robots.txt cannot enforce crawler behavior. Perplexity is gone from the places where the file might matter, since Perplexity's crawler documentation says nothing about its bots reading
llms.txton other sites. - October 29, 2026. Nothing here promises any more that AI picks up
FAQPagemarkup or the entity graph: Google asks for no special markup in its AI features, and a Markdown version of a page is a courtesy to agents, not a condition. The opening definition and the answer on who coined the term lost their unsourced dates, and the llms.txt answer now says what the file does not do.
