Skip to main content
Crawl errors appear in Search Console → Pages. Most stores have some, and most of them do not matter. Knowing which do is the useful skill.

​
The error types

​
Which to fix first

Server errors. A 5xx means the site was unreachable. Persistent 5xx damages crawl rate and rankings. Check hosting and app-induced load. Soft 404s. Empty product pages, empty categories, pages that removed their content but still return 200. Fix by populating, removing, or redirecting. These accumulate silently on stores that empty pages instead of deleting them. Redirect chains and loops. Collapse A → B → C to A → C. Loops break crawling entirely. 404s with inbound links or traffic. These are lost value. Redirect them to the closest genuine equivalent. “Crawled — currently not indexed” at scale. Google read the pages and declined. Nearly always thin or duplicate content — see programmatic SEO.

​
Which to ignore

404s for pages that should not exist and have no links. A 404 is the correct response. You do not need to redirect every deleted page. Blocked URLs you intentionally blocked. Filter and sort parameters showing as blocked is the system working. Small numbers of “Discovered — not indexed” on a large catalogue. Some of this is normal. Do not chase zero errors. A large store with zero reported issues usually means something is not being crawled at all.

​
Diagnosing at scale

If discovered-but-not-indexed counts are very large relative to your product count, the likely cause is a crawl trap — usually faceted navigation generating unbounded URL combinations. Google is spending its budget on filter permutations instead of products. Check crawl stats: if parameter URLs dominate, that is the problem. See crawl budget.

​
What Ryze does

The Technical Audit finds pages and links returning 4XX or 5XX errors, robots.txt rules that block crawlers, and sitemap problems. Fix with agent fixes what your site connection allows and tells you what to change yourself.

​
The audit says “No audit yet” or never finishes

The Technical Audit scores the top pages from your Google Search Console, so connect Search Console first for a meaningful result. The audit runs weekly on its own; to start one now, open SEO → Technical Audit and click Run Scan — it takes a few minutes, and you can close the page while it works. If your site is behind bot protection — for example Cloudflare Bot Fight Mode or a high Security Level, Wordfence, or another firewall (WAF) — the audit’s crawler can be blocked, and the audit can’t check your pages. Allow automated requests to your site or lower the protection, then click Run Scan again.