Inventory what the current site actually does.
Begin with the live URL. Identify pages, templates, service areas, forms, tracking, domains, redirects, structured data, third-party scripts, and every destination a customer can reach.
Vyra Sites can use that system as the first source for a rebuilt draft, but the inventory remains the contract for what cannot disappear silently.
Separate durable truth from inherited presentation.
Service definitions, locations, policies, proof, contact paths, and legal requirements are durable inputs. Old navigation, duplicated pages, visual conventions, and plugin workarounds are implementation choices that can change.
The rebuild should preserve the business truth while improving how customers find, understand, and act on it.
- Keep: verified facts, valuable URLs, customer proof, and operating requirements
- Reconsider: hierarchy, page structure, copy, forms, and conversion paths
- Remove deliberately: duplicates, unsupported claims, obsolete scripts, and dead journeys
Connect capture before launch.
Every Vyra Form should be tested through the full path into Vyra: source context, consent, routing, notifications, assignment, and the first Phone or email action.
A successful form confirmation is not enough. The responsible person must receive a decision-ready record and the customer must receive the expected response.
Treat launch as a reversible operational event.
Domains, certificates, caching, redirects, analytics, and monitoring should be prepared before traffic moves. The prior site remains recoverable until the new release is verified against the inventory.
After launch, inspect real navigation, form delivery, search-crawler behavior, performance, and error logs before the migration is considered complete.