**TL;DR** — Across 30 client sites through May 2026 we audited a point-of-view choice that lives in the subject of the answer sentence: whether the passage that answers the query is written in **second person**, addressing the reader directly ("You can cut page weight by 40% with compression", "Your schema markup tells search engines what your content means"), or in **impersonal third person**, with no addressee ("Page weight can be cut by 40% with compression", "Schema markup tells search engines what content means"), and whether addressing the reader changes how often the AI Overview lifts that sentence into the card. Across 7,690 cited-passage events we joined each cited sentence to whether its main clause addressed a "you"/"your" reader or stated the fact impersonally. The headline is that second-person framing is a real but double-edged citation lever, and it is really a self-containment-versus-context lever wearing a pronoun costume. The relationship was not monotonic: a sentence written to "you" was cited 1.9× more often than a matched impersonal sentence on instructional, how-to queries — but on definitional and factual queries the direction reversed, and the impersonal sentence was cited 1.4× more. The strongest predictor was query register — the composer matched second-person answers to action-and-advice queries and impersonal answers to definition-and-fact queries. The second was addressee resolvability — a "you" that referred to anyone reading was cited more than a "you" that only resolved to a specific persona named earlier on the page. The third, and the warning, was pronoun churn — flipping a whole page to second person to chase the instructional win stripped the impersonal voice from genuinely factual sentences and was cited no more, and on 6% of pages slightly less. One change — matching the answer sentence's point of view to the query's register, second person for how-to and impersonal for definitional, instead of a single house voice — lifted cited-passage rate by 21% on the affected sites over a 30-day follow-up.
Why we ran this audit
The AI Overview composer lifts a sentence and reads it as an answer to a specific query, and a query carries an implicit point of view. "How do I speed up my site" is a request for advice aimed at the asker, and an answer that says "You can speed up your site by…" answers the asker in their own frame, while an impersonal "Site speed can be improved by…" answers a more abstract version of the question. "What is INP" is a request for a fact about a thing in the world, and an answer that says "You measure INP in milliseconds" drags the reader into a definition that has no addressee. We suspected the composer was matching the point of view of the answer sentence to the point of view of the query — second person for queries that ask the reader to do something, impersonal for queries that ask about a thing — and we wanted to know whether that match was real and which direction each register pulled.
The second motivation was a tension between two house styles we kept seeing collide. Conversion-minded writers address the reader everywhere — "you", "your site", "your customers" — because second person is warmer and sells better, so even definitional sections get a "you". Reference-minded writers strip the reader out everywhere — "the user", "one", "a site" — because impersonal voice reads as authoritative, so even how-to steps go agentless. Each style produces a page that is half-matched to its queries: the conversion page wins the how-to citations and loses the definitional ones, the reference page does the reverse. We needed to know whether the composer actually rewards matching point of view to query register, because if it does, the fix is not picking a house voice — it is varying the voice section by section to fit what each section answers.
How we ran the measurement
30 client sites — 12 SaaS, 6 publisher, 7 B2B services, 5 DTC — each with a fixed 200-query basket of its real in-market queries, deliberately split between instructional queries ("how do I X", "how to X", "best way to X") and definitional or factual queries ("what is X", "what does X mean", "how much is X"), so we could read the effect of point of view against query register rather than averaging the two together. Twice daily through May 2026 we captured every AI Overview card, and for cards citing a client page we identified the specific lifted sentence and classified its point of view: second person (a "you"/"your" addressee in the main clause), impersonal third person (no addressee, the fact stated about a thing), or mixed. For each cited sentence we built a matched control: a comparable sentence on a similar query whose point of view differed, so the comparison was second-person-vs-impersonal rather than good-page-vs-bad-page. The cited cohort was 7,690 events.
Two normalisation moves matter. We scored point of view on the sentence as it would be lifted — alone, with no surrounding context — because that is the unit the composer extracts, and a "you" that the paragraph above had carefully defined reads as an unscoped "anyone" in the card. And we matched on sentence citability before comparing point of view — we paired each cited sentence with a control our existing cited-paragraph rubric scored as equally liftable (concrete, right length, directly on the query), so the effect we attribute to point of view is not just the second-person pages being better written overall. The 1.9× and 1.4× figures are from those matched comparisons within each query register, not raw averages across both.
The shape of the second-person pattern
The headline is that the effect flips with query register, so the flat average hides it. Pooled across all queries, second person and impersonal were cited at nearly the same rate, which is why a single-number summary would have called this a null result. Split by register, the two pulled hard in opposite directions: on instructional how-to queries the second-person sentence was lifted 1.9× more than a matched impersonal one, and on definitional or factual queries the impersonal sentence was lifted 1.4× more than a matched second-person one. The composer behaves as though it prefers an answer whose point of view matches the question — it wants advice phrased to the asker and facts phrased about the world.
The most decision-relevant cut was that this is register-matching, not a global preference for either voice. We tested whether second person carried an intrinsic advantage that the definitional reversal merely dampened, and it did not: within instructional queries the second-person win was clean and large, within definitional queries the impersonal win was clean and large, and neither voice won when pointed at the wrong register. The composer is not scoring "you" as warm or "the user" as authoritative; it is checking whether the answer addresses the reader on a query that asked for advice, or describes the world on a query that asked for a fact. Choose point of view to fit the query register, not to fit a brand voice guideline.
Driver one: match the point of view to the query register
The single strongest predictor was whether the answer sentence's point of view matched the query's register. Holding the sentence constant, a second-person version on a how-to query was lifted at 1.9× the rate of its impersonal twin, and an impersonal version on a definitional query was lifted at 1.4× the rate of its second-person twin. The composer extracts a sentence and reads it as the answer to the specific query; an instructional query is a request the reader makes on their own behalf, so a sentence that answers "you" closes the loop, while a definitional query is a request about a thing, so a sentence that addresses "you" answers a question that was never about the reader. A human reader tolerates either voice on either query; the composer behaves as though the register match is part of what makes the sentence a good answer.
We ran a structural test on 26 answer sentences across 14 clients, each a how-to answer written impersonally — "page weight is reduced by", "the cache is cleared from" — on queries that asked the reader how to act. We rewrote each into second person addressing the reader directly, changing no steps — only promoting the reader into the subject. Over the 45 days that followed, 18 of the 26 sentences began being lifted on at least one instructional query where they had previously been skipped. We ran the mirror test on 22 definitional answers written in second person — "you measure INP in", "your bounce rate is" — and rewrote them impersonal; 15 of the 22 improved on their definitional queries. The lever was not new content; it was pointing the answer sentence at the register the query came in on.
Driver two: keep the "you" resolvable to any reader
Holding register constant, the second driver was addressee resolvability. On instructional queries, a "you" that meant anyone reading the sentence — the general reader the query represents — was lifted more than a "you" that only made sense as a specific persona the page had defined earlier ("As a Shopify merchant, you…", where the merchant framing lived two paragraphs up). The composer reading the sentence cold cannot recover a persona established elsewhere on the page, so a scoped "you" reads as addressing someone the card cannot identify, while a general "you" addresses the person who typed the query. The reading consistent with the data is that the second-person win depends on the addressee resolving to the query's asker, not to a narrower character the surrounding page set up.
We ran a structural test on 19 answer sentences across 11 clients whose "you" was silently scoped to a persona named earlier in the section. We rewrote each so the sentence stood for any reader of that query, moving the persona qualifier elsewhere or cutting it, keeping the instruction the same. Over the 60 days after the change, 13 of the 19 sentences improved their cited-passage rate on the broad instructional queries. The two drivers compound: a second-person sentence on a how-to query whose "you" only resolves to a narrow persona is half-built, and an impersonal sentence forced onto a how-to query is the other half — the sentences that won addressed the general asker on the queries that asked for advice.
Driver three: pronoun churn, and the all-second-person page that backfires
The third driver was the warning. Point of view is a per-section lever matched to that section's register, not a page-wide switch, and flipping the whole page to second person to chase the how-to win backfires. A page rewritten so every sentence addressed "you" — including its definitional and reference sections — was cited no more often overall than one that varied voice by register, and on 6% of audited pages the all-second-person version was cited slightly less, because the definitional sentences now answered factual queries in the wrong frame ("You measure INP in milliseconds" answering "what is INP"). The reading consistent with the data is that each register has a voice the composer prefers, and forcing one voice across both registers wins the matched sections and loses the mismatched ones, netting to nothing or worse. Match per section; do not pick one pronoun for the page.
We confirmed this on 17 sections across 10 clients where an earlier conversion-driven rewrite had pushed second person into definitional content. We reverted the definitional answer sentences to impersonal while keeping the how-to sections in second person. Over the following 45 days the reverted definitional sentences regained citation on their factual queries while the instructional sections held theirs, and the page net-gained over the all-second-person version. The actionable rule is blunt: write the answer sentence to "you" when the query asks the reader to do something, and write it impersonally when the query asks about a thing — and let a single page carry both voices, one per section, rather than imposing a house pronoun on every answer.
What changed in our content checklist
Three changes. We added a register pass: before publishing, we read each section's lead answer sentence and ask whether the query it targets asks the reader to act or asks about a thing, and we write the sentence in second person for the first and impersonally for the second — because the composer matches the answer's point of view to the query's register. We added an addressee check to the same pass: a second-person answer sentence should address any reader of that query, so a "you" silently scoped to a persona two paragraphs up gets broadened or the persona moved off the answer sentence. And we added a churn guard: we vary voice section by section to fit each register and refuse to flip a whole page to one pronoun, because forcing second person onto definitional sections loses the citations the impersonal voice would have won.
We dropped one habit. For years each writer had carried a single point of view as a personal default — the conversion writers addressed "you" everywhere, the reference writers stripped the reader out everywhere — and a page came out in one consistent voice regardless of what each section answered. The audit removes that default: the one sentence the composer lifts has a register to match, and a uniform house voice mismatches half the sections by construction. So single-voice pages left our playbook — we now set point of view per answer sentence to fit the query its section targets, and accept that a good page reads in two voices because it answers two kinds of question.
- 01Match the answer sentence's point of view to the query register. Second person was cited 1.9× more on instructional how-to queries, while impersonal was cited 1.4× more on definitional ones — the composer wants advice addressed to the asker and facts stated about the world.
- 02Write how-to answers to "you". 18 of 26 impersonal how-to sentences were lifted after the reader was promoted into the subject on queries that asked the reader to act.
- 03Write definitional answers impersonally. 15 of 22 second-person definitional sentences improved after the reader was removed — a fact about a thing reads better with no addressee.
- 04Keep the "you" resolvable to any reader, and do not flip the whole page. A "you" scoped to a persona named earlier reads as unidentified in the card; an all-second-person page was cited no more, and hurt on 6% of pages, by forcing the wrong voice onto definitional sections.
Where this argument breaks
For queries with no clear register — ambiguous queries that could be read as either "how do I" or "what is" — the point-of-view match is weak and either voice does roughly equally, so the lever is for queries whose register is unambiguous. For navigational and brand queries there is no answer sentence whose point of view matters. For narrative and persuasive passages — case studies, opinion, story-driven content — point of view is a craft and tone choice serving the prose, not a citation lever, and the register pass is for the answer sentences only. For some languages the effect may differ — in our parallel Chinese-language audit (文心一言, 元宝, 通义) the instructional second-person win was present but smaller, since Chinese often drops the pronoun entirely and an imperative already implies the reader without a marked "你"; the register-matching pattern held but the surface device that carried it was different. The 6% churn penalty is small and noisy; we are confident a uniform pronoun does not help and mildly confident it hurts, but it is the weakest finding here and we would not restructure a page on it alone. Our window was 60 days and the cohort was 30 sites; the multipliers are point estimates that will move by vertical and query type. Outside those carve-outs the lesson holds: in 2026 the AI Overview lifts an answer whose point of view matches the query's register — second person for the reader who asked how, impersonal for the thing the reader asked about — the unit is the individual answer sentence rather than the page, and the cheapest citation win is to write each answer sentence in the voice its query came in on, even when that means one page speaks in two.