Case study · SleepyCat
600% more organic traffic for a D2C sleep brand
A competitor gap-led keyword and category page programme across the full catalogue.
Read case studyCase study · CultureMonkey
Keyword and content architecture across category, comparison and use case intent.
The brief
CultureMonkey sells an employee engagement product on subscription, in a B2B SaaS category where buyers research and compare before they commit. The brief was to build a keyword and content architecture covering three kinds of search intent: category, comparison and use case. Each intent needed a clear home on the site, so pages would support each other instead of competing for the same queries.
What we did
We started with a technical audit covering crawl and indexation, site speed, internal linking and URL hierarchy. Keyword research then mapped the searches buyers make across the category and sorted them into category, comparison and use case intent. Each intent was given its own page type, section and linking rules within the architecture. Founders and marketing leads received monthly reporting on progress.
The outcome
The engagement delivered a keyword and content architecture that gives category, comparison and use case intent each a defined set of pages, built on a technically audited site.
How we approached it
Every engagement runs on the four-stage method, applied to CultureMonkey's site and category.
A full technical crawl plus a check of how Google and the major AI engines currently see, describe and cite your brand.
Keyword and intent mapping to page types, with the internal linking and schema that let both crawlers and LLMs understand the site.
A monthly cadence of category, comparison and answer-first content, drafted with AI and finished by people who know the subject.
Quarterly refresh cycles, off-site presence and reporting to pipeline, so the gains keep stacking instead of decaying.
Scope of work
Every engagement starts with a technical audit. A content architecture is a plan for where pages live and how they connect, so it has to sit on a site that search engines can crawl and index cleanly. Designing new sections on top of unresolved technical issues only spreads those issues further.
The audit covered:
The URL hierarchy findings fed straight into the architecture work, because the new structure had to fit the site as it stood.
We built a full map of the searches buyers make around employee engagement: the problems HR and people teams search for, the software category terms, the names of competing products, and the specific jobs teams want a tool to do. For a subscription product, this map needs to reach well beyond the product's own features, since many buyers start with a problem and only later learn which category of software solves it.
Every keyword was then classified by intent. This is the step that decides what kind of page each query deserves:
Keeping these apart matters. A category page that also tries to be a comparison page usually ranks for neither, and two pages chasing the same intent split their signals.
Each intent was given its own page type and its own section of the site. Category pages act as hubs. Comparison pages sit together, each covering one matchup or one set of alternatives. Use case pages sit together, each built around one job. Every keyword cluster maps to exactly one URL, which removes the risk of the site competing with itself.
The architecture includes rules for how pages link. Category hubs link down to the relevant use case and comparison pages. Use case pages link back up to their category and across to related use cases. Comparison pages link to the use cases where the products differ most. Written rules keep the structure intact as new pages are published.
Founders and marketing leads received monthly reporting, which kept the architecture decisions visible and gave the team a shared reference for what was built and what came next.
| Intent | What the searcher wants | What the page needs |
|---|---|---|
| Category | To understand a type of software and shortlist options | A clear definition, the problems it solves, and links into use cases and comparisons |
| Comparison | To choose between named products or find an alternative | A fair side-by-side view and an honest who-it-suits section |
| Use case | To see how a tool handles a specific job | The job in the buyer's language, the workflow, and links back to the category |
The architecture is what makes later content efficient. When every new piece already has a defined place and defined links, the content team spends its time on writing instead of debating where a page should go.
If your SaaS content has grown page by page without a plan, an intent-led architecture gives it a shape: a home for every type of search and clear links between them, so each new page adds to the whole.
Your turn
Start with a free AI search audit. Our founder reviews your site personally and shows you the fixes worth the most revenue.
More work
Talk to the founder
Tell us what you want to rank for and where growth has stalled. We will tell you straight whether search is the right lever, and what it is worth.
Abhishek DwivediFounder and Lead Strategist, AD Search Studio
