Home / Knowledge Base / Rank Tracker, Audit and Shield / Audit: Indexing Issues and What They Mean

Audit: Indexing Issues and What They Mean

Rank Tracker, Audit and Shield 2 min read Updated 13.09.2026
Five out of nine audit errors fall into this category. We analyze 4xx and 5xx codes, redirect loops, canonical conflicts, forgotten noindex, and crawler blocking.

The 'Indexability' category answers a single question: will the page appear in search. Here are all five audit errors out of nine — if the page is unavailable or closed, the other remarks about it make no sense.

Errors: Fix First

Code in ReportWhat HappenedWhat to Do
Page returns 4xxThe address does not exist, but there are links to itRestore the page or set a 301 to the current address and remove the links
Server Error 5xxThe server could not deliver the pageCheck the logs: usually it's a database issue, limits, or a code error
Page UnavailableTimeout or connection dropCheck the stability of the hosting and response time
Redirect LoopThe address redirects to itself in a loopBreak the chain: usually a conflict of www/https rules and CMS
Multiple CanonicalsThere are two or more canonical addresses on the pageKeep one — otherwise, search will choose one itself

Warnings

  • Page Closed with Noindex — sometimes intentionally, but more often it's a forgotten restriction after development. Check if this page is really not needed in search.
  • Closed in robots.txt — the robot will not crawl the page. Remember: this is not the same as removal from the index, see analysis of three directives.
  • Redirect Chain — more than one step: speed and some weight are lost.
  • Meta Refresh — an outdated method of redirection, search understands it worse than a regular redirect.
  • Hreflang without Self-Reference — language version markup does not work, see hreflang check.

Remarks

No Canonical and Canonical to Another Address — the second is especially insidious: the page is excluded from the index in favor of the specified one. Internal Redirect — links within the site lead to an address that redirects; it's better to link directly to the final one. Access Restricted — hosting protection has blocked our crawler: the page is likely working, but check manually. Sitemap.xml Not Found — see sitemap check.

Most Common Finding on Live Sites
Forgotten noindex after migration from the test server and canonical address copied from the template to all pages at once. Both errors silently remove pages from search — the site still appears functional.

How to Check a Specific Page

The audit shows the picture for the site, but for a single page, it's faster to use indexing checker and response headers — the restriction may be returned by the server, and it's not visible in the page code.

FAQ

What finding is the most dangerous?
Forgotten noindex and a canonical address copied from the template to all pages: they silently remove pages from search, while the site appears functional.
What does 'access restricted' mean?
Hosting protection has blocked our crawler. The page is likely working in the browser — check manually or add the crawler to exceptions.
What is wrong with a redirect chain?
Speed and some weight are lost, and the robot may not reach the final address. One step is normal, three or more is a reason to fix.
Was this article helpful?
Try it on your project Everything described in the article is available in the dashboard — the registration bonus is already in your balance.
Open dashboard