Writing pages that AI search engines can cite

Generative engine optimization is the work of writing a page so an answer engine can quote it without distorting it. The page defines the term, states the recommendation, and names the source of any number. A model that lifts the first sentences should still be telling the truth.

This is a writing standard before it is a tactic. The Princeton GEO study, published at KDD 2024, measured about a 10% drop in visibility when pages stuffed keywords, against gains for citations, statistics, and quotations. The practical lesson is ordinary: say the thing, show where a figure came from, and stop repeating the phrase you hope to rank for.

A definition in the first lines

Answer engines quote passages that can stand alone. A definition does that job. It names the subject, says what it is, and stops before the anecdote. "A seed-stage homepage has one job: make a stranger understand the product and see how to talk to you" is a liftable passage. "In this article we will explore the world of homepages" is not.

Write the definition as if it will be separated from your introduction. If it depends on the previous paragraph, it will be quoted badly or skipped. Two short sentences are enough. The rest of the page can qualify them.

Do this for the terms your buyer actually uses. Core Web Vitals, design tokens, WooCommerce, a client portal. Precise names are easier to cite than a private metaphor. Define a term the first time it appears, in words a founder can repeat.

Answer first, then the steps, then the limit

The shape that gets cited is the shape a careful person already prefers. The answer comes first. The steps come next. The limit of the advice comes last, in the same piece, so the quote does not overclaim.

A page about replatforming should say, early, that redirects and stable titles protect the equity you have, and that nobody honest can promise the rankings will be unchanged. A page about hiring a studio should say what to look for, then say when a freelancer or an in-house hire is the better shape. The condition is what makes the recommendation safe to repeat.

Lists help when the reader is choosing or checking. A numbered sequence of a launch, or three questions to ask, is easier to quote than a long narrative with the same content hidden inside it. Use a list for the decision. Keep the prose for the judgment around it.

Google's people-first guidance belongs beside the GEO findings, because the two fail in the same place. Search Central says ranking systems aim to reward content created for people, and it treats content made mainly to manipulate rankings as the wrong aim. A page tuned so a model will mention you, and useless to the founder who lands on it, is the same mistake in a new channel.

Cite a source you actually used

A citation is a name, a publisher, and a link, placed on the sentence that needed it. The GEO paper's own result is the example: keyword stuffing was associated with about a 10% drop in visibility, while citations, statistics, and quotations were associated with gains. That sentence is citable because the source is real and the figure is attached to the publisher and the year.

Inventing a statistic to look citable does the opposite. A fake percentage, a client quote you wrote yourself, an award that does not exist: an answer engine may repeat it, and then you own the error in public. If you do not have a number, write the recommendation without one. Omit the source rather than decorate the paragraph.

Quotations have the same rule. A short line from a public document, attributed, is fair. A sentence placed in a customer's mouth is not. Paraphrase long passages. The reader should be able to click through and find the claim you summarized.

Use a source when it changes the advice. A threshold, a definition, a finding about what helps or hurts visibility. A link dropped at the bottom with no sentence attached is a bibliography, and it gives a quoting model nothing to lift.

Do not stuff the phrase

The primary phrase belongs in the title and once in the opening. After that, vary the language. Say "an answer engine," "a citing model," "the passage," "the page." Repeating the same query in every paragraph reads as stuffing, and the GEO study measured a visibility cost for that pattern.

Stuffing also makes the page worse for the human who came to learn. They can feel the phrase being aimed past them. Write the H2s as the real sections of the argument. Let the excerpt state the point in a sentence that could serve as the search snippet. Neither of those slots needs the phrase welded on twice.

The same restraint applies to synonyms stacked in a single sentence to catch every wording of the query. One precise term, defined, beats a pile of near-duplicates. If a second term matters, give it a section and a definition of its own.

A passage a model can lift

When you draft, highlight two or three passages and read them out of context. Each one should survive.

A definition. "The work is writing a page so a quoting system can lift a true passage: a definition, a sourced figure, and a recommendation with its limit attached."

A sourced figure, with the year and the publisher in the sentence. The KDD 2024 GEO paper's finding on stuffing is the model. Your page might instead cite a Core Web Vitals threshold or a Nielsen Norman Group observation, if that figure is the one your reader needs. The rule is the attachment, not the topic.

A recommendation with a condition. "Publish the FAQ on the page if you want an answer engine to use it. A question that exists only in the markup, hidden from the reader, is a poor candidate for trust."

That last example is why the next article matters. FAQ sections that help buyers and search engines is the piece to read next, because a visible question with a self-contained answer is one of the passages models can lift cleanly.

Author, date, and a specific description of the page's image support the same goal. A quoting system is more likely to trust a passage when a reader can see who wrote it and when. None of that replaces the sentence. The sentence still has to be true alone.

What this does not guarantee

A citable page is not a promise that any particular assistant will name you. Citation follows clarity, and it also follows all the other pages on the same question. The work you control is the passage. You can make it accurate, sourced, and short enough to lift. You cannot schedule the mention.

Write for the founder who lands on the URL. If the passage helps them decide, it is fit to be quoted. If it only helps a model, it will bore the founder and, on Google's terms, it is aimed at the wrong reader. The overlap is the opportunity. People-first pages that define terms and show their sources are the pages worth citing.

Hanabi builds the sites those pages live on: clear structure, a sentence that says what the company is, and production code that stays fast enough to read. When that is the work you want done, look at Hanabi's services.