Recommended Free Tools
An SEO audit is a structured review of whether the right pages on your website can be discovered, crawled, rendered, indexed, understood, and found useful by the people you want to reach—and whether organic search contributes to business goals. It is not a crawler score or a promise of higher rankings. A useful audit verifies issues, weighs their impact, and ends with an evidence-backed plan for what to fix first.
Use the checklist below to move from scope and baseline data through technical SEO, content, links, and measurement. The deliverable should be an actionable workbook: URL inventory, verified findings, impact and effort, owners, validation steps, and a 30-, 60-, and 90-day plan.
What an SEO audit covers
A complete audit looks beyond technical warnings. It connects the site’s business goals and measurement setup to the pages search engines can access and the audience can use.
- Business goals, audience, markets, and measurement.
- Crawlability, indexability, rendering, and technical delivery.
- Site architecture, internal links, and canonicalization.
- On-page optimization, content quality, and search intent.
- Structured data, performance, and mobile experience.
- Backlinks and authority, plus local, international, ecommerce, or JavaScript-specific checks when relevant.
- Prioritization, implementation, validation, and monitoring.
Google’s technical requirements are narrower than this full review: Googlebot must not be blocked, a page must return a successful HTTP status, and it must contain indexable content. Meeting those requirements does not guarantee crawling, indexing, ranking, or traffic. The broader Search Essentials cover technical requirements, spam policies, and key best practices; they are not a ranking guarantee.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
When to conduct an audit
Audit when a meaningful change or risk warrants investigation: a new launch, redesign, CMS or domain migration, major template deployment, international expansion, ecommerce navigation problem, JavaScript framework change, acquisition review, or significant search traffic or conversion decline. A major content-pruning project merits checks before and after changes.
Frequency should reflect site size, change rate, and risk. A small, stable brochure site might use an annual full review plus ongoing monitoring; a large ecommerce or publishing site may need continuous technical monitoring and more frequent sampled reviews. Do not treat an arbitrary schedule as a substitute for event-driven checks.
Prepare access and define the scope
Record the business context before changing anything. First preserve a baseline; otherwise, later comparisons may not show whether a change helped or when a problem began.
Access and inputs
- Verified Google Search Console property and Google Analytics 4 or another analytics platform.
- Bing Webmaster Tools if Bing visibility matters; server logs for large, complex, or crawl-budget-sensitive sites.
- CMS and deployment access, XML sitemap locations, and the robots.txt URL.
- Current domain and URL-variant inventory, target markets and languages, priority products or services, and important templates.
- Conversion and revenue definitions, plus known migrations, outages, deployments, traffic changes, and previous audit findings.
- Staging, development, test, and login-protected environments identified so they are crawled separately and never accidentally exposed.
Scope worksheet
Write down the primary domain, preferred HTTPS and hostname version, included subdomains, countries and languages, mobile and desktop requirements, site type, priority conversions, and the audit’s focus. Note approximate URL volume and complexity. Decide whether this is a full-site, template-based, migration-focused, or decline-focused audit. Identify which pages should attract organic search and which should not.
Also document how filters, parameters, internal search, user-generated pages, and multiple brand or regional versions should behave. For a JavaScript-heavy site, note which content and links depend on client-side rendering.
Establish a performance and indexation baseline
Use a consistent date range—preferably at least the previous 12 months when data is available—and record significant release or migration dates. In Search Console, examine Performance, Page indexing, Sitemaps, URL Inspection, Core Web Vitals, and HTTPS or enhancement reports where relevant. Google lists these and other reports among the tasks covered by Search Console.
- Search visibility: clicks, impressions, average position, click-through rate, top queries, and landing pages.
- Segments: brand versus non-brand, country, device, directory, and page template.
- Business outcomes: organic sessions, leads, transactions, revenue, conversion rate, and lead or customer quality.
- Technical trends: indexed and non-indexed URL patterns, sitemap errors, Core Web Vitals, and relevant rich-result reports.
- External authority: referring-domain and backlink trends, with attention to links to important pages.
Do not set 100% indexation as the goal. Google explains that duplicate, blocked, unsuitable, or intentionally non-indexable URLs may legitimately remain out of the index in its Page indexing report guidance. The objective is appropriate discovery and indexation of valuable canonical pages, not inclusion of every URL the site can generate.
Verify domain versions, HTTPS, and redirects
Check all versions of the domain and confirm one preferred version. For example:
http://example.com
http://www.example.com
https://example.com
https://www.example.comThe preferred URL should return 200 OK. Other versions should redirect directly to it, without chains or loops. Check that internal links, canonicals, XML sitemaps, structured data, and hreflang references (if used) consistently use the preferred version.
curl -I https://example.com
curl -IL http://example.comFor each variant, record every hop’s status, destination, redirect type, and final URL. Check that HTTPS is enforced and that hostname behavior, cookies, and security headers are not unexpectedly inconsistent.
Crawl the site and build a URL inventory
Run two complementary crawls: a linked crawl to see what can be discovered through internal links, and a crawl seeded from the XML sitemap or a known URL list to find submitted pages that are poorly linked or unreachable from navigation. Configure the crawler to follow internal links, capture HTML and relevant assets, and render representative JavaScript-dependent pages. Respect robots.txt for a normal crawl; test blocked paths deliberately only when the audit calls for it.
Separate authenticated, staging, and development environments from the public-site crawl. Do not confuse a crawler’s health score with a search-engine metric: use its raw evidence, then verify important findings manually.
Export at least these fields for each URL: status and final destination, content type, crawl depth, indexability and reason, canonical, title, meta description, H1, word count, internal inlinks and outlinks, external links, image information, structured-data types, hreflang, response time, and last-modified information if available. Add template, topic, primary intent, query group, clicks and impressions, conversions or revenue, business importance, and similar or competing URLs to the working inventory.
Check crawlability: robots.txt and sitemaps
Robots.txt
Fetch /robots.txt on the correct hostname and check its status and contents. Look for rules that unintentionally block important directories or the CSS and JavaScript resources needed for rendering. Check whether parameter-heavy or faceted URLs are consuming crawl demand, and whether a sitemap is declared where appropriate. A rule intended for one crawler does not necessarily control all crawlers.
curl -s https://example.com/robots.txt
curl -I https://example.com/robots.txtRobots.txt controls crawler access; it is not a reliable way to keep a page out of search results. A blocked URL may still be discovered and appear without a normal description. To use a page-level noindex directive, allow the crawler to fetch the page. For genuinely private material, use authentication or access controls. Google explains these limits in its robots.txt documentation. Do not put noindex in robots.txt.
XML sitemaps
Check that each sitemap returns 200 OK and valid XML, and that submitted URLs are absolute, canonical, preferred-host HTTPS URLs that are indexable and return 200. Remove redirects, errors, noindex pages, and unnecessary duplicates. Use truthful last-modified dates; do not update every URL on every request without a real content change. Monitor counts and errors, and use sitemap indexes for large inventories. Include image, video, or news extensions only where relevant.
curl -I https://example.com/sitemap.xml
curl -s https://example.com/sitemap.xml | headA sitemap helps discovery, particularly for new, large, complex, or media-heavy sites, but it does not guarantee crawling or indexing. Google notes that some sites of roughly 500 pages or fewer may not need one if important pages are comprehensively linked; this is conditional guidance, not a universal cutoff. See Google’s sitemap overview.
Check indexability in Search Console
For representative URLs, compare the crawl with Search Console’s Page indexing report and URL Inspection. Select the correct property, enter the complete URL, and review indexing status, the crawled page, user-declared and Google-selected canonicals, HTTPS, and applicable enhancements. If a change may have resolved the issue, test the live URL and inspect the rendered content. Request indexing only after the page is technically correct.
Use URL Inspection on the homepage, a key category or service page, an article, a product page, a recently changed URL, a reported exclusion, and a page that lost traffic. Google describes URL Inspection as a way to request a crawl or recrawl of an individual page; sitemaps are generally more suitable for bulk discovery and monitoring in its Search Console guidance.
For important pages, check that they are publicly accessible, normally return 200, have no accidental noindex or conflicting X-Robots-Tag, and are not blocked from inspection by robots.txt. Confirm that the canonical points to the intended live, indexable representative page, the main content is available after rendering, and the page has meaningful internal links.
Free tools Windows power users keep installed
One-click scans. No signup required.
Useful starting checks include:
curl -I https://example.com/page
curl -Ls https://example.com/page | grep -iE 'noindex|canonical|hreflang'Common failures include a staging noindex carried into production, a robots.txt rule blocking a valuable directory, every canonical pointing to the homepage, sitemap URLs that redirect, an empty JavaScript shell, soft 404 pages, and parameter URLs multiplying near-duplicates. A page can be technically eligible yet remain undiscovered if it is effectively orphaned.
Review status codes, redirects, and canonicals
Classify crawl results as 200 success, 3xx redirect, 4xx client error, 5xx server error, or timeout, DNS, TLS, or connection failure. Look for broken internal links, important broken external links, chains, loops, irrelevant redirect destinations, temporary redirects where a permanent move is intended, and old URLs that should point to a close replacement. Investigate soft 404s: pages returning 200 despite presenting a not-found or empty state.
Fix high-value pages, whole-template or directory problems, and redirect chains before low-value isolated errors. Do not automatically redirect every 404: leave a genuinely removed page as a 404 when no relevant replacement exists.
Compare the preferred URL, response, canonical tag, internal links, sitemap, hreflang, Open Graph URL, structured-data URLs, redirect destination, and variants involving parameters, capitalization, trailing slashes, or ports. Common duplicate sources include faceted navigation, internal search, tracking parameters, archives, alternate paths, and mobile or AMP versions. A canonical is a hint, not an absolute command; it should point to a live, indexable, representative URL and agree with other site signals. Do not canonicalize distinct search intents merely because pages are similar, or create near-identical pages for trivial keyword variations.
Choose the right URL control
| Goal | Appropriate approach |
|---|---|
| The old URL should no longer serve users | Use a redirect to a relevant replacement when one exists. |
| Several accessible URLs remain useful or technically necessary, but one should represent the group | Use a consistent canonical to the representative URL. |
| A public page should not appear in search | Allow crawling and use a page-level noindex directive. |
| Content is private | Use authentication or access control. |
| A page is permanently removed with no useful replacement | Delete it and return an appropriate not-found or gone status; do not send every removed page to the homepage. |
Test JavaScript rendering
For JavaScript-heavy templates, compare the raw HTML response with the rendered DOM and visible page. Check the main text, crawlable links, title, description, canonical, robots directives, and structured data before and after rendering. Confirm that important product details, prices, availability, and reviews appear correctly, and that content is not hidden behind interactions users or search engines cannot access.
Check whether pagination, filters, and infinite scroll expose discoverable URLs, whether client-side routes return sensible page titles and status codes, and whether the server or a static fallback supplies useful content. Google’s ability to render JavaScript does not remove timing, hydration, resource-loading, or application-state risks.
Audit mobile experience and Core Web Vitals
Review responsive layouts, viewport setup, tap targets, horizontal scrolling, mobile navigation, content parity, sticky elements, intrusive interstitials, fonts, media, forms, and checkout usability. Check for mobile-only errors and whether important internal links work without inaccessible interactions.
Google’s current Core Web Vitals good thresholds are LCP of 2.5 seconds or less, INP under 200 milliseconds, and CLS under 0.1, covering loading, responsiveness, and visual stability. See the current Core Web Vitals guidance.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11| Metric | Good threshold | Measures |
|---|---|---|
| LCP | ≤ 2.5 seconds | Loading performance |
| INP | < 200 milliseconds | Responsiveness |
| CLS | < 0.1 | Visual stability |
Use field data from Search Console or CrUX where available to understand real users, and lab diagnostics from PageSpeed Insights, Lighthouse, or browser DevTools to investigate causes. Field results vary by device, location, and connection; lab results are not a substitute for field data. Test the homepage, high-traffic and high-revenue pages, representative templates, and pages with the largest field-data problems. Segment by device and geography and investigate scripts, ads, consent tools, and personalization. A passing score does not make content useful; prioritize failures by user and business impact.
Review on-page optimization
Titles, descriptions, and headings
- Titles should accurately describe the page, reflect intent, be distinct on priority pages, and match visible content. Avoid repetitive keyword strings.
- Meta descriptions should explain the page’s value and fit likely intent. Write distinct descriptions for priority pages to support qualified clicks; they are not a guaranteed ranking factor and do not need to satisfy a universal character limit.
- Use a clear page topic and logical heading hierarchy. Headings should describe actual sections; an H1 is not a substitute for a title tag.
URLs, images, and content presentation
Keep URLs stable, readable, and consistent; do not change them solely to insert a keyword. Use useful alt text for informative images and empty alt text for decorative ones. Where practical, use descriptive filenames, appropriate dimensions, compatible modern formats, and careful lazy loading so the primary content is not delayed or hidden. Ensure key facts such as authorship, dates, prices, and availability are accurate, and that the main content is accessible without unnecessary interaction or obstruction.
Assess content quality and search intent
For each priority URL, record its topic, primary intent, query group, organic clicks and impressions, conversions or revenue, business importance, indexability, competing pages, and intended action. Review pages with declining clicks, high impressions but weak click-through, rankings near page one, high traffic but low conversion, stale terminology, overlapping topics, or no clear business role. Check whether the page answers the query usefully and has appropriate evidence or sourcing for its subject.
Rank #4
Choose an action based on purpose and evidence:
- Keep and improve: The page serves a distinct need but has gaps, stale information, or presentation issues.
- Consolidate: Similar pages compete for the same intent and can be combined without losing useful distinct coverage.
- Rewrite for another intent: The URL has a legitimate role, but its content targets the wrong audience or query.
- Redirect: A removed or consolidated page has a close, useful successor.
- Noindex or remove: The page should not appear in search and has no suitable replacement; select the technical treatment deliberately.
- Add internal links or leave unchanged: The page is useful but under-discovered, or the evidence does not justify editing it.
Do not equate low traffic with low quality: a narrow page may support valuable conversions or assist another page. High traffic is not automatically success if it attracts the wrong audience. Before pruning, check seasonality, query diversity, conversions, backlinks, internal links, assisted value, and business importance; removal can destroy useful reach, links, or supporting content.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Audit internal links and site architecture
Check that important pages are reachable through meaningful category hubs and navigation, with no valuable orphan URLs. Review crawl depth, internal inlink counts, breadcrumbs, pagination, and whether links systematically point to redirects or outdated URLs. Use natural descriptive anchor text; do not hide important links behind scripts or inaccessible interactions. Ensure category, product, service, and editorial pages support one another, and that no key page depends on a single link.
Compare internal link support with business importance. Look for important pages buried several meaningful clicks deep, pages with strong external authority but weak internal links, and pages with many outlinks but little topical purpose. Treat a page flagged as orphaned in context: some URLs are deliberately excluded from navigation and search.
Validate structured data
Markup should accurately describe visible page content, use an appropriate type, and keep required and recommended properties—such as prices, ratings, availability, dates, and authors—current. Check valid JSON-LD, conflicting blocks, and whether production templates preserve the markup. Use the Rich Results Test for Google rich-result eligibility, the Schema.org validator for broader schema validation, and Search Console enhancement reports after deployment.
Google’s structured data guidance explains how markup relates to Search. Valid markup can make a page eligible for an enhanced appearance; it does not guarantee that Google will show one or act as a shortcut to rankings.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Add specialist checks when the site needs them
Ecommerce and faceted navigation
Review product availability, variants, category and product canonicals, filter and sort parameters, internal search, product markup, review accuracy, price and availability consistency, breadcrumbs, pagination or load-more discovery, and out-of-stock or discontinued-product handling. Compare product feeds with on-page facts where a feed is used.
Decide for each parameter whether it should be crawlable and indexable, crawlable but non-indexable, canonicalized, blocked cautiously, replaced with a clean landing page, or available only to users. Do not block all parameters indiscriminately: some combinations may serve valuable intent, while others create low-value URL explosions.
Local SEO
For local businesses, check Google Business Profile ownership and completeness, name/address/phone consistency, categories, service areas, useful location pages, opening and holiday hours, reviews and responses, local structured data, contact details, map behavior, relevant citations, and duplicate or suspended listings. Avoid thin city pages that only substitute a place name.
International SEO
Check reciprocal hreflang annotations and self-references where appropriate, valid language and region codes, absolute indexable URLs, matching content, and consistency with canonicals and sitemaps. Verify that localized pages actually differ in ways users need—currency, availability, shipping, contact details, or legal information. Avoid forced geolocation redirects that prevent access to alternatives and regional pages differing only by currency symbol.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Common errors include using en-uk when en-GB is intended, omitting a reciprocal alternate, or pointing a regional page’s canonical to another language.
Large sites, publishing, and migrations
For large or complex sites, use server logs to examine bot request distribution, crawl frequency by template, parameter volume, response times, server errors, sitemap freshness, and URLs exposed by infinite calendars, internal search, or session IDs. Crawl budget is not a default concern for a small site; diagnose waste before treating it as a problem.
After a migration, verify redirects from old URLs to their closest relevant destinations, canonical and internal-link updates, sitemap changes, and production indexability. For publishing sites, assess archive, author, tag, and date pages in relation to their distinct user and search value rather than assuming that every archive belongs in the index.
Review backlinks and authority carefully
Review referring domains, gains and losses, links to important pages, links to redirected or deleted URLs, relevant editorial links, brand mentions, competitor gaps, and anchor text in context. Investigate patterns and placement before drawing conclusions. Third-party “toxic” scores are proprietary metrics, not proof that Google considers a link harmful. Do not recommend removals or disavowal as routine cleanup; reserve disavowal for a credible, substantial link-manipulation problem or clear manual-action context, and consult Google’s current documentation before acting.
Audit analytics and SEO measurement
Confirm the analytics property and data stream, consent and cookie behavior, cross-domain tracking, internal traffic filters, referral exclusions, organic channel grouping, form and transaction events, revenue attribution, phone-call tracking, lead quality, and Search Console integration. Check landing-page reporting, bot or spam traffic, and continuity across migrations. Reconcile Search Console, analytics, CRM, and sales data rather than assuming their totals should match exactly.
- Visibility: impressions, rankings, clicks, and appropriate indexed pages.
- Engagement: organic sessions and engagement measures.
- Business outcomes: qualified leads, transactions, revenue, and margin.
- Quality: conversion rate, assisted conversions, and customer value.
- Technical health: crawl and indexation issues, errors, Core Web Vitals, and crawl efficiency where relevant.
When investigating a decline, first rule out tracking or data changes, then examine seasonality, demand, brand versus non-brand, device and country, directories and templates, rankings and click-through, indexation, deployments, and relevant security or manual-action notices. Consider competitor and search-results changes alongside content and intent. A drop in traffic alone does not establish a technical SEO cause.
Prioritize findings instead of exporting a to-do list
Act on a warning only when the page or template matters, the issue is verified, it affects crawling, indexability, relevance, usability, or business outcomes, and the proposed fix is not likely to create a larger problem. Rate scope and evidence as well as apparent severity. A useful model is:
Priority score = business impact × affected-page importance × confidence ÷ implementation effortUse a consistent rating for impact, scale (URL, template, directory, or site-wide), evidence source, confidence (confirmed, likely, or hypothesis), effort, owner, dependency, and validation method. Example entries:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →| Finding | Evidence | Scope | Impact | Effort | Owner | Validation |
|---|---|---|---|---|---|---|
Production template adds noindex |
HTML and URL Inspection | 18,000 URLs | Critical | Low | Developer | Re-crawl and inspect sample URLs |
| Sitemap contains redirected URLs | Crawl and sitemap comparison | 4,200 URLs | High | Low | SEO/developer | Recheck sitemap report and crawl |
| Important service pages are orphaned | Crawl graph | 35 URLs | High | Medium | Content/SEO | Add useful links and recrawl |
| INP is poor on checkout template | Field data and lab test | Checkout pages | Medium/high | High | Engineering | Monitor field data and Search Console trend |
| Duplicate articles compete for similar queries | Query and content review | 12 URLs | Medium | Medium | Content | Consolidate deliberately and monitor performance |
Do not prioritize every missing description, low word count, multiple H1, redirect, orphan warning, or backlink score equally. A concise contact page may be appropriate; accessible markup may validly contain several H1 elements; a controlled redirect may be correct; and a deliberately excluded URL may not need links.
Build a 30-, 60-, and 90-day plan
Turn the findings into owned work rather than an unfiltered export. Sequence by confidence, risk, dependencies, and implementation capacity; the time windows below are planning buckets, not promises of ranking recovery.
Days 1–30: contain verified high-risk problems
- Fix site-wide or template-level indexing blocks, broken preferred-domain behavior, severe server errors, and migration redirect failures.
- Correct sitemap entries, tracking defects that invalidate the baseline, and high-value broken internal links.
- Assign each item an owner, dependency, acceptance check, and deployment date.
Days 31–60: improve important page groups
- Resolve priority canonical and rendering problems, add useful internal links to important pages, and improve high-value content with clear intent gaps.
- Address mobile or performance issues that affect valuable templates and users.
- Re-crawl changed templates and review representative URLs in Search Console.
Days 61–90: consolidate and operationalize
- Complete lower-risk content consolidation and specialist improvements, such as faceted-navigation or international annotations.
- Review visibility, engagement, and business outcomes against the baseline, accounting for seasonality and other changes.
- Document unresolved hypotheses and schedule the next sampled or full audit according to site risk and change rate.
Validate fixes and monitor changes
After deployment, crawl affected URLs and templates again, inspect representative live URLs, confirm response headers and rendered content, and check sitemap and Search Console reports. Compare before-and-after data over a suitable period, annotate deployments and content changes, and distinguish changes in visibility from changes in clicks, sessions, and conversions. A fix is not validated merely because a crawler warning disappeared.
Quick Recap
Printable SEO audit checklist
Business and measurement
- Scope, audience, market, conversion events, and priority templates are documented.
- Baseline covers visibility, traffic, outcomes, and important historical changes.
- Analytics, consent, attribution, and lead or revenue tracking are checked.
Crawlability and indexability
- Preferred host and HTTPS behavior are consistent.
- Robots.txt does not block important pages or rendering resources.
- Sitemaps contain preferred, canonical, indexable 200 URLs.
- Priority URLs have appropriate status, directives, canonicals, and internal links.
- Search Console exclusions are compared with intended indexation.
Technical delivery and performance
- Status codes, redirects, soft 404s, and server errors are reviewed by scope and impact.
- JavaScript pages expose useful content, links, metadata, and structured data after rendering.
- Mobile layouts, forms, navigation, field data, and lab diagnostics are checked on representative pages.
On-page, content, and architecture
- Priority titles, descriptions, headings, images, and visible page content fit the page’s intent.
- Pages are assessed for usefulness, overlap, business role, and query performance.
- Important pages are linked from relevant hubs; orphan pages and redirecting internal links are reviewed.
Specialist signals and action plan
- Structured data is accurate and tested; local, international, ecommerce, or large-site checks are applied when relevant.
- Backlink patterns are reviewed in context without acting on a third-party toxicity score alone.
- Every finding has evidence, impact, scope, confidence, effort, owner, dependency, and validation.
- Changes are re-crawled, monitored, annotated, and scheduled for follow-up.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
