Short answer: an SEO audit is a check of your website through a search engine's eyes. First, you confirm your pages are indexed. Then you review the technical layer: robots.txt, sitemap, redirects, HTTPS, speed and mobile rendering. Next come page elements: titles, H1s, duplicates and language versions. Finally, content plus internal and external links. Every finding is scored for impact and effort and goes into one list. That turns "fix everything" into a workable plan.
For a company entering Uzbekistan, the audit has two local twists: Yandex matters alongside Google, and the site almost always runs in Uzbek and Russian. The broader strategy, keyword research and realistic timelines are covered in the complete guide to SEO in Uzbekistan. This article focuses only on the audit process and the checklist.
Preparing for the audit: what you need
- Access. Google Search Console and Yandex Webmaster, both verified for the local domain or folder. If they are missing, set them up today: the reports take a few days to fill with data.
- Analytics. GA4 or Yandex Metrica, so you can see which pages generate leads.
- A list of key pages. Home page, service and category pages, contacts. Usually 10–30 URLs per language.
- A spreadsheet. For every finding: issue, URL, impact, effort, owner, deadline.
For a larger site you will need a crawler, such as the desktop tool Screaming Frog SEO Spider or an online service. It walks the site like a search bot and lists the status code, title, H1 and canonical for every URL.
Step 1: indexing
The first question is simple: can the search engines see your site?
Also read 300 Sign-Ups, 40 Attendees: Where Webinar Leads Get Lost in UzbekistanIn Google Search Console, open the Page indexing report. It shows which pages are indexed and why the rest are not. Compare the indexed count with the real number of pages on the site.
The URL Inspection tool shows, for a single page, the canonical you declared next to the one Google selected. If they differ, Google treats another page as the main one. Requesting indexing here does not guarantee it, as Google itself notes.
In Yandex Webmaster, open Site diagnostics. Issues are grouped into four levels: fatal, critical, possible problems and recommendations. Start with fatal and critical. Then check the excluded pages under Pages in search, where each URL is listed with a reason.
Typical findings: a key service page missing from the index, filter or staging URLs cluttering it, or sharply different page counts in Google and Yandex.

Step 2: technical health
robots.txt. Google warns that robots.txt is not a mechanism for keeping a page out of search: a blocked page can still be indexed if other sites link to it. To keep a page out, use noindex. Check that no leftover Disallow: / from development remains and that CSS and JS files are not blocked. The robots.txt analysis tool in Yandex Webmaster shows immediately which URLs are blocked.
Sitemap.xml. List only open, canonical pages that return 200. Redirected, blocked or 404 URLs do not belong there. Submit the file in both consoles and review the errors.
HTTPS and the main host. The site should resolve to one address. The http and https, www and non-www variants all 301-redirect to the main version. The server response check in Yandex Webmaster shows the status code for any URL.
404s and redirects. From the crawler export, pull out three things:
- 404 pages that internal links still point to;
- redirect chains with several hops;
- places where a 302 is used for a permanent move instead of a 301.
Replace each chain with a single direct 301, and update the internal link to the final URL.
Speed and Core Web Vitals. Google defines "good" thresholds for three metrics:
- LCP (Largest Contentful Paint) — 2.5 seconds or less;
- INP (Interaction to Next Paint) — 200 milliseconds or less;
- CLS (Cumulative Layout Shift) — 0.1 or less.
They are measured at the 75th percentile of page visits, separately for mobile and desktop. The Core Web Vitals report in Search Console groups pages, while PageSpeed Insights tests a single URL.
Mobile. Google indexes sites mainly by their mobile version. Open your key pages on a real phone. Is the text readable? Are buttons easy to tap? Does the form work? Is any text or block from desktop hidden on mobile?
Step 3: page elements
Title. Every page needs its own title. Google sets no official character limit, but long titles are truncated in results to fit the screen width, so put the main term first. Duplicate and boilerplate titles are the first fix. If a title is empty or vague, Google may build its own title link from the H1 or other page text.
Meta description. A short, accurate, unique summary for each important page. Google sometimes uses page text instead.
H1. One clear main heading per page. It should match the title in meaning, not necessarily word for word.
Duplicates. The same content often opens at several addresses: filter parameters, UTM tags, print versions, with and without a trailing slash. According to Google's documentation, 301 redirects and rel="canonical" are strong signals, and sitemap inclusion is a weak one. Do not use robots.txt or noindex for canonicalization: noindex removes the page from search entirely. Yandex Webmaster also flags duplicate pages separately.
Multilingual site: hreflang (uz/ru). This is where Uzbekistan sites break most often. Check that:
- each language version has its own URL (
/uz/...,/ru/...); - each page lists itself and all its language alternates;
- links are reciprocal: if the uz page points to ru, the ru page points back, otherwise Google ignores the annotations;
- URLs are fully qualified, including
https://; - language codes follow ISO 639-1:
uz,ru,en; x-defaultis added if there is a language selector or an automatic redirect.
One detail is easy to miss: Yandex no longer supports language versions in sitemaps and recommends link rel="alternate" elements in the page <head>. If your global setup declares hreflang only in the sitemap, add it to the pages for Yandex.
Step 4: content and internal links
Thin content holds back even a technically clean site. Look for four things.
- Thin pages. A service page with two or three lines and no price range, examples or answers. The structure of a high-converting landing page is a good model for filling it out.
- Cannibalization. Two pages compete for one query. A sign is two URLs alternating for the same query in the Search Console Performance report.
- Orphan pages. Listed in the sitemap but not linked from anywhere on the site.
- Depth. If an important page is more than 3–4 clicks from the home page, revisit the menu and internal links.
Use plain <a href> links with descriptive anchors. How to link from blog articles to service pages is covered in detail in the article on a company blog and SEO articles.

