Crystal Ball checks covered

NON_200_STATUS, HTTP_REDIRECT_STATUS, REDIRECT_CHAIN

What the flag means

A normal, indexable page should usually return a 200 OK status. If Crystal Ball sees a non-200 status, a redirect, or a chain of redirects, it means the URL tested is not the clean final page. One redirect can be normal, especially from HTTP to HTTPS. A chain of redirects is messier: it makes users and crawlers take extra steps before reaching the real content.

This matters because broken, slow, or confusing URL paths waste crawl time, weaken user experience, and can make reports harder to trust.

Common causes

Common causes include old URLs, changed slugs, deleted pages, HTTP-to-HTTPS redirects, www/non-www conflicts, trailing slash mismatches, migration leftovers, redirect plugins, Shopify product changes, Wix automatic redirects, or Webflow 301 rules stacked on top of hosting rules.

How to fix it

  • Custom HTML/static: Test the URL with your browser and a header checker. Fix server rules, hosting redirects, or .htaccess so the page returns one clean final URL. Google’s redirect guide is the best starting scroll.
  • WordPress: Check page slugs, permalink settings, SEO plugins, and redirect plugins. The Redirection plugin is a common option for managing 301s and 404s.
  • Shopify: Use Shopify’s URL redirect manager when products, collections, or pages move. See Shopify URL redirects.
  • Wix: Use the URL Redirect Manager for changed page slugs or moved pages. See Wix 301 redirects.
  • Webflow: Use Webflow’s 301 redirect settings and avoid chaining old URLs through multiple hops. See Webflow 301 redirects.

Need help?

If the fix gets murky, visit Support and send the details. Bug reports and Crystal Ball questions are free support. Implementation and development work may be paid support, but we will tell you clearly before anything becomes paid. No surprise invoices from the tower.