fix-writer

Reads: ../improve-search-visibility/references/finished-fix-examples.md, ../improve-search-visibility/references/gap-to-fix.md, ../improve-search-visibility/references/prioritising.md; ../improve-search-visibility/references/page-map.md; the page map row the fix or brief comes from; the brand's voice; product records; the CMS and who ships (from intake). Claims are decided by the claims-gate skill (../claims-gate/SKILL.md), run over every finished fix in SKILL step 4 — this atom never decides a claim itself.

Does: 0. Honor the request's count and job scope from ../improve-search-visibility/references/seo-jobs.md. A technical finding with insufficient code/CMS access gets an exact engineering handoff (affected URLs, observed defect, proposed outcome, verification and risk/undo), not guessed implementation. Use Agent: <time> - Human: <active time> when estimating work.

1. Write the change itself: the exact title/meta/H1/opening paragraph, Q&A block, markup, field values, robots line, listing text or drafted inclusion request — in the CMS's terms (where in Shopify / WordPress / Webflow it goes; markup as an edit to the theme's existing block with live values, never a second hard-coded block).
2. Facts in the draft: mark every sentence that states a fact with its source (a "Claims you may use" fact, a product record field, or [PROOF NEEDED]) so the claims gate can keep, rewrite or cut it. The live page supplies plain product facts only (name, price, size, listed ingredients, how to use) — re-read prices from it; ratings and review counts appear only as a "Claims you may use" fact, or in markup that mirrors reviews shown on the page. The brand's own marketing lines are claims too ("closes the loop", "self-improving", "growth outcomes" from the site, the kit description or value props): without sign-off they are cut or rewritten to plain facts, or shown as [needs your sign-off: …] — never pasted into fix copy as ready to publish. No comparison table or outreach line about a rival unless each cell comes from that rival's own page, read this run and cited; otherwise leave the rival out. Competitor facts come only from the competitor's own page, read this run and cited with its date — never from a list or a review site — and only if the human allows naming rivals.
3. Two versions of every fix. For the report's "What to do" section, plain words only: what changes and where, who does it and how long, why it is a priority (the gap it closes, said as the buyer question it fixes — never a question id), how we'll know it worked. For the report's last section, "For whoever edits your site": the finished copy, field values or code and exactly where it goes, plus time to show, risk and undo.
4. Page briefs ("needed" rows of the page map, listed separately from this week's visibility fixes) to search/briefs/<page-slug>.md in the exact shape in ../improve-search-visibility/references/page-map.md (make-content's brief input).

Writes: both versions into the report, the working copy into search/fixes/<date>.md; brief files. Briefs name the questions they answer in words, not ids. Never: "add an FAQ", "improve E-E-A-T" or any instruction without the finished text; invented stats, prices, dates or reviews; FAQ markup promised as a rich result.