Start from affected evidence
Open a specific issue or report before requesting a fix plan. The best plan names the actual page set, the observed pattern, the likely shared cause, and the test that will confirm the repair.
Treat generated output as a reviewed change
Check framework, template ownership, escaping, environment assumptions, and rollback before applying code. A technically valid snippet can still be wrong for a particular stack or deployment path.
Use edge patches deliberately
An edge layer can provide a reversible title or metadata correction while the permanent source fix is prepared. Record the affected paths, publish time, owner, and removal condition so the temporary layer does not become invisible infrastructure.
Recheck after deployment
Verify the live response first, then let the next crawl confirm the expected issue and page movement. Mark work verified only when the saved evidence supports it.