TECHNICAL SEO

Technical SEO Consultant Who Diagnoses Before Prescribing

I'm a technical SEO consultant and former Head of SEO who finds what is actually stopping a site from being crawled, indexed and ranked, then writes fixes developers can ship and validates them afterwards. The work covers crawling, rendering, migrations, structured data and AI crawler access. For one publisher, auditing 5,800+ URLs and fixing the issues found led to a Google penalty being lifted.

At a glance

  • For: sites with indexing or ranking problems, JavaScript-heavy sites, upcoming migrations and teams who need an audit their developers can act on.
  • Covers: crawl and indexation, rendering and JavaScript, site architecture, Core Web Vitals, structured data, migrations and AI crawler access.
  • Output: prioritised findings with evidence, developer-ready tickets with acceptance criteria, and validation after release.
  • Free tools: my CSR vs SSR checker, AI crawler checker and HTTP status checker are a start, not an audit.
  • How you can work with me: hourly consultation for a specific problem, a full technical audit, or ongoing technical oversight.

OUTCOMES

What this engagement is measured on

Every client's goals are different, and most are a mix. In the first weeks we agree which of these matter to you, record a baseline, and report against it every month. Targets are set after the audit, never promised up front.

Traffic and engagement

Grow non-branded organic clicks to the pages that matter commercially.

What we measure
Non-branded organic clicks, organic sessions and users, engaged sessions and click-through rate.
What usually moves first
Impressions, rankings and click-through rate on pages that are fixed or rewritten.
What follows
Sustained growth in organic clicks and engaged sessions.

Leads, sales and revenue

Turn that traffic into enquiries, sales or sign-ups you can see in GA4 or your CRM.

What we measure
Organic enquiries and leads, conversion rate of key pages, and organic revenue and its share of the total.
What usually moves first
Conversion tracking you can trust, and better conversion paths on the pages that already get traffic.
What follows
Growth in organic leads, sales and revenue share.

Authority: backlinks and topic authority

Build the links and topic depth needed to compete for harder terms.

What we measure
Relevant referring domains, link quality, Domain Authority/Rating trend and how much of each topic your site covers and ranks for.
What usually moves first
New links from relevant sites and more of your topic pages indexed and ranking.
What follows
Rankings on the competitive head terms that need authority to move.

Value delivered vs investment

Show what the organic results are worth against paid clicks and paid leads.

What we measure
What the organic results would cost to buy as paid clicks or paid leads (CPC and CPL based value), and hours saved where work is automated.
What usually moves first
An agreed baseline and the tracking needed to put a value on results.
What follows
A value-to-investment ratio you can track month by month.

See a worked example of the value calculation →

Who this is for

A tool that crawls your site will give you a score and a list of 300 warnings. Most of them don't matter, a few matter enormously, and the tool can't tell you which, because it doesn't know your business, your traffic or your templates. That's the gap a technical SEO consultant fills: diagnosis before prescription.

My approach follows one sequence: symptom, diagnosis, root cause, fix, validation. A traffic drop is a symptom. "Google can't render the product listings because they load after a client-side API call" is a root cause. The fix is specified for your developers, and afterwards I check in Search Console and the logs that it worked.

Proof of where this leads: for a multinational IT firm, Google for Jobs structured data and technical fixes took job-page clicks from 68 to 112K year on year; for a stockbroking firm, a carefully managed redesign recovered 93% of organic traffic within two weeks.

  • Sites whose pages are 'Discovered' or 'Crawled' but not indexed in Search Console
  • React, Next.js, Angular or other JavaScript-heavy sites where content may not reach crawlers
  • Teams planning a migration, replatform or redesign in the next six months
  • Businesses with an unexplained traffic drop and no clear diagnosis
  • Developers and SEO leads who need a senior technical second opinion

DIAGNOSIS

Problems I solve

Common constraints teams face before we begin working together.

Hurdle 01

"Our pages aren't getting indexed"

