Technical SEO services that end in shipped fixes
Crawl. Render. Index. In that order.
Our technical SEO services start with a full crawl, server logs and Search Console data, and end with fixes live on your site. You get a findings document with evidence behind every issue, a backlog ordered by impact against effort, and someone checking the site again after each release.
- 01Full crawl, log-file analysis, rendered-HTML testing
- 02One ticket per issue, with acceptance criteria
- 03Senior consultants only
Get a technical audit
FreeStart with the free automated audit: it crawls your site and comes back within 24 hours. To scope the work that follows we need your domain, URL count, platform, markets and log availability.
Prefer to talk it through? Book a free 30-minute intro call →
What technical SEO actually covers
Everything that decides whether a search engine can crawl, render, index and trust your site. Not content, not links.
Crawling and crawl budget
Robots directives, sitemap accuracy, redirect chains, parameter traps, crawl reach.
Indexation
Canonicals, duplicate templates, thin URLs, staging noindex, soft 404s. Which URLs deserve indexing, and whether the site says so.
Architecture and internal links
Click depth, orphan pages, category structure, anchor distribution.
Rendering and performance
Raw against rendered HTML, hydration, lazy-loaded content, Core Web Vitals.
Structured data
Schema that matches what is visible and qualifies for a rich result. Validated, not guessed.
International
Hreflang reciprocity, x-default, language against market targeting, real localisation.
It does not fix weak content, absent demand or missing authority. How a page is written and targeted sits under on-page SEO optimization, and authority under link building. Moz's primer is a fair definition to compare ours against.
The symptoms that bring people here
Most of them get diagnosed as a content problem first, and a quarter's content budget gets spent before anyone checks the crawl.
Symptoms you can see
Pages submitted and never indexed. Traffic that fell the week a release shipped. "Discovered - currently not indexed" climbing monthly. A category that ranked for two years and quietly stopped.
Sites that need it most
Ecommerce catalogues with faceted navigation, multi-market sites, large affiliate portfolios where near-identical URLs compete for crawl budget. Any headless build, and anything replatformed in the last year.
When you do not need us
A small site on a maintained theme, crawling cleanly, no migration planned. Run the free audit, then spend the budget on content, links or conversion work.
Not all of it is technical. We check your release log and the algorithm-update calendar against the date traffic moved before we sell you a crawl, because a core update and a broken canonical look identical in a line chart.
Audit, or ongoing engagement?
Two different purchases. Most sites need one of them, not both.
Buy the audit
You need to know what is broken, in what order, and who owns each fix. The site is stable, releases are rare, and you have developers who will ship a backlog once it lands. That is fixed scope with an end date: the technical SEO audit service.
Buy the ongoing service
You release weekly, run several markets, or have watched the same issue come back twice. Here the value is in the fixes and the monitoring between releases, not in the document. This page is that service.
Both, in that order
Large sites usually audit first, then keep a retainer for implementation and release monitoring. The audit is quoted separately, and we will tell you at scoping if the second half is not worth buying yet.
What we check, and with which data
The crawl
Mobile user agent, run twice: rendering on, then off. What appears only in the rendered crawl is a risk. Cross-checked against Ahrefs Site Audit.
Server log files
What Googlebot requested and what it got back. Distribution by template, hits wasted on parameters and redirects.
Search Console
Coverage by status and template rather than one total, Crawl Stats, and the URL Inspection API for rendered HTML.
Core Web Vitals
Field data first, by device and template. Lab data second, for cause: LCP element, render-blocking resources, layout shift, interaction delay.
Canonicals, pagination, facets
Which parameter combinations are crawlable, canonicalised or blocked. Filter and session parameters, links pointing where you never wanted indexing.
Structured data and hreflang
Markup validated against current specs, mismatches between schema and visible content, hreflang reciprocity in both directions.
What ongoing technical SEO involves
An audit is a snapshot you buy once. The service is what keeps that picture true through every release after it.
Baseline and access
Crawl with rendering on and off, Search Console read by template, logs where hosting allows, field data by device. Tracking is checked before anything is measured against it, since a broken setup makes every later number arguable, and repairing one sits under Google Analytics implementation. That baseline is what every later claim gets compared with.
The first fixes ship
Blockers first: anything stopping a template being crawled, rendered or indexed. Tickets go out with acceptance criteria, each one verified after it deploys rather than when it is marked done.
Crawl diff and regression watch
A crawl after every significant deploy, compared with the last. Robots, canonicals, noindex, internal links and schema break quietly during releases, and a staging noindex that reaches production costs weeks.
Re-rank the backlog
Coverage, crawl stats and vitals reviewed by template rather than as a site total. New findings enter the backlog, resolved ones leave it, and you get a written note on what changed.
This is the part a one-off audit cannot do. A document is accurate on the day it is written. A site with a release cycle is not the same site a month later.
What you actually get
The findings document serves two readers: whoever signs off the budget and the developer who ships the fix. Each finding states what is wrong, where we saw it, what it costs, and what a correct fix looks like.
The backlog is separate: one ticket per issue with acceptance criteria a developer can test against. When fixes ship we re-crawl and confirm each.
In an ongoing engagement the backlog never closes. Resolved items leave it, new findings enter after each release, and the document is versioned rather than rewritten from scratch every quarter.
Every engagement includes
How we work with your developers
The real question is who does the work once the document lands. Two modes, priced differently.
We write, your team ships
We write the tickets, answer questions during implementation, verify each one after deployment.
We implement
On WordPress and Shopify we do the work: templates, schema, redirect maps, robots and sitemap logic. Heavier builds go through our WordPress development team; store work sits under Shopify SEO.
Migrations
Crawl of the old site, a URL-level redirect map, staging validated with indexing blocked, then coverage and rankings watched daily after launch.
Every ticket carries the same six things: what is wrong, the evidence we saw it in, the templates or URLs affected, what a correct fix looks like, acceptance criteria your QA can test, and how we verify it after release. Developers push back on SEO tickets when they read as opinions. These read as bugs.
What we need: Search Console, analytics, server logs and staging. Nothing reaches production without someone on your side approving the release, and changes to redirects, robots or canonicals go out in a release you can roll back rather than as a live edit.
What technical SEO services cost
Ongoing technical SEO is a monthly retainer covering implementation, monitoring and the re-checks after each release. A one-off audit is fixed scope, quoted before it starts, with URL count and template list written into the scope.
Four things move the price: URL count; template count, since a large catalogue on few templates is a smaller job than a small bespoke site; markets and languages; and whether we implement or hand over.
A re-audit verifies fixes against the existing backlog. New sections, new markets or a replatform are new scope, quoted separately.
What we will not do
"Nothing enters the backlog that we cannot justify with evidence from the crawl, the logs or Search Console."
The Web Push technical standardCrawlers produce hundreds of flags and most are noise; a missing meta description on a paginated URL is not a finding. We also flag what we cannot fix: platform limits, a container nobody controls, a theme that needs replacing.
We never attach a traffic number to a technical fix; nobody honestly forecasts recovery from an indexation fix. We report what changes mechanically: pages crawled, pages indexed, render parity, LCP.
Who does the work
The person who crawls your site writes the document and takes the call. Senior-led, with no account manager relaying questions. We cover both European and US business hours.
Our depth is in large affiliate and iGaming portfolios and multi-market ecommerce. That work sits under NDA, so instead of screenshots we walk you through a redacted audit document on the scoping call.
Fair questions, straight answers
What is included in technical SEO services?
Six areas: crawling and crawl budget, indexation, architecture, rendering and Core Web Vitals, structured data, international. The evidence comes from a crawl run with and without JavaScript, server logs, Search Console and field data. You get a findings document, a prioritised ticket backlog, verification after each fix ships, and a crawl diff after every significant release.
How much do technical SEO services cost?
Ongoing work is a monthly retainer. The price moves with URL count, template count, how many markets and languages are involved, and whether we implement the fixes or hand the backlog to your developers. A one-off audit is quoted separately as fixed scope, before it starts, so you never get an open-ended bill. The free automated audit is the fastest way to get a figure for either.
What platforms do you work on?
We implement directly on WordPress and Shopify. On any other stack we write the tickets and your developers ship them, which is faster than teaching an outside team a codebase. We test headless and JavaScript builds whatever the framework, because the checks run against rendered output rather than source code.
Do you fix the issues or just report them?
Both, priced differently. With developers in-house, we write tickets with acceptance criteria and your team ships them, usually faster and cheaper. Without dev capacity we implement on WordPress or Shopify, staging first, with your sign-off. Whoever writes the code owns deployment and testing.
Is technical SEO a one-off or an ongoing service?
A one-off suits a small, stable site, and that is a fixed-scope job: the technical SEO audit service. If you release weekly or run several markets, technical debt returns with every deployment. Ongoing means a crawl diff after each significant deploy, coverage watched between releases, and a standing backlog.
We have developers and run our own crawls. What do you add?
A crawler produces hundreds of flags with no order and no evidence attached. What we add is the diagnosis and the priority: which flags are costing you indexed pages, which are noise, and what a correct fix looks like inside your templates. Good developers ship faster than we could. They should just not be the ones deciding whether a canonical is wrong. If your team already does that work, you do not need us.
How long before technical fixes show in search?
The free automated audit comes back within 24 hours. Fixes move at two speeds after that. Crawl and indexation changes can show inside a crawl cycle, sometimes a fortnight on a site Google visits often. Architecture, rendering and vitals work takes longer, because it has to be recrawled at scale before it counts for anything. Mechanical numbers move before commercial ones, and we report them in that order.
Will technical SEO fix my traffic drop?
Only if the cause is technical. We diagnose first: drop date against your release log and known algorithm updates, then coverage and rendering on the affected templates. Just as often it is a core update, content decay or lost links, which is a link building problem. Diagnosis is a fixed-scope piece of work, quoted up front.
Do you handle site migrations?
Yes, and before launch rather than after. Before: a crawl of the old site, a URL-level redirect map, staging validated with indexing blocked, templates checked for tags and schema that disappear in rebuilds. After: coverage, redirect hits and rankings monitored daily through the first crawl cycle. Migrations change everything at once, which makes them the riskiest job.
Can you work on a JavaScript or headless site?
Yes. We compare raw against rendered HTML per template, then test hydration, client-side routing, lazy-loaded content and internal links. Common headless failures: content that appears only after an interaction, a 200 shell where a 404 belongs, canonicals injected client-side. Some of that needs a front-end change, not an SEO setting. Rendering matters for AI crawlers too, covered under AI SEO.