Redirects audit

A redirects audit is a one-time narrow check of the redirect system on your site: redirect chains and loops (when one URL leads to a second, that to a third — this slows things down and loses link equity), the correctness of the type (301 — permanent, passes equity and updates the index; 302 — temporary, wrong for permanent moves), where redirects lead (to a relevant page or all to the homepage or a 404 — a common error after a migration), consistency of http→https, www and non-www, trailing slashes, the correctness of the redirect map after a migration or structure change, soft 404s, and the speed and number of "hops". The goal is to put things in order so users and robots land where they should and page equity does not leak. Honestly about the main point: this is diagnosis, not setup and not a guarantee of restoring rankings or traffic. The audit shows what is wrong, but the effect appears after the fixes are implemented, and rankings depend on many factors; "we will bring back the traffic after a migration" cannot be promised — we remove technical losses, but that is only part of the picture. It is a snapshot in time. Access to the code, server or CMS or at least the ability to crawl the site is needed; without server access we use external crawlers (e.g. Screaming Frog, Ahrefs) — they have volume and completeness limits, some server-level data is closed, and the check goes by the available URLs and public data. What you get: a report (PDF or spreadsheet) with redirect problems by priority (chains, wrong types, lost pages) and a map of recommendations — what should lead where; implementing the fixes and a re-check are separate work, usually on the server or CMS side. If the site is small and there have been no migrations, we will honestly say a separate redirects audit is excessive. Picture this: instead of "redirects seem to be there" you learn that after a migration 200 old URLs lead in one chain through three hops to the homepage instead of relevant pages, and some return a 302 instead of a 301. The base price starts from 7,000 ₽; it depends on the site size and the number of redirects.

• There was a migration or structure change and part of the traffic dropped.
• You suspect redirect chains or errors after a migration.
• Old links lead to the wrong place or to a 404.
• You moved to https but are not sure everything redirects correctly.

• Redirect chains and loops, unnecessary "hops"
• Correctness of types: 301 (permanent) versus 302 (temporary)
• Relevance: where redirects lead (to the right page or to the homepage/404)
• Consistency of http→https, www and non-www, trailing slashes
• The redirect map after a migration or structure change
• Soft 404s and broken redirects
• Redirect speed and the number of hops
• A prioritized report with problems and a map of recommendations

• Clear understanding of which redirects are set up incorrectly
• A prioritized list of problems (chains, types, lost URLs)
• A map of "what should lead where" (implementation is separate)
• Understanding where it is a technical equity loss and where other factors

• We clarify the migration history and structure and collect access (server/CMS — where possible)
• We crawl the site and check redirects, types, chains and target pages
• We prepare a report with problems and a map of recommendations and review it with you

• Will traffic come back after the audit following a migration?

  The audit itself does not bring it back. It finds technical redirect problems and gives a fix map; the effect comes after implementation. But traffic and rankings depend on many factors, so "we will restore it to how it was" cannot be promised — we remove technical losses, not guarantee the result.

• What is the difference between 301 and 302 and why does it matter?

  301 is a permanent redirect: it tells the search engine the page has moved for good, passes equity and updates the index. 302 is temporary: it is not suitable for permanent moves, and equity may not be passed properly. Mixed-up types are a common and costly error — that is exactly what we check.

• I have had no migrations — do I need a redirects audit?

  Probably not. If the structure has not changed and there are few redirects, a basic check within a technical SEO audit is enough. A separate audit is more useful after migrations, a domain or CMS change, or merging sites.