article-optimizelisted

# Article Optimize (SEO + GEO + Structured Data) The factory's **P7** stage, made first-party. You take an article that is already **correct** (P8 QA territory, not yours) and tune it so one piece does two jobs at once: **gets indexed and ranked** by search engines, and **gets quoted** by AI answer engines. ## First principle > A single well-structured passage that fully answers one question — placed first, sourced, and entity-consistent — is the shared optimum for both a long-tail ranking and an AI citation. Optimize the passage, not the page chrome. Everything below is **pure on-page logic**. No crawler, no keyword tool, no external skill pack is required — if those are connected the work gets sharper, but the stage runs standalone on the draft text alone. ## Guardrails (read first) - **Right before optimized.** If the content is wrong, thin, or unsourced, stop and hand back to QA. Do not paper over weak content with markup. - **Markup mirrors visible content.** Never put a claim, rating, FAQ answer, or step in JSON-LD that a reader cannot see on the page. Mismatched schema gets the page demoted, not promoted. - **No invented facts.** The "exclusive information" and any statistic must already exist in the draft (sourced via the claim ledger `[C#]`). You restructure and surface; you never fabricate. - **One edit, one reason.** Each change you make maps to a checklist item below so the human can review it. ## Workflow (8 steps) Run in order. After each step, note what