Technical SEO consulting
Stability before scale — authority can’t compound on an unstable foundation.
One consultant for the layer that decides whether anything else you do can work: indexing, rendering, speed, and structured data. For search engines and, increasingly, for AI systems that have to resolve who you are.
This is one step of a larger process. It has its own page because it’s its own discipline.
Problem
Everything is fine, except the results
Your content isn’t the problem. The machine reading it is. You publish. It looks right in the browser. Analytics shows people arriving. And still, the pages that should rank don’t, or they rank and nobody clicks, or a machine describes your business and gets it wrong.
Technical problems don’t announce themselves. There’s no error message for “Google renders this page without the content”, and none for “your structured data is invalid, so the AI ignored it”. The site looks fine to you because you’re not the one reading it.
Symptom 01
The site feels slow, and nobody can fix it
The team says it’s slow. The developers have optimized it three times. The score went up; the feeling didn’t. Usually because the score measures a lab and the feeling comes from the field — a phone on a train, not a laptop on the office Wi-Fi.
Symptom 02
People leave before the page has said anything
The content is fine — you’ve checked. But the page takes four seconds to become usable on a phone, or it jumps while they’re reading, and they’re gone before the first paragraph. Analytics calls it a bounce. It’s a rendering problem wearing a content problem’s clothes.
Symptom 03
Google has seen the page and still won’t show it
Search Console says “Crawled – currently not indexed.” Nothing is broken: the crawler visited, the server answered, the page rendered. Google just declined to keep it. On ecommerce sites the cause is often the thousands of filter and parameter URLs competing with the page that matters — and the fix is rarely the one the first forum reply suggests.
Symptom 04
The redesign launched. The traffic didn’t come with it.
New site, new URLs, cleaner design — and rankings that fell within a month. Usually something the launch checklist never had: redirects that were never mapped, a staging robots.txt that shipped to production, or pages that quietly didn’t make the cut. The design did nothing wrong. The migration did.
What this is
What technical SEO actually covers
Five questions, in order. The first no stops everything behind it.
Can it be reached
crawlability
Whether search engines — and now AI crawlers — can reach your pages at all.
The work here: robots rules and sitemaps · internal links · redirect chains cleaned up, so authority stops leaking through them.
And a newer one: the same file that lets Googlebot in also decides whether GPTBot, ClaudeBot and PerplexityBot get in. Plenty of sites block them by accident — sometimes in robots.txt, sometimes at the CDN — and then wonder why AI systems never mention them. Same layer, two scorecards. AI visibility (GEO)
Crawling becomes a real constraint past roughly ten thousand URLs that change often, or when filters and parameters multiply them. Below that, it usually isn’t the problem — and I’ll tell you if it isn’t.
Can it be stored
indexability
Whether the pages that matter are the ones actually stored.
The work here: URL structure · canonicals, so it’s clear which version of a page counts as the real one · duplicate and filtered URLs kept out of the way.
This runs first in every diagnosis: a page that isn’t there can’t be improved.
Can it be read
rendering
What the crawler receives isn’t always what you see. JavaScript-built content, blocked resources and slow server responses all produce the same result: a page that exists but arrives empty.
The work here: what renders without JavaScript and what doesn’t · blocked scripts and stylesheets · mobile rendering integrity — the page as the machine receives it, on the device most of your buyers actually hold.
Can it be read fast
performance
Not a technical detail. On one ecommerce site the correlation between load time and completed purchases was −0.81 — strong enough to treat speed as a revenue line.
The work here: Core Web Vitals — how fast the page actually feels on a phone: how long until it’s usable (INP), how long until the main content appears (LCP), how much it jumps while loading (CLS) · server response time · what the hosting can and can’t do.
Can it be understood
structured data
The layer that used to be optional. It isn’t anymore: generative systems resolve who you are from it, and they do it silently — invalid markup is discarded without a warning anywhere.
The work here: schema validity — the machine-readable summary of what a page is about · entity consistency across the site · every declared relationship matched by a real link.
How it works
How the work runs
01
Crawl and index
What’s indexed, what isn’t, what’s competing with itself. The inventory before the opinions.
Tools: Screaming Frog · Google Search Console · Bing Webmaster Tools
02
Rendering
What the crawler actually receives, compared against what a visitor sees. The gap between the two is where content silently disappears.
Tools: Screaming Frog · Rich Results Test
03
Speed
Field data first, then lab data. Field tells you what your buyers experience; lab tells you why. The fixes get priced by effect, not by score.
Tools: PageSpeed Insights · WebPageTest
04
Structured data and entity integrity
Every JSON-LD block parsed, every entity resolved, every declared relationship backed by a link on the page. This is the GEO half of the work.
Tools: Rich Results Test · Schema Markup Validator
05
Verification
Re-run the same measurements against the baseline. Same method, same queries, so the numbers are comparable.
Tools: Search Console · GA4 · the frozen measurement set
Pricing model
What it costs.
I charge €50 per hour. Every figure below is hours × €50, so you can see what each budget buys.
Hourly consulting€50 / hour
Two example projects
B2B website
Around 500 pages
Audit and fixes
- 01
Technical audit
Indexing, rendering, speed and structure, ranked by effect.
€800
16 h · one-off
- 02
Fixes, template by template
One fix on a template reaches every page built on it.
€1,000
20 h · one-off
- Site-wide: indexing, redirects, speed8 h
- Homepage3 h
- Service page template5 h
- Blog and article template4 h
- 03
Monitoring
Indexing, errors and speed checked after releases.
€200
4 h / month
or
Standalone audit
Audit & handover
Fix list and tickets your developers can work from
€1,200
24 h · one-off
Webshop
Around 5,000 products
Audit and fixes
- 01
Technical audit
Crawling, indexing, filters, templates and speed.
€1,200
24 h · one-off
- 02
Fixes, template by template
One fix on a template reaches every page built on it.
€1,800
36 h · one-off
- Site-wide: indexing, crawl, speed10 h
- Homepage3 h
- Category template8 h
- Product template8 h
- Filters and faceted navigation7 h
- 03
Monitoring
Indexing, errors and speed checked after releases.
€300
6 h / month
or
Standalone audit
Audit & handover
Fix list and tickets your developers can work from
€1,800
36 h · one-off
These are indicative budgets, not fixed prices. The platform, the number of templates, how the site is built and what the audit finds all change the final quote.
No VAT is added to these figures — I’m VAT-exempt under Hungarian law.
Why is the audit lower when I also do the fixes?
An audit on its own has to work without me. Every issue is written up as a ticket with acceptance criteria, so your developers can fix it without having to ask.
When I do the fixes myself, the audit only has to point me to them. The detailed write-up happens in the work itself, which is why the audit costs less upfront.
What the audit covers
The audit crawls the whole site and checks what search engines can reach and index, how pages render, how fast they load, and how the site is structured: redirects, canonical tags, internal links and structured data. I also use the data you already have in Search Console, Bing Webmaster Tools and Google Analytics.
Every finding is ranked by its effect on search and tied to the template it comes from. You get a fix list, not a list of warnings exported from a tool.
B2B website: template by template
A website with around 500 pages is usually built on a handful of templates: the homepage, service pages, blog articles and a few landing pages. Most technical problems sit in these templates or in site-wide settings, so fixing a template fixes every page built on it.
On WordPress, I make the fixes myself. On other platforms, I write the tickets and work with your developers while they ship them.
After the fixes, monitoring checks indexing, errors and speed after each release, so a new problem is caught before it spreads.
Webshop: templates, categories and filters
A webshop with around 5,000 products has few templates but many pages: the homepage, category pages, product pages, and the pages generated by filters. Filters are where the index usually grows out of control, so they get their own line.
The crawl covers the whole shop. The manual review focuses on each template and its important exceptions, such as discontinued or out-of-stock products.
Monitoring follows new products, categories and platform updates, the usual source of new technical problems.
What the monthly budget covers
Research, strategy, implementation or coordination with your developers, monitoring, meetings and reporting. Reporting time counts in the hours.
You get access to the project management tool, where you can see the priorities, who is responsible, progress and what comes next. Each month starts with agreed priorities and ends with a review of what changed and what the data shows.
Priced separately
Content writing and production, including an external writer if needed.
Outreach and digital PR. The audit includes the backlink analysis and recommendations.
Setting up or repairing measurement. The audit analyzes your existing data; new tracking and integrations are scoped separately.
Development beyond the agreed hours, including external developer fees.
AI search research or monitoring beyond the agreed topics, languages and AI systems.
Before you start
You receive a proposal with the scope, the estimated hours, the audit fee and the monthly budget. It also states whether the first phase includes implementation, when the ongoing work begins, and what your team needs to provide.
There is no lock-in. Any change to the scope or budget is agreed before the extra work starts.
Related areas
Technical work is the floor the other layers stand on.
Technical SEO is one layer of a system that only compounds when the others hold.
Search / SEO consulting
The parent process: research, strategy, content, links. Technical work is one step of it.
Explore SEO consultingAI visibility (GEO)
The other parent. Same technical layer, scored differently: parseable instead of rankable.
Explore GEOUX & Conversion
Speed is where technical work and conversion meet. The fix serves both.
Explore UX & conversionMeasurement
The verification step runs on this: Search Console, GA4, and a frozen query set. If the numbers can’t be trusted, neither can the before-and-after.
Explore measurementExecution
Five questions, answered in order, priced per fix. This is where the fixes get shipped — or handed to your developer with the method written down.
Explore executionQuestions
Questions people ask about technical work
Isn’t this something my developer should handle?
Often yes — and if you have one, I’ll work with them. The difference is that a developer fixes what you report; this finds what nobody reported. Most of what I surface has never generated a single error message.
My site is on WordPress. Does that change anything?
It changes what breaks. Plugin conflicts, theme-generated markup and caching layers produce a specific set of technical problems, and I’ve spent years inside them — I implement the fixes myself rather than filing them.
We’re replatforming. Is that this?
Partly, and it’s the highest-stakes version of it. A migration touches every one of the four questions at once — URLs, redirects, rendering, structured data — and it’s where the most organic revenue gets lost on a single bad decision.
It isn’t a core area of technical SEO; it’s technical SEO under time pressure, with one chance to get it right. If that’s what you’re facing, say so early: the work is planned differently.
Does technical SEO help with AI search too?
It’s the part that transfers most directly. Ranking needs crawlable, fast pages; AI systems need the same pages to be parseable and internally consistent. The technical layer is one job with two scorecards.
How do I know if I have a technical problem at all?
Sometimes you don’t, and the audit says so. The signals worth taking seriously: pages that never get impressions, content that appears in the browser but not in the page source, and a site that feels slow on a phone on mobile data.
Next step
Not sure whether it’s technical?
Send me your most important page. I’ll tell you what a crawler sees, how fast it arrives, and whether a machine can resolve who you are — before you commit to anything.