SERVICE / 02

Engineering discipline, not a black box.

Migrations, JavaScript rendering issues, crawl-budget waste, Core Web Vitals — the technical debt that's expensive to get wrong. Every fix we make is logged: what changed, why, and the before/after state.

You get a change record, not a vague "we optimised your site" summary at the end of the month.

Book a free call Add to basket — from €900/mo

A close-up of a technical audit with logged code changes and timestamps.

WHO IT'S FOR

—Sites with real technical debt — legacy CMS quirks, JS-framework rendering, large catalogues.
—Teams mid-migration or rebuild, where a wrong move is expensive to reverse.
—Anyone who's been told their site is "technically optimised" and has no way to check it.

SIGNALS YOU NEED IT

—Pages you know exist aren't showing up in Search Console's index.
—Core Web Vitals scores are red and nobody's sure what's causing it.
—A recent replatform or redesign happened and rankings dipped afterwards.
—Your product catalogue is large enough that crawl budget is a real constraint, not a theory.

WHAT'S INCLUDED

What changes, logged.

Illustrative example

Before	After
Crawl budgetFaceted-filter URLs with no ranking value	Parameters canonicalised and blocked; budget redirected to real pages
Core Web VitalsLCP 4.8s on mobile product pages	LCP reduced via image sizing and script deferral, verified in field data
RenderingClient-rendered content invisible to Googlebot on first pass	Server-side or dynamic rendering fallback applied to critical templates
Duplicate contentDuplicate content across parameterised and paginated URLs	Canonical tags and pagination signals corrected, indexed count reduced

Before

Crawl budget

Faceted-filter URLs with no ranking value

After

Parameters canonicalised and blocked; budget redirected to real pages
Before

Core Web Vitals

LCP 4.8s on mobile product pages

After

LCP reduced via image sizing and script deferral, verified in field data
Before

Rendering

Client-rendered content invisible to Googlebot on first pass

After

Server-side or dynamic rendering fallback applied to critical templates
Before

Duplicate content

Duplicate content across parameterised and paginated URLs

After

Canonical tags and pagination signals corrected, indexed count reduced

Retainer, ongoing, min. 3 months · one-off project from €1,800

Every change is logged, not just made.

"We optimised your site" isn't a report, it's an assertion. Each fix on a technical SEO engagement is recorded with what was changed, why, and its measured before/after state — so you can verify the work instead of trusting a monthly summary.

— Every technical change is dated and logged, with the reasoning behind it.
— Nothing ships to production without an explanation you could repeat back to your own developer.
— Tools handle first-pass crawls and data-gathering — the fix and its priority are a human call.
— We flag what we're not touching and why, so nothing gets silently skipped.

PRICING

Pricing snapshot

€900

mo · MIN. 3 MONTHS

Technical SEO retainer Ongoing, monthly €900/mo Technical SEO — one-off project Scoped per project €1,800

Book a free call

What changes the price: Site size · CMS/platform · Extent of existing technical debt · Retainer vs one-off

See full pricing →

Frequently asked questions

Crawlability and indexing, Core Web Vitals and page speed, structured data, rendering (especially JS frameworks), duplicate content, and migration/redesign risk. Ambiguous cases get discussed with you before we touch anything.

Usually staging access and the ability to propose changes via ticket or pull request is enough; direct production access is discussed case by case and always logged.

Both exist. Ongoing technical debt and monitoring is a retainer from €900/mo; a scoped, time-boxed project (e.g. a migration audit) is a one-off from €1,800.

It gets flagged, explained, and staged/tested before going live — a wrong move on technical SEO is expensive, and the change-log exists specifically so risk is visible, not hidden.

The change-log states the before and after state for each fix, and monthly reporting ties changes back to what moved (or didn't) in Search Console and Core Web Vitals data.