Preservation review
Identify useful pages, search entry points, forms and components before replacing them.
Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

A product-site redesign for an Arcadia team needs decisions about existing records, document links and enquiry destinations before layouts change. We review which material remains accurate, which explanations need improvement and which URLs already have a continuing role in sales conversations.
A few clients we’ve worked with










Revise the page system while accounting for existing content, URLs and working enquiry paths.
We do not have an office in Arcadia. The map pin marks our Florida office in Fort Myers. We can work with teams in Arcadia from that office.
Old document links may still appear in sales correspondence.
Related products need explicit differences in the revised layout.
Current enquiry routes must be accounted for during replacement.
The redesign can introduce clearer product and comparison templates while preserving approved technical content and useful addresses. Changed pages receive an explicit mapping rather than a blanket redirect. We review representative specifications on smaller screens and define the new editing responsibilities. Implementation and cutover checks follow the agreed scope, with unresolved product facts returned to the client reviewer.
Identify useful pages, search entry points, forms and components before replacing them.
Decide which page roles stay, change or merge and record the reasons.
Test hierarchy, content length and enquiry paths across desktop and phone layouts.
Specify URL mappings and acceptance checks for the agreed implementation.
The approved scope determines the final deliverables:
An inventory of pages and functions to retain or change.
An approved page map and representative wireframes.
Responsive page designs and reusable component rules.
A redirect and launch-check specification for the build team.
Our process
Review existing pages, search data where available and the work performed by forms and integrations.
[ 01 ]Agree content ownership, page roles and which existing paths must be preserved.
[ 02 ]Review new layouts with actual service copy and proof.
[ 03 ]When implementation is included, check redirects, forms and critical pages before and after release.
[ 04 ]
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get started