Geo Citation Pass Not Keyword Stuffing

Answer engines quote sentences. They do not reward a page that repeated "best heat pump Portland" eight times. Generative engine optimization (GEO), and the adjacent AEO work, is a citation pass on a page you already have: make claims extractable, date them, and mark NO_DATA where you were bluffing.
This is not a 90-day SEO map. That post is cluster, calendar, and internal links. This post is what you do to one URL so a model can cite it without inventing your proof. Matching citation rewrite (Geo Ai Overview Citation Rewrite Pass) and product-page GEO/AEO prompts are in the PromptDig library (Browse more prompts).
Do not name a vendor as if they guaranteed a citation. You can make the page citable. You cannot make the overview pick you.
Stuffing makes sentences worse to quote
Keyword stuffing produces the opposite of a citation: a sentence no honest model should lift. "Our professional heat pump installation services in Portland deliver fast, affordable, best-in-class results" contains no number, no date, and three superlatives. An overview that quotes it is quoting fog.
GEO wants the opposite shape:
- One claim per sentence
- Subject, verb, object
- The date in the sentence, not only in a footnote
- A source you actually have, or the label NO_DATA
If you do not have the number, cut the sentence. Do not hedge it into "many homeowners find." Hedging is still unciteable.
Run a citation pass, not a new outline from vibes
Paste the current draft. Paste facts you can stand behind, with dates. Paste sources by name. Then ask for a pass that is allowed to delete.
A skeleton:
You are a GEO editor, not a keyword strategist.
Do not output a 90-day map or a backlink plan.
Target question: [question a person would ask].
Facts I can stand behind (with dates): [list].
Sources I actually have: [names, dates, URLs if public].
Banned claims: [ranks, savings, competitor traffic].
Last updated I will publish: [date].
Output:
1) Uncitable lines, quoted.
2) Answer-first block, 40-80 words, every number from Facts.
3) Claim sentences, one fact each, date in the sentence.
4) Evidence box per claim, or NO_DATA.
5) FAQ with 40-60 word answers a model can quote.
6) Last-updated footer.
If Facts do not support a line, cut it. Do not invent a study.
The answer-first block is the artifact overviews actually lift. It must stand alone. If you need the rest of the page to make a number true, the number is not ready.
Product pages: specs and proof, not "#1 for ice"
A PDP fails GEO the same way it fails a skeptical shopper. "#1 for ice" and "fits any car" are not claims. "Base 2.75 in; we measured a 2018 Civic holder at 2.9 in in our garage" is a claim, and it is honest about the sample.
The product-page pass should skip comparison tables unless every cell is in your spec sheet. Empty competitor cells are how models invent a rival's price.
FAQ answers should be reusable citations, not another keyword dump. "Will it fit my car?" needs the measurement you have and NO_DATA for the rest.
A second skeleton for PDPs:
GEO/AEO pass for this product page. Not a keyword map.
Question a shopper asks: [question].
Specs I can stand behind: [list].
Proof with dates: [tests, warranty, measurements].
Banned: #1, fastest, any-car, medical hydration.
Write: uncitable quotes, answer-first 50-80 words, eight claim sentences,
five FAQ answers, last-updated footer.
Comparison table only if every cell is in Specs. Else skip, write NO_DATA.
Dates belong in the sentence
"Median on-site duration was 2 days" is weaker than "In 2025 we logged 86 ducted swaps inside Portland city limits; median on-site duration was 2 days." The year and the count are what make the sentence safe to quote. If the log is 2025, do not let the model say "currently." Last-updated on the page is a different date. Keep both.
Internal job logs can be sources. Say they are internal. Do not mint a fake DOI.
Those 86 swaps and 2 days are an example of the shape of a claim (year, count, place), not a statistic about PromptDig or about heat pumps in general. Use your own log. If you do not have one, the pass should print NO_DATA, not a typical-industry guess.
What this pass refuses
- A keyword map (wrong job)
- A 90-day calendar (wrong job)
- Invented experts, invented studies, invented traffic
- Superlatives with no source
- Guarantees ("we will be cited," "ChatGPT will pick this")
When a pass actually turns a foggy page into dated claims, share that checklist (Share a prompt) with the page type in the title. Browse the library on PromptDig (Browse more prompts) for the citation rewrite and the product-page fork.
The point is not to game an overview. The point is to stop publishing a paragraph that cannot be quoted without becoming a lie. Write facts with dates. Delete the rest. That is GEO.