Technical SEO
The groundwork that everything else depends on.
I diagnose complex technical problems that automated tools will not catch. I specialize in large online stores and JavaScript-based websites, where one error lowers the visibility of the whole catalog, not of a single page.
Who it is for
When does technical SEO really make sense?
Technical SEO is not a service for every website. It makes sense when a technical problem blocks visibility, or when a change of platform or domain threatens to cost a large part of your traffic.
Four situations in which technical diagnosis and optimization pay off the fastest:
01
E-commerce with hundreds or thousands of URLs
Online stores have their own technical problems: duplicate URLs created by filters and sorting, category cannibalization, inefficient crawling of the catalog and wrong canonical tags. In a large store, one error can block the visibility of a whole category, not just one page.
02
JavaScript-based websites (React, Vue, Angular)
Googlebot renders JavaScript with a delay and does not click or scroll the page like a user, which many developers do not expect. I diagnose CSR, SSR and SSG rendering problems at the framework level: Next.js, Nuxt.js, Angular Universal. When Search Console says “indexed” but there are no rankings, rendering is often the cause.
03
A company before or after a domain migration or redesign
A domain change, a new CMS or a new URL structure done without a technical audit and a redirect plan can take away a large part of your existing traffic from Google. I plan migrations on the technical side and check the redirects after launch.
04
A website with a technical problem nobody can figure out
A sudden drop in visibility, pages indexed despite noindex, duplicate content with no visible cause, Googlebot ignoring the sitemap. I specialize in problems that need server log analysis and manual crawling, not just a tool report.
Next step
Do you have a technical problem
nobody can figure out?
The intro call is free. Describe the problem, and then I will analyze the logs, crawl the staging version and check the JavaScript rendering.
What technical SEO is
The groundwork that everything else depends on.
Technical SEO is the part of optimization that Googlebot sees, not the user. It covers everything that decides whether Google’s crawler reaches a page, indexes it correctly and rates it well on the technical side: crawling, performance, URL structure and structured data.
Technical problems work like roadblocks. If Googlebot cannot index a page, no content and no links will bring it to high positions.
I specialize in complex technical problems, especially in large stores and portals built on JavaScript (React, Vue, Angular, Next.js). I analyze server logs, crawl the staging and production versions and check the rendering.
Working on large stores, media portals and financial websites taught me things you do not see in small projects: how Google allocates crawl budget on websites with hundreds of thousands of URLs, and how to look for errors in server-side rendering.
Experience
In SEO since 2012, mostly at agencies.
I know where the errors that Screaming Frog will not show are hiding, because I have diagnosed them in large stores, media websites and financial websites.
Service scope
What does technical SEO cover?
Three pillars handled in parallel: crawling and indexing (does Googlebot see what it should see), performance (how fast the page loads according to Google’s metrics) and architecture with structured data (how Google understands the structure and meaning of the content). I diagnose each problem, set its priority and prepare an implementation specification.
Pillar 01
Crawlability and indexing
What I check in detail
- Crawling the website (Screaming Frog and the Page indexing report in GSC)
- Server log analysis: Googlebot behavior and crawl budget
- Diagnosing and fixing indexing errors (noindex, nofollow, robots.txt blocks)
- Robots.txt and sitemap.xml structure: correctness and freshness
- JavaScript rendering diagnosis (React, Vue, Angular, Next.js, Nuxt.js)
- Redirect audit: chains, loops, 404 errors
- Finding duplicates and setting canonical tags
Pillar 02
Performance and Core Web Vitals
What I check in detail
- Measuring and analyzing Core Web Vitals (LCP, INP, CLS) in PageSpeed Insights and CrUX
- Performance bottlenecks (render-blocking resources, the LCP image, layout shifts)
- Page speed optimization: a specification for the developer
- Lighthouse and Web Vitals analysis on staging and production
- Coordinating the work with the developer during implementation
- Measuring the results after the performance optimizations go live
Pillar 03
Architecture and structured data
What I check in detail
- URL architecture: hierarchy, parameters, canonicalization
- Hreflang and multilingual setups: implementation and validation
- Schema.org structured data: full implementation (Article, Product, FAQPage, BreadcrumbList, Organization)
- Internal linking: topic clusters and the flow of authority
- Pagination: indexable subsequent pages with their own canonical tag
- Technical specifications ready for developers to implement
What you get
A specification, priorities
and implementation oversight.
Instead of a list of errors exported from a tool, you get a technical specification you can hand to a developer, with priorities, an impact estimate and a check after implementation.
- A diagnostic report with prioritiesEach problem with a score for difficulty (1–5) and estimated impact (1–5). You know where to start and what to expect from it.
- A technical specification for the developerA ready-to-use implementation document, not an “SEO wish list”. The developer knows what to change and how, so the problem gets solved rather than worked around.
- Verification after implementationI check whether the changes made by the developer actually solved the problem: a new crawl, a rendering test and GSC analysis. Without this check, “implemented” often means “fixed only on paper”.
Step by step
How does a technical diagnosis work?
Five stages: from a free intro call, through crawling and diagnostics, to an implementation specification and a check after launch.
The duration depends on the size of the website and the complexity of the problem. A simple technical audit: 3–5 days. A complex diagnosis of a large store or a JavaScript-based website: 1–3 weeks.
01
Free intro call
We talk online. You tell me about the problem: its history, symptoms and what has already been checked. Based on that, I estimate the scope and the time of the diagnosis.
02
Crawling and diagnostics (Screaming Frog, GSC, logs)
I crawl the website (staging, production or both), analyze the indexing report in Google Search Console and, if available, the Apache/nginx server logs. On JavaScript-based websites I check the rendering. Time: 1–5 business days, depending on the scale.
03
Report with priorities
You get a report with a list of technical problems, scored for difficulty and estimated impact (1–5 scale). It is a priority map, not an alphabetical list of errors: you know which fixes bring the biggest gains at the lowest cost.
04
Technical specification for the developer
I prepare an implementation document for your developer or IT department, with specific instructions, code examples (robots.txt, schema.org, hreflang, redirects) and acceptance criteria. Optionally: a 60-minute session with the developer.
05
Verification after implementation (optional)
After implementation I check whether the changes actually solve the problem: a new crawl, a rendering test and GSC analysis. Without this check, “implemented” often means “fixed only on paper”.
Pricing
How is technical SEO priced?
I bill by the hour or per project, depending on the scope and your preference. I quote projects after the intro call, once I know the size of the website and the complexity of the problem. The table shows the variants and how long each usually takes.
Option
Typical time
Technical diagnostics: small website
up to 500 URLs, 1 specific problem
3–5 business days
Full technical audit
500–5,000 URLs, report + specification
7–10 business days
Technical audit: large e-commerce / JS
over 5,000 URLs or a JavaScript-based website (React, Vue, Next.js)
2–3 weeks
Implementation oversight, ongoing technical support
billed by the hour, change reviews and answers for developers
ongoing
For regular clients I can also price the whole project instead of billing hours. The hourly rate is the same as for consulting and audits, with no hidden fees for tools.
Next step
Free intro call
An online call. You describe the problem, I assess the scale and give you a quote. No obligation.
FAQ
Common questions about technical SEO
What is technical SEO?
Technical SEO is the part of website optimization that Googlebot sees, not the user. It covers crawling and indexing, performance (Core Web Vitals: LCP, INP, CLS), URL structure, structured data (schema.org) and technical configuration (robots.txt, sitemap.xml, hreflang). Without sound technical SEO, content and links will not bring high positions, because Googlebot will not reach the right pages or will treat them as duplicates.
How is technical SEO different from an SEO audit?
An SEO audit is a one-time diagnosis of the website: it covers the technical side, content and the link profile, and ends with a report with recommendations. Technical SEO as a service is deeper work in one layer: diagnosis, technical specification and implementation oversight. The audit is broader, technical SEO goes deeper. Most companies start with an audit to see the scale of the problem, and then order specific technical work.
When do I really need technical SEO?
In four situations: you have a large store with duplicates or crawl budget problems; the website runs on JavaScript (React, Vue, Angular) and rankings are not growing despite good content; a domain migration or redesign is planned or has just happened; visibility has suddenly dropped for an unknown reason. On small WordPress websites, most technical problems can be fixed within a standard SEO audit.
How long does a technical diagnosis take?
It depends on the size of the website and the complexity of the problem. A small website (up to 500 URLs, one specific problem): 3–5 business days. A medium website (500–5,000 URLs): 7–10 business days. A large store or a JavaScript-based website (over 5,000 URLs, rendering, server logs): 2–3 weeks. I always give the time after the intro call, once I know the specifics of the project.
Is technical SEO enough to improve rankings?
No, but nothing else will work without it. Technical SEO is the groundwork: if Googlebot cannot index a page, even the best content and links will not help. On the other hand, technical optimization alone, without the right content and domain authority, is not enough for high positions in competitive industries. The technical side removes the blockers, content and links build visibility.
How much does technical SEO cost?
I bill by the hour or per project, and the price depends on the size of the website and the problem. Technical diagnostics of a small website (up to 500 URLs), a full technical audit (500–5,000 URLs) with a report and a specification, and large stores or JavaScript-based websites (over 5,000 URLs, rendering) are usually priced per project. Implementation oversight and ongoing technical support are billed by the hour. I give a detailed quote after the intro call.
What next
What else can help you?
Without a sound technical base, content and links will not improve your rankings. Below are the services that complement technical SEO or are the next step after it.
- Do you want a full diagnosis of the website before making technical changes? An SEO audit covers the technical layer, content and the link profile. SEO audit
- Once the technical side works, ongoing SEO builds visibility on top of it, month after month. Ongoing SEO
- Do you have a developer and prefer oversight to a full project? Change reviews and a technical session fit into SEO consulting. SEO consulting
- Structured data and a sound technical setup also affect visibility in AI search. AI search optimization
- Do you want your developers to understand technical SEO and avoid costly mistakes during implementation? SEO training
Let’s start with a free intro call.
You describe the problem, I assess the scale and give you a quote. No obligation.