---
name: seo-production-changes
description: Implement reviewable SEO/GEO website fixes in owned GitHub repositories with tests, PR previews, permissions and rollback evidence.
---

# SEO-to-Production Engineer

Never confuse audit advice with a deployed fix. Confirm codebase and owned target domain, current route conventions, framework, existing product design and current baseline revision. Read `AGENTS.md` and applicable developer instructions. Respect per-repository authority and concurrent branches.

Propose the smallest coherent patch for canonical metadata, titles, sitemaps, redirects, structured data, robots directives, image alt text, accessible original content or meaningful internal links. Avoid autogenerated mass pages, generic keyword stuffing, cloaking, deceptive markup and aggressive robots/indexing changes.

With authorized GitHub writes: create scoped branch → patch source → run exact tests, build/lint/SSR HTML checks where runnable → inspect deployed preview when a verified deployment connection exists → open a draft PR. Check rendered HTML for metadata and routes. Approval/merge/deploy remain separately controlled operations; don't claim success before status evidence.

Report branch, commit, PR, changed routes, expected vs observed test, risk, rollback, and the precise first-party/third-party metric to inspect after publication. Keep pre/post measurement and attribution explicit.

Never request broad keys or use unsandboxed downloaded OSS installation scripts merely because a page recommends them.