Skip to content
Naveed Ganatra

Technical SEO

Remove the crawl, render and speed problems that stop good content from ever ranking.

for the audit and prioritised roadmap
2–3 wksfor the audit and prioritised roadmap
of Search Console data reviewed
16 mthsof Search Console data reviewed
percentile — the Core Web Vitals threshold that counts
75thpercentile — the Core Web Vitals threshold that counts
to clear the high-impact items on most sites
6–8 wksto clear the high-impact items on most sites

The problem

What this solves

You can publish excellent content and still lose, because Googlebot cannot crawl it efficiently, cannot render it, or abandons pages that take four seconds to become interactive. Technical debt is invisible in your CMS and brutally visible in Search Console — soft 404s, discovered-not-indexed, duplicate canonicals, and a crawl budget being spent on faceted URLs nobody will ever search for.

You are probably here because

  • Search Console shows pages discovered but not indexed
  • Your Lighthouse score is high and Core Web Vitals still fail
  • New pages take weeks to appear in the index
  • Crawl stats show Googlebot spending its time on parameter URLs
  • Content visible in the browser is missing from the rendered HTML

What's included

Everything this service covers

Scope is fixed and written down before we start, so there is no argument later about what was and was not included.

Crawl and log-file analysis

A full crawl of the site, plus server log review where logs are available, to see what Googlebot actually requests rather than what you assume it requests.

Indexation audit

Every Search Console coverage state traced to a root cause — soft 404s, duplicate canonicals, discovered-not-indexed, crawled-not-indexed — rather than reported as a count.

JavaScript rendering audit

The raw HTML response compared against the rendered DOM, to find content Googlebot never sees. Fixed with server rendering, prerendering or hydration changes depending on your stack.

Core Web Vitals remediation

Prioritised, developer-ready tickets against field data from the Chrome User Experience Report, not lab scores. LCP, INP and CLS handled separately because their causes rarely overlap.

Site architecture and link depth

How many clicks from the homepage your commercial pages sit at, and what that is costing them. Depth is one of the cheapest things to fix and one of the most commonly ignored.

Structured data across templates

Schema implemented and validated at template level, so one change corrects thousands of URLs and it survives updates.

Crawl directive rebuild

robots.txt, canonical strategy and XML sitemaps rebuilt deliberately for your site rather than inherited from a plugin default.

Post-deploy verification

A re-crawl and Search Console watch after each release, to confirm the fix landed and introduced no regression.

Process

How the engagement runs

  1. 01

    Baseline

    Crawl the site, pull 16 months of Search Console data, and record current Core Web Vitals from field data — not just lab scores.

  2. 02

    Diagnose

    Every issue is traced to a cause and scored by traffic impact against implementation effort. You get a ranked list, not a 200-page PDF nobody reads.

  3. 03

    Ship

    I write tickets your developers can action directly — file, change, expected result. Where I have access, I implement the changes myself.

  4. 04

    Verify

    Post-deploy re-crawl and Search Console monitoring to confirm each fix actually landed and no regression was introduced.

Outcomes

What success looks like

  • More of your site indexed, and indexed faster after publication
  • Core Web Vitals passing on field data, not just in Lighthouse
  • Crawl budget spent on pages that earn revenue

Honest fit

Is this the right service for you?

I would rather tell you no now than take a retainer for work that was never going to help.

This is a good fit if

  • Search Console is reporting indexation or coverage problems
  • You have a large site where template fixes scale
  • You have development capacity to action tickets
  • You suspect something structural is capping an otherwise good site

This is the wrong service if

  • Your site is small and technically simple already
  • You have no development access and no budget for one
  • Your real problem is that the content is thin — that is a different fix
  • You expect technical work alone to produce rankings

Definitions

The terms on this page, explained

Plain definitions of the concepts this service works with — so you can evaluate the work rather than take the vocabulary on trust.

Crawl budget
How much crawling Google is willing to do on your site. Wasted on faceted and parameter URLs, it stops reaching the pages that earn revenue.
Field data
Real-user performance measurements from the Chrome User Experience Report, at the 75th percentile over a rolling 28 days. This is what Google uses for the ranking signal — not Lighthouse.
Lab data
A single simulated page load, as produced by Lighthouse. A debugging tool, not a ranking input, and routinely mistaken for one.
INP
Interaction to Next Paint. Measures how quickly the page responds to real clicks, taps and key presses. Harder to pass than the metric it replaced, because it measures the whole interaction.
Rendering
The step where Google executes JavaScript to see the final page. Content that only exists after execution can be missed entirely, which is invisible in your CMS and obvious in the index.

Proof

Technical SEO in practice

Pharmaceutical Export

A Karachi Pharma Exporter, Cited Beside Three Manufacturing Giants

In Google AI Overview
CitedIn Google AI Overview
Organic position
TopOrganic position
Sources named
1 of 4Sources named

A non-manufacturing exporter competing against manufacturers for US-facing export queries — now cited in the AI Overview and ranking organically for its head term.

Read the case study

FAQ

Frequently asked questions

My site is fast in Lighthouse but Search Console says it fails. Why?

Lighthouse is a lab test on a simulated device. Search Console reports the Chrome User Experience Report — real visitors, real devices, real networks. Field data is what Google uses for the ranking signal, so that is what I optimise against.

Do you work directly in the codebase?

Yes, where you want me to and access allows. I work comfortably in WordPress, Shopify, Webflow, Drupal and modern JavaScript stacks. If you prefer, I hand your developers precise tickets and review the pull requests instead.

What if my pages are rendered with JavaScript?

That is a specific audit within this service. I compare the raw HTML response to the rendered DOM to find content Googlebot never sees, then recommend server-side rendering, static prerendering or hydration changes based on your stack.

How long does a technical SEO engagement take?

The audit and prioritised roadmap take two to three weeks. Implementation depends on your development capacity — most sites clear the high-impact items within six to eight weeks.

Free audit

Want Technical SEO done properly?

Send me your domain and I'll reply with the three issues costing you the most organic traffic right now — and whether this service is the right one for them.

  • The three issues costing you the most organic traffic
  • Whether those are quick fixes or structural problems
  • An honest view on whether SEO is worth it for you

You work with me directly — no account managers, no offshore handoff, no junior taking over after the sales call.

Or watch the free SEO training first

Request your free audit

Two business days, written by me, no call required.

Include the country code — it is the fastest way for me to reach you.

Your details come to me and nobody else. No newsletter, no automated sequence, no reselling.

WhatsApp me