Technical SEO Audit: 20-Point Checklist Before You Start
A technical SEO audit checks whether Google and Yandex can find, read and index your pages. Without it, content and links often work in a vacuum: a search engine does not rank what it cannot process. Below are twenty points to check before you edit a single line of copy.
Technical SEO audit: what to prepare first
You need access to Google Search Console, Yandex Webmaster, analytics and the CMS admin. Verify the whole domain, not a single version of the address. For tools, a crawler such as Screaming Frog (the free version crawls up to 500 URLs), PageSpeed Insights and the Rich Results Test are enough.
Record a baseline right away: screenshots of Search Console reports, a crawl export and PageSpeed numbers. Without a starting point, three months later you cannot prove the audit changed anything.
Indexing and accessibility: points 1-5
1. Open robots.txt and look for a stray Disallow: / left over from development, a common reason a new site stays out of the index for months. Also check for a noindex meta tag in templates. 2. Keep only live pages with a 200 status in sitemap.xml and remove URLs that return 404 or redirect. 3. In Search Console, work through each reason in the Page Indexing report, such as Crawled - currently not indexed, instead of looking only at the total.
4. Check the canonical on every template type — homepage, category, product, article: it should point to the page itself or to a deliberately chosen version. 5. Configure HTTPS without mixed content: browsers block http images and scripts on an https page. Watch the certificate expiry date too.
Duplicates, structure and internal links: points 6-10
6. The site should open at one address: http to https and www to non-www through a 301 redirect, otherwise link equity splits between copies. 7. Export duplicate titles, descriptions and H1s from the crawler: identical headings on different pages usually point to a template problem.
8. Keep important pages within two or three clicks of the homepage — the deeper they sit, the less often they are crawled. 9. Find orphan pages by comparing the URLs in the sitemap with the list the crawler discovers through links. 10. Pagination and filters: next pages should be ordinary <a href> links with their own URLs, and filter parameters that multiply near-identical pages should be handled with canonical or noindex.
Speed, Core Web Vitals and mobile: points 11-15
11. Check LCP for mobile: good is up to 2.5 seconds, poor is above 4. Rely on real-user data, not only the lab test. 12. CLS: good is up to 0.1; shifts come from images without width and height and from late-loading banners. 13. INP replaced FID in March 2024, and good is up to 200 ms; heavy analytics scripts and chat widgets slow responses.
14. Images: JPEG and PNG instead of WebP or AVIF, and originals several thousand pixels wide, are a frequent cause of slow LCP in online stores. 15. Test mobile by hand: Google retired the separate Mobile Usability report, so check font size, spacing between buttons and parity with desktop content on a real phone and in Lighthouse. Test on a slow 4G profile, not only office Wi-Fi.
Structured data, hreflang and response codes: points 16-20
16. Check structured data in the Rich Results Test: Product and BreadcrumbList for a store, LocalBusiness for a company with an office, Article for a blog; markup must match the visible text. 17. For ru/uz/en, each language version links to itself and to the others, plus x-default; Google ignores one-way links.
18. Titles and descriptions should be unique across the site. 19. Use one H1 per page and a heading sequence that does not skip levels. 20. Provide a custom 404 page with navigation, use 410 or 301 for removed pages, and avoid soft 404s — pages that say not found but return 200. Also fix chains of several redirects in a row.
FAQ
How long does a technical SEO audit take? For a site of a few hundred pages, usually from a few days to two weeks including the report; longer for a large store. Fixes depend on the developer's queue.
How much does it cost? A market guide for Uzbekistan: roughly 1,500,000-8,000,000 UZS for a one-off audit, depending on page count and depth. This is only a guide; an exact price is given after looking at the site.
Can I run the audit myself? Yes, most points can be checked with free tools. Server logs, JavaScript rendering and migrations are better left to a specialist.
How often should the audit be repeated? Every six months and after major changes: a redesign, a CMS or domain change, or a new language.
What should be fixed first? Whatever blocks indexing: noindex, robots, canonical, and 5xx or 404 errors on important pages.
What to do with the audit results
Sort the findings into three groups: blocks indexing (noindex, robots, canonical, 5xx) — fix immediately; hinders crawling (duplicates, orphan pages, redirects); worsens user experience (speed, markup). Give every task an owner, a deadline and a way to verify it.
Indexing and duplicate issues are usually fixed within days, and the effect shows after a few weeks. Core Web Vitals need a developer, and field metrics are calculated over a rolling window of about a month, so compare against the baseline after 4-8 weeks, not the next day.
If you would rather hand the task to specialists, SEO promotion at 4 Digital starts from 3,600,000 UZS per month, and it makes sense to begin with a technical audit before moving to content.