Technical SEO audits and fixes

Your site can look fine to visitors while Google and AI tools struggle to crawl, render and understand it. Technical SEO finds what's in their way and fixes it.

A server rack full of network cables, in black and white with a red streak across it

01 Why it matters

The problem

Google and AI tools read your site through its code, not the design your visitors see. When pages render late, links lead to errors or the same page lives at five different URLs, crawlers waste their time and some pages never get indexed.

These problems build up quietly as plugins, filters and tracking scripts get added over the years. Nothing looks broken on screen, but rankings stop growing.

02 Signs you need this

Sound familiar?

  • Pages you've published don't show up in Google's index.
  • Search Console lists 404 errors and broken links.
  • Pages built with JavaScript frameworks load slowly, or show crawlers an empty page.
  • Filters and URL parameters create thousands of near-duplicate pages.
  • Canonical tags or redirects point to the wrong pages.
  • Schema markup is missing or broken.

03 What I do

What's included

  1. 01

    Full technical audit

    A crawl of the whole site with Screaming Frog and Search Console data, written up as a prioritised list of fixes. On larger sites the audit usually takes two to six weeks.

  2. 02

    Crawling and indexing

    Fixing what blocks crawlers or wastes their time: crawl traps, parameter URLs, 404s and pages missing from the index.

  3. 03

    Rendering

    Checking that pages built with React or Next.js render fully for Google and AI tools, as well as in a browser.

  4. 04

    Canonicals and redirects

    Making canonical tags and redirects consistent, so each page has one clear URL.

  5. 05

    Schema markup

    Structured data that tells search engines and AI tools what each page is about.

  6. 06

    Structure, internal links and speed

    A site structure that's easy to crawl, internal links that point to the pages that matter, and faster load times.

  7. 07

    AI extractability check

    Checking that AI tools can pull clean answers from your pages.

  8. 08

    Large and enterprise sites

    For sites with hundreds of thousands of URLs: log file analysis, crawl budget, faceted navigation and international setups, with fixes written as tickets your engineering team can schedule.

04 What you get

Deliverables

  • A written audit with every issue ranked by impact and effort
  • Fixes made directly, or clear tickets your developer can work from
  • Before and after crawl data, so you can see what changed
  • A schema and internal linking plan for your key pages

05 How a quarter runs

Four steps, every quarter

  1. 01

    Crawl and review

    Crawl the site and pull Search Console data to see what Google sees.

  2. 02

    Prioritise

    Rank every issue by how much it holds back traffic and how hard it is to fix.

  3. 03

    Fix

    Work through the list, starting with whatever blocks crawling and indexing.

  4. 04

    Re-crawl and report

    Crawl again to confirm the fixes, and report what changed.

06 A result

A result from a client

+380%

key events · Digital marketing agency

Six months. Technical clean-up and NAP fixes came first, then the Google Business Profile and the service pages.

See the case studies
Chaitanya Kore in round sunglasses, facing the camera

07 Who you'll work with

Chaitanya Kore

AI & SEO Strategist · Pune · Since 2017

I've worked in SEO since 2017. I led a team of 19 SEO analysts across more than 70 projects at GO MO Group, managed client accounts end to end at WSI ALM Corp, and now run AI and SEO strategy for international clients there.

You work with me from the first quarterly review to the last report.

See the career timeline

08 Questions

FAQ

How long does a technical audit take?

On larger sites it usually takes two to six weeks. Smaller sites take less.

Do you audit enterprise sites?

Yes. On large sites the audit adds server log analysis and crawl budget work, and covers faceted navigation, international versions and JavaScript rendering. Fixes come as tickets with the evidence attached, so your engineering team can prioritise them.

Do I need a developer?

Some fixes, such as redirects, meta tags and schema, can often be made in your CMS. Others, like rendering problems, need a developer. The audit says which is which.

Does the audit cover AI tools as well as Google?

Yes. It includes a check of how well AI tools can pull answers from your pages, and the fixes for whatever gets in their way.

09 How it fits

Part of a 12-month plan

This is one of eight groups of work that each quarter's activity list draws from. The review at the start of every quarter decides how much of it your site needs.

Anything that goes on a quarter's list is covered by the guarantee. If it isn't delivered, I do it in extra hours and you don't pay for them.

10 Get in touch

Plan your first quarter

Based in Pune and working with companies across India. If anything on a quarter's list isn't delivered, the extra hours are on me.