A Free SEO Audit That Produces a Fix List You Can Actually Validate

A useful SEO audit is not a screenshot collection or a crawler export. It is a diagnostic record that connects an observed problem to evidence, a severity decision, an owner, a corrective action, and a validation step.

Review four layers separately:

• Technical access and indexation: confirm that important pages can be crawled, rendered, indexed, and served consistently.
• On-page implementation: review titles, headings, canonicals, response codes, internal links, and other page-level signals that can be checked directly.
• Content usefulness and query fit: compare the page with the queries and intent it is actually receiving impressions for, then identify duplication, weak coverage, or competing pages.
• External authority evidence: review known referring domains, linked pages, and suspicious patterns without assuming a vendor score proves quality or harm.

This guide does not combine paid search, social performance, or conversion optimization into the same audit. Those require different evidence and ownership.

The source editorial material contrasted a lightweight audit with a 90-page deliverable. Length is not the quality test. A shorter audit is more useful when every finding is traceable to a URL or page group and has a clear next action.

Before opening tools, capture the baseline you will use for validation: current organic performance, important landing pages, known site changes, migrations, deployments, and any recent incidents. The related free SEO tools statistics guide can provide context for tool usage, but your own first-party evidence should decide what is material on your site.

Evidence: open Google Search Console for the verified property and review indexing reports, URL Inspection for representative pages, manual actions, security issues, and Core Web Vitals. Use PageSpeed Insights when a page group needs a closer performance check.

Pass condition: priority pages return the intended response, are not unintentionally blocked or excluded, and have no unresolved property-level manual action or security warning. An excluded URL is not automatically a failure; confirm whether exclusion is intentional before creating a fix.

High-severity examples: an important URL returning a 404 response despite still being linked or expected to rank, an unintended noindex directive, a broken canonical target, a redirect failure that prevents access, or a manual action affecting the property.

Performance evidence: when PageSpeed Insights identifies a heavy resource, record the actual request or asset rather than treating the score as the problem. The source material used an image above 200KB as an operating example, not an official Google ranking threshold.

Owner: assign infrastructure and response-code issues to the developer or platform owner, content-indexation decisions to the SEO or content owner, and manual-action or security remediation to the person with the access required to investigate the underlying cause.

Corrective action: fix the specific implementation that caused the failed state. Do not change a page solely because a generic audit warning exists.

Validation: rerun the relevant inspection, recrawl the affected URL, confirm the production response and directives, then monitor Search Console after Google has had an opportunity to revisit the page. Use the free SEO tool setup checklist to confirm the diagnostic tools are configured before relying on their output, and consult the common free SEO tool mistakes guide when a finding may be caused by setup or interpretation error.

Evidence: crawl the site with Screaming Frog SEO Spider. The free tier supports up to 500 URLs, so define the crawl scope before starting and document any important areas excluded by the limit.

Review page titles and flag titles over 60 characters or under 30 characters as editorial review prompts, not ranking violations. The correct decision depends on clarity, duplication, intent, and how the title appears in search.

Review H1 implementation and record missing, duplicated, or confusing headings. For an indexable page, a clear H1 should describe the primary topic. Record whether the first H1 matches the intended page purpose and whether the final H1 shown to users is the one the owner intends.

Response-code evidence: inspect 3xx paths and internal links that land on a 404 response. A redirect is not automatically a problem; flag it when it is unnecessary, broken, points to the wrong destination, or creates avoidable crawl and user friction. For any H1-related finding, keep the page-level evidence alongside the response-code evidence so unrelated warnings are not merged into one issue.

Owner: template-wide title, heading, and internal-link defects belong with the developer or CMS owner; page-specific wording belongs with the content or SEO owner.

Corrective action: fix the source template or page field that creates the pattern. If the issue repeats across a page type, correct the template once instead of editing every affected URL independently.

Validation: rerun the crawl using the same scope, compare the affected rows, and manually inspect a sample in the browser. If rendered content is missing from the crawler, use URL Inspection to verify what Google can render rather than assuming the crawl output is complete.