Pages sit in 'Discovered' or 'Crawled, currently not indexed' for weeks, and requesting indexing doesn't help.
Hurdle 02

"The audit gave us 300 issues"

A tool export with no priority, so developers either ignore it or fix the easy, unimportant items.
Hurdle 03

"Traffic dropped after a release"

Something changed in templates, rendering or redirects, and nobody can say what or where.
Hurdle 04

"Is our JavaScript hurting SEO?"

Content, links or metadata load in the browser, and you're not sure what Google or AI crawlers actually see.

How a technical SEO consultant prioritises: impact, reach, confidence, effort

Every finding gets four scores from 1 to 5, and the priority is Impact × Reach × Confidence ÷ Effort:

  • Impact: how much fixing it could change rankings, crawling or conversions on the affected pages.
  • Reach: how many pages or how much traffic it affects (5 = sitewide or money pages).
  • Confidence: how sure the diagnosis is (5 = confirmed in Search Console or logs).
  • Effort: how hard it is to fix (5 = hardest, a major engineering project).
Example issueImpactReachConfidenceEffortScoreBand
Canonical on product template points to page 1 of category554250Fix now
Internal links to redirected URLs in main navigation355325Plan
Missing structured data on blog posts235310Monitor
Minor Core Web Vitals issue on low-traffic template22343Defer

These rows are illustrations, not findings from a real audit. The scoring doesn't replace judgement; it makes the reasoning visible so everyone can challenge it.

From symptom to validated fix: an indexing example

A typical investigation, written the way I'd document it for a client:

  1. Symptom: new product pages stay "Discovered, currently not indexed" for weeks.
  2. Checks: URL Inspection on a sample; crawl comparing raw and rendered HTML; server logs for Googlebot requests; internal links to the new pages.
  3. Diagnosis: the pages are only linked from a client-side "load more" listing, so crawlers find them through the sitemap alone and treat them as low priority.
  4. Fix: server-rendered pagination links on category pages, plus links from related products.
  5. Acceptance criteria: new products linked in raw HTML from at least one crawlable page within one click of the category.
  6. Validation: Googlebot requests the new URLs in the logs, and the Pages report shows them moving to indexed.

The CSR vs SSR checker shows step 2 for a single URL in seconds. An audit does it across every template and connects it to traffic.

A free tool score isn't a technical SEO audit

Free crawlers and score-based tools are useful for spotting symptoms, and I built several free tools myself. But a score can't tell you:

A tool showsAn audit adds
300 warningsWhich 10 matter for your traffic and revenue
"Missing meta descriptions"Whether it affects any page that earns clicks
A rendering warningWhat Googlebot and AI crawlers actually receive
A list of redirectsWhich chains sit on pages with links and traffic
A score out of 100Root causes, fixes, owners and how to validate them

If someone shows you a free tool's score as an audit, ask what they would fix first and why. My SEO audit checklist explains the full method.

Technical SEO for AI crawlers, and what clients ask

AI search adds two technical checks. First, access: many sites block OAI-SearchBot, ClaudeBot or PerplexityBot by accident through a CDN or firewall rule, not robots.txt. Second, rendering: most AI crawlers don't run JavaScript, so content that only appears after scripts run is invisible to them. My guide to checking AI crawler access covers both.

"How long does a technical audit take?" Usually two to four weeks, depending on site size and access to logs.

"Will you implement the fixes?" I write the specifications and review them in staging. My team can implement where your developers lack capacity.

"Can you guarantee our traffic comes back?" No. I can find the cause, fix it properly and show whether the fix worked.

DELIVERABLES

What you get

Tangible assets, strategic roadmaps and documentation provided during the engagement.

✓

Technical SEO audit

Crawl, index coverage, rendering, architecture, internal links, Core Web Vitals and structured data, with evidence for every finding.
✓

Prioritised fix list

Each issue scored on impact, reach, confidence and effort, grouped into fix now, plan, monitor and defer.
✓

