LEYUN · SITE LAUNCH CHECKLIST独立站上线自查清单库

Release Review for Site Version Updates

Sections: Review & Verticals · Reviewed: 2026-11-21 · 12 items

Key takeawayAny release can touch routes, templates, markup or scripts, and problems often appear hours later. This sheet fixes the actions before and after a release so a rollback decision has something to stand on.

Industries and use cases

  • Before a major template or feature release
  • When routes and URL structure change
  • After adding a new third-party script
  • When an anomaly appears after release and a rollback must be judged

Checklist

Checklist: release review for version updates
Check itemPass criteriaRisk levelFix hint
Change listChanges, affected page scope and owners are listed before releaseHighList by module and flag impact on URLs, templates, scripts and data.
URL change mappingWhen addresses change, the old-to-new 301 map is complete and deployedHighCheck the map line by line and spot test immediately after release.
Staging validationCore flows pass in staging, including forms, payment and downloadsHighKeep staging close to production so differences do not hide problems.
Canary releaseMajor changes open to a small traffic share first, watching error rate and conversionMediumRelease by region or user percentage and go full once stable.
Cache purgeHTML and CDN caches are purged after release and external access shows the new versionHighPut the purge step into the release runbook so no node is missed.
Markup revalidationStructured data on changed pages is re-tested with no new errorsMediumFocus on product, article and breadcrumb types.
Sitemap updateAdded and removed URLs are synced in the sitemap and lastmod is updatedMediumSubmit once after release and watch the read status.
Form regressionInquiry, subscription and download forms are each submitted once and notifications arriveHighTest with a real mailbox and check spam and auto-replies.
Analytics eventsKey event tracking is intact and data appears in reportsMediumCheck real-time reports on release day to confirm data is flowing.
Rollback planPrevious files and a database snapshot are kept and rollback steps are executableHighRehearse rollback at least once and define who is allowed to call it.
Post-release monitoringError rate and core page status are checked hourly for 24 hours after releaseHighSet alerts for anomalies instead of refreshing pages manually.
Legacy link monitoring404 and redirect reports are reviewed daily for a week after releaseMediumMap newly broken URLs as they appear.

Common misjudgements

  • Treating an open page as a successful release, when forms, tracking and redirects often fail only on a real submission.
  • Not recording small changes, so when a problem appears after several of them there is no way to identify the cause.
  • Rolling back files without the database, which creates a new inconsistency after a schema change.

How to use this checklist

  • Pair with the full launch sheet: this one covers iteration on a live site, not the first launch.
  • Run for every release and repeat once a week after a major version.
  • Link with the periodic review sheet so release records feed long-term monitoring.

FAQ

Do small changes need the full process?
They can be reduced to URLs, forms and cache, but a record should still be kept.
How much traffic does a canary release need?
Usually 5% to 10%, enough to observe anomalies within hours.
What follows a rollback?
Purge caches, re-check forms and redirects, and record why the rollback happened.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.

If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.

Note: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.