Published September 8, 2026.
Maintenance becomes risky when a small request quietly expands. Set a boundary before touching a published page so reviewers know what is changing and what is protected.
Name the trigger
Link the broken fact, changed instruction, reader confusion, or measured query mismatch. Describe the affected passage and observation date. “Needs freshness” is not a sufficient trigger on its own.
List in-scope fields
Specify body sections, citations, metadata, links, or images that may change. Explicitly protect the slug, original publication date, unrelated claims, and page family unless the content owner approves a broader migration.
Define acceptance
Write the tests that close the work: factual correction, source support, clean render, unchanged protected fields, self-canonical, and successful linked assets. If investigation reveals a larger problem, stop and open a separate decision rather than stretching the original ticket.
This habit keeps daily SEO work auditable and makes rollback practical because the intended diff was clear before editing began.