Website errors decoded: 404, 500, 503 and what each one means

An error page is information — if you can read it. Here are the four codes you will meet, translated.

404 — Not Found (the polite one) The address exists nowhere: a mistyped URL, a deleted page, a broken internal link. Cause: yours (content/links). Fix: find what linked there (Search Console's coverage report lists 404s), redirect or rebuild the page. A custom 404 page with your menu turns dead-ends into detours.

403 — Forbidden (the permission one) The server understood but refuses. Usually file permissions or a protection rule blocking a legitimate file. Cause: hosting configuration. Fix: check what changed (a new .htaccess line, moved file), then support if unclear.

500 — Internal Server Error (the vague one) Your code crashed. In WordPress: usually a plugin/theme conflict or an exhausted resource. Custom PHP: a syntax error from tonight's edit. First move: recall the last change and reverse it (deactivate the newest plugin, restore the last edited file via version history). The error log (support shares it) names the culprit.

503 — Service Unavailable (the busy one) The server is overloaded or your account hit a resource limit — or maintenance is running. First move: one retry after a minute. Persistent? It is a limit or an incident — support confirms which, and the usage graph shows if you have simply outgrown the plan (the good problem).

The universal first response (any error) 1. Note the URL and exact code 2. Screenshot (the support-art of champions) 3. Recall the last change 4. One cache-clear + hard refresh (solves a surprising share) 5. Then — and only then — WhatsApp support with the screenshot

Errors are the server talking. Now you speak back.