Skip to content
Tutorials Center
My learning

Topics

Lesson 33 of 36 ยท Analytics and Measurement

SEO Audits and Tools

Learn how to run a complete SEO audit step by step: crawling, indexing, on-page, content, links and performance checks, the tools to use, log files and how to prioritize fixes.

An SEO audit is a structured check of a site against everything that affects its search performance. The goal is not a long list of warnings but a short, prioritized list of changes that will make a difference. This lesson gives you a repeatable process and the tools that support each step.

Before you start

Agree on what success means (traffic, leads, sales), which markets and languages are in scope, and which pages matter most. Collect access to Search Console, analytics, the CMS, the server or CDN settings, and any previous audit or changelog. Take a baseline of key metrics so you can measure the effect of your fixes.

The audit process

flowchart LR
  A["1. Crawl the site"] --> B["2. Indexing and crawlability"]
  B --> C["3. Technical and speed"]
  C --> D["4. On-page and content"]
  D --> E["5. Links and authority"]
  E --> F["6. Prioritize and report"]

Work from the foundation upward: pages that cannot be crawled or indexed cannot rank.

1. Crawl the site

Use a crawler (Screaming Frog, Sitebulb, Lumar, or a free open-source option) to fetch your URLs the way a bot does. Export status codes, titles, descriptions, headings, canonicals, robots directives, word counts, internal links and response times. Compare the crawl with your sitemap and with Search Console's list of indexed URLs to find orphans and pages that should be indexed but are not.

2. Indexing and crawlability

  • Is robots.txt accidentally blocking important sections or resources (robots.txt and XML Sitemaps)?
  • Are important pages marked noindex by mistake, especially after a staging deployment?
  • Do canonicals point to the right URLs, and do the sitemaps list only canonical 200 pages (Canonicals, Redirects and Duplicate Content)?
  • How many URLs are in the index versus the number you expect? A big gap either way is a finding.
  • Are there redirect chains, loops, soft 404s or 5xx errors?

3. Technical and speed

4. On-page and content

  • Unique, accurate titles and descriptions; one clear H1 and logical headings.
  • Search intent match for target queries, thin or duplicate pages, cannibalization (Refreshing and Pruning Content).
  • Image alt text and file sizes, internal linking and anchor text.
  • Evidence of expertise, author information and up-to-date facts.
  • Referring domains, quality and anchor distribution; toxic patterns; sudden spikes or losses (Backlinks and Link Building).
  • Internal link distribution: are important pages well linked?
  • Brand mentions and unlinked mentions.

6. Prioritize and report

For each finding record the issue, evidence (URLs, screenshots, counts), why it matters, the fix, effort and expected impact. Then sort by impact over effort.

Python Prioritize findings by impact and effort

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Always fix blockers first (noindex, robots blocks, server errors, broken redirects). Polishing meta descriptions is pointless if the pages are not indexed.

Tools

Need Examples
Search data and indexing Google Search Console, Bing Webmaster Tools
Behaviour and conversions GA4, Matomo, Plausible
Site crawling Screaming Frog, Sitebulb, Lumar, command-line crawlers
Speed and vitals PageSpeed Insights, Lighthouse, WebPageTest, Chrome DevTools
Structured data Schema Markup Validator, Rich Results Test
Backlinks and keywords Ahrefs, Semrush, Moz, Majestic (paid), Search Console Links report (free)
Rank tracking Paid trackers, or your own sampled checks
Log analysis Server log files with a log analyser or your own scripts

No tool is the truth. Tools estimate traffic and difficulty using their own data, so cross-check important findings with Search Console and your own analytics. Prefer free official tools for the facts and paid tools for scale and competitor comparison.

Server log analysis

Your web server records every request, including those from search engine bots. Logs show which URLs bots fetch, how often, what status codes they receive and which sections they ignore. Verify bot identity by reverse DNS (anyone can fake a user-agent string).

Python Summarize bot requests from a log

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A high share of bot requests spent on parameter URLs, errors or redirects is a sign of wasted crawl effort (E-commerce and Large Site SEO).

Making the audit useful

  • Lead with a short summary of the three to five biggest issues and opportunities.
  • Show evidence, not opinions, and explain the business effect in plain language.
  • Offer a roadmap in phases (quick wins, medium projects, long projects) with owners.
  • Re-crawl after fixes and compare with the baseline.
  • Schedule recurring lightweight audits (monthly crawl, weekly Search Console review) and a deep audit yearly or before and after major changes such as redesigns and migrations.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why fix indexing blockers before meta descriptions?

    Crawlability and indexability are the foundation; everything else depends on them.
  2. 2. How should audit findings be ordered?

    Prioritizing by impact over effort gets the most improvement for the time spent.
  3. 3. What can server logs reveal that a crawler cannot?

    Logs record real bot visits, showing crawl waste and ignored sections.
  4. 4. How should you treat third-party tool numbers?

    Third-party tools model data; verify important claims against first-party data.

Summary

  • An audit is a structured, evidence-based review, not a warning list.
  • Work from crawlability and indexing upward to content and links.
  • Use crawlers, Search Console, analytics, speed tools and logs together.
  • Prioritize by impact and effort, and report clearly with a roadmap.
  • Re-check after changes and audit regularly.

Next: Project: Build a Meta Tag Auditor