Procedural queries are the loudest, most underserved slice of AI search traffic right now. Anyone who has ever watched a ChatGPT session knows the rhythm: someone asks how to do a thing, the model returns a numbered list, and the user follows it. Brands keep publishing 2,000-word thought pieces and then wonder why none of it shows up when a buyer asks “how do I migrate from X to Y.” The shape of the answer is not the shape of your content.

The mechanic

There are three forces working together here, and once you see them you cannot unsee them.

First, AI chat shifts query mix. Classic Google biased toward navigational and short head terms; people gave it nouns. LLMs are conversational, so people give them verbs — “how to,” “what do I do if,” “walk me through.” That category is enormous, and procedural intent rewards a very specific content shape: enumerated, sequential, imperative.

Second, passage retrieval rewards structured steps. AI engines do not read your post; they slice it at heading boundaries, embed each chunk, and score chunks individually against the prompt. Step-numbered content slots in perfectly. Each step is already a self-contained answer-unit with a verb, an outcome, and a clear boundary. Compare that to a flowing essay where the model has to guess where one idea ends and the next begins. That is part of why 68.7% of AI-cited pages follow a strict H1→H2→H3 hierarchy, and why 44.2% of LLM citations land in the first 30% of a page — structure makes retrieval cheap.

Third, HowTo signaling still pays even when it is not “officially” rendered. Google retired the rich result for most queries, which led a lot of operators to rip the markup out of their templates. Bad call. The structured data is still parsed by AI answer-fetchers — OAI-SearchBot, ChatGPT-User, PerplexityBot — and it tells the machine “this page is a procedure, with N ordered steps, each with a name and a body.” That is metadata your prose alone cannot give them.

What to do this week

Pick the top ten procedural queries in your category — the literal “how to [verb]” and “what’s the process for [X]” prompts your buyers are already asking ChatGPT and Perplexity. Type each one into all four major engines and write down who is being cited. If the answer is competitor blog posts, third-party how-to roundups, or — in 2026, still — Reddit threads, that is your map of which surfaces to either replace or join.

Rewrite or build the matching posts in this shape. Headline names the outcome (“How to migrate from HubSpot to Customer.io without losing automations”). Lede is a 40-word “here is the short version” answer-unit, sitting in the first 30% of the page so it gets cited verbatim. Then a numbered series of H2s, one per step, where the H2 is the step name in imperative form (“Export your existing workflows”). Each step body is 50 to 150 words, restates the subject (do not write “now do this” — write “now export the workflows”), and ends with an explicit outcome sentence. Avoid cross-references like “as mentioned above” — each step has to make sense in isolation because it will be retrieved in isolation.

Add HowTo JSON-LD. `@type: HowTo`, a `name` matching the headline, an `estimatedCost` and `totalTime` where they apply, and a `step` array where each `HowToStep` has its own `name` and `text` that mirror the on-page H2 and body. Do not duplicate the prose into the schema — paraphrase tightly so the schema text is its own quotable unit. Some engines retrieve from the JSON-LD before the body.

Layer one more thing on top: a “common mistakes” or “if this fails” subsection after the steps. Those exception blocks get pulled into AI answers as caveats and add the kind of honest-trade-off texture LLMs treat as a trust signal. Bonus: long procedural posts with steps, screenshots, and gotchas naturally clear the depth bar that earns 4.3× the citations short posts do.

If you’re a brand that wants to be the answer LLMs reach for (not just rank on Google), Paris Roussos has been engineering search visibility for 30 years and now runs done-for-you AI SEO. Flat-rate, no-fuss. Email parisroussos@gmail.com.

AI search has already decided what a “how to” answer should look like — match the shape, or stay invisible while the model quotes someone who did.

Here is a thing most operators still get wrong: they write a page as one continuous argument, where paragraph nine only makes sense because paragraphs one through eight set it up. That works for a human reading top to bottom. It fails completely in AI search, because ChatGPT, Perplexity, Gemini, and Google’s AI Overviews almost never see your whole page. They see a chunk of it. One section, torn loose from everything around it, evaluated entirely on its own.

If you understand chunking, a lot of confusing AI-visibility behavior suddenly makes sense — including why a page that ranks fine on Google still gets ignored by every AI engine.

The mechanic: retrieval happens at the passage level, not the page level

