A well-organized site audit is a decision-making system that connects each finding to a business outcome, an owner and a next step. This framework uses six workstreams, one URL inventory and one issue log. Audit date:.

Start with the site's goals, then build a complete URL database, collect data from several sources and group findings by problem type. Finish with a prioritized roadmap that tells the team what to fix first.

This approach prevents a common problem: collecting hundreds of tool warnings without knowing which ones deserve attention.

Site Audit Structure at a Glance

Audit stage Main output
Define scope and goals Audit brief
Build a URL inventory Complete page database
Collect data Crawl, Search Console and analytics exports
Review audit workstreams Findings grouped by problem type
Prioritize issues Impact and effort ranking
Create the roadmap Assigned tasks with deadlines
Validate fixes Before-and-after results

1. Define the Purpose and Scope of the Audit

Before opening Screaming Frog, Semrush, Ahrefs or another crawler, write down what the audit needs to answer.

Possible questions include:

  • Why has organic traffic declined?
  • Which pages are not indexed?
  • Is the site ready for a migration?
  • Which templates create duplicate or thin content?
  • Why are important pages not ranking?
  • Which technical issues affect conversions?
  • Is the website suitable for a redesign?

The scope should also identify:

  • Domains and subdomains included
  • Country and language versions
  • Desktop and mobile versions
  • Main page types
  • Date range for performance data
  • People responsible for fixes
  • Business goals and conversion actions

The scope should match the reason for the audit. A traffic recovery audit will not follow the same process as a pre-migration audit. A local business website also needs a different review from a large ecommerce site with faceted navigation.

2. Create One Master URL Inventory

The URL inventory is the working database for the audit. Do not rely only on crawler discoveries. Important pages may be orphaned, blocked, excluded from internal links or missing from the site's XML sitemap.

Create one row for each known URL and include:

  • URL
  • Page type
  • Website section
  • HTTP status
  • Indexability
  • Canonical URL
  • Title tag
  • Meta description
  • H1
  • Word count
  • Organic clicks
  • Organic impressions
  • Organic conversions
  • Internal links
  • Backlinks
  • Last updated date
  • Recommended action
  • Assigned owner
  • Status

Useful page-type labels include:

  • Homepage
  • Product page
  • Category page
  • Service page
  • Location page
  • Blog post
  • Editorial guide
  • Case study
  • Landing page
  • Search result page
  • Tag or archive page

For a large website, review pages by template and section before reviewing every URL manually. A problem affecting one product template may matter more than an isolated issue on a low-value blog post.

Screaming Frog supports segmentation by page type, website section, crawl data and connected data sources. That makes it useful for grouping findings instead of treating a large export as one list.

3. Separate the Audit Into Workstreams

Use separate workstreams for different types of problems. A practical SEO site audit usually includes six.

A. Technical SEO and Indexability

Check whether search engines can access, understand and index the pages that matter.

Review:

  • Robots.txt
  • XML sitemaps
  • HTTP status codes
  • Redirect chains
  • Broken internal links
  • Canonical tags
  • Noindex directives
  • Orphan pages
  • Duplicate URLs
  • HTTPS implementation
  • JavaScript-rendered content
  • Mobile accessibility
  • Structured data
  • Pagination and faceted navigation

Google describes robots.txt as a way to control crawling, not as a reliable method for preventing indexing. Pages that should stay out of search generally need an appropriate noindex directive or an access restriction.

Treat canonical tags as signals rather than absolute commands. Google may select a different canonical URL when other signals, such as redirects, sitemap inclusion or page quality, conflict with the declared preference.

Use Google Search Console's URL Inspection tool to investigate important URLs individually. It can show index status, crawling information, rendered resources and the canonical URL selected by Google.

Review how users and search engines move through the website.

Check:

  • Navigation hierarchy
  • Category and subcategory structure
  • Click depth
  • Breadcrumbs
  • Internal links to priority pages
  • Orphan pages
  • Links pointing to redirected URLs
  • Generic anchor text
  • Important pages buried in the site structure
  • Internal links from high-authority pages

