Find missing pages
Review URLs that return 404 and the pages that linked to them.
Find internal links and URLs returning 404 Not Found and decide whether to restore, redirect, or remove them.
This page focuses on 404 pages in crawl context. The crawler records the fetched URL, response status, discovery source when available, metadata, redirect outcome, and history signals that explain why a finding appears.
Use the check to review missing URLs discovered during the crawl. The goal is not just to report a problem, but to show the URL-level evidence needed to decide whether the issue is intentional, accidental, fixed, or still unresolved.
Review URLs that return 404 and the pages that linked to them.
Update the internal link, restore the page, or add a deliberate redirect.
Run another crawl and confirm 404 findings are resolved.
Small technical issues become expensive when they remain invisible. For 404 pages, a repeatable crawl helps distinguish a one-time anomaly from a persistent problem caused by templates, redirects, routes, metadata, or content changes.
Start with the concrete evidence: affected URL, source page, HTTP status, metadata value, redirect target, or comparison row. After the fix is made, run another crawl with comparable settings to confirm the finding is resolved.
It checks missing URLs discovered during the crawl and presents the result as summary counts plus URL-level evidence. That makes the audit useful for deciding what to fix and for verifying the result in a later crawl.
No. The URL is transferred to the crawler seed field so you can review scope, limits, redirects, and sitemap policy before starting.
Yes. Registered users can create scheduled audits and review whether findings are new, resolved, or still unresolved across completed crawls.
No. The same findings are useful for site maintenance, release validation, migration checks, and general quality assurance.
Enter a website URL and inspect 404 pages with URL-level evidence in the live crawler.