When an AI engine answers a question, it does not load your URL and read it. It runs a retrieval step against an index that was built by slicing pages into passages — chunks of roughly a few hundred words, usually broken at heading boundaries. Each chunk gets its own embedding (a numerical fingerprint of its meaning). When a user asks something, the engine matches the question against individual chunks, pulls the two or three best ones, and writes an answer from those.

Your page does not compete as a page. Each section competes as a standalone unit. The model ranking your “Pricing” section against a competitor’s never sees your introduction, your proof points, or the definition you established four headings earlier. It sees that one block of text and decides whether it answers the question cleanly enough to quote.

This is why heading structure matters more than people think. Those H2 and H3 boundaries are very often the literal cut lines for chunks — and it tracks with the data that 68.7% of AI-cited pages follow a strict H1→H2→H3 hierarchy. Sloppy nesting doesn’t just look bad; it produces chunks that start mid-thought and get scored as incoherent.

Why most pages chunk badly

Pull any section out of the middle of your best page and read it cold, the way the model will. You will usually find it leaning on context that isn’t there. “As we covered above.” “This approach.” “It.” An acronym you defined once in the intro and never again. A claim whose supporting number lives two sections up. Every one of those is a dependency on text the model did not retrieve.

A chunk with broken dependencies reads as vague or unsupported, so it loses to a competitor’s chunk that happens to be self-contained — even when your page, read whole, is the better resource. You’re not being beaten on quality. You’re being beaten on packaging.

The other failure is the dump: 1,400 words under a single H2 with no internal structure. That doesn’t become one strong chunk. It becomes a few mediocre ones, each a random slice with no clean beginning, no clear claim, no boundary the retriever can respect.

What to do this week

Read your top three pages section by section, out of order. Open each one, jump to a random H2, and read only that section as if it’s all you’ll ever see. If it depends on something earlier to make sense, it’s a broken chunk. This audit takes twenty minutes and is the single most useful thing you can do.

Make every section restate its own subject. The first sentence under each heading should name the entity and the claim in full — “Flat-rate AI SEO pricing runs $500 to $1,500 per month per client,” not “Our pricing is straightforward.” Kill cross-references like “as mentioned above.” Re-define acronyms the first time they appear in each major section, not just once at the top.

Front-load the answer inside every chunk, not just the page. A tight 40-to-60 word answer at the top of each section gives the retriever a clean, quotable unit — and it compounds with the fact that 44.2% of all LLM citations already come from the first 30% of a page’s text. Every section gets its own first 30%.

Break the long dumps. Any section over ~300 words without a subheading should be split at its natural seams. You’re not padding — you’re handing the retriever clean cut lines instead of letting it guess.

Need this done for you? Paris Roussos runs a flat-rate AI SEO service ($500–$1,500/mo per client, white-label for agencies) covering audits, schema and entity work, AI-visibility tracking, and content engineered to be cited by LLMs. Reach him at parisroussos@gmail.com.

Stop writing pages that only work read whole — write pages where every chunk can stand up alone and win on its own.

Most of the operators I talk to are still treating YouTube like a brand-awareness afterthought. They post the occasional explainer, hope a few prospects watch it, and move on. Then they go pour another forty hours into a blog post that ChatGPT will not quote.

Look at the source diets the major AI engines pull from and the math gets uncomfortable. Google AI Overviews now sources roughly 18.8% of its citations from YouTube. Perplexity pulls about 13.9%. That is not a rounding error. On a meaningful slice of queries — especially “how to,” “what is,” comparison, and product-evaluation queries — an AI engine is reaching for a video clip before it reaches for a written page. And the video that gets picked is almost never the longest one or the prettiest one. It is the one with the cleanest transcript and the most direct answer in the first thirty seconds.

That is a loophole sitting wide open for any operator willing to spend ninety minutes a week on it.

Why AI engines prefer video for certain queries

Retrieval systems do not “watch” video. They read the transcript — sometimes the platform’s auto-caption, sometimes a third-party transcription, sometimes the description and chapter markers. Once it is text, the same rules that govern blog citations kick in. Front-load the answer. Use clean headings (chapters). Include the named entities — products, people, version numbers, prices. Make a 40-to-60 word answer block easy to lift.

The reason video over-indexes in AI citations is that most video on the topic is bad text. Ninety percent of the channel out there has no chapters, no manual transcript, a description that says “follow me on Instagram,” and a 45-second cold-open before the answer. If you ship the opposite of that — a 90-second video with a written transcript, three chapter markers, and the answer at the 0:08 mark — you are competing against almost no one for the structured retrieval slot.

