Services · Search
SEO Strategy and Delivery
Search work for publishers and review websites, delivered as documents your team can act on: a prioritised audit, a demand map, a section architecture, development tickets with acceptance criteria, and reporting that separates what we changed from everything else.
What the work covers
Five Areas, Each With a Defined Result
| Area | What we do | What you receive |
|---|---|---|
| Technical audit | Crawl and render analysis, indexation, canonicalisation, structured data, performance and template-level issues, with the impact of each finding explained. | A prioritised audit: issues ranked by impact and effort, each with an owner and a proposed fix. |
| Audience and demand research | Search demand by topic, intent and market, mapped against what your audience already reads and what competitors cover. | A demand map by topic cluster and market, with the gaps and priorities marked. |
| Site structure and internal linking | Section architecture, URL patterns, navigation, hub and article templates, and the internal linking rules that hold them together. | A section map and a linking plan that fits your existing site rather than replacing it. |
| On-page implementation | Titles, headings, metadata, structured data and template changes specified precisely enough to build and test. | Development tickets with acceptance criteria, and implemented templates where we build them ourselves. |
| Measurement and ongoing improvement | Tracking of indexation, visibility, traffic and engagement, with changes annotated so effects can be attributed honestly. | A dashboard and a monthly report with the next period's priorities. |
Technical SEO
Technical SEO: Specifications, Not Suggestions
Most SEO recommendations fail at the hand-off. We write every change as a ticket your developers can pick up: the current behaviour, the required behaviour, the templates and URLs affected, the acceptance criteria and how we will verify the change after release. Where a change is risky, we propose a staged rollout and a rollback condition.
- Tickets with acceptance criteria and test steps
- Staging checks before and after release
- Redirect and canonical maps for structural changes
- Release notes annotated in the reporting
- Regression checks for indexation and performance
- Documentation your team keeps after the engagement
Analytics and reporting
What We Measure and What We Do Not Promise
We report on the work delivered and on the indicators it is meant to move, such as indexation coverage, visibility for the mapped demand, organic traffic and engagement, separating organic from paid traffic and revenue from profit. We do not promise rankings, traffic levels or revenue, and we do not present correlation as proof. Where attribution is uncertain, the report says so.
Discuss Your SEO Project
Tell us about the site, the markets you serve and the problems you are trying to solve. We will propose a scope and a first set of deliverables.