SEO management for pages that sell
One monthly programme: technical fixes, content architecture and internal links, aimed at the queries that end in a sale rather than the ones that end in a visit.

The problem
Traffic arrives and nothing follows it. The pages that rank were written for a topic, not for a buyer, and the page that would close the question either does not exist or is competing with three older ones for the same words.
You are probably here if
If three or more of these are true, this pillar is where your constraint lives.
- 01The blog outranks the pages that sell
- 02Rankings move and enquiries do not
- 03Two or three pages compete for one query
- 04A migration lost positions nobody has recovered
- 05Nobody can say which page is supposed to win which search
What we actually do
Technical SEO
Crawl, index, speed and structured data. The faults that hold every page back at once, fixed first.
Intent mapping
Every commercial query matched to the one page that should answer it, and the gaps named.
Content architecture
Merge what competes, write what is missing, retire what earns nothing.
Internal linking
The structure that tells a search engine which page you consider the answer.
Migration cover
A replatform or redesign without losing the positions you already paid for.
AI search readiness
Clear answers, structured data, and being the source that gets cited rather than summarised away.
Question map
The questions buyers actually ask before they sign, ranked by how close each one sits to a decision.
Long form
The pages that take a whole decision apart. Written by somebody who understood the answer before writing it.
Refresh programme
The published pages that lost their answer, found and corrected before they lose their position.
How it runs, and where you can stop
Each phase ends with something you own. Stopping after any of them leaves you better off than before it.
- 012w
Audit
Crawl, index coverage, Core Web Vitals, and the queries you already rank for without noticing.
- 022w
Architect
The page map: what merges, what gets written, what dies, and the link structure that connects them.
- 03ongoing
Execute
Fixes shipped, briefs written, pages published and linked. A monthly cycle with a standing report.
- 046mo+
Compound
Double down on the clusters that moved. Retire the ones that did not, on the evidence.
What you receive
Artifacts, not a slide deck. Each one is usable by your team without us in the room.
- Technical audit with fixes ranked by what they cost and what they return
- Intent map from query to page
- Content architecture and page map
- Internal linking structure
- Briefs for every page worth writing
- Monthly report against enquiries, not sessions
What this is usually built on
One engagement from this pillar
Most traffic landed on pages nobody could buy from
Strong organic volume, weak pipeline, and a content library built on a publishing calendar rather than on intent.
Read the case- Enquiries
- 1.0x2.4x
- Indexed pages
- 368118
- Enquiry cost
- 1.0x0.76x
Rolling 12 months against the preceding 12. Source: PostHog and CRM, July 2025
Not a fit if
We would rather lose the engagement on this page than at week six.
- Nobody internally can approve deleting or merging existing pages
- The result is needed this quarter and there is no organic base to build on
- Success is defined as rankings rather than enquiries
Asked on almost every first call
How long before this works?
Technical fixes move within weeks. Architecture compounds over two to three quarters. If the quarter itself is the deadline, paid search is the honest answer and we will say so.
Do you write the content?
We write the architecture and the briefs, and the content too when the subject is technical enough that a generalist would get it wrong.
Will you delete pages?
Usually yes. Thin pages competing with each other is the most common fault we find, and merging them is the fastest win available.
What about AI search?
The same work. Clear answers, structured data, and being the source worth citing. It is not a separate programme and we do not sell it as one.
Do you guarantee a position?
No, and neither can anybody honest. We report the queries you gained, the pages that took them, and what it did to enquiries.
Bring the constraint, not the brief
If three or more of these are true, this pillar is where your constraint lives.