Skip to content
SERP TimesSERP Times

    Type at least two letters to search news and guides.

    to open · ↑↓ to move · Esc to close

    HTTP Status & Redirect Checker

    Follow a URL's full redirect chain and see the status code, location and timing of every hop.

    Checks public URLs from our server, up to 20 checks an hour.

    Public websites only. Try .

    This tool is being set up and will be available soon. The other free tools work right now.

    How to use it

    1. 1

      Enter the URL you want to check, for example an old page you've redirected.

    2. 2

      Run the check. We request the URL like a crawler and follow up to 5 redirects.

    3. 3

      Read each hop: its status code, where it points and how long the server took to answer.

    4. 4

      Fix chains and temporary redirects: point every old URL straight at the final page with a single 301.

    Why it matters

    Redirects decide where links, bookmarks and old rankings end up. A chain (A to B to C) slows visitors down and wastes crawling. Googlebot follows up to 10 hops, but each one adds delay and another chance to break.

    The status code matters too. 301 and 308 say a move is permanent, which Google treats as a strong signal to show the new URL. 302 and 307 say it's temporary, so Google may keep showing the old one.

    This tool checks server-side HTTP redirects. Meta refresh and JavaScript redirects happen in the browser, so they aren't followed here.

    Frequently asked questions

    What's the difference between a 301 and a 302 redirect?

    A 301 means the page has moved permanently and a 302 means temporarily. Google treats a permanent redirect as a strong sign to index the new URL, and a temporary one as a weak sign. Use 301 (or 308) for moves you don't plan to undo.

    How many redirects is too many?

    Aim for one. Google follows up to 10 hops and this tool stops after 5, but every extra hop slows the page down. Update old redirects so they point straight at the final URL.

    Do redirects lose PageRank?

    Google has said server-side redirects, permanent or temporary, don't lose PageRank. Chains still cost speed and crawl efficiency, so keep them short.

    Why is the result different from what my browser shows?

    Your browser may have cached an old redirect, or the site may answer differently by location, device or cookie. We request the URL without cookies, as SERPTimesBot.

    Why can't I check localhost or a private IP address?

    For security, the tool only checks public websites on the standard web ports, 80 and 443. Addresses inside private networks are blocked, including when a redirect points to one.

    Related guides

    More SEO guides