Instead of showing you a giant list of errors, often for irrelevant or low value content, SiteSeer organizes your opportunities by Click Potential.

For certain crawl issues, we estimate what the potential is for fixing it. An easy example is a page that suddenly becomes a 404: SiteSeer will estimate your traffic loss from this error and prioritize it along with your other opportunities.

This way, you can focus on your largest opportunities, instead of sifting through lists of mundane crawl errors.

We are continually adding and improving what sorts of issues affect a page’s Click Potential. Keep reading for more information about some specific issues that SiteSeer prioritizes:

404 Not Found / Server Error

Broken pages are a dead end for users. Your options are to add a 301 redirect to some other relevant content, or bring the old page back. We increase the page’s Potential by an estimate of how much traffic you’re losing. Fix the problem and click “re-crawl” in the sidebar.

Page redirecting to a broken URL (404 or otherwise)

Very similar to the error above: This particular URL is a 301, but when we attempted to follow it, we ran into an issue. Google and your users will experience the same problem.

Page’s canonical value is pointing to a broken URL

Even though this is invisible to web users, it can still affect your organic performance. Adjust the canonical tag to point to a valid URL. Learn more about canonicalization at Moz’s Learn Center.

Noticeably Slow Page Load

Web performance is a proven ranking factor. This means that if you have pages that are noticeably slow to load, your organic search will suffer. SiteSeer shows this warning when your server’s response time is above 600 ms. We adjust the page’s Click Potential based on an estimate of how this might be affecting your organic traffic.

Note that we do not do any “real user” emulation. Page’s with a fast Response Time could still be noticeably slow to load due to many other factors. Read more about Google’s performance tools on web.dev.