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

We redesign existing sites where changing offers and operating details have become difficult to keep consistent. The work connects the public layouts with a deliberate content structure, while preserving useful URLs and planning how obsolete information will be handled.
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 Fort Myers Beach. The map pin marks our Florida office in Fort Myers. We can work with teams in Fort Myers Beach from that office.
Current and old offers look equally active
Shared details disagree across pages
Retired pages have no migration decision
The scope can include offer templates, shared information components, clear date context where appropriate, and an editorial workflow. We map retained, revised, merged, and redirected URLs before launch. Verification checks both the redesigned pages and known old entry points, including forms and contact links. Your team confirms what is current before the replacement is published.
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