Convert Your Website to WordPress
  • Protocol
  • Tiers
  • Our Work
  • Articles
  • About
  • Request Blueprint
  • EN
  • NL

This checklist defines what “done” actually means for a migration. Acceptance becomes a clear review, not a vague feeling that the site “looks fine”.

PurposeGive clients a clear sign-off framework.
ScopePages, links, SEO basics, forms, WordPress settings, backup and rollback.
ResultA site ready for handover, not just visually complete.

1. Acceptance overview

Area Checks Pass criteria
Pages and links Homepage, key pages, navigation, assets, sitemap and important old URLs. Important paths load correctly and core links are not broken.
Content and SEO Titles, meta descriptions, canonical URLs, headings and social metadata. Search-critical information points to the production domain.
Display and interaction Header, footer, menus, responsive layout and visible errors. The site works on normal desktop and mobile review points.
Forms and email Test submissions and visible success/error states. Forms behave correctly and messages arrive where applicable.
WordPress configuration Site URLs, active theme, permalinks, page/post counts and cleanup. The WordPress installation is ready for production use.
Backup and rollback Backup folder, database/file snapshot and rollback notes. A practical recovery path exists for post-launch issues.

2. Page and URL checks

  • Homepage and all agreed key pages load successfully.
  • Navigation links point to real destinations, not placeholder anchors.
  • Important old URLs redirect to the correct new locations when redirects are in scope.
  • Images, CSS, JavaScript and downloads load without obvious errors.

3. Content and SEO checks

  • Page titles and main headings match the intended content.
  • Meta descriptions and canonical URLs use the production domain.
  • No staging, temporary or development URLs are visible in public HTML.
  • Important calls-to-action and contact paths are present.

4. Form and interaction checks

  • Each important form renders correctly.
  • A test submission is sent with a unique marker.
  • The user sees the correct success or error state.
  • The receiving mailbox is checked when email delivery is part of the project.

5. Handover checks

  • Temporary importer, fixer or migration scripts have been removed.
  • Backup and rollback location are documented.
  • Known limitations, skipped checks or client-side follow-up items are noted.
  • The client confirms that the agreed acceptance scope has passed.

Acceptance is evidence-based. The goal is not just that the site looks good, but that important paths, forms, SEO basics and recovery measures have been verified.

Convert Your Website to WordPress

We reconstruct outdated, locked legacy layouts into clean, custom-built, high-performance WordPress sites with visual parity, isolated staging, protected cutover, rollback planning, and verification.

Safe Passage

  • Our Completed Work
  • Articles
  • About the Founder
  • Twin-Vault Staging Protocol
  • Production Cutover Safety
  • Rollback Path Prepared
  • Migration Blueprint Request

Service Tiers

  • Starter Conversion
  • Business Migration
  • Multilingual Content Migration
  • Complex Rebuild

Legal & Verification

  • Privacy Policy
  • Client Protection Agreement
  • Acceptance Checklist
  • Contact & Scope Review
  • LinkedIn
© 2026 Convert Your Website to WordPress. Built with staging-first delivery discipline.
Native WordPress · No-bloat Gutenberg theme · Verification-led migration system