Skip to content

We use analytics cookies to see how the site is used. They are only set if you accept. Accepting also turns on session recording (pages viewed, clicks and scrolls) so we can fix problems; what you type stays hidden. Read the privacy policy

SitePatent
login$ submit
Editorial

Launch & Discovery Guides

Practical guides on launching products, getting discovered, and reaching the right audience - written for founders and developers.

RSS Feed
All PostsAccessibilityBrandingCLSDMARCDiscoveryDiscovery PlatformsDomainsE-E-A-TFTC rulesFaviconGrowthHTTPSHostingINPLCPLaunchLink PreviewsListingsMaintenanceOpen GraphOutreachPerformanceProduct DiscoveryProduct LaunchProduct VisibilitySEOSecuritySite QualityStartupsSubmissionsTrustVisibilityWeb Designabout pageclarityconversioncopywritingcore web vitalscredibilitydeliverabilityearly customersemail authenticationlanding pagelaunchpage speedreviewssecurity headerssocial prooftestimonialstrust signalsusability testing
LatestSite Quality

Your 404 Page: The Status Code It Must Send, and What to Put On It

A good "page not found" page does two jobs: it sends HTTP status 404 (or 410) so search engines drop the dead URL, and it shows visitors a way back into your site. What to put on the page, which code to send in each case, the settings to check in Apache, Nginx, Next.js, WordPress, Netlify and Cloudflare Pages, and a 6-point test.

SitePatent Editorial Team

October 23, 20268 min read