Developer-ready tickets

Problem, evidence, affected URLs or templates, the fix, acceptance criteria and how it will be validated.
✓

Rendering and JavaScript review

What's in the raw HTML versus the rendered page, for Googlebot and for AI crawlers that don't run JavaScript.
✓

Migration plan and QA

Redirect mapping, staging checks, launch-day verification and post-launch monitoring.
✓

AI crawler access check

robots.txt, CDN and firewall rules for OAI-SearchBot, ClaudeBot, PerplexityBot and others, verified in server logs.

WORKFLOW

How an engagement works

A clear, four-phase delivery model ensuring accountability from kickoff to ongoing impact.

  1. 01Phase 1

    Diagnose

    Search Console, crawl and log data reviewed against the symptoms: what changed, where and when.
  2. 02Phase 2

    Prioritise

    Findings scored and grouped so the few issues that matter are fixed first.
  3. 03Phase 3

    Specify

    Tickets with acceptance criteria, reviewed with developers and tested in staging.
  4. 04Phase 4

    Validate

    Post-release checks in Search Console, crawls and logs to confirm the fix solved the original problem.

Ways to work together

Every engagement is led by me personally. For execution, I work with a small team of specialists — technical SEO, content, development and automation — so you get senior thinking without agency layers, account managers or hand-offs.

Audit & roadmap

A fixed-scope diagnosis with a prioritised roadmap your team can act on. Typically 2–4 weeks.

Advisory retainer

Ongoing senior guidance: monthly strategy, reviews of your team's work, and a direct line to me when decisions come up.

Strategy + execution

I own the strategy and stay your single point of contact; my specialist team handles implementation — technical fixes, content, builds and reporting.

Proof from past work

~70% → 98%

Quality improvement

Built quality frameworks and delivery processes that improved execution across international campaigns.

International operations

1400+ HOURS SAVED

Reporting automation

Automated repetitive reporting workflows, saving 1400+ hours of manual effort and reducing operational dependency by the equivalent of 10 team resources.

International operations

TOOLING

Tools I use

Industry-standard platforms and custom automation stacks used to audit, track, and execute.

Screaming Frog
Screaming Frog
Google Search Console
GA4
SEMrush
Ahrefs
Ahrefs
Python
Looker Studio

FAQ

Technical SEO consultant: questions clients ask

Straight answers to what people usually want to know before a first call.

A technical SEO consultant makes sure search engines and AI crawlers can crawl, render and index a website, and that its structure sends the right signals. The work covers crawl and index problems, JavaScript rendering, site architecture, page speed, structured data and migrations, ending with prioritised fixes developers can ship and checks that they worked.

Start from the symptom and the date it began, then compare Search Console data, a crawl of raw and rendered HTML, and server logs. Look for what changed at that time: releases, templates, redirects or robots rules. The aim is a root cause supported by evidence, not a list of every warning a tool can find.

Crawlability and indexation, rendering and JavaScript, site architecture and internal links, redirects and status codes, canonicals and duplicates, Core Web Vitals on key templates, structured data, international tags if relevant, and AI crawler access. A good audit prioritises findings and explains how to fix and validate each one.

Run a full audit once or twice a year, before and after any migration or redesign, and whenever traffic drops without an obvious cause. Between audits, automated monitoring of key templates and Search Console alerts catch most problems sooner.

Not automatically. Google can render JavaScript, but rendering adds delay and risk, and most AI crawlers don't run it at all. Content, links and metadata that matter should be in the server-rendered HTML. A quick way to check one page is to compare the page source with what you see in the browser.

Usually both. The consultant diagnoses the problem, decides what to fix first and writes the specification; the developer builds it. A developer alone may fix what a tool reports without knowing which issues affect rankings. A consultant alone can't ship code.

Have a growth problem worth solving?

Tell me where you're stuck. On a 30-minute intro call I'll tell you where I think the constraint is and what I'd look at first — whether or not we end up working together.