Technical SEO
I audit your site at code level and hand developers briefs they can ship. Most often for e-shops and JavaScript apps. At Flashscore I handle technical SEO across 25+ markets.
How to spot a technical problem
A technical problem usually shows up as pages that won't index, a slow site, a growing error list in Google Search Console or an organic drop after a redesign.
Pages don't get indexed or drop out of the index
New content never shows up in Google, or important pages fall out of the index. The cause can be crawling, canonicalization, content quality or indexing directives.
The site loads slowly
Weak Core Web Vitals, heavy scripts and unoptimized images hurt the user experience. On large sites they can get in the way of efficient crawling too.
Errors keep piling up in Search Console
The indexing report shows 5xx errors, soft 404s, redirects or blocked resources. Each one can be a page Google doesn't process correctly.
Traffic dropped after a redesign or migration
Without correct redirects and an indexing check, a site can lose part of its rankings. Some of them don't come back on their own.
Google can't see the content on JavaScript pages
Key text or links only appear in the browser and are missing from the index. It's a typical JavaScript-site problem and hard to catch without checking the rendering.
The audit shows which of these actually hold the site back and which are cosmetic.
SEO oversight for a Next.js migration
Clients often come to me with a Next.js migration on the calendar. Losses come from nobody writing acceptance criteria before development starts. The sample below is a template for that brief.
Sample acceptance criteria for a Next.js migration
- Initial state
- A migration can introduce errors in URL mapping, canonicals or structured data. The impact on search results may only show up on the next crawl and indexing pass.
- Evidence
- The mipaco.cz migration (WordPress → static site → Next.js, January 2026).
- Decision
- Acceptance criteria belong in the brief before development starts, not in a check after deployment.
- Developer ticket
- An approved map of old and new URLs: every old URL has a matching new URL and a direct permanent redirect (301 or 308). URLs without a relevant replacement return 404 or 410.
- Canonicals and the sitemap use the corresponding new URLs, hreflang points to the correct language versions, meta robots matches the intended indexation and the URLs in JSON-LD are updated.
- Pages render key content in the HTML response without JavaScript.
- Acceptance criteria
- 100% of the old sitemap URLs tested against the approved map: redirect targets return 200, removed URLs return 404 or 410.
- Sample of 20 pages: title, H1 and main text match the original page, and the canonical matches the new URL from the approved map.
- GSC: after 14 and 28 days, compare the reasons for non-indexing against the baseline.
- Deployment check
- Crawl staging before launch, crawl production after launch and compare; GSC check 14 and 28 days after migration.
Why do technical SEO with me
I do technical SEO every day on a site spanning 25+ markets, and I build in Next.js myself, so I understand both the code and how search engines read it. My recommendations come from running production sites and implementing the fixes myself.
Livesport and Flashscore
In the Betting Content Section, the part of the site with betting content, I handle content and technical SEO across 25+ markets. I test crawling, indexing and rendering at a scale where every bug multiplies.
Hands-on Next.js development
Next.js is my main stack and this site runs on it. I fix rendering, metadata, sitemaps and performance in the code myself.
My own Python tooling
For repetitive technical jobs like mapping redirects in a migration, I use my own Python scripts. Automation speeds up the processing and leaves more time for checking the risks.
If the technical findings need to fit into wider business and content priorities, the next step is SEO consulting.
Testimonials
5.0 / Google ★★★★★ See the reviews on Google
★★★★★
"Thoroughness, quick responses and a passion for the work. Those are the qualities you want. I've really enjoyed working with Mira, and I still do. Recommended."
Patrik Pilous
Freelance consultant
01 / 04
What a technical SEO audit includes and what it costs
The single-area diagnostic costs from €1,200 per project. I check crawling, indexing, architecture, performance, structured data and rendering, and write a dev brief with acceptance criteria and a post-deployment validation. The final quote depends on site size, the number of templates and technical complexity. I confirm the price once I've seen the site.
Crawling and indexing
Robots.txt, sitemaps, canonical URLs, status codes, indexing directives and crawl budget.
Architecture and linking
URL structure, click depth, internal links and how authority flows through the site.
Performance and Core Web Vitals
LCP, INP and CLS, resource loading and layout stability on mobile and desktop.
Structured data and rendering
Schema.org markup and a check that Google sees the content of JavaScript pages.
Want to know what's holding the site back technically?
from €1,200 per projectI set the scope and deliverables with you. Start with the intro consultation (€240).
What technical SEO is
Technical SEO is work on a site's code, server and architecture so search engines can crawl, render and index it without trouble. It covers speed, indexing, URL structure, structured data and JavaScript rendering. It's the layer under the content, and the one people forget.
If Google can't crawl, render or index a page, great content won't do its job. So I fix critical technical blockers before tuning copy and links. Cosmetic findings don't get to jump ahead of content work with a bigger impact.
What technical SEO covers
In technical SEO I check crawling and indexing, site architecture, performance, structured data and JavaScript rendering. Any of them can quietly hold a site back while the content looks fine.
| Area | What it covers | Typical problem |
|---|---|---|
| Crawling and indexing | Robots.txt, the sitemap, canonical URLs, status codes and indexing directives. | Google indexes the junk and can't see the pages that matter. |
| Crawl budget and server logs | What Googlebot actually does on the site: which URLs it crawls, how often, and how much capacity goes to pages with no business value. | Parameter and duplicate URLs eat the crawling that should go to the pages that sell. |
| Architecture and internal linking | URL structure, click depth and how internal authority flows through the site. | Key pages sit deep in the structure with only weak internal links pointing at them. |
| Performance and Core Web Vitals | Load speed and layout stability (LCP, INP, CLS). | A slow site hurts the user experience, and speed is one of the ranking signals. |
| Structured data | Schema.org markup that describes the page content to search engines. | The site misses out on rich results and search engines understand the content less well. |
| JavaScript rendering | How Google renders content on sites built with Next.js, React or Vue. | Google doesn't see client-generated content, or indexes it late. |
Crawling and indexing
Robots.txt, the sitemap, canonical URLs, status codes and indexing directives.
Typical problem: Google indexes the junk and can't see the pages that matter.
Crawl budget and server logs
What Googlebot actually does on the site: which URLs it crawls, how often, and how much capacity goes to pages with no business value.
Typical problem: Parameter and duplicate URLs eat the crawling that should go to the pages that sell.
Architecture and internal linking
URL structure, click depth and how internal authority flows through the site.
Typical problem: Key pages sit deep in the structure with only weak internal links pointing at them.
Performance and Core Web Vitals
Load speed and layout stability (LCP, INP, CLS).
Typical problem: A slow site hurts the user experience, and speed is one of the ranking signals.
Structured data
Schema.org markup that describes the page content to search engines.
Typical problem: The site misses out on rich results and search engines understand the content less well.
JavaScript rendering
How Google renders content on sites built with Next.js, React or Vue.
Typical problem: Google doesn't see client-generated content, or indexes it late.
Technical SEO for modern JavaScript sites
JavaScript sites built with Next.js, React or Vue have one extra step compared with plain HTML: Google has to render the content first. That step is where SEO bugs tend to appear. When key text, links or metadata only get built in the browser, Google sees them after rendering at the earliest. With a broken implementation they can be missing from the final HTML altogether.
I build in Next.js and tune rendering, metadata generation and JavaScript indexing directly in the code. This site runs on Next.js.
FAQ
What is technical SEO?
Technical SEO is work on a site's code, server and architecture so search engines can crawl, render and index it without trouble. It covers speed, indexing, URL structure, structured data and JavaScript rendering: the foundation that content and links depend on.
How much does a technical SEO audit cost?
The single-area diagnostic for one narrowly defined area (indexing, a single template, rendering) costs from €1,200 per project. It includes a dev brief with acceptance criteria and a validation after deployment. If you're not sure where the problem sits, start with the intro consultation for €240.
How do I know I have a technical SEO problem?
Typical signals are indexing problems, slow loading, new errors in Google Search Console, an organic drop after a redesign, or content missing from the rendered HTML. An audit separates a real blocker from a cosmetic finding.
What's the difference between technical and content SEO?
Technical SEO makes sure the site is accessible and understandable to search engines. Content SEO deals with what's on the pages and which queries they answer. The two layers depend on each other: the tech makes the content reachable, and the content gives the page a reason to rank.
Do you do technical SEO for JavaScript sites (Next.js, React)?
Yes, that's my specialty. I build in Next.js myself and handle rendering, hydration and JavaScript indexing directly in the code. There's more on the JavaScript SEO page.
Do you fix the findings, or just report them?
I write the technical brief for developers: what to fix, why, and in what order by impact. Your team can do the implementation, or I oversee it. On Next.js projects I can make selected changes myself.
Tell me what you need to solve
Tell me what you are working on and what you want to achieve. I propose the next step and a scope of work. We agree on the price before starting.