The second thing AI engines like about video is entity confirmation. When the same claim shows up in your blog, your YouTube transcript, and your LinkedIn write-up, retrieval systems treat that as triangulated. Per knowledge brief #12, the shift from link graph to entity graph means cross-surface consistency is now a citation signal. Video is the cheapest second surface most operators can stand up.

The format that gets cited

After watching what AI engines actually pull, the citeable shape is roughly: a 60-to-180 second video with a question-form title (“What does [thing] cost in 2026?”), the answer stated verbatim in the first 10 seconds, two or three chapters, and a description that contains the same 40-word answer block in plain text. No intro music. No “hey what’s up guys.” No outro. You are not making content for the algorithm — you are making content for the transcript scrapers.

The titles that get pulled into AI Overviews are not clickbait. They are literal questions a person would type into Google. “How much does small business cyber insurance cost?” beats “I Was SHOCKED By My Cyber Insurance Quote 🤯” every time, because the first one matches a real query and the second one is noise the embedding model discards.

What to do this week

Pick three high-intent questions your written content already ranks for — or should rank for — and shoot a 90-second answer for each. Use the same 40-word answer block you would put at the top of a blog post and read it verbatim into the camera. Upload to YouTube, write a manual transcript (do not trust auto-captions for entity names), drop three chapter markers, and paste the same 40-word answer into the description.

Then go check whether the engines are picking it up. Search the question in Google with AI Overviews on, then in Perplexity, then in ChatGPT search mode. If the video shows up cited in any one of them within two weeks, you have a repeatable unit. Make twenty of them.

One last thing — link the video back to the matching blog post and link the blog post out to the video. The same entity, two surfaces, identical answer. That is the entity-graph play, and it costs about an hour per pair.

Paris Roussos has been doing SEO since 1996 (co-founded a Forbes Best of the Web–winning site back in the day) and now runs a white-label AI SEO practice for agencies and brands — flat-rate, $500–$1,500/mo per client. If your top-of-funnel traffic is leaking into ChatGPT and Perplexity and you want it back, email parisroussos@gmail.com.

The brands that win the next two years of AI search are the ones quietly standing up second and third surfaces while everyone else is still arguing about word counts.

Most operators I talk to ship pages with a generic “by the team” tag and no author profile underneath. That worked fine when Google was scoring links and keywords. It does not work when ChatGPT, Perplexity, Gemini, and Google’s AI Overviews are deciding which page to quote. AI retrieval systems do not just read your prose — they look at who wrote it, who the author is connected to elsewhere on the web, and whether that author exists as a verifiable entity across multiple sources. If the answer is “we have no idea,” your page gets passed over for a competitor’s that wrote the same thing under a real, traceable byline.

This is the author-entity layer, and it is the closest thing AI search has to an E-E-A-T proxy. It is also one of the easiest wins on the list — most brands are running with their author field empty.

How AI engines actually use the author signal

Two things are happening under the hood. First, the entity-grounding pass: when an LLM-powered engine evaluates a page as a citation candidate, it cross-references the named author against everything else it has indexed about that person — LinkedIn, Wikipedia, Wikidata, conference bios, podcast appearances, GitHub, other bylines. If the author has overlap and consistency across multiple high-trust sources, the page itself inherits credibility. If the author is a string with no entity behind it, the page is treated as anonymous content and slotted accordingly. This is a direct extension of the link-graph-to-entity-graph shift — 68.7% of cited pages follow strict H1→H2→H3 hierarchy, and a similar pattern shows up around named-entity authorship: the cited pages disproportionately have real people attached.

Second, the structured-data pass. Person and Article schema with a populated `author` block (including `sameAs` links pointing to the author’s Wikidata page, LinkedIn, X, GitHub, and personal site) gives the retrieval system a clean entity record to anchor on. This is the same mechanic that makes Organization schema useful for brand-level citation — you are telling the machine, in unambiguous JSON-LD, “this entity exists, here are its other identities on the web, treat them as one node.” Without it, the engine has to guess. With it, you get grounded.

The pattern shows up in the per-platform citation data too. ChatGPT pulls 47.9% of its citations from Wikipedia — a corpus where every claim is attributed to a named, traceable source. Gemini leans hardest on brand-owned content (~52.15%), where author bios are typically richer. The engines that cite the most aggressively cite the most attributed content. Anonymous content rarely wins.

