How to Use This 404 Audit Checklist
A 404 error occurs when a browser requests a URL that the server cannot find. For ecommerce stores, each unresolved 404 costs real revenue: shoppers hit dead ends, crawl budget gets wasted on broken URLs, and link equity from inbound links dissolves. This checklist covers 12 specific audit items across discovery, redirect logic, custom page quality, internal linking, and monitoring.
Run this audit quarterly at minimum, and immediately after any site migration, platform upgrade, or large-scale product discontinuation. Each item below has a clear pass condition and a fail condition so there is no ambiguity about whether action is required.
Discovery and Crawl Checks (Items 1–4)
**Item 1 — Google Search Console 404 Report Is Reviewed Weekly.** Pass: The Pages report under Indexing is checked at least once per week and all 404s logged there are triaged within 14 days. Fail: The report has not been opened in more than 30 days, or there are unresolved 404s older than 30 days with more than 50 impressions each.
**Item 2 — A Full Site Crawl Has Been Run in the Last 90 Days.** Pass: A crawl using a tool such as Screaming Frog, Sitebulb, or Ahrefs Site Audit has been completed within 90 days and all returned 404 URLs are documented in a live spreadsheet. Fail: No crawl has been run in over 90 days, or crawl data exists but has not been reviewed.
**Item 3 — Crawl Covers Paginated URLs and Filtered Category Pages.** Pass: The crawl configuration explicitly follows pagination parameters and faceted navigation URLs (e.g., ?color=red, ?size=xl). Fail: The crawl is set to ignore query strings entirely, meaning filter-generated 404s go undetected.
**Item 4 — Server Log Analysis Confirms Which 404s Googlebot Is Actually Hitting.** Pass: Server logs from the last 30 days have been parsed to identify URLs Googlebot requested that returned 404. These are cross-referenced with GSC data. Fail: No server log access exists or logs have never been analyzed for bot behavior.
Redirect Logic Checks (Items 5–8)
**Item 5 — Every Discontinued Product URL Returns a 301, Not a 404.** Pass: All product pages removed in the last 12 months redirect via 301 to the closest relevant category page or a best-match replacement product. Fail: Any removed product URL returns a 404 with no redirect in place, especially if that URL has inbound backlinks or was previously indexed.
**Item 6 — Redirect Chains Are Three Hops or Fewer.** Pass: No redirect path from an old URL to a final destination involves more than three intermediate redirects. Fail: Any redirect chain exceeds three hops, which dilutes link equity and slows page load for users following those links.
**Item 7 — Redirect Map Is Maintained as a Living Document.** Pass: A spreadsheet or redirect management app tracks every active redirect, its source, destination, date created, and the reason for the redirect. Fail: Redirects are added ad hoc with no central record, making it impossible to audit or remove stale rules.
**Item 8 — No Redirect Points to a Page That Has Since Become a 404.** Pass: All redirect destinations resolve with a 200 status code. Fail: Any redirect destination itself returns a 404, creating a redirect-to-broken-page scenario that wastes both user experience and crawl budget.
Custom 404 Page Quality Checks (Items 9–10)
**Item 9 — The Custom 404 Page Returns HTTP Status Code 404, Not 200.** Pass: When a nonexistent URL is requested, the server returns a true 404 HTTP status header. Fail: The server returns a 200 status code while displaying a "page not found" message — a soft 404 — which causes search engines to index a useless page and fail to register the error properly.
**Item 10 — The Custom 404 Page Includes Navigation, Search, and Relevant Category Links.** Pass: The 404 page contains the site header, a functional search bar, and at least three links to high-traffic category or bestseller pages. Fail: The 404 page is a bare error message with no navigation, forcing users to hit the back button or abandon the session entirely.
Internal Linking and Sitemap Checks (Items 11–12)
**Item 11 — No Internal Links on Live Pages Point to 404 URLs.** Pass: A crawl of live pages returns zero internal links where the destination URL resolves to 404. Fail: Any live page — including navigation menus, footer links, blog posts, and product description cross-links — contains a href pointing to a 404. These are entirely within the store's control and have no excuse for going unaddressed.
**Item 12 — The XML Sitemap Contains No 404 URLs.** Pass: Every URL listed in the sitemap.xml file resolves with a 200 status code, verified by crawl or a bulk URL checker. Fail: Any URL in the sitemap returns a 404 or 301, both of which signal poor site hygiene to crawlers and waste crawl allocation on non-canonical or nonexistent pages.
Turning Audit Results Into a Fix Queue
After completing all 12 checks, prioritize failures by traffic impact first, then crawl frequency, then link equity. A 404 URL receiving 500 or more organic impressions per month in GSC warrants a same-week fix. A 404 with zero impressions and no inbound links can be batched into a monthly cleanup task.
Document every fix with a before-and-after status code confirmation. Re-run the specific check within two weeks to confirm the fix held — platform deployments, app updates, and CMS changes can silently reintroduce 404s. The audit is not a one-time project; it is a standing maintenance process that protects both revenue and search visibility.