Free HTTP Status and Redirect Checker
Paste HTTP response headers to review the status code, redirect hops, and common crawl issues. You can also paste an optional HTML body or a robots.txt snippet.
This is a checker for text you already have, not a live site crawl and not a Google ranking score. A browser page cannot freely request other websites, so nothing is fetched for you and nothing you paste is uploaded.
Response headers
Optional HTML body
Optional robots.txt snippet
Pasted responses
Improvement checklist
These reminders can help you review a URL. They are not a Google score, and they do not change the labels above.
Report
Copy this if you want a text record of the pasted status codes. This page does not change your site or your Search Console property.
Checks
No items in this filter.
What the tool checks
This page is a reader for HTTP responses you already have. Paste the status line and headers from a URL you control, and the tool will label the status class, count redirect hops in that text, and add notes taken from official Google crawler documentation.
A 2xx code means success, but it does not guarantee indexing. If the content looks empty or like an error, Search Console may report a soft 404. A 3xx code is a redirect. Google’s crawlers follow up to 10 hops by default. 301 and 308 are permanent and a strong signal that the target should be processed. 302 and 307 are temporary and weaker. A 4xx code is not indexed, and a 404 or 410 is the correct response when a URL is gone. 429 is treated as a server error. A 5xx code can slow crawling, and persistent server errors are dropped from the index.
If you paste an HTML body, the checker can look for a not-found title, a thin error message, a noindex robots meta tag, or a canonical link element. If you paste a robots.txt snippet, it can warn when a general Disallow rule appears to block the whole site. Those checks are hints from the text, not a verdict from Google.
The input checklist score only says whether the pasted text can be used and whether any cautions apply. It is not a Google score, and it is not a grade of your website. A clean 404 can still receive a high input score if the headers are complete, because the score is not asking whether the URL should exist. That is a decision you make from the page, the links, and Search Console.
How to use it
Open the URL in a browser, or request it from a machine you control. Copy the HTTP status line and the response headers. In many browsers this is available from the Network panel in developer tools. You can also paste output you already produced with a local command. Do not paste access tokens, cookies, or other private header values; strip those first.
Paste one response, or paste several responses from a redirect path, one after another. You can also paste a simple hop list: the URL, the three-digit status code, and the next URL if there is a redirect. Then add the HTML body if you want a soft 404 hint, and a robots.txt snippet if you want that extra check.
Choose Check headers, or load a sample to see how the results are laid out. The sample is a demonstration, not a live report. The issue sample shows a 200 response with a not-found title and a robots snippet that blocks the site, so you can see those warnings. Reset clears the form. Copy report and Download report give you a text record of the pasted status codes. Nothing is saved on this page after you leave.
This tool cannot request a public URL for you. Browser security stops a page on this site from freely calling another domain. That is why the input is pasted text, and why Search Console remains the official place to see what Google crawled. If you manage many URLs, use this page for a suspicious response, not as a replacement for a site-wide crawl on your own server.
How to read the result
Start with the two summary cards: the final status in the pasted text, and the number of redirect hops you provided. Then read the official-style explanation under the cards. A 200 result can still carry a soft 404 hint if the body or title looks like a missing page. A 301 result is a permanent move. A 404 result is expected when the URL no longer exists.
The hop list shows each pasted response in order, including a Location target when one is present. A missing Location header on a 3xx response, or a loop where URLs point back at each other, is flagged as a fail. A chain of three or more hops is flagged as a warning, because a single hop to the final page is easier to maintain even though crawlers may follow up to 10 hops.
Pass, warning, fail, and info are checklist labels. They do not change your site, and they do not update Search Console. After you fix a URL, inspect it in Search Console and give Google time to recrawl.
The improvement checklist is a short review: match the status code to the situation, keep redirects short, avoid a 200 not-found template, use robots.txt and noindex for their real jobs, and keep the sitemap pointed at working URLs.
If the first hop is a temporary redirect, the tool will say so. That is useful when you meant the move to be permanent. In official documentation, a permanent redirect is the stronger signal that the new URL should be processed, and a temporary redirect is appropriate when the original URL should stay in results for a while. Server-side redirects are the method Google is most likely to interpret correctly.
Give a pasted robots.txt snippet a second look if a Disallow rule seems to block the whole site. robots.txt is for managing crawling. It is not a reliable way to hide a page from Search, and a blocked URL may still be indexed without being fetched. If you want a page held out of the index, use a noindex rule and allow the crawler to reach the page so it can see that rule.
What this tool cannot do
It cannot crawl your site, follow a live redirect chain, or log into Search Console. It cannot see whether Google has indexed a URL, and it cannot measure page speed. It does not send any request to the address you are checking.
It also cannot invent a good error rate or a ranking promise. A site can have some correct 404 pages and still be healthy. A page can return 200 and still be left out of the index for other reasons, such as quality, duplication, or a choice Google has not yet made. There is no official shortcut that forces indexing, and a request in Search Console is not a guarantee of a date.
Use this checker to read the response you copied, then go back to the URL and to Search Console to make the real fix. If you changed a slug, test the old address as well as the new one. If you published a new robots file, inspect an important URL after the change. The official report is still the record of what Google has seen.