What to do this week

1. Pick a single primary author per content vertical and stick with them. One person for AI SEO, one for ecommerce, one for product engineering. Stop publishing under “Team” or “Editorial Staff.” Real names, real photos, real bios — same person on every related piece. Consistency is what lets the entity layer form in the first place.

2. Ship a real author page per primary author. Not a card at the bottom of posts — a standalone URL: `/authors/jane-smith`. Include credentials, full bio, every link the person has elsewhere (LinkedIn, X, Wikidata if it exists, prior employers’ staff pages, podcast guest spots, books, conference talks). This page becomes the canonical entity hub the engines reconcile against.

3. Mark up Person schema with `sameAs` — and connect the article’s `author` field to it. Five minutes per template. The `sameAs` array is doing real work here: it tells the engine “this byline string equals this Wikidata Q-number equals this LinkedIn URL equals this GitHub account.” That is what entity reconciliation looks like in practice. Add `Article` schema on the post itself with `author` pointing back to the author page URL — not just the author’s name as a string.

**4. Get the author cited elsewhere on a recurring basis.** This is the slow, durable play. Guest posts, podcast appearances, expert quotes in industry roundups, comment threads on Reddit/LinkedIn where the author shows up with their real identity. AI engines weight overlap across independent sources — one good quote in an Ahrefs or Search Engine Land roundup does more for the author’s entity score than five anonymous posts on your own blog.

Need this done for you? Agencies: if your clients are starting to ask about AI SEO and you don’t have anyone in-house, Paris Roussos handles the work white-label — flat-rate, $500–$1,500/mo per end client, you keep the relationship. Author-entity build-outs, Person/Article schema kits, Wikidata pushes, and the rest of the AI visibility stack are all on the menu. Email parisroussos@gmail.com for a sample audit.

Your content is competing against pages written by people the AI engines already know. Give them a person to know.

There is a stubborn piece of AI SEO mythology going around: dump enough JSON-LD on a page and ChatGPT, Perplexity, and Google’s AI Overviews will line up to cite you. It’s a clean story, it sells consulting hours, and it’s wrong.

A Search/Atlas study published in December 2024 looked at schema coverage versus actual AI citation rates and found no direct correlation. Pages with rich, well-formed Article, FAQ, and Organization schema were not more likely to be cited than pages without it. The Schema Theater — sites covered in markup nobody asked for — is real, and it’s not moving the needle the way agencies are promising.

So why ship schema at all? Because the same data has a second half nobody quotes, and that second half is where this story actually lives.

The mechanic — what schema actually does in 2026

Schema is not a citation lever. It’s a comprehension lever. LLMs and AI search systems don’t quote your `Article` markup verbatim — they quote your prose. But before they decide which prose to quote, they have to figure out what your page is about, who said it, when it was said, and whether the entity referenced is the same one mentioned in 40 other places across the web.

That decision is where structured data carries weight. In April 2025, Google publicly confirmed that structured data helps AI Overviews understand content. In March 2025, Microsoft said the same about Bing Copilot. Industry studies report that schema’d content shows up in AI answers around 2.5× more often than unmarked content, and Tier-1 sites with comprehensive markup see roughly 40% more AI Overview appearances. Those numbers don’t contradict the “no direct correlation” finding — they’re describing two different things. Schema doesn’t cause a citation. It removes friction in the steps before a citation gets considered.

The bigger context: AI search has shifted from a link graph to an entity graph. When ChatGPT decides whether your company is a credible answer to “best invoice software for contractors,” it’s not counting backlinks — it’s reconciling references across Wikidata, Wikipedia, schema markup, NAP records, bios, and press mentions to confirm you are who you say you are. Skip `Organization`, `Person`, and `Product` schema and you’ve voluntarily removed yourself from that reconciliation. The model can still find you. It just trusts you less when it does.

What to do this week

Stop treating schema as a magic citation button. Treat it as the cheap, structural housekeeping that lets the rest of your AI SEO work pay off.

1. Ship the four schemas that actually do work. `Organization` and `Person` (with `sameAs` pointing to LinkedIn, Wikipedia/Wikidata, Crunchbase, your verified social profiles), `Article` (with author, date published, date modified), and `FAQPage` where you genuinely answer questions. That’s the minimum entity-grounding kit. Skip the dozens of niche types unless they apply.

