
Every time a browser asks for a page, the server answers with a three-digit status code before it sends anything else. Most of the time you never see it, until you hit a 404 or a 500. This Seahawk Learn video explains the common codes in plain language, then takes a detour into one of the strangest: 418 I’m a Teapot.
The article below covers the same ground, plus what status codes mean for WordPress site owners and SEO.
What HTTP status codes are
A status code is the server's short answer to a request. The first digit tells you the category:
- 1xx informational: the request was received and processing continues.
- 2xx success: the request worked.
- 3xx redirection: the content lives somewhere else.
- 4xx client error: the request has a problem, such as a wrong URL or missing permission.
- 5xx server error: the server failed to complete a valid request.
The common codes
200 OK
The page was found and delivered. This is what you want for every working page.
404 Not Found
The server cannot find the URL. It usually means a broken link, a deleted page or a typo. If this happens on your site, see our guide to fixing or redirecting a 404 error in WordPress.
403 Forbidden
The server understood the request but will not allow it, often because of file permissions or security rules. Our guide to fixing a 403 Forbidden error in WordPress lists the usual causes.
500 Internal Server Error
Something went wrong on the server and it cannot say more. In WordPress, a faulty plugin, a damaged .htaccess file or exhausted PHP memory are common culprits. Read how to fix the 500 Internal Server Error in WordPress.
What 418 I’m a Teapot is
418 began as an April Fools' joke. In 1998 the specification RFC 2324 described the Hyper Text Coffee Pot Control Protocol (HTCPCP), a tongue-in-cheek way to control coffee pots over a network. Within it, a teapot that is asked to brew coffee replies with 418: I'm a teapot. The reasoning is simple: a teapot cannot make coffee, and the error says so.
The joke includes silly protocol details. The video mentions methods such as BREW and WHEN, and headers that describe adding milk, with WHEN meaning "say when" to stop pouring.
Why it still exists
Despite starting as a prank, the code has taken on a life of its own. Developers have used it in libraries, frameworks and browsers, and when proposals came up to remove it, the community pushed back and it stayed. It now serves as a sign of the web's sense of humour, and some tools use it as a placeholder response. Google has also served a teapot page at its own domain, which the video uses as a real-world example.
How to create your own 418 response
The video demonstrates making your own 418 page. The principle is the same on any server: return the status code 418 together with a short page.
- Pick a URL. Choose a path that will only be used for fun, such as /teapot.
- Return the status. Configure your server or application to send 418 for that URL. In a WordPress theme or plugin you can call the status_header function with 418 before any output, or set the status in your web server configuration.
- Add a message. A short line such as "I'm a teapot" and an image is enough.
- Check the status. Use your browser's developer tools (Network tab) or a header checker to confirm the code, not just the page text.
Edit server files and theme code only if you are comfortable doing so, and test on a staging copy first.
SEO impact and crawler issues
The video closes with the SEO angle. Search engines treat 4xx responses as errors: a page that returns 418 is not a normal page, and it is unlikely to be indexed or ranked. Crawlers will not treat it as a "teapot" any differently from other client errors. For that reason:
- Never return 418 on pages you want in search results.
- Keep joke pages away from important sections and out of your sitemap.
- Make sure real pages return 200, and moved pages return a proper 301 redirect.
- Watch for unusual codes in server logs and in Google Search Console reports.
A 418 appearing in your logs for a real page is worth investigating. Slow answers matter to crawlers as well, so see our explanation of server response time.
What the video covers
- 0:00 Introduction
- 0:32 Common codes explained: 200, 404, 500, 403
- 0:53 Introducing 418 I’m a Teapot
- 1:11 The Hypertext Coffee Pot Control Protocol explained
- 1:50 Funny protocol methods: BREW, WHEN, headers
- 2:20 Real-world 418 implementation
- 3:02 Creating your own 418 page
- 4:20 SEO impact and crawler issues
What to take away
You do not need to memorise every code. Know the families, recognise 200, 301, 404, 403 and 500, and check the actual status of important pages rather than trusting how they look. 418 is a fun piece of web history, but keep it away from anything you want to rank.
FAQs
What does HTTP 418 I’m a Teapot mean?
It comes from an April Fools' specification for controlling coffee pots over HTTP. A teapot asked to brew coffee returns 418 to say it cannot do so.
Is 418 a real error I should fix?
Usually it is a joke or a placeholder, but if it appears unexpectedly on a real page, check your server, security rules and plugins, since it should not be returned for normal content.
Does a 418 page hurt SEO?
A page returning 418 is treated as a client error and is unlikely to be indexed. It will not hurt unrelated pages, but never use it on pages you want to rank.
What is the difference between 4xx and 5xx errors?
4xx codes mean the request has a problem, such as a missing page or no permission. 5xx codes mean the server failed to handle a valid request.
