SEO issues and how to fix them

These are the 27 checks IndexZero's site audit runs on every page it crawls. Each has a one-line explanation, and the ones with a guide give the exact rule the crawler applies, so you know what a flag does and does not mean.

The guides also cover why the issue matters, what usually causes it, how to fix it at the template rather than page by page, and a prompt a coding agent can run to do the fix in your repo.

Critical (4)

  • Crawler was blockedThe site returned a bot challenge or access denial (e.g. a Cloudflare challenge, 403, or 429) instead of the page. It is reported as blocked, not broken, but it means this page could not be audited, and other crawlers like search engines may face similar friction.
  • Server error (5xx)The page returned a 5xx server error. Search engines that repeatedly see server errors will crawl the site less and may drop the page from the index.
  • Broken internal linkThis page links to an internal URL that returns an error status (4xx/5xx). Broken links waste crawl budget, leak link equity, and frustrate users — they are among the most common and most damaging technical SEO issues.
  • Missing title tagThe page has no <title>. The title is the strongest on-page relevance signal and the headline shown in search results; without it search engines generate one themselves, usually badly.

Warning (14)

Info (9)

  • Title too longThe title exceeds ~60 characters, so search results will truncate it and the ending may be cut off mid-phrase.
  • Title too shortThe title is under ~10 characters, which is usually too generic to describe the page or attract clicks.
  • Meta description too longThe meta description exceeds ~160 characters, so search engines will truncate the snippet.
  • Meta description too shortThe meta description is under ~70 characters. Short descriptions waste the snippet space search results give you, and search engines often ignore them in favor of text pulled from the page.
  • Heading levels skipThe heading hierarchy skips levels (e.g. an H4 directly after an H2). This weakens document structure for accessibility tools and content parsing.
  • Slow server responseThe HTML response took over 1.5 seconds. Slow time-to-first-byte drags down every downstream performance metric and reduces crawl rate on large sites.
  • Page is noindexThe page asks search engines not to index it (via robots meta tag or X-Robots-Tag header). That's often intentional — this is a heads-up, not an error.
  • Canonicalized to another URLThe page declares a different URL as its canonical, telling search engines to index that URL instead. Fine when intentional (parameter pages, syndication) — a problem if this page was meant to rank.
  • Page is deep in the site structureThe page is 5+ clicks from the homepage. Deep pages get crawled less often and receive less link equity.