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.