You can write the best article in your industry and still get no traffic. The reason is often simple. Search engines may not be able to find the page, read it or trust the site it sits on.

That is what a technical SEO audit checks. It looks at the foundation of your website, so every page you publish has a fair chance to rank.

This technical SEO audit checklist has 25 checks in five groups. It works for a small business site and for a large online store. Work from top to bottom. Problems at the top, like blocked pages, matter more than the polish at the bottom.

“Most sites we audit do not have one big problem. They have fifty small ones that nobody ever wrote down.” Highviso SEO team

What a technical SEO audit really checks

A technical SEO audit answers three questions:

• Can search engines reach your pages? This is crawling.
• Are the right pages in the search index? This is indexing.
• Is the site fast, safe and easy to use? This is the experience.
  
  

Content and backlinks matter too, but they only work well on a healthy base. If you want to see how audits fit into a full growth plan, take a look at our SEO services.

Group 1: Crawling and indexing (checks 1 to 5)

• Check 1: robots.txt. Open yoursite.com/robots.txt. Make sure it does not block important pages, images or files your pages need to load.
• Check 2: XML sitemap. It should list only live pages that return a 200 status, can be indexed and point to themselves as the canonical. Submit it in Google Search Console.
• Check 3: Noindex tags. Look for noindex on pages that should rank. A noindex tag left over from a test site is one of the most common and costly mistakes.
• Check 4: Status codes. Every important page should return 200. Pages that return 404, 500 or long redirects need attention.
• Check 5: Index coverage. Compare the pages in your sitemap with the pages Google has indexed. A big gap tells you where to look next.

Group 2: Site structure and links (checks 6 to 10)

• Check 6: Broken internal links. Links that lead to 404 pages waste your visitors’ time and your crawl budget. Fix them or remove them.
• Check 7: Redirect chains and loops. A chain sends a visitor from page A to B to C. Point A straight to C. Loops never end, so fix them at once.
• Check 8: Orphan pages. These are pages with no internal links pointing to them. Visitors and search engines struggle to find them.
• Check 9: Click depth. As a rule of thumb, keep your key pages within three clicks of the homepage.
• Check 10: Anchor text. Use clear words like “technical SEO checklist”, not “click here”, so people and search engines know what the next page is about.

Group 3: Speed and mobile (checks 11 to 15)

• Check 11: Core Web Vitals. Test your main pages in PageSpeed Insights and the Core Web Vitals report in Search Console. They measure loading (LCP), responsiveness (INP) and layout shifts (CLS).
• Check 12: Images. Compress large images and use modern formats like WebP. Images are often the biggest part of a slow page.
• Check 13: Mobile layout. Check that text is easy to read, buttons are easy to tap and nothing scrolls sideways on a phone.
• Check 14: Scripts and plugins. Remove tools you no longer use. Every extra script can slow the page down.
• Check 15: Server response and caching. Slow hosting makes every other fix harder. If pages still feel slow after you compress images, the cause may be your theme or hosting. A website development team can usually find it faster than trial and error.

Group 4: On-page technical basics (checks 16 to 20)

• Check 16: Page titles. Every page needs a unique title that fits in search results, usually under about 60 characters.
• Check 17: Meta descriptions. Write a unique summary of about 150 characters for each key page. It does not change rankings directly, but it can help more people click.
• Check 18: Headings. Use one H1 per page and a logical order of H2 and H3 headings.
• Check 19: Canonical tags. Each page should name its preferred URL. Wrong canonicals can quietly remove good pages from search results.
• Check 20: Image ALT text. Describe each meaningful image in plain words. It helps people who use screen readers and gives search engines more context.

Group 5: Security, structured data and clean URLs (checks 21 to 25)

• Check 21: HTTPS everywhere. Your site should load on one secure version only. Look for mixed content, where a secure page loads insecure files.
• Check 22: Structured data. Add schema markup that matches what is visible on the page, then test it for errors.
• Check 23: Hreflang. If you serve more than one country or language, check that every language version points back to the others.
• Check 24: Clean URLs. Prefer short, readable URLs. Avoid long strings of parameters that create many versions of the same page.
• Check 25: A helpful 404 page. A good 404 page offers a search box and useful links. Also make sure deleted pages return a real 404 status. A page that looks like an error but returns a normal 200 status is called a soft 404, and it confuses search engines.

What to fix first

Do not try to fix all 25 at once. Use this order:

1. Anything that blocks search engines: robots.txt, noindex tags and server errors.
2. Broken pages and redirect problems on your most important pages.
3. Duplicate pages and canonical mistakes.
4. Speed problems on pages that bring leads or sales.
5. Titles, headings, ALT text and other polish.

A small fix on a page that earns money beats a perfect fix on a page nobody visits.

How to run this checklist without a messy spreadsheet

You can check many of these items by hand, but it gets slow after about twenty pages. A crawler does the walking for you. It visits every page, the way a search engine does, and lists what it finds.

We built Sarvexa for this job. It is a desktop SEO crawler that runs on your own computer. In one crawl it shows status codes, redirect chains, indexability, orphan pages, missing titles and ALT text, and schema or hreflang errors.

It can also turn each issue into a task with a priority and an owner. After your developer makes the fix, you re-crawl only those URLs to confirm it worked. Your crawl data stays on your computer, and there is a free trial if you want to test it on your own site.

Use whatever tool you like. The method matters more than the brand: crawl, list, fix in order, then check again.

Technical SEO audit FAQs

What is included in a technical SEO audit?

A technical SEO audit checks crawling, indexing, site structure, redirects, speed, mobile use, on-page technical elements, security and structured data. It ends with a list of fixes ranked by importance.

How long does a technical SEO audit take?

With a crawler, a small site can be checked in a few hours. Large sites take longer. Fixing the problems usually takes more time than finding them.

How often should I run a technical SEO audit?

Most sites should run a full audit every quarter. Large or fast changing sites may need one every month. Always run one after a redesign, a move to a new domain or a platform change.

Can I do a technical SEO audit myself?

Yes, you can handle the basics yourself with Google Search Console, PageSpeed Insights and a crawler. Server settings, page speed and JavaScript problems often need a developer.

What is the best tool for a technical SEO audit?

There is no single best tool. Most people combine Google Search Console, PageSpeed Insights and a site crawler such as Sarvexa. Together they show what Google sees and what your visitors feel.