Google recommends crawlable HTML links with an href attribute. Internal links help Google discover pages and understand their relevance, while descriptive anchor text gives context about the linked page.

Record architecture problems against affected page groups instead of creating hundreds of duplicate rows. For example:

Product pages in the /software/ section require three navigation steps from the homepage and receive no contextual links from related guides.

That finding gives the team a clear problem to solve. Listing the same issue against every URL does not.

C. Content Quality and Search Intent

Review content by page type and search intent, not only by word count.

For each important page, ask:

  • What query or customer need does this page target?
  • Does it satisfy that need better than competing results?
  • Is the content current and factually accurate?
  • Is the page substantially different from similar pages?
  • Does it have a clear next step?
  • Does another page on the site target the same intent?
  • Should the page be improved, merged, redirected, removed or left unchanged?

Classify each URL with an action such as:

  • Keep
  • Improve
  • Consolidate
  • Redirect
  • Remove
  • Create
  • Monitor

This turns a content audit into a set of decisions. It also prevents the team from treating every page as equally valuable.

D. On-Page SEO

Review page-level elements in the URL inventory.

Check:

  • Title tags
  • Meta descriptions
  • H1 headings
  • Heading hierarchy
  • Image alternative text
  • Descriptive URLs
  • Duplicate metadata
  • Missing metadata
  • Internal anchor text
  • Structured data
  • Alignment with search intent

Do not automatically rewrite every title that exceeds a preferred character range. First ask whether the title describes the page accurately, matches the searcher's intent and encourages a qualified click.

E. Performance, Accessibility and Mobile Experience

Use both site-level data and page-level testing.

Google Search Console provides a Core Web Vitals report based on real-world usage data. The current Core Web Vitals are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Google's recommended "good" targets are:

  • LCP within 2.5 seconds
  • INP of 200 milliseconds or less
  • CLS of 0.1 or less

Test representative templates rather than only the homepage:

  • Homepage
  • Product or service page
  • Category page
  • Blog article
  • Contact or checkout page
  • Mobile navigation
  • High-conversion landing page

Lighthouse separates its findings into performance, accessibility, best practices and SEO categories. Use it to investigate example pages, but do not treat one Lighthouse score as a complete assessment of the entire site.

F. Search Performance and Conversions

Connect technical findings to business outcomes.

Review:

  • Organic clicks and impressions
  • Rankings by page
  • Queries with high impressions but low clicks
  • Pages losing traffic
  • Landing pages with traffic but few conversions
  • Conversion paths
  • Form and checkout completion
  • Branded versus non-branded traffic
  • Country and device performance

Google Search Console's Performance reports provide query, page, country, click and impression data. Use this information to identify which technical and content issues affect valuable pages instead of treating every URL equally.

4. Collect Data in the Right Order

Use this sequence to keep the audit connected to the business problem:

  1. Business baseline: goals, conversions, priority pages and recent changes.
  2. Google Search Console: performance, indexing, manual actions, security and Core Web Vitals.
  3. Analytics: landing pages, engagement and conversion data.
  4. Full crawl: status codes, metadata, canonicals, links and directives.
  5. Sitemap and robots.txt review: compare declared URLs with crawled and indexed URLs.
  6. Template testing: performance, rendering, accessibility and mobile usability.
  7. Manual review: important pages, top traffic pages and representative templates.
  8. Competitor or SERP review: use this when rankings, search intent or content quality are part of the audit objective.

If the website relies heavily on JavaScript, run a rendered crawl as well as a raw HTML crawl. Screaming Frog provides JavaScript rendering options for sites where content or links are populated after the initial HTML response.

5. Keep One Issue Log

Use one master issue log for technical SEO, content, architecture and performance findings.

Recommended columns:

