TECHNICAL SEO — MONTHLY RETAINER
Crawling, indexing, and Core Web Vitals, treated as infrastructure — not a marketing footnote.
Log-file analysis, render/indexing diagnostics for JS-heavy stacks, and Core Web Vitals work tied to specific templates — delivered as ticket-ready specs your engineering team can pick up directly.
Who it’s for
Sites that migrated or replatformed and lost rankings
Sites that migrated or replatformed and lost rankings — a domain move, CMS switch, or redesign changed URLs, templates, or rendering.
JS-heavy stacks
JS-heavy stacks — React/Vue/Angular front ends where what Googlebot renders isn't what a browser renders.
Failing Core Web Vitals
Failing Core Web Vitals — LCP, INP, or CLS in the red on Search Console, with no clear owner on the dev team.
Crawl-budget waste
Crawl-budget waste — large sites where Googlebot spends its budget on parameter URLs and thin pages instead of the ones that convert.
What’s included
This retainer runs the way a piece of production infrastructure gets maintained: log-file analysis to see exactly what Googlebot is requesting and ignoring; render-and-indexing diagnostics that compare what's served to what's rendered on JS-heavy templates; Core Web Vitals investigation broken down by template and component, not a single site-wide score; and canonicalisation, redirect, and structured-data work specified precisely enough that a developer can implement it without a follow-up call.
Process
01 — Log-file & crawl-budget analysis
What Googlebot actually requests, how often, and where it wastes budget.
02 — Render/indexing diagnostics
What's rendered client-side vs. server-side, and whether Google sees the same page a user does.
03 — Core Web Vitals investigation by template
LCP/INP/CLS broken down by the templates and components that actually drive it, not a single blended score.
04 — Ticket-ready handoff
Findings specified as tickets your engineering team can pick up directly: priority, evidence, fix, and owner, ready to drop into a sprint.
Proof
Illustrative example — a JS-heavy marketplace client's indexed-page count and Largest Contentful Paint, before and after the render-fix work shipped. Indexed pages: roughly 61% of the eligible catalog before, 94% after, over ten weeks. LCP on product templates: 4.1s before, 2.3s after.
Illustrative examplePricing
Technical SEO
2.400 € / month
3-month minimum term, then 30 days' written notice.
FAQ
General web-performance work and technical SEO at scale overlap but aren't the same discipline — crawl budget, render/indexing gaps, and structured data rarely show up in a standard performance audit. We scope this as a complement to your existing team: ticket specs your developers implement, not a request to hand over or rebuild your stack.
No. Findings are delivered as specifications; your team, or a contractor we coordinate with, implements them.
It depends on how much is client-side vs. server-side today and how quickly engineering can ship the fixes — we'll give you a realistic range on the call, not a fixed date.
That's a common starting point. We can scope the review around the migration timeline specifically: redirects, canonical mapping, and rendering checks before and after cutover.
No — the fastest return is usually on mid-size JS-heavy sites where a handful of templates carry most of the organic traffic. Site size changes scope, not eligibility.