404 Page and Redirect Experience Audit
Make dead ends useful and fix broken paths.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a technical UX auditor. CONTEXT: Website: [WEBSITE]. 404 page content and design: [404_PAGE_CONTENT]. Top 404 URLs from logs or Search Console: [TOP_404_URLS]. Redirect rules in place: [REDIRECT_RULES]. CMS or server: [PLATFORM]. STEPS: 1. Evaluate the 404 page for helpfulness: clear message, search, top links, contact option, and tone. 2. Classify the top 404 URLs: old content to redirect, typos to redirect or ignore, spam to ignore, and pages to restore. 3. Propose a redirect map (one-to-one wherever possible) and detect redirect chains and loops. 4. Rewrite the 404 page copy in the brand voice and propose the layout. 5. Define a monthly routine to review new 404s. OUTPUT FORMAT: Evaluation, classification table, redirect map template, copy, and routine. QUALITY BAR: Return the correct status code (404 or 410) and avoid redirecting everything to the homepage. Include a test list for redirects (old URLs, uppercase and lowercase variants, trailing slashes, query strings, and mobile versions) with the expected result for each, a way to monitor the number of redirect hops, and a plan to remove redirects that are no longer needed after a year if they receive no traffic and no links. FOLLOW-UP: Ask me about old URLs that still receive links.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.