Verify the starting point and the delivered system
A migration record should identify the original platform, affected pages, implementation scope, and production date. The prior narrative mentions a custom HTML and CSS rebuild, but those details require confirmation against the delivered artifact. A general criticism of website builders does not prove the cause of a particular site’s performance or search behavior.
- ✓ Confirm client naming permission and implementation ownership.
- ✓ Collect the source inventory and the deployed destination.
Compare technical performance under equivalent conditions
Before-and-after tests need the same device profile, network conditions, cache state, and relevant tool settings. A single laboratory score can change without representing the full user experience. Inspect semantic structure, asset delivery, script load, accessibility, and real journey completion. Do not infer ranking causation from a faster page or the presence of structured data.
- ✓ Retain original reports and the exact pages tested.
- ✓ Check redirects, canonicals, indexability, and forms after migration.
Publish only what the record can support
Historical score changes, speed multipliers, and percentage reductions are withheld in this rebuild until the original reports are reviewed. If the evidence confirms only an implementation, describe that output rather than a commercial result. A similar project begins with its own constraints, migration plan, and rollback process; no score or search position is guaranteed.
- ✓ Separate deployment completion from measured business impact.
- ✓ Review future claims with the client before public use.