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, and a backlog ordered by impact against effort.
- Full crawl, log-file analysis, rendered-HTML testing
- One ticket per issue, with acceptance criteria
- Senior consultants only, no juniors
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: that is link building, and Moz’s primer is a fair definition to compare ours against.
When you need a technical SEO audit
Symptoms you can see
Pages submitted and never indexed. Traffic that fell the week a release shipped. “Discovered — currently not indexed” climbing monthly.
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.
When you do not need one
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.
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 you get at the end
The 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.
Every audit 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.
What we need: Search Console, analytics, server logs and staging. Nothing reaches production without someone on your side approving the release.
What a technical SEO audit costs
The audit is fixed-scope, quoted before it starts, with URL count and template list in the scope. Ongoing technical work is a monthly retainer covering implementation, monitoring and re-checks after each release.
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, markets or a replatform are new scope.
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 audit 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. No juniors, no account manager relaying questions. We work from Oradea, Romania, covering the European day and the US morning.
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 a technical SEO audit?
Six categories: crawling and crawl budget, indexation, architecture, rendering and Core Web Vitals, structured data, international. Sources: a crawl with and without JavaScript, server logs, Search Console, field data. Deliverables: a findings document and a prioritised ticket backlog.
How much does a technical SEO audit cost?
Fixed scope, quoted before we start — you never get an open-ended bill. 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. Ongoing technical work is a separate monthly retainer. The free automated audit is the fastest way to get your exact figure.
How long does a technical SEO audit take?
The free automated audit comes back within 24 hours. For the paid audit we agree a delivery date at scoping, once we know URL count, templates and log availability. Delays are almost always access, and critical findings reach you first.
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 audit suits a small, stable site. 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.
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 audit 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.
Get a technical audit
Start with the free automated audit: it crawls your site and comes back within 24 hours. To quote a manual audit we need your domain, URL count, platform, markets and log availability.
Prefer to talk it through? Book a free 15-minute intro call →