Review a technical SEO fix

Start with a real issue#

Select a specific SEO or technical finding. Read the affected URL and source observation. Confirm the current site still exhibits the issue before asking for a patch; a stale scan can point to code that has already changed.

Prepare and validate#

1. Describe the desired behavior and the page or template involved.
2. Confirm the GitHub connection is scoped to the intended repository and permitted access mode.
3. Ask the Coding agent for a bounded proposal with the reasoning and verification steps.
4. Review the diff for unrelated changes, content accuracy and possible indexing effects.
5. Run the repository’s checks and inspect the rendered page in a safe preview.
6. Use your normal reviewed deployment process, then recheck the live page and source observation.

Do not skip the owner#

Changes to redirects, canonical URLs, robots rules or structured data can have wide consequences. The tool’s output is not authority to overwrite production files. Keep the responsible site owner involved and preserve a rollback path.

If repository access or a publishing adapter is unavailable, use the proposed change as a manual review artifact. Do not label a generated patch as a deployed fix.