How to perform an SEO audit for your website
An SEO audit helps a webmaster find the pages, templates, and search signals that are quietly limiting discovery, clicks, and conversions before the problem turns into a larger traffic drop. A useful audit does not chase every warning on the site; it shows which issues are blocking important pages from being crawled, indexed, understood, or chosen in search results.
The practical workflow starts with Google Search Console because it shows how Google is indexing the site's canonical URLs, what search queries already produce impressions, and whether discovery or serving problems are affecting the domain. From there, the audit moves to live page review and PageSpeed Insights so title links, snippets, internal links, canonical signals, and page-experience problems can be checked against what visitors actually load.
Keep the scope tied to the pages that support the site's real goals, such as the homepage, category hubs, service pages, product collections, and lead or checkout flows. Search Console data is delayed rather than live, and the Crawl stats report is mainly useful for larger or recently unstable sites, so a small-site audit should still prioritize indexability, internal links, snippet quality, and template-level performance.
Steps to perform an SEO audit for your website:
- List the site's priority pages and page types before opening reports so the audit stays tied to URLs that matter to the business instead of every low-value archive, tag, filter, or utility page on the domain.
Home page Primary category or service pages Top landing pages Contact or lead form Checkout or booking flow
Use one representative URL for each important template so the audit can separate a single bad page from a site-wide pattern.
- Open Search results in Google Search Console, compare the last three months against the previous period, and look for important pages or queries where impressions are present but clicks, CTR, or average position have dropped unexpectedly.
Switch on Total clicks, Total impressions, Average CTR, and Average position, then use the Pages, Queries, and Devices tabs to isolate where the loss is happening.
- Open Page indexing and use the Why pages aren't indexed table to focus on important canonical pages that are missing from the index instead of treating 100 percent URL coverage as the goal.
Intentional duplicates, redirects, login-only paths, parameter URLs, and other non-canonical pages do not need to be indexed if Google has the correct canonical page.
- Inspect representative priority URLs with URL Inspection and use Test live URL when the indexed state does not match the current page so the audit can confirm crawl access, chosen canonical, last crawl, and rendered resource availability for the exact page that matters.
Request indexing is for a meaningful page change or fix on a specific URL, not a substitute for sitemap submission or broad discovery.
- Open Sitemaps and confirm the live sitemap URL is submitted, readable, and processing successfully before you treat missing discovery as a page-level content problem.
https://www.example.com/sitemap.xml
- If the site is large, recently redesigned, or showing serving problems, open Settings → Crawl stats and review host status, response types, average response time, and crawl-purpose changes before blaming indexing gaps on content alone.
Crawl stats is aimed at advanced users, and Google notes that sites with fewer than a thousand pages usually do not need this level of crawl detail for routine audits.
- Review the live page, the page HTML, and the search snippet signals for URLs with high impressions but weak clicks, and look for duplicated or unclear title links, weak meta descriptions, conflicting canonicals, or content that no longer matches the search intent it is attracting.
Google can generate title links and snippets from multiple page signals, so a rewritten search snippet usually points to weak titles, weak descriptions, or on-page copy that does not clearly support the query.
- Review how a visitor reaches each priority page from the homepage, navigation, category hubs, breadcrumbs, and supporting articles so weakly linked, orphaned, redirected, or broken paths do not leave important pages technically available but practically buried.
- Run the homepage and each important page template through PageSpeed Insights, compare Mobile and Desktop, and separate recurring field-data problems from one-off lab-test findings before assigning a performance fix.
Field data reflects real-user Chrome User Experience Report (CrUX) measurements from the previous 28 days, while the lower Lighthouse section is the debugging view for the current test run, and PageSpeed Insights can fall back to origin-level field data when a specific URL does not have enough samples.
Related: How to check website performance online
Related: How to speed up page load time - Rank the findings by business impact and recheck the affected URLs after each fix until the pages that matter most are crawlable, indexed, clearly linked, and free from the specific issue that triggered the audit.
High Important page not indexed or wrong canonical High Broken internal path to lead or product page Medium Weak title or snippet on high-impression page Medium Slow mobile template affecting many URLs
An audit is only useful when it ends with a prioritized repair list and a rerun of the affected URLs, not a long report of warnings with no owner or follow-up check.