Column What to record
Issue ID Unique reference, such as TECH-001
Workstream Technical, content, architecture or performance
Finding What is wrong
Evidence URL, screenshot, export or report
Affected URLs Specific URLs or page template
Business impact Traffic, revenue, usability or compliance effect
SEO impact Crawl, indexation, ranking or internal-link effect
Recommendation Exact action required
Priority P1, P2 or P3
Effort Low, medium or high
Owner Person or team responsible
Status Open, in progress, blocked or complete
Validation method How the fix will be checked

Write findings as actions.

Weak:

Duplicate title tags.

Strong:

The 146 product pages use the same title template without the product name. Update the product template so each title identifies the product and its main differentiator.

The second version identifies the affected pages, the cause and the required fix.

6. Prioritize Issues by Impact and Effort

Do not copy the priority labels produced by an audit tool without reviewing them against the site's goals.

P1: Fix First

These issues can prevent important pages from being crawled, indexed, accessed or converted.

Examples:

  • Important pages blocked by robots.txt
  • Incorrect noindex directives
  • Broken migration redirects
  • Widespread server errors
  • Checkout or lead forms not working
  • Canonical tags pointing to irrelevant pages

P2: Fix Next

These issues affect performance, relevance or usability across a meaningful section of the site.

Examples:

  • Poor internal linking on commercial pages
  • Duplicate content across a template
  • Slow product pages
  • Missing titles on high-value URLs
  • Important content rendered incorrectly with JavaScript

P3: Improve Continuously

These issues are useful but should not displace critical fixes.

Examples:

  • Minor metadata inconsistencies
  • Low-value image alt text improvements
  • Small heading-order issues
  • Recommendations affecting only low-traffic pages

A simple internal scoring model is:

Priority score = business impact × SEO or user impact × confidence ÷ implementation effort

Rate each factor from 1 to 5. The calculation does not need to be mathematically perfect. Its purpose is to make trade-offs visible and consistent.

7. Convert the Audit Into a Roadmap

An audit is incomplete until someone knows what happens next.

Create a roadmap with:

  • Issue ID
  • Recommended fix
  • Owner
  • Effort estimate
  • Dependencies
  • Planned release
  • Validation metric
  • Status

Group the work into delivery phases.

Phase 1: Critical Protection

Fix indexing, security, broken redirects, server errors and conversion blockers.

Phase 2: High-Impact Improvements

Improve templates, internal links, page speed, content overlap and important landing pages.

Phase 3: Growth Opportunities

Create missing content, improve commercial page coverage, expand structured data and refine conversion paths.

Phase 4: Ongoing Monitoring

Track Search Console, analytics, crawl errors, rankings, Core Web Vitals and completed recommendations.

8. Validate the Fixes

After implementation, rerun the relevant test instead of simply marking the issue complete.

Validation may include:

  • Re-crawling affected URLs
  • Checking the live URL in Search Console
  • Confirming redirects resolve correctly
  • Checking that the intended canonical is selected
  • Testing rendered content
  • Comparing Core Web Vitals over time
  • Reviewing organic clicks and impressions
  • Confirming conversions or form submissions
  • Checking that the fix did not create new errors

Google notes that recrawling and reprocessing can take several days to several weeks. Requesting indexing does not guarantee immediate inclusion in search results.

Use a consistent folder and spreadsheet structure:

Site Audit/
├── 00_Audit_Brief
├── 01_URL_Inventory
├── 02_Search_Console_Data
├── 03_Analytics_Data
├── 04_Crawl_Exports
├── 05_Technical_Findings
├── 06_Content_Findings
├── 07_Performance_Findings
├── 08_Issue_Log
├── 09_Implementation_Roadmap
└── 10_Validation

For most websites, use one workbook with these tabs:

  1. Audit brief
  2. URL inventory
  3. Technical findings
  4. Content findings
  5. Performance findings
  6. Issue log
  7. Roadmap
  8. Validation

The folders hold source files and exports. The workbook holds the working analysis, decisions and delivery status.

A useful site audit does not aim to produce the longest list of warnings. It makes the next five actions clear, assigns each action to someone and defines how the result will be checked.