Step 5: external links
The Links report in Search Console and the external links section in Yandex Webmaster show who links to you. Answer three questions:
- which pages attract most links, and do those pages still work;
- if a link points to a removed page, is there a 301 in place;
- is there a mass of links from dubious sites with identical anchors.
Buying links violates Google's spam policies. Cleaning up such links and stopping any purchases is a key audit takeaway. Also check the Manual actions section in Search Console for penalties.
The 25-point SEO audit checklist
Indexing
- ☐ 1. Search Console and Yandex Webmaster are connected and verified.
- ☐ 2. The indexed page count is close to the real page count.
- ☐ 3. All key commercial pages are indexed.
- ☐ 4. No technical, staging or filter pages are in the index.
- ☐ 5. Yandex Site diagnostics shows no fatal or critical issues.
Technical
- ☐ 6. robots.txt does not block needed pages, CSS or JS.
- ☐ 7. Pages that should stay out of search carry
noindex. - ☐ 8. The sitemap lists only canonical 200 pages and is submitted in both consoles.
- ☐ 9. The site resolves to one main address, all other variants 301 to it.
- ☐ 10. HTTPS works on every page.
- ☐ 11. No internal links point to 404 pages.
- ☐ 12. No redirect chains; permanent moves use 301.
- ☐ 13. Core Web Vitals for key pages are in the "good" range.
- ☐ 14. Key pages work fully and comfortably on a phone.
Page elements
- ☐ 15. Every page has a unique title.
- ☐ 16. Important pages have their own meta description.
- ☐ 17. Every page has one clear H1.
- ☐ 18. Duplicates are consolidated with canonical or 301.
- ☐ 19. The Google-selected canonical matches the one you declared.
- ☐ 20. uz and ru versions are linked with reciprocal hreflang, including in the
<head>.
Content and links
- ☐ 21. Every main service or category has its own complete page.
- ☐ 22. No two pages compete for the same query.
- ☐ 23. No orphan pages; key pages are within 3 clicks.
- ☐ 24. Old pages with backlinks 301 to their replacements.
- ☐ 25. No manual actions and no purchased links.
Turning findings into a priority matrix
An audit can produce dozens of findings. You do not need to fix them all at once. Give each finding two scores:
- Impact (1–3): how much fixing it will affect indexing, traffic or leads.
- Effort (1–3): how much time it takes and whose work it needs.
Then sort them into four groups:
- Now — Impact: High; Effort: Low; What to do: This week; Typical examples:
Disallow: /in robots.txt,noindexon a key page, no http-to-https redirect - Plan — Impact: High; Effort: High; What to do: Monthly roadmap, with developers; Typical examples: rebuilding hreflang, speed work, consolidating filter duplicates
- Quick wins on the side — Impact: Low; Effort: Low; What to do: When there is spare time; Typical examples: duplicate meta descriptions, one or two internal 404s
- Park — Impact: Low; Effort: High; What to do: Set aside for now; Typical examples: a full redesign just to fix a minor CLS issue
Give every item an owner and a deadline. After the fixes, measure results in leads from search, not rankings. That requires correct source tagging, which is explained in the article on identifying lead sources with UTM tags and GA4.
Making the audit a process, not a one-off
A one-time audit goes stale within months as pages, code and language versions change. A simple rhythm helps:
- weekly: Search Console and Yandex Webmaster notifications;
- monthly: indexed page count, Core Web Vitals, new 404s;
- quarterly: all 25 checklist points;
- before every major release: robots.txt, canonicals and hreflang checked on staging.
Automatically routing notifications to an owner and compiling a monthly report cuts manual work. Where to start with such automations is covered in the article on business process automation.
Summary
An SEO audit has five steps: indexing, technical health, page elements, content and links. At each step, findings go into one sheet and are scored for impact and effort. Quick high-impact fixes come first.
Three things you can do today:
- Open Page indexing in Search Console and Site diagnostics in Yandex Webmaster.
- Type the four address variants of your site into a browser.
- Open your three most important pages on a phone and check the title and H1.
Frequently asked questions
Can our marketing team run the audit without a developer?
Most of it, yes. Reading Search Console and Yandex Webmaster reports, checking titles and H1s and testing pages on a phone needs no coding. A developer is needed mainly to fix what you find: redirects, canonicals, hreflang and speed.
How often should we audit the Uzbekistan site?
A full audit once or twice a year is common practice, plus after every major change such as a redesign, a CMS switch, a domain move or a new URL structure. Checking Search Console and Yandex Webmaster notifications weekly is usually enough in between.
Our site has 404 pages. Is that hurting SEO?
A deleted page returning 404 is not an error in itself. The problem is internal links pointing to 404 pages, or an important page with external backlinks that has disappeared. In that case, add a 301 redirect to the closest matching new page.
Is Yandex Webmaster really necessary if we already use Search Console?
If a meaningful part of your audience searches in Russian, yes. Yandex indexes sites on its own terms, reports its own errors and handles some things differently, for example it no longer reads language versions from sitemaps. Setting it up takes little time and closes a blind spot.
Want a second pair of eyes on your audit results?
We can go through what your checklist uncovered on the Uzbek-market site and help you decide calmly what to fix first. Free consultation, no obligation.