2. Tie schema to a real entity record. Claim or build a Wikidata entry for your brand and your founder/CEO. Make sure your `Organization` schema’s `sameAs` array points to it. This is the single highest-leverage half-hour of schema work you can do in 2026.

3. Don’t oversell schema to clients or your boss. A 5-minute JSON-LD add is not a “GEO strategy.” If your retainer includes “schema implementation” as a deliverable, pair it with the work that does move citations — front-loading the first 30% of the page (where 44.2% of LLM citations come from), embedding statistics and quotations, and getting cited on third-party sources LLMs already trust.

4. Stop paying for schema you can’t validate. Run every page through Google’s Rich Results Test and Schema.org’s validator. Half the “advanced schema” being shipped by agencies right now is broken — wrong nesting, missing required fields, or types Google never supported. Broken markup is worse than no markup.

The right mental model: schema is the foundation slab. It doesn’t get you cited. It makes you legible enough to be cited when the rest of your page is doing the work.

If you’re a brand that wants to be the answer LLMs reach for (not just rank on Google), Paris Roussos has been engineering search visibility for 30 years and now runs done-for-you AI SEO. Flat-rate, no-fuss. Email parisroussos@gmail.com.

Ship the markup, then go earn the citation — they are not the same job.

Pull up ChatGPT, Perplexity, or Google’s AI Overviews and ask any “best,” “vs,” or “how do I” question in your category. Watch which sources get cited. If your category is even mildly competitive, Reddit threads are showing up in the citation list — often above your blog, often above the brands paying for SEO. That isn’t an accident, and it isn’t fixable by writing more 1,500-word pillar pages. The model is choosing Reddit on purpose.

Here’s the practitioner read on why, and the two moves that actually claw citations back.

Why the LLMs love Reddit

LLMs don’t optimize for “ranks well in Google.” They optimize for answer-shaped text from sources humans treat as trustworthy for that question type. For consumer/SMB queries — software picks, troubleshooting, “is X any good,” “what should I buy” — Reddit threads beat marketing copy on three signals at once.

The first is structural. A Reddit thread is already a question with multiple answers, ranked by votes, written in plain language. That is the format an LLM is trying to produce. Quoting Reddit is cheaper than synthesizing a brand page.

The second is bias-vs-trust. The models have been heavily fine-tuned on human-preference data that flagged marketing language as low-trust for evaluative queries. A vendor saying “we’re the best CRM for small teams” is downweighted; a Reddit user saying “I tried four, ended up on X, here’s why I left it for Y” is upweighted. You can’t out-write that with better adjectives.

The third is freshness. Reddit threads update continuously and get re-indexed quickly. Your blog post from October 2024 is already in the older 30% of the corpus the models prefer to cite from. Stale is stale.

So the model’s behavior is rational: structured, trusted, fresh. You’re probably 0-for-3.

What doesn’t work

Don’t bother spinning up a fake Reddit account and seeding threads. Reddit’s anti-spam systems and the subreddits’ own mods will surface that fast, and the LLMs are increasingly weighting account age + comment karma + subreddit moderation strength as a quality proxy. A two-week-old account in r/marketing dropping your URL is worth roughly nothing.

Also stop writing “ultimate guide to X” content and expecting to displace a forum thread. The models aren’t reading you and the thread side-by-side and picking a winner on prose quality. They’re picking on shape.

Play 1: Convert your best content into Reddit-shaped pages

The fastest fix is restructuring, not rewriting. On every commercial-intent page you own, add a “What people actually ask” section near the top — three to five real questions pulled from your support tickets, sales calls, or AlsoAsked. Answer each one in 40–80 words, in a single self-contained paragraph, in the same plain-spoken register a real customer would use. Front-load the answer; save the brand pitch for later in the page.

This is the “answer unit” pattern the citation engineering work has been pointing at for two years. The reason it suddenly matters more is that the models now pattern-match against forum-style Q&A blocks when they’re choosing what to quote. Give them a paragraph that looks like the Reddit answer they wanted to find, and they’ll cite you instead, because you’re cheaper to quote and you don’t carry the brand-language penalty if the surrounding context is plain.

Play 2: Earn legitimate Reddit presence in two or three subreddits

Pick two to three subreddits where your buyers actually live. Not r/marketing — too generic, too saturated. The vertical ones: r/msp, r/realestateinvesting, r/smallbusiness, r/Accounting, whatever your category is. Spend 60 days commenting helpfully without linking to yourself. Build karma. Get to know which mods care about what.

