Glossary · Glossary

HTTP Status Code

An HTTP status code is the server response that tells browsers and crawlers what happened when a URL was requested.

Updated Jun 4, 2026 Reviewed Jun 4, 2026 en

An HTTP status code is the numeric response a server returns when a browser, crawler, or other client requests a URL. It tells the client whether the request succeeded, redirected, failed, or hit a server problem.

For SEO, status codes are one of the first technical signals to inspect. A crawler cannot evaluate a page as intended if the URL returns the wrong response, redirects through a messy chain, or intermittently fails.

Why it matters

Status codes shape the crawl and indexing path. A glossary page intended for search should usually return a stable 200 response at its canonical URL. A moved page should return a redirect to the best current URL. A removed page should return a real 404 or 410 instead of pretending that an error page is normal content.

This also matters for GEO and AI visibility. AI-influenced search experiences still depend on accessible source pages. If a guide, report, or definition returns errors, unstable redirects, or soft error content, it is less likely to become a reliable source for search systems or answer engines.

How it differs

A status code is the server’s response to a URL request. Crawlability is the broader condition that lets crawlers discover, request, and access a page. Indexing is the later decision to store and organize content for search results.

A status code also differs from a robots directive. A 200 page can still carry noindex; a 404 page does not need noindex because the server is already saying the resource is missing.

Common status families

Status family	Typical meaning	SEO interpretation
`2xx`	Successful response	The page can be fetched and evaluated, but indexing is not guaranteed.
`3xx`	Redirect	Crawlers follow the target; redirect type and chain quality matter.
`4xx`	Client error	The URL is unavailable, blocked, missing, or otherwise invalid.
`5xx`	Server error	Crawling and indexing may be delayed or disrupted if errors persist.

Example check

Use a header request to see the status code without downloading the full page:

curl -I https://www.geolyze.org/glossary/canonical-url/

A healthy response for a public glossary page should look broadly like this:

HTTP/2 200
content-type: text/html; charset=utf-8

If an old path has moved, the response should send users and crawlers to the current path:

HTTP/1.1 301 Moved Permanently
Location: https://www.geolyze.org/glossary/canonical-url/

How teams use it

Teams check status codes after publishing pages, changing routes, adding redirects, migrating domains, or diagnosing missing pages in search tools. A practical review asks:

Does the canonical page return 200?
Do old URLs redirect directly to the best current URL?
Are important pages avoiding 404, 410, and 5xx responses?
Are error pages returning real error status codes?
Do internal links point to final URLs instead of redirecting URLs?

Common misunderstanding

A 200 response is not an indexing guarantee. It only means the server returned a successful response. Search systems still evaluate crawl permission, content quality, canonical signals, noindex, duplication, and query relevance before a page can become visible in search.