How to Write a 404 Page With Two Useful Next Clicks

Anyone shipping a site can write a 404 page with two useful next clicks in 8 minutes: name the miss, offer search and one clear home path. Run it in ChatGPT, Claude, or Gemini before a joke 404 trains people to bounce instead of recover.

A useful 404 is a map after a wrong turn, not a meme. If the page only says "oops" and shrugs, you never wrote next clicks. Two honest paths beat a clever illustration with nowhere to go.

This is not 404 copy that sends onward only as poetry — this skill forces exactly two clicks. It is not empty-state copy when a table is empty. An empty state is a zero-data screen. This is a missing URL. It is not a form error that names the missing field. A form error is a blank box. This is a dead link. Save the two-click shape as a skill prompt you can rerun.

What you need

Your real home URL label, your search entry point (or top two nav destinations if search does not exist), ChatGPT, Claude, or Gemini, and eight minutes. A five-second scan test on a phone.

Banned before you start: oops, whoops, this page is lost in space, funny 404 comic as the only help, click here, unlimited link farms, and selling a webinar on the error page.

Write a 404 page with two useful next clicks

1. Name the miss. Do not draft a joke

If your CMS shows the requested path, you may add one short clause: "We cannot find /guides/old-slug." Only do this when the path is safe to echo. Never reflect raw query strings that could look like an attack.

Keep the tone adult even if your brand is playful elsewhere. Error recovery is not the place to debut a mascot bit that delays the buttons.

Instruct ChatGPT, Claude, or Gemini: "Do not draft a meme. One plain sentence that the page is missing. No oops. No astronaut. No pun. Then stop."

Good: "We cannot find that page. It may have moved or the link is wrong." Bad: "Looks like you discovered our secret void." Void is a shrug with eyeliner.

Paste your brand voice only as a constraint like "plain, adult, no slang," not as a request for personality fireworks on an error.

2. Offer exactly two next clicks

Wire the real routes before you polish adjectives. A perfect label on a dead href is still a second 404. Paste the production URLs into the prompt as ground truth.

If marketing wants a third "popular posts" module, park it below the fold as text links, not as a third primary button. Primaries stay at two.

Instruct: "Add exactly two actions. Button one: Search [site] — or Go to [primary category] if we have no search. Button two: Home. No third button. No 'contact support' unless I paste a support URL."

Good pair: "Search guides" and "Home." Bad pair: "Home," "Blog," "Pricing," "Twitter," "Contact," "Status." Five exits is a maze.

If you lack search, pick the single highest-traffic useful section as click one (Guides, Library, or Docs) plus Home. Still two.

3. Label buttons with destinations, not vibes

Check localization early: if your UI is bilingual, generate both languages with the same two destinations. Do not let one language keep a joke the other language cut.

Align button casing with your design system (sentence case vs title case). Inconsistent casing makes one path look like a leftover.

Tell the model: "Button labels must name the destination. Ban click here, take me back, help, and try again with no target."

Good: "Search the library" / "Go to homepage." Bad: "Rescue me" / "Start over." Rescue is theater.

Match the words your nav already uses. If the site says Guides, the button says Guides. A new noun is how people hunt for a page that does not exist — again.

4. Force the short stack, then stop the model

Reject any model output that adds a countdown, a mini-game, or a "guess the URL" prompt. Those patterns burn time and trust.

If legal requires a tracking note on error pages, put it in microcopy under the buttons, not inside the miss sentence.

Hard cap: one miss sentence, optional one-line reason, two buttons. No hero essay. No newsletter gate. No related-posts wall of ten cards.

Tell the model: "Output the miss sentence, then two button labels. If a banned joke appears, rewrite that line only."

ChatGPT will add a cute illustration brief. Claude will add a soft apology paragraph. Gemini will invent a help center URL you do not have. Cut all three unless you pasted real URLs.

5. One human pass as a stranger with five seconds

Have one teammate who did not write the copy do the five-second scan. Authors forgive their own jokes. Strangers do not.

Log the final copy next to the engineering ticket with the two destination URLs. Ambiguity at handoff is how Home becomes Pricing.

Open the draft on your phone. Count to five. You must know what happened and where you can go. If you only smile at a joke, you failed.

Check three traps: more than two primary clicks, a button that says Home but routes to pricing, and a miss sentence that blames the user. Fix labels to match real routes. Then send edits back: "Replace only the words I changed. Do not re-expand. Do not add oops."

One pass. Ship as draft copy to engineering. If a meme still sits above the two clicks, you never wrote a useful 404. Stop.

What good looks like

Trigger: You are about to approve a funny 404 because the illustration is cute, or about to dump the whole sitemap as links.

Input: Miss sentence constraints, two real destinations, ChatGPT/Claude/Gemini, phone scan.

Output: One miss sentence plus exactly two destination-named buttons. No meme-only page.

Stop: After one five-second stranger scan. No third button. No webinar sell.

Takeaways

- Name the miss. Then exactly two next clicks. Stop.

- Button labels name destinations. Click here is fog.

- Search + Home (or top section + Home). Not a link farm.

- Jokes are optional decoration. Recovery is the job.