Visitors find things without searching
Navigation and page relationships are defined around what people look for, so the right page is reachable from where they start.
Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

We define a page structure that reflects the property business’s actual offerings and makes the relationship between locations, services and records clear.
A few clients we’ve worked with




















We define a page structure that reflects the property business’s actual offerings and makes the relationship between locations, services and records clear.
Service names used inconsistently across pages make page relationships difficult to maintain.
A location page needs a clear purpose beyond repeating a city name.
Every site works at twelve pages. The structure decides whether it still works at eighty, once the company has added two products and a resource library.
Navigation and page relationships are defined around what people look for, so the right page is reachable from where they start.
A defined content model means the next service, case study or guide goes somewhere obvious instead of into the menu.
Deliberate relationships between pages help both buyers and search engines understand which pages matter.
The scope follows the property business’s actual services and verified information. Availability, pricing and property claims need approval from the responsible team.
Give distinct offerings a defined place and consistent name.
Connect real locations with the services genuinely available there.
Map menus, breadcrumbs and relevant cross-links to enquiry destinations.
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
The agreed engagement includes the relevant outputs below.
A sitemap and URL map.
A content relationship model.
Navigation requirements.
Explore the wider scope behind the website.
Define the audience, message, page structure, and requirements before the website moves into production.
Write the pages that explain your offer, answer buyer questions, and support your claims with evidence.
Resolve website requirements, stakeholder priorities, technical constraints, and scope before the build.
Write project stories using documented work, verified outcomes, and approved source material.
Explore the scope, deliverables and process for each part of the website.
Our process
Review services, locations and property information using actual examples.
[ 01 ]Define parent pages, shared records and routes appropriate to each audience.
[ 02 ]Walk through representative tasks and document retained URLs, redirects and internal links.
[ 03 ]No account layer between you and them. These are the Norml specialists this work runs through.

Founder & Architect

Co-founder · Design & Strategy

UI/UX Designer

“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