Technical SEO

Technical SEO Consultant: Audits That End in Fixed Sites, Not Reports

Most technical audits end as a 90-page PDF nobody implements. Mine end when the issue is gone from the live site. I crawl your site the way Google's smartphone bot does, check what Search Console says Google actually indexed, test whether your content survives JavaScript rendering, and read your server logs to see where Google spends its visits. Every issue becomes a finding with evidence, a consequence, a one-line fix and a way to prove the fix worked.

If rankings stalled and nobody can say why, start with the audit lane that fits, or all eleven.

See what's included
Audit lanes
11, run in order
Every finding
Evidence · fix · proof
Fixes delivered
Twice: dev + you
The Rendered vs Raw Audit tool comparing raw HTML against the rendered page
My render-audit tool: compares what your server sends against what Google actually sees after JavaScript runs.
Sound Familiar?

Signs this is what's holding you back

01

Indexing gaps

Pages exist, but Google hasn't filed them

You publish pages and they never show up in search. Search Console lists hundreds as “Crawled – currently not indexed” and nobody can tell you why.

02

Crawl budget waste

Google spends its visits on pages that don't matter

Filter URLs, sort orders and old tag pages soak up Google's attention while your service and product pages wait weeks to be re-read.

03

Rendering failures

Content only appears after JavaScript runs

Your page looks fine in a browser, but the tabs, accordions and reviews are invisible in the initial HTML Google reads. To Google, half the page is missing.

04

Core Web Vitals

Google's measure of how fast and stable a page feels

Phones wait four seconds for your page to settle. Visitors leave before it loads, and Google notices they left.

What's Included

What Technical SEO covers

Each part below is a real piece of the work, with the trade term it goes by and what it means in plain English.

  1. 01

    Crawl audit

    Walking every URL the way Googlebot does

    I crawl as Google's smartphone bot, not a desktop browser. Crawling a mobile-indexed site as desktop hides real problems. Every issue is listed with its URLs and a specific fix, not a bucket count. The audit isn't closed until a second crawl confirms the issue is gone.

    You get
    • Broken links, redirect chains and loops, 4xx and 5xx errors
    • Duplicate and near-duplicate pages, soft 404s, thin pages
    • Titles, meta descriptions and H1s: missing, duplicated, out of order
    • URL hygiene: parameters, uppercase, spaces, repeated paths
    • Re-crawl after fixes to verify, not assume
  2. 02

    Search Console audit

    What Google's own index says about you

    The crawl shows what your site presents. Search Console shows what Google did with it. I check the two against each other: crawl requests, response times, which bot visits most, and every page that isn't returning a clean 200.

    Search Console page indexing report showing indexed and not-indexed pages over time
    Indexing tracked daily in Search Console, not checked once and forgotten.
    You get
    • Crawl request breakdown and crawl-expense by asset type
    • Server response time checked against a 150 ms target
    • 301s replaced with their final destination, 404s resolved
    • Structured-data errors by type: product, review, breadcrumb, FAQ
    • Robots and sitemap fetch frequency validated
  3. 03

    Rendering audit

    Proving Google sees what your visitors see

    I render every key template through Google's Rich Results Test on mobile and desktop, then tally those screenshots against a real phone and a real laptop. Text inside tabs, sliders and accordions has to be in the HTML, not only painted in by JavaScript.

    You get
    • Raw HTML vs rendered page, compared template by template
    • JavaScript errors and blocked scripts, fonts and assets
    • Content hidden behind dynamic elements surfaced
    • Mobile and desktop render checked against live devices
  4. 04

    Log-file analysis

    Reading Google's actual visit history from your server

    Your server records every Googlebot visit. I read those logs to see which pages Google visits, which it ignores and how much of its budget it burns on URLs that should never have existed.

    You get
    • Googlebot visits by page type and status code
    • Crawl waste on parameters, filters and duplicates
    • Money pages Google rarely re-visits, flagged
The Method Behind It

The IFESE finding format

Every issue arrives as a work item someone can act on

No “we found some issues” summary. Each finding is a self-contained record: what's wrong, the proof, what it costs you, the fix in one sentence, who does it and how, and how we'll know it worked. Every finding is scored for effort, impact and confidence, so the top of the list is the work that pays back soonest.

Issue
The category of problem
Finding
The exact URL or template affected
Evidence
A screenshot, log line or Search Console data point
Consequence
What it breaks in search or in sales
Solution + Execution
The fix, and the steps for your developer
Verification
The metric or re-test that proves it's fixed
An audit workbook with columns for task, what it means, measured evidence, consequence and solution
A real findings sheet: every row has measured evidence, a consequence and the exact fix.
Deliverables