Evidence: combine Search Console page and query data with the crawl inventory. Review pages that receive impressions but weak engagement, pages that are indexed without a clear search purpose, and multiple URLs appearing for the same important query.

The source used more than 50 impressions and fewer than five clicks over a 90-day window as a review example. Preserve it as an operating example, not as a universal quality threshold. A low click rate can reflect rank position, query mismatch, SERP features, title presentation, or other factors.

Pass condition: each priority page has a distinct purpose, matches the intent of the queries it targets, and does not unnecessarily compete with another page owned by the same site.

Severity: raise severity when competing pages split a commercially important topic, an important page is omitted from the index without an intentional reason, or a weak page is receiving substantial impressions for a query it does not satisfy.

Corrective action: when two pages genuinely serve the same intent and one should replace the other, consolidation can include moving useful content and applying a 301 redirect to the retained destination. Do not redirect merely because two pages share a keyword.

Content depth should be judged by usefulness, not by word count. A 2,000-word page can be unfocused, while a 400-word page can fully answer a narrow question. Use query evidence, page purpose, duplication, and user value to decide whether to improve, merge, retain, or remove content.

Owner: assign page-purpose and consolidation decisions to the SEO and content owner, with developer support when redirects, templates, or routing must change.

Validation: after the change, verify the final URL and response, confirm internal links point to the retained page, request or wait for recrawl as appropriate, and compare the same query and page data in a later period without assuming a ranking change was caused by one edit alone.

Evidence: start with Google Search Console's Links report for the verified property, then use any available free backlink view as supplementary evidence. Record linked pages, referring domains, anchor context, and unusual concentrations rather than reducing the profile to one authority score.

Pass condition: there is no known manual action related to links, important pages are not entirely isolated from external references when the site has earned coverage, and suspicious clusters have been manually reviewed before any destructive action is proposed.

Severity: treat a manual action or clear evidence of deliberate manipulative linking as high severity. A low vendor score, an unfamiliar domain, or a spam label by itself is not enough to justify removal or disavowal.

Supplementary review: the source referenced a free backlink view limited to the top 100 backlinks. Use any such limit as a sampling constraint, not as proof that the visible sample represents the entire profile.

Owner: the SEO owner should document the evidence and recommendation; legal, PR, developer, or site-owner involvement may be needed if the links relate to hacked pages, partnerships, or site changes.

Corrective action: remove or disavow only when the evidence and current Google guidance support that action. Do not use automated toxicity labels as a substitute for inspecting the actual linking pages.

Validation: record the exact links or domains affected, preserve the before-state, confirm any requested removals or file changes, and monitor Search Console for relevant messages. Absence of an immediate ranking change does not invalidate the remediation, and a later change should not be attributed to it without supporting evidence.

Do not finish with a flat list. Every finding should become a work item with evidence, severity, owner, corrective action, and validation.

Axis 1 - impact: grade how strongly the issue can affect crawlability, indexation, user access, search visibility, or an important page group. Base the grade on the affected URLs and evidence, not on how alarming a tool label sounds.

Axis 2 - effort: estimate the implementation dependency and who must make the change. A content-field correction and a template or infrastructure change belong in different queues even when both are important.

Use four practical buckets:

• High impact, low effort: implement first when the evidence is clear and validation is straightforward.
• High impact, high effort: schedule as a scoped project with technical ownership and rollback considerations.
• Low impact, low effort: batch as maintenance when it does not distract from more material work.
• Low impact, high effort: defer unless new evidence raises the business impact.

The source editorial material separately used 60 as an operating reference and described a 60 to 90 day review window for some changes. Treat those timeframes as historical workflow examples, not guarantees. Name the stage being measured: implementation verification can happen immediately, recrawl confirmation depends on discovery, and performance evaluation needs enough later data to compare responsibly.

For each row, record the affected URL or template, the evidence source, severity, owner, corrective action, implementation date, and validation method. This makes the audit reusable during the next review instead of turning it into a static report.

If the audit repeatedly surfaces issues requiring access or expertise you do not have, document the dependency and delegate the corrective action. To work through the same workflow with the available utilities, run your audit with our free SEO tools.