geo-optimizelisted

# GEO Two different jobs are called GEO. Say which one out loud before doing anything, because the work does not overlap. | the user means | this is about | go to | |---|---|---| | Generative Engine Optimization | being **quotable** by an answer engine | §1 onward | | geography — local, market, "near me" | being **placed** | §6 | ## 1. What changed, in one paragraph SEO gets a human to click a ranked link. GEO gets a machine to lift a passage out of your page and cite it, and the reader may never arrive at all. That makes the unit of success different: not a page that ranks, but **a passage that still means something once it is cut out of its page**. Everything below follows from that one sentence. This is why a piece can hold its rankings and lose its traffic. Nothing about it got worse. It just was not written in a shape anything could quote. ## 2. Run the audit first, not last ```bash node scripts/geo-audit.mjs --in brain/<slug>/post.md ``` It is rule-based — no key, no network, no model. It exits `1` when a **must** rule fails, so it works as a gate in the same place `validate-post` sits. Read the failures before you read the draft. The rules are the shape; the draft is your opinion about the shape. | rule | level | what it means | |---|---|---| | `answer-first` | must | the sentence under a question heading answers it, in ≤30 words, with no run-up | | `self-contained` | must | no paragraph opens on "Nó", "Điều này", "However" | | `sourced-numbers` | must | ever