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 St. Petersburg redesign should leave the business with coherent page patterns and clear operational responsibilities. We review the existing structure, content and dependencies alongside the visual identity before defining what changes.
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 St. Petersburg, and the map is honest about it: the pin is our Florida office in Fort Myers, about 135 miles north-west of our Fort Myers office. The distance changes how easy it is to meet, not how the work runs.
New visual designs retain an unsuitable service hierarchy.
Each added page requires a different editing process.
Existing integrations and account owners are missing from the brief.
We inventory page roles, functional connections and useful URLs, then design reusable patterns around the B2B offer. The migration plan covers content, redirects, forms and measurement behaviour. Handover requirements are reviewed before launch so the company knows how the redesigned system is maintained and which dependencies remain.
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