Then, when a question comes up that you can answer with real expertise — answer it as a person, with your professional context disclosed in your flair, and link to the underlying primary source (a study, a public dataset, a how-to on your site that’s genuinely useful, not a landing page). Studies in 2025–2026 found the top 3 ranked replies in a high-engagement thread are disproportionately what AI engines quote verbatim. One upvoted comment in the top three is worth more citation weight than a hundred backlinks from middling B2B blogs.

These two plays compound: the on-site answer-unit work makes you quotable when the LLM lands on your domain, and the Reddit work makes the LLM more likely to land there in the first place.

What to do this week

1. Pick your top three commercial pages. Add a four-question “What people actually ask” block to each, with 40–80 word self-contained answers. Plain register.

2. Open ChatGPT and Perplexity. Ask 10 buying-intent queries in your niche. Note which subreddits show up in the citations. Those are your two or three.

3. Go create accounts in those subreddits today and start commenting. Don’t link anywhere for the first 30 days.

4. Audit your three oldest evergreen posts. If they’re more than 18 months old and untouched, they’re being downweighted for staleness — schedule a refresh, not a rewrite.

Paris Roussos has been doing SEO since 1996 (co-founded a Forbes Best of the Web–winning site back in the day) and now runs a white-label AI SEO practice for agencies and brands — flat-rate, $500–$1,500/mo per client. If your top-of-funnel traffic is leaking into ChatGPT and Perplexity and you want it back, email parisroussos@gmail.com.

Reddit isn’t your enemy here — it’s the format the models are asking you to imitate.

For 25 years, SEO meant winning at the link graph. Earn the right citations, point them at the right pages, and Google would do the math. The page with the strongest backlink profile usually won.

That model is breaking.

ChatGPT, Perplexity, Gemini, and Google AI Overviews don’t rank pages — they answer questions by stitching together facts from multiple sources. To do that, they need to know what you are, not just where you sit on a SERP. The new substrate underneath the answers is the entity graph: people, companies, products, places, and concepts, cross-referenced for overlap, consistency, and reliability. Links still help. They are no longer the main currency.

The mechanic

When Perplexity gets asked “which CRMs are best for solo consultants in 2026?”, it isn’t ranking ten URLs. It’s asking: which entities show up consistently across reputable sources for this query? What attributes of those entities are agreed upon? Whose name keeps appearing next to “solo consultant”? The system retrieves passages that talk about the same entity from different angles, weights them by source authority and internal consistency, then writes a synthesis.

Two things follow. First, the model has to recognize you as an entity at all — that means a stable, machine-readable identity (your business, your founder, your products) that reads the same in twelve different places. Second, your association with the topic has to be reinforced from outside your own domain. Self-published claims aren’t a signal. Pattern-matched mentions across the open web are.

The practical mechanics: name-address-phone consistency (still — and now more than ever), Wikidata and Wikipedia presence, schema entity references with `sameAs` pointing to authoritative profiles, structured Person and Organization markup, and consistent founder/team bios across LinkedIn, Crunchbase, podcast appearances, guest posts, and your own About page. Each of these is a vote that says “this entity is real, this is what it does, this is who runs it.” When Gemini cross-checks, it finds agreement. That’s what gets cited.

The numbers already reflect the shift. Sites with 32K+ referring domains are roughly 3.5× more likely to be cited by ChatGPT than thin-profile sites. That stat isn’t really about links per se — it’s about the entity having enough surface area for the retrieval system to lock onto it. The link graph and the entity graph are correlated; they aren’t the same thing.

What to do this week

Pick the top three entities you want to own — usually the company, the founder, and the flagship product or service category. For each one:

1. Audit the bio. Pull your current About copy, your LinkedIn summary, your Crunchbase blurb, and three guest-post bios. They should agree on what you do, who you serve, and the descriptive phrase you most want to be associated with. Most founders have four different versions written years apart. Pick the one you want, propagate it everywhere.

2. Ship Person and Organization schema. On your homepage and About page, mark up Organization with `name`, `url`, `logo`, and `sameAs` (LinkedIn, Crunchbase, X, Wikidata if you have it). On founder/author pages, mark up Person with `sameAs` pointing to the same external profiles. Schema isn’t the citation lever. The point is that you’re handing AI engines a clean entity card so they don’t have to guess.

