We work on the parts of SEO that live in your repository: how your site is crawled,
rendered, indexed and understood. If your problem is that nobody is writing enough
content, we are the wrong studio. If your problem is that the content you already
have is not being found, read on.
Technical SEO Audit
A complete technical review of how search engines experience your site. We crawl
it the way Googlebot does, read your server logs where you have them, and test
Core Web Vitals per template rather than per page. The output is not a 90-page
PDF nobody reads — it is a prioritised list of fixes, each one scored on effort
against likely impact, written so your engineers can pick it up without a
translation layer.
Full crawl with render comparison, JavaScript included
Indexation audit: submitted vs. crawled vs. indexed
Replatforming, redesigning or consolidating domains is the single fastest way to
lose organic traffic that took years to build. We sit alongside the project from
before the URL structure is finalised through to thirty days after launch: a
complete redirect map, a staging environment QA pass, and monitoring on the day
itself so a problem is caught in hours rather than at the next monthly report.
Pre-migration crawl and ranking baseline
Complete old-to-new URL redirect map, reviewed line by line
Most structured data we find on B2B sites is either incomplete, pasted into a tag
manager where it renders after the crawler has left, or describing a page that no
longer exists. We implement schema in your templates, generated from the same data
the page renders from, so it stays correct as the site changes. Then we validate
it properly, not by looking at a green tick in a testing tool.
Entity model for your organisation, product and content
Template-level JSON-LD, generated from real page data
Validation against the Rich Results and schema.org specs
An audit is only worth what gets shipped from it. The retainer is the execution
half: a capped number of hours each month worked against an agreed plan, whether
that means writing the pull request ourselves or reviewing your team's. Every
month closes with the same dashboard, so the question at renewal is a matter of
record rather than opinion.
Capped hours, tracked against an agreed plan
Monthly crawl, regression watch and deploy review
Implementation in your repo or specs for your team
The same dashboard, in the same format, every month
Most engagements start with an audit, because it is hard to price execution against
a problem nobody has measured yet. Send us a URL and we will tell you.