The repository is the editing surface
Vercel and Cloudflare Pages deploy the site, but the durable source of truth is the repository. SEO changes should be branches and pull requests with the same tests, review, authorship, and recovery expectations as other product changes.
Use framework-native primitives
Start with Next.js metadata, canonical and alternate rules, sitemap and robots routes, redirects, JSON-LD, static generation behavior, and the rendered link graph. Avoid injecting a second competing metadata system when the framework already owns the document.
Verify the preview before merge
Crawl the preview deployment, inspect page metadata and structured data, check links and status codes, and compare the intended diff with the rendered output. Approval should bind to the reviewed commit and change set.
Pair deployment rollback with Git recovery
Rolling traffic back at the provider does not change the repository. Create a revert pull request too, or the next deployment may restore the defect.