Technical SEO Audit Checklist: 25 Checks for Your Website

Introduction

• Content can be excellent and the design beautiful, yet the site never appears because a technical barrier stops Google from reaching or understanding the pages.
• A technical audit comes first because it exposes the faults that waste every other effort: better writing cannot help a page that is not indexed.
• This is a practical list of twenty-five checks in seven groups, mostly using free tools (Google Search Console, your browser, PageSpeed Insights). You do not need programming skills to start.

Before you begin

• Get access to Google Search Console for your site. It is the most accurate source for what Google actually sees.
• Record findings in a simple table: check, result, priority, owner.
• Start with faults that block visibility (crawling and indexing) before cosmetic gains such as fine-tuned speed.

1) Crawlability

1. Open /robots.txt and confirm it does not block important pages or CSS/JS files.
2. Confirm a correct sitemap exists and is submitted in Search Console (see our sitemap and robots article).
3. Look for orphan pages: important pages that no internal link points to.
4. Check that menus and links are real links (<a href>), not buttons without URLs that crawlers struggle to follow.

2) Indexability

5. Review the page indexing report: what is indexed, what is excluded, and why.
6. Look for accidental noindex tags on important pages (common right after a staging site goes live).
7. Check the canonical tag: each URL should point to its preferred version, not mistakenly to another page.
8. Find duplicate content: www and non-www, http and https, and parameter URLs showing the same page.

3) Link structure and responses

9. Internal broken links (404): fix them or redirect to the closest replacement page.
10. Redirect chains: a redirect should reach the final URL in one step (301), not through a chain.
11. One stable URL per page, lowercase, with clear words and no strange symbols.
12. A useful 404 page that points back home or to search, and that genuinely returns a 404 status (not 200).

4) Security and compatibility

13. HTTPS on every page, with full redirection from http to https.
14. No mixed content (images or scripts loaded over http inside an https page).
15. A valid security certificate, set to renew before it expires.
16. Mobile test: the page renders correctly, text is readable without zooming, and buttons have enough space between them.

5) Speed and page experience

17. Run PageSpeed Insights on the home page and your key service page, and review LCP, INP and CLS.
18. Images: right dimensions, modern formats, and lazy loading below the fold.
19. Cut unnecessary third-party scripts (trackers, widgets, multiple font families).
20. Use caching and compression on the server, and ask your host if you are unsure.

6) Structured content and headings

21. A unique title and meta description on every page, and a single H1.
22. Appropriate Schema (Organization, LocalBusiness, Article, FAQ where relevant) that passes a rich results test without errors.

7) Languages and tracking

23. For bilingual sites: reciprocal hreflang tags between the two versions of each page.
24. Confirm GA4 and Search Console are linked and working, and that key events (calls, forms) are recorded.
25. Schedule recurring checks: a light one monthly, and a full one after any major update.

How to set priorities

What each speed metric means

These thresholds are the ones Google currently uses as a reference and may change, so check its official documentation.

Common mistakes

• Starting with speed before indexing. Optimising a page that is not indexed brings no result.
• Fixing symptoms, not causes. Many 404s usually come from a URL structure change made without redirects.
• Relying on one tool. Each tool sees one angle; compare Search Console with an independent crawler.
• Chasing a score of 100. What matters is the real visitor experience, not a perfect number.
• Auditing once. Sites change, and faults return with every update.
• Ignoring mobile. Most visits to local businesses come from phones.

How to read audit results without panic

• Do not fix everything. Many tool alerts are warnings, not real faults. Ask: does this finding stop an important page from appearing?
• Tie each finding to a valuable page. An error on an old page with no visits matters less than one on your main service page.
• Record the state before changing anything. Capture the indexing and speed reports so you can compare after the fix.
• Change one thing, then watch. If you change several things at once, you will not know the cause when performance moves.
• Involve your developer early. Some fixes (redirects, canonicals, performance) need server or template access.
• Wait before judging. Google needs days or weeks to recrawl pages and update reports after a fix.

What does Xposio do?

1. We start with Search Console data and an independent crawl of the site, so we see what Google sees rather than what we assume.
2. We classify every finding by impact (critical, high, medium, low) with evidence, so you do not receive a long list without priorities.
3. We fix what falls within our scope and document the changes. Anything that needs a decision from you is explained clearly.
4. We re-test after implementation to confirm the fix actually worked.
5. We stay honest: fixing technical issues removes obstacles but does not guarantee a particular ranking. Content, competition and trust still matter.

Internal link: Learn about the Technical SEO service at /en/services/technical-seo and the SEO & Search Visibility service at /en/services/seo-search-visibility.

You can order the Digital Snapshot report for your site at /en/report, and browse sample reports at /en/reports.

Conclusion

• A technical audit comes before content and ads because it finds what blocks visibility in the first place.
• Work in order: crawling and indexing first, then links and security, then speed, then details.
• Use Search Console as your first source and back it with other checking tools.
• Rank findings by impact instead of trying to fix everything at once.
• Repeat the audit after each update, because faults slip in with changes.
• Sound technical SEO is a foundation, not a ranking guarantee.

Related reading

• /en/blog/sitemap-robots-explained
• /en/blog/core-web-vitals-simple-guide
• /en/blog/google-search-console-guide