**TL;DR** — Across 30 client sites through May 2026 we audited a structural choice that lives in the grammatical mood of the answer sentence on procedural queries: whether the passage that answers a "how do I" question is written as a **direct imperative instruction** that commands the reader ("Compress images to WebP before upload to cut page weight by about 40%.") or as a **descriptive statement** that reports the same procedure in the third person ("Compressing images to WebP before upload cuts page weight by about 40%."), and whether the imperative mood changes how often the AI Overview lifts that sentence into the card. Across 7,690 cited-passage events on procedural queries we joined each cited sentence to whether its main clause was an imperative or a declarative. The headline is that the imperative sentence is a real and large citation lever on procedural queries, and it is really a query-intent-match lever wearing a "command form" costume. An imperative answer sentence was cited 2.3× more often than a matched declarative one describing the same procedure on the same "how do I" query. The strongest predictor was action-verb-first — a sentence that opened on the verb the reader was being told to perform was lifted far more than one that buried the action behind a subject noun phrase. The second was single-action scope — an imperative carrying one step was lifted more than one chaining three actions with "and" and "then". The third, and the warning, was mood-query mismatch — forcing imperatives onto definitional and informational queries ("what is X") cited no better and on 5% of pages read as off-register, so the composer paired the command with a competitor's declarative that matched the question. One change — rewriting descriptive answer sentences on procedural queries into a verb-first single-action imperative — lifted cited-passage rate by 22% on the affected sites over a 30-day follow-up.
Why we ran this audit
The AI Overview composer lifts a sentence and drops it into a card as the answer to a query, and a procedural query asks for an action. "How do I reduce my page weight" is a request for something to do, and a sentence that answers it well names the action and tells the reader to perform it, while a sentence that describes the same procedure in the third person reports a fact about the action rather than handing it over as an instruction. We had spent weeks measuring second-person address — whether writing the answer to "you" helped — and the imperative is the natural next question, because an imperative is the most compressed second-person form there is: it addresses the reader by dropping the subject entirely and leading on the verb. We wanted to know whether the composer, matching a "how do I" query, preferred a sentence whose grammatical mood matched the question's request for an action.
The second motivation was a house-style habit. Editorial writing leans declarative because the imperative can read as bossy or thin — "Compress your images" feels like a fragment next to "Compressing your images reduces load time, which improves both user experience and search ranking." So our procedural pages had been written as descriptive statements that reported the steps rather than commanding them, on the reasonable belief that fuller declarative prose read better. A human following a how-to infers the instruction from the description anyway. The composer, hunting for one sentence that answers "how do I X", finds a declarative that reports the procedure and has to decide whether a report of an action answers a request for one. We needed to know whether the declarative mood cost the citation, because if it did, the fix is nearly free — recast the lead answer sentence in the imperative — and it does not require new content.
How we ran the measurement
30 client sites — 11 SaaS, 6 publisher, 8 B2B services, 5 DTC — each with a fixed 200-query basket of its real in-market queries, deliberately weighted toward procedural queries ("how do I X", "how to X", "steps to X", "ways to X") where the answer is an action. Twice daily through May 2026 we captured every AI Overview card, and for cards citing a client page on a procedural query we identified the specific lifted sentence and classified its mood: imperative (the main clause is a bare command, verb-first or near-front, no grammatical subject), or declarative (the same procedure stated in the third person with an explicit subject). For each cited sentence we built a matched control: a comparable sentence on a similar procedural query whose mood differed but whose underlying instruction was the same, so the comparison was imperative-vs-declarative rather than good-page-vs-bad-page. The cited cohort was 7,690 events.
Two normalisation moves matter. We scored mood on the sentence as it would be lifted — alone, with no surrounding context — because that is the unit the composer extracts, and a declarative that reads as an obvious instruction inside a numbered how-to list reads as a flat statement of fact in the card. And we matched on sentence citability before comparing mood — we paired each cited sentence with a control our existing cited-paragraph rubric scored as equally liftable (concrete, on the query, factually complete), so the effect we attribute to imperative mood is not just the imperative pages being better written overall. The 2.3× and 1.7× figures are from those matched comparisons, not raw averages.
The shape of the imperative pattern
The flat headline first. On procedural queries, imperative sentences are cited more. A sentence written as a direct command was lifted 2.3× more often than a matched declarative describing the same procedure on the same "how do I" query. The effect held through the quality match and the citability control: among sentences our rubric scored as equally liftable, the imperative ones were lifted far more than the declarative ones. The composer behaves as though it prefers a sentence whose mood matches the query's request for an action over one that reports the same action as a fact.
The most decision-relevant cut was that this is about matching the query's intent, not about the command form for its own sake. We tested whether the win came from the imperative mood itself or from the verb landing early in the sentence, and both mattered but the verb position was the larger half: a declarative that front-loaded the action verb ("Compressing images cuts page weight") was cited better than a declarative that buried it ("Page weight can be cut by compressing images") but worse than a true imperative ("Compress images to cut page weight"). The imperative wins partly because it forces the action to the front. Lead on the verb the reader is being told to do.
Driver one: lead on the action verb
The single strongest predictor was whether the answer sentence opened on the action verb. Holding the instruction constant, a sentence that led on the verb the reader was being told to perform was lifted at 2.3× the rate of one that buried that verb behind a subject noun phrase. The composer extracts a sentence and reads it as the answer to "how do I X"; a sentence that opens "Compress images…" presents the action in the first word, while one that opens "Image compression is a technique that…" makes the composer travel past a definition to reach the instruction. A human scanning a how-to finds the verb wherever it sits; the composer matching a procedural query rewards the sentence that puts the action where the question points.
We ran a structural test on 27 answer sentences across 14 clients, each a declarative on a procedural query that opened on a subject noun phrase and buried the action verb. We rewrote each into a verb-first imperative, changing no underlying instruction — only moving the action to the front and dropping the grammatical subject. Over the 45 days that followed, 19 of the 27 sentences began being lifted on at least one procedural query where the declarative version had been skipped. The lever was not new content; it was leading the single sentence the composer would extract on the verb the reader actually had to perform.
Driver two: one action per sentence, not a chained sequence
Holding mood constant, the second driver was whether the imperative carried one action or several. A sentence that issued a single command ("Compress images to WebP before upload") was cited more than one that chained three steps with "and" and "then" ("Compress your images, then resize them, and finally enable lazy loading"). The reading consistent with the data is that the composer lifts a sentence as a self-contained answer, and a single-action imperative is a complete answer to one step while a chained imperative is a compressed list the composer would rather extract as a real list — so the multi-action sentence competes with the page's own `<ol>` and loses to it.
We ran a structural test on 22 chained imperatives across 13 clients, each bundling three or more actions into one sentence. We split each into a lead single-action imperative followed by the remaining steps as a short list, changing no instruction — only unbundling the sequence. Over the 60 days after the change, 15 of the 22 lead sentences improved their cited-passage rate, and several pages additionally won the list-card slot for the full sequence. The two drivers compound: a buried-verb declarative chaining three actions is the worst case, a verb-first imperative carrying one clean action is the best, and the cheapest move is to lead on the verb and stop after one step.
Driver three: mood-query mismatch, and the imperative on the wrong question
The third driver was the warning. The imperative wins on procedural queries because it matches the request for an action, and forcing it onto definitional and informational queries backfires. A sentence like "Understand that compression removes redundant data" — an imperative bolted onto a "what is compression" query — was cited no more often than a clean declarative definition, and on 5% of audited pages the composer paired the awkward command with a competitor's declarative that answered the definitional question in its natural mood, so the citation was shared rather than won outright. The reading consistent with the data is that the composer rewards a mood that matches the query's intent, and an imperative on a "what is" query is a mood mismatch the composer reads as off-register. A "what is X" query wants a declarative definition; only the "how do I" query wants the command.
We confirmed this on 17 sentences across 11 clients where an earlier optimisation pass had recast definitional answer sentences as imperatives. We rewrote each back into a clean declarative definition for the informational query while keeping the imperative on the adjacent procedural query, matching mood to intent on each. Over the following 45 days the definitions regained their solo citation on the "what is" queries while reading naturally, and none drew a shared-citation pairing. The actionable rule is blunt: write the imperative for the procedural query and the declarative for the definitional one — the mood has to match what the question is asking for, and a command on a definition reads as off-register the composer will not lift alone.
What changed in our content checklist
Three changes. We added a mood pass for procedural queries: before publishing, we read each how-to section's lead answer sentence and check that it is a verb-first imperative, and a declarative that reports the step gets recast as a command — because the composer lifts a sentence whole and reads a verb-first imperative as a direct answer to "how do I". We added a single-action check to the same pass: the lead imperative carries one step, with the rest of the sequence moved to a list, because the composer prefers a self-contained command over a chained one it would rather extract as a list. And we added a mood-intent guard: we match the mood to the query, imperative for procedural and declarative for definitional, so a command never lands on a "what is" question it does not fit.
We dropped one habit. For years our procedural pages had leaned declarative, on the belief that reporting a step in fuller prose read better than barking it as a command — "Compressing your images reduces load time" felt more substantial than "Compress your images". The audit removes that default for the lead answer sentence on procedural queries: the one sentence the composer would lift on a "how do I" query has to be the verb-first imperative, and a descriptive statement spends the citation to sound fuller. So declarative answer sentences left our playbook for procedural queries — we now write the lead answer sentence as a single-action command and let the surrounding prose carry the explanation, accepting that the cited sentence reads more terse than an essayist would choose because it is built to answer the request for an action alone.
- 01Lead on the action verb. A verb-first imperative was cited 2.3× more than a declarative that buried the action on the same procedural query — the composer reads a verb-first sentence as the answer to "how do I".
- 02One action per sentence. A single-action imperative was lifted more than one chaining three steps with "and" and "then" — a multi-action sentence competes with your own list and loses.
- 03Match mood to query intent. An imperative on a "what is" query was cited no more than a declarative definition, and on 5% of pages the composer shared the citation with a competitor that answered in the natural mood.
- 04Recast the descriptive step. 19 of 27 buried-verb declaratives were lifted after being rewritten as a verb-first imperative.
Where this argument breaks
For definitional and informational queries — "what is compression", "why does page weight matter" — the imperative is a mood mismatch and the declarative wins, so the lever is for queries that ask for an action. For navigational and brand queries there is no answer sentence whose mood matters. For narrative and persuasive passages — case studies, opinion, story-driven content — the imperative is a tone choice serving the prose, not a citation lever, and the mood pass is for the answer sentences on procedural queries only. For some languages the effect may differ — in our parallel Chinese-language audit (文心一言, 元宝, 通义) the imperative win was present but the verb-first effect was smaller, since Chinese imperatives already drop the subject by default and the marked politeness particle («请») rather than word order carries the command, so the composer read the instruction reliably even when the verb did not lead. The 5% mismatch figure is small and noisy; we are confident the imperative does not help on definitional queries and mildly confident it splits the citation there, 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 imperative answer sentence — verb-first, single-action, matched to a procedural query — far more readily than a declarative that reports the same procedure as a fact, the unit is the individual answer sentence rather than the page, and the cheapest citation win on a "how do I" query is to write the answer as a command that leads on the verb.