Tools / HTTP diagnostics
URL Status Code Checker
See the HTTP response behind a public URL. Trace redirects to the final destination with one anonymous GET check.
Your response path will appear here
See each followed redirect, the final status and the destination URL.
Read the response
A status code is a server response
Use this checker after a URL change, a broken-link report or an unexpected error. It records the requested address, each followed redirect and the final HTTP response so you can decide what to investigate next.
The check runs from SearchVector’s server without your browser’s login session. A 200 response means the request succeeded; it does not establish that the page is useful, indexed or available to every visitor.
What should you do with the status?
Read the final response alongside the redirect path. A redirect can be intentional; a successful destination can still contain the wrong page.
200–299 · Success
The request succeeded.
Check that the destination contains the intended page.
301 / 308 · Permanent
A permanent redirect was returned.
For a moved page, point internal links at the intended final URL.
302 / 303 / 307 · Redirect
The server directed the request elsewhere.
Confirm the redirect matches the intended temporary or see-other behavior.
401 / 403 · Access
Authentication is needed or access was refused.
Review access controls; do not treat every refusal as a broken page.
404 / 410 · Missing
The resource was not found or is gone.
Restore a page that should exist, or update links to a relevant replacement.
429 · Rate limited
The destination limited requests.
Wait before retrying and check your site’s traffic limits.
500–599 · Server error
The server or a gateway could not fulfill the request.
Inspect application, origin and proxy logs if you manage the site.
Reference: HTTP status definitions (MDN).
What this check observes
The checker sends GET requests and follows at most three supported HTTP redirects. It does not follow JavaScript navigation or HTML refresh tags. HEAD requests can receive different responses; this report does not mix the two methods.
A twelve-second server deadline covers the request and redirects. HTML responses must fit the helper’s size and encoding limits; non-HTML resources are checked from their response headers. A timeout, blocked destination, excessive chain or unsupported response produces an inspection error, not a made-up HTTP status.
Only public HTTP and HTTPS URLs on ports 80 and 443 are supported. Each redirect is checked again. Private addresses, credentials in URLs and unsupported IPv6 destinations are rejected. No cookies or custom request headers are forwarded.
Fix, then recheck
Unexpected destination
Follow the path from top to bottom. Check hostnames, HTTP-to-HTTPS changes and trailing-slash rules against the intended URL.
Long chain or possible loop
If the redirect limit is reached, inspect your redirect rules and server logs. The checker cannot confirm a loop or show a partial chain when inspection fails.
A missing page returning 200
This can be a soft 404. Review the page content and use Search Console for Google’s indexing assessment; the status alone cannot identify it.
For crawler-specific guidance, see Google’s HTTP status documentation.