Pages, not spreadsheets
Terms grouped by intent and mapped to existing or proposed pages give the content team something to act on.
Optional analytics, advertising and case-study videos are off. Allow them all, or open settings to choose. Privacy policy

We research the terms customers use for the range, including relevant attributes and buying questions. The output groups queries by useful page purpose and records measured demand separately from gaps in available data.
A few clients we’ve worked with




















Keyword research for ecommerce businesses: catalogue language, intent research, page mapping.
An attribute query needs products that actually meet the attribute.
Supplier terminology may differ from customer language.
Care questions and purchase queries can require different content formats.
A keyword list is not a plan. Research is only useful once each term is attached to a page that could realistically win it.
Terms grouped by intent and mapped to existing or proposed pages give the content team something to act on.
Checking the result pages shows where the intent is commercial and where a term only looks valuable in a volume column.
One page per intent prevents two of your own pages fighting over the same search.
Plan catalogue language, intent research and page mapping as connected parts of the engagement.
Collect product types, attributes and customer terminology. Distinguish supplier labels and terms shoppers use to compare items.
Review search results and available metrics in the intended market. Separate purchase, comparison, care and support needs.
Assign query groups to products, collections or supporting content. Exclude topics the current range cannot satisfy.
“What I appreciate most is that the team always communicates openly and stays honest throughout.”
“They delivered what they said they would, on time.”
“They met all our expectations by providing great strategies based on our needs.”
The agreed keyword research scope is documented in the following work products.
Source-linked query and intent research
Keyword groups mapped to pages
Metric gaps and editorial dependency notes
Explore the wider scope behind the website.
Connect search research, technical improvements, page structure, and content planning with your business priorities.
Keep ongoing updates, backups, functional checks, technical support, and website improvements organized.
Measure loading bottlenecks and implement targeted improvements with comparable verification.
Test critical journeys, responsive layouts, content, and integrations with reproducible bug reports.
Explore the scope, deliverables and process for each part of the website.
Our process
Review range attributes and purchase questions rather than relying only on supplier labels.
[ 01 ]Inspect search context and available metrics for purchase, comparison and support queries.
[ 02 ]Assign query groups to relevant products, collections or guides and record unsupported-range exclusions.
[ 03 ]No account layer between you and them. These are the Norml specialists this work runs through.

“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