3. Get on Wikidata. Even a barebones Wikidata item with your company, founder, founding date, and a couple of `sameAs` links costs an hour and feeds into nearly every retrieval system. If you can earn a Wikipedia page later, great. Wikidata first.

4. Audit five external mentions. Search your brand name. Find the top five non-owned references — directories, partner pages, podcast notes, press hits. Are they describing you correctly? Wrong category, wrong founder name, wrong tagline? Fix the ones you can edit. Ask politely on the ones you can’t.

This work is unsexy and almost entirely off your own site. That’s the point. The link graph rewarded what you could pull onto your domain. The entity graph rewards what the rest of the web says about you when you’re not in the room.

If you’re a brand that wants to be the answer LLMs reach for (not just rank on Google), Paris Roussos has been engineering search visibility for 30 years and now runs done-for-you AI SEO. Flat-rate, no-fuss. Email parisroussos@gmail.com.

The brands that win the next two years won’t have the most pages. They’ll have the cleanest, most consistent entity record across the open web — and the AI engines will quietly start naming them before the competition figures out what changed.

If your best argument is in paragraph nine, the LLMs will never see it. That is the uncomfortable finding from the 2025–2026 citation studies, and it has quietly upended how I write for clients.

The number to memorize: 44.2% of all citations LLMs hand back to users come from the first 30% of a page’s text. Another 31.1% come from the middle third. The bottom third — where most “thought leadership” essays bury their actual point — accounts for less than a quarter of citations. ChatGPT, Perplexity, Gemini, and Claude are all behaving more like impatient skimmers than careful readers, and they are using your intro to decide whether you are worth quoting at all.

The mechanic

Retrieval-augmented generation does not “read” your page. It chunks it, embeds the chunks, and pulls the highest-scoring passages back to the model. That scoring is biased toward semantic density near the top. Why? A few overlapping reasons.

First, page structure. Most LLM crawlers and retrieval pipelines treat the first heading and the first paragraph or two as the canonical answer to whatever query the user just asked. If your page is about “schema for AI search” and the first 200 words actually tell me what schema does for AI search, the embedding similarity to the query is high. If your first 200 words are about your team’s coffee habits and a clever metaphor about lighthouses, similarity is low and the retrieval ranker pushes you down.

Second, snippet extraction. AI engines are optimizing for the same thing Google optimized for a decade ago — pull-quotes that answer in 40 to 60 words. The top of your page is where those answer blocks fit cleanly. A well-placed answer block near the top often becomes the literal text the LLM cites, sometimes verbatim.

Third, crawl economics. Embedding pipelines have budget limits. Long pages get sampled — and the sample almost always favors the head and the H2-anchored sections. Your closing paragraphs may not even make it into the index in a meaningful way.

The result is a citation distribution that looks like a left-skewed graph with a long, lonely tail. If you are a founder writing a 1,500-word post and your “money line” is in the conclusion because that is how blog posts are supposed to flow — you are leaving citations on the table every time.

What this looks like in practice

I rewrote a client’s pillar page last quarter. Original structure: 280-word setup, two anecdote paragraphs, then the actual framework around word 700. New structure: framework in the first 90 words, named, numbered, with a 50-word tight definition right under the H1. Same content, same length, same conclusions. Citations in ChatGPT and Perplexity for their target query roughly doubled inside three weeks. Nothing else changed — no new backlinks, no schema additions, no new content. Just the order of the words.

That is not a one-off. The pattern is consistent across the rewrites I’ve audited.

What to do this week

1. Pick your three highest-traffic or highest-intent pages. Pull each one up. Read only the first 200 words. Ask: if an LLM cited only this, would the citation actually answer the query? If the answer is “no, you have to keep reading,” rewrite.

2. Move your strongest factual claim, your strongest stat, and your tightest definition into the first 30% of the page. Front-load them. Do not “build to” them. The TL;DR goes at the top, not the bottom.

3. Add a 40-to-60-word answer block immediately under the H1. Treat it like a featured snippet — direct, declarative, no qualifiers. This is the passage LLMs are most likely to extract.

4. Keep the bottom of the page useful, but stop expecting it to do citation work. Use it for examples, FAQs, and supporting detail that earns its keep on dwell time, not visibility.

This is one of those changes that feels small and writerly but maps directly to whether you show up when ChatGPT answers a question in your category. The retrieval layer rewards pages that get to the point.

About the service: Agencies — if your clients are starting to ask about AI SEO and you don’t have anyone in-house, Paris Roussos handles the work white-label. Flat-rate, $500–$1,500/mo per end client, you keep the relationship. Audits, schema and entity work, AI-visibility tracking, and content engineered to be cited by LLMs. Email parisroussos@gmail.com for a sample audit.

Write like the LLM is going to stop reading at word 250 — because most days, that is exactly what it does.

The most expensive lie marketers are still telling themselves in 2026 is that ranking #1 on Google means you’re winning organic. You can hold the top three blue links for a buyer’s exact query, watch your Search Console graphs sit at all-time highs, and still be invisible in the conversation actually closing the deal — the conversation happening inside ChatGPT, Perplexity, Gemini, and Google’s own AI Overviews.

I’ve been doing SEO since 1996, and I’ve never seen a layer of the funnel rotate this fast. Here’s the part most agencies are still working out: AI search doesn’t reward the same things classic SEO does. A page can be perfectly optimized for Google’s old algorithm and structurally invisible to the model deciding what to quote. Below is what’s actually happening, and the work that gets you back into the answer.

The mechanic — LLMs don’t rank pages, they cite sentences

Google was a page-ranker. It picked URLs, ordered them, and handed the click to you. LLMs are answer-engines. They synthesize a response from many sources and quote the parts that are the cleanest, shortest, most authoritative articulation of the user’s question. When you read a ChatGPT response and see “according to [Brand X]” — that’s not a search result. That’s a citation.

Three things determine whether a page becomes a citation:

1. Quotability. Does the page contain a one-or-two-sentence answer to a well-defined question, near a clear heading? Long, meandering “ultimate guide” posts get read by the model but rarely cited by it. The model picks the page that lets it lift a clean line.

2. Entity disambiguation. Has the LLM mapped your brand, your product, your founders, and your concepts to a stable identity it can quote with confidence? This is where schema markup, Wikipedia / Wikidata presence, and consistent NAP-style structured data stop being nice-to-haves and start being the gating factor.

3. Trusted-corpus mentions. LLMs lean disproportionately on a relatively small set of sources their training and retrieval systems already trust — Wikipedia, major industry publications, well-known reference sites. Backlinks are still a signal, but brand mentions inside trusted corpora are now a stronger one.

Notice what’s not on that list: keyword density, exact-match anchors, and most of what content briefs from 2019 obsessed about.

What to do this week

If you want your top-ranking pages to actually start showing up inside AI answers, here are four moves you can make in the next seven days — they’re not all of it, but they’re the ones with the highest leverage per hour of effort.

1. Audit your top 20 pages for “quote-blocks.” Open each one, find the most common questions buyers ask, and rewrite the answer as a single tight paragraph immediately under a clear `

` matching the question. Don’t bury it after 600 words of preamble. The goal is one liftable sentence per concept.

2. Implement (or fix) `Organization`, `Person`, and `FAQPage` schema. Most sites have schema. Most have it wrong. Use Schema.org’s full vocabulary for every named entity — your company, your founders, your products. Cross-link them with `sameAs` to your Wikipedia, LinkedIn, and X profiles. This is what lets an LLM say “Brand X” without hedging.

3. Run brand-mention tracking against the LLMs themselves. Stop measuring rank. Start measuring cite-rate. Ask the models the questions your buyers actually ask, log how often you’re named, and which competitors get named instead. This is the metric that maps to revenue now.

4. Get one credible third-party citation per quarter. A mention in an industry trade publication, a Wikipedia footnote that survives, an inclusion in a respected listicle. One real one beats fifty SEO-grade backlinks. The corpus the model trusts is smaller than you think.

None of this requires you to abandon traditional SEO. Google still drives traffic. But the slope of the curve is unmistakable: the share of buyer-question traffic that resolves inside an AI answer is climbing every quarter, and the work you do to win that real estate is different from the work that won the blue links.

---

Paris Roussos has been doing SEO since 1996 (co-founded a Forbes Best of the Web–winning site back in the day) and now runs a white-label AI SEO practice for agencies and brands — flat-rate, $500–$1,500/mo per client. If your top-of-funnel traffic is leaking into ChatGPT and Perplexity and you want it back, email parisroussos@gmail.com.

The buyers haven’t disappeared. They’re just asking the question somewhere else. The brands that build for that, instead of mourning the old SERP, are the ones still getting the click.