What lands on your desk

  • Master audit

    A two-page executive summary plus the top 20 findings ranked by impact, confidence and effort.

  • Per-lane workbooks

    One workbook per audit lane, every row a finding in the IFESE format.

  • Developer fix folder

    Each fix packaged for your developer, generated from the same source as your report, so the two can never drift apart.

  • 30 / 60 / 90-day plan

    The fixes sequenced into phases your team can actually schedule.

  • Three-status tracker

    Every issue marked Audit, Solution and Implementation separately, so you always see what's diagnosed versus what's live.

  • Verification re-crawl

    A second crawl after implementation, proving each issue is closed.

How It Runs

The order the work happens in

  1. Lane 01

    Step 1: Foundation check

    Crawl setup, sitemap, robots rules and an indexing baseline: everything later lanes depend on.

  2. Lanes 02–04

    Step 2: Logs, rendering, staging

    How Google really crawls you, whether it can see your JavaScript content, and whether your test site is leaking into search.

  3. Lanes 05–10

    Step 3: Specialist lanes

    Links, e-commerce decline, page-worthiness, trust signals, AI citation tracking and accessibility, commissioned one at a time or all together.

  4. Close

    Step 4: Root causes, then fixes

    Findings that show up in two or more lanes are traced to their shared root cause, so you fix the disease rather than twenty symptoms.

Proof

What this looked like on a real site

Managed IT / MSP · Texas, US
average Google position
41 → 21
average Google position
keywords in the top 3
199
keywords in the top 3
findings traced to root causes
20 → 2
findings traced to root causes

The audit traced twenty separate findings back to two root causes, and the work went at those two instead of the symptoms. Over the engagement the site's average position moved from page 4–5 to page 2, and 199 of its 717 ranking keywords now sit in Google's top three.

The honest part: Raw impressions fell while position improved. Google now shows the site for fewer, better-matched searches. Figures are from Search Console and Ahrefs, September 2026.

Source: Search Console + Ahrefs, anonymised case GMore results
Case G chart: search impressions as bars and average position as a line, April 2025 to September 2026
See It Happen

Watch this part of the work play out

All six chapters
site-audit · outdoor-store.com780 URLs
  • /
  • /women/
  • /women/boots/
  • /women/boots/hiking-boot-x1
  • /men/
  • /men/boots/
  • /men/boots/trail-runner-z
depth 3 clickscrawl on money pages 91%
Chapter 6 · Large e-commerce

Four thousand URLs, restructured

An eight-year-old store with no plan gets audited, cut and rebuilt into a shape Google can follow.

Watch the full chapter
Industries this fits

Technical SEO by industry

The same service does a different job in each trade. Here is the move it makes in each industry I've written up.

Trade Terms, Plain English

The words you'll hear, and what they mean

SEO has its own vocabulary. Here's the part of it this service uses, so a report never reads like a foreign language.

Crawl budget
How many of your pages Google is willing to visit in a given period.
Indexing
Google filing a page so it can appear in results. Crawled isn't the same as indexed.
Canonical tag
A note telling Google which of several similar URLs is the real one.
Rendering
Running a page's JavaScript to build what the visitor sees. Google does this later, and sometimes not fully.
Core Web Vitals
Google's speed and stability scores for how a page feels to load.
Soft 404
A page that says “not found” but tells Google everything is fine.
Anup Luintel
Before you decide

Everything on this page comes from how I actually run this work. The checklists, the tools and the results are real. Tell me what's happening on your site and I'll tell you honestly whether this is the right place to start, or whether something else needs fixing before it.

Anup Luintel
Senior SEO Strategist · Kathmandu, Nepal
Questions

What people ask before starting

Do you just send a report, or fix things too?

Both. Every finding comes with a fix written for your developer, and where I have access I implement it myself. An issue isn't closed until a re-crawl shows it's gone from the live site.

Can I buy one audit lane instead of all eleven?

Yes. The lanes are built to be commissioned one at a time. Most sites start with the foundation check and the Search Console audit, then add lanes as the findings point to them.

My developer is busy. Will this create a mountain of work?

Findings are ranked by impact against effort, so the top batch is short and pays back fastest. Each fix arrives in its own folder with the exact steps, so your developer isn't reading a 90-page audit to find their task.

How do I know a fix actually worked?

Every finding carries a verification line: the metric to watch or the test to re-run, and what result counts as fixed. That's checked, not assumed.

Often Paired With

Services that work alongside this one

Fix the foundation

Website Migrations

Redesigns, platform moves, rebrands and domain changes run in gated phases, with every URL mapped and every ranking baselined before anything moves.

See the service Fix the foundation

Traffic Recovery

Find out what actually caused the drop, fix the cause instead of the symptoms, and track the recovery week by week.

See the service Specialist

E-commerce & Shopify SEO

Collection and product pages that rank and convert, filters that don't waste Google's time, and a Merchant Center feed that actually gets approved.

See the service

Ready to talk about Technical SEO?

Send me your site and what you're trying to grow. I'll look at it myself and reply personally, usually within one business day.

See the results