Security and data
- Replace shared admin access with named users, roles, and activity history.
- Remove the demo/VPS environment’s access to production data.
- Use isolated staging with synthetic test records and files.
- Enable database and private-bucket backup/PITR; test restore.
- Apply upload allowlists, size limits, malware controls, rate limits, and private storage.
- Approve claim retention, deletion, access, and backup requirements.
Route-by-route quality
For English and Spanish: verify navigation, titles, headings, product facts, disclosures, links, forms, confirmations, error states, metadata, canonical tags, hreflang, structured data, sitemap inclusion, robots behavior, keyboard access, contrast, responsive layout, performance, and consent behavior.
WordPress preservation
- Crawl URLs, content, media, forms, scripts, pixels, rankings, backlinks, and email dependencies.
- Approve keep/rewrite/retire decisions and one-to-one redirects.
- Preserve Search Console, analytics history, and important campaign parameters.
- Run the cutover with lowered TTL and a written rollback.
- Validate critical journeys for seven clean days and monitor SEO for 30 days.
- Keep a private archive for 60–90 days, then decommission after approval.
Launch approval record
Record date, approvers, exact commit/deployment, database environment, redirect-map version, DNS before/after values, backup reference, rollback owner, business-contact availability, and post-launch monitoring window.