A good technical SEO audit answers one question: can search engines find, render, understand and trust every page that matters? If the answer is "no" anywhere, content and links won't reach their potential.

This is the checklist I use when I start with a new website — from small stores to enterprise sites with hundreds of thousands of URLs.

Tools you need

  • Google Search Console — indexing, Core Web Vitals, sitemaps, manual actions.
  • A crawler — Screaming Frog or Sitebulb.
  • PageSpeed Insights — lab and real-user (field) speed data.
  • GA4 — to connect technical problems to lost traffic and revenue.

Step 1: Crawlability

  1. robots.txt — is anything important blocked? Are CSS and JS files accessible?
  2. XML sitemap — only indexable 200-status URLs, submitted in Search Console.
  3. Status codes — find 4xx and 5xx errors and redirect chains in your crawl.
  4. Orphan pages — pages in the sitemap with no internal links pointing to them.

Step 2: Indexing

Open Search Console → Pages and read the "Why pages aren't indexed" table carefully:

Status What it usually means What to do
Crawled – currently not indexed Google saw the page but didn't think it was worth indexing Improve quality, merge thin pages, add internal links
Discovered – currently not indexed Google knows the URL but hasn't crawled it Improve internal linking, reduce low-value URLs
Duplicate without user-selected canonical Similar pages competing Add canonical tags or consolidate
Alternate page with proper canonical tag Working as intended Usually nothing

Pro tip: on e-commerce sites, filters and sorting parameters often create thousands of near-duplicate URLs. Control them with canonicals, internal linking rules and careful robots.txt use.

  • Important pages should be reachable in 3 clicks or fewer from the home page.
  • Use descriptive anchor text, not "click here".
  • Link from strong pages (high traffic or many backlinks) to pages you want to grow.
  • Use breadcrumbs with BreadcrumbList schema.

Step 4: Core Web Vitals

Since March 2024, INP (Interaction to Next Paint) replaced FID. The "good" thresholds, from web.dev, are:

≤ 2.5s

LCP — Largest Contentful Paint

≤ 200ms

INP — Interaction to Next Paint

≤ 0.1

CLS — Cumulative Layout Shift

Common fixes: compress and convert images to WebP/AVIF, set width and height on images, preload the hero image, defer non-critical scripts, and remove unused tracking tags.

Step 5: On-page technical elements

  • One clear H1 per page.
  • Unique title tags (roughly under 60 characters) and meta descriptions.
  • Self-referencing canonical tags on indexable pages.
  • Alt text on meaningful images.

You can test titles and descriptions with my free Google snippet preview tool.

Step 6: International and multilingual SEO

For Arabic/English sites, hreflang is where I find the most mistakes:

  • Every language version must link to all others and to itself.
  • Use ar and en (or ar-SA, ar-EG if content differs by country).
  • Add an x-default for the fallback version.
  • Don't auto-redirect users and bots by IP without giving a way to switch.

Google's documentation on localized versions is the reference.

Step 7: Structured data

Validate with the Rich Results Test. The most useful types for most businesses: Organization or LocalBusiness, Person (for authors), BreadcrumbList, Article/BlogPosting, Product and FAQ where relevant.

Step 8: AI search readiness

  • Key content available in the HTML (not only after JavaScript).
  • Clear question-style headings with direct answers.
  • Author and company information that's easy to verify.

More in my guide to Generative Engine Optimization.

How to prioritize the fixes

Score every issue on impact (traffic or revenue affected) and effort (developer time). Fix high-impact/low-effort issues first, then plan the bigger ones with your developers. A good audit ends with a ranked task list — not a 90-page PDF.

FAQ

How often should I run a technical SEO audit?

A full audit once or twice a year, plus a monthly health check of Search Console and a crawl after every major release or migration.

Can I do a technical SEO audit without a developer?

You can find most issues yourself with Search Console and a crawler. Fixing them — especially speed and rendering — usually needs a developer.

What is the most common technical SEO problem you find?

On large sites, index bloat: thousands of low-value URLs (filters, tags, parameters) that waste crawl budget and dilute quality signals.

#technical SEO#SEO audit#Core Web Vitals#indexing#hreflang

Written by

Mohamed Abdelkhalk

SEO Manager & Growth Strategist with 8+ years in technical SEO, AI search, content strategy and media buying across Egypt, the Gulf and the USA. Founder of Souqly.

اقرأ هذا المقال بالعربية