A website SEO audit is a structured review of whether important pages can be found, indexed, understood, and used. This checklist helps you inspect the issues that matter before you spend time polishing small details. It cannot predict or guarantee rankings.
Start with a small scope: list your homepage, main product or service pages, and a few pages that should bring in search traffic. Fix confirmed blockers on those pages first, then expand the review.
1. Record a baseline before changing anything
Write down the pages you are auditing and the action each page should help a visitor complete. In Search Console, review the Performance report by query and page when data is available. Note impressions, clicks, and the queries that appear relevant. A newly connected property may need time to collect enough useful data; you can still check whether pages are technically accessible in the meantime.
Google's Performance report guide explains the metrics and page/query views.
2. Confirm the preferred URL and response
Open each page and confirm that it loads at the preferred HTTPS address, returns the expected status, and does not bounce through avoidable redirects. Choose one canonical URL for each page. Keep internal links and sitemap entries pointed at that version.
Check several pages together with the bulk URL checker, and trace specific hops with the redirect checker.
3. Check whether Google can crawl and index each page
Use URL Inspection in Search Console to inspect Google's known version and test the live URL. Review the page's robots directives, robots.txt access, and canonical. A page can return HTTP 200 and still be excluded from the index; discovery and indexing are not guaranteed just because a URL is in a sitemap.
Use the robots.txt tester to check crawler access. For duplicate or very similar URLs, read Google's canonicalization guidance before choosing a canonical or redirect.
4. Make sure the page answers one clear search need
Compare the page with the query and the visitor's likely goal. Does it answer the main question early? Is the next step clear? Add first-hand examples, original details, or practical instructions where they help. Do not expand a page just to reach a word count.
Google's people-first content guidance recommends useful, reliable pages made for readers rather than pages produced primarily to manipulate rankings.
5. Review the title, main heading, and snippet
Give each important page a distinct, descriptive title and a visible main heading that accurately describe its purpose. Put key context where a person can recognize it, but avoid repeating the same phrase unnaturally. Write a concise meta description that summarizes the page; Google may choose a different snippet for a particular query.
Use the SERP preview tool to review draft text. See Google's title-link guidance and snippet guidance.
6. Inspect the page structure and content
Check that headings describe the sections below them, paragraphs are readable, and important information is available as text rather than only inside an image. Add useful alternative text to informative images; leave decorative images with empty alt text. Remove stale details and unsupported claims.
7. Follow internal links to important pages
Can a visitor reach each important page from a relevant page using a normal link? Use clear anchor text that describes the destination. Look for orphaned pages, menus with dead ends, and links that point through unnecessary redirects.
8. Verify broken links before changing them
Check whether an automated error is a real error: some sites block automated checks, require a login, or respond differently to a browser. For confirmed internal errors, update the link or restore the intended page. For links to moved content, point directly to the correct destination.
The broken link checker checks links found on the page you enter; it does not crawl your whole site.
9. Check sitemap and robots.txt consistency
Keep your sitemap limited to preferred URLs you want search engines to discover. Review it after URL changes and make sure it does not list redirects or duplicate versions. Submit it in Search Console to see whether it was processed, while remembering that a sitemap is a discovery hint rather than an indexing guarantee.
Google's sitemap guide explains sitemap basics.
10. Validate structured data against visible page content
Only add markup that describes information people can see on the page. Check required fields and test the output with Google's rich result tools where applicable. Structured data can make a page eligible for supported search features, but it does not guarantee that Google will show one.
Draft JSON-LD with the schema markup generator, then review it before publishing.
11. Test the page on a phone and check field experience
Try the page on a phone: make sure the main content is readable, controls work, and visitors can complete the intended task. Use PageSpeed Insights for diagnostics and Search Console's Core Web Vitals report for field data when available. Treat a tool score as a clue to investigate, not a ranking prediction.
12. Review errors and security after major changes
After a migration or redesign, check key URLs, redirects, canonical tags, robots rules, and sitemap entries again. Review server errors and any Search Console security or manual-action reports. Fix the underlying problem rather than hiding an error page behind a successful status code.
13. Prioritize fixes by impact and confidence
Write down each issue, the URLs affected, evidence that confirms it, and the next action. Fix confirmed indexing blockers and broken user journeys before cosmetic improvements. If a finding is uncertain, test it on one page and verify the result before rolling the change across the site.
14. Measure the result and repeat
After publishing a meaningful change, record the date and page. Give search systems time to revisit it, then compare impressions, clicks, query mix, and user behavior over a reasonable period. Search Console data can vary, and changes do not prove that one edit caused a ranking movement.
SEO audit checklist summary
- Set a page-level goal and record the current state.
- Check response codes, redirects, crawl access, indexability, and canonicals.
- Improve the page's answer, title, heading, links, and visible content.
- Review sitemap, structured data, mobile usability, and real-world performance.
- Prioritize evidence-backed fixes and measure after Google has had time to recrawl.
Run the free SEO Wins audit on a key page to get a starting list of checks, then verify important findings manually and in Search Console.