Pixelquil logoPixelquil

HTTP Header & Status Code Checker

Check status codes, response headers, and redirect chains in bulk, with support for spoofing Googlebot and other crawler user-agents.

URLs to check (one per line)

Enter one or more URLs above, then click Check Status.

Fetched through a small server-side proxy. Spoofing a crawler's User-Agent here is standard practice for checking cloaking or bot-specific responses on your own site, nothing is stored.

How it works

  1. 1

    Paste one or more URLs

    Enter one URL per line, single or bulk checks both work the same way.

  2. 2

    Choose a User-Agent

    Check as a regular browser, or spoof a specific crawler like Googlebot to see exactly what that crawler would receive.

  3. 3

    Enable canonical consistency check, if needed

    Flags any protocol, host, or path change between the input URL and where it finally resolves after redirects.

  4. 4

    Click Check Status

    Every URL is checked concurrently, each with its status code, redirect count, and key header flags shown.

  5. 5

    Review flagged headers

    X-Robots-Tag noindex, missing Cache-Control, and missing security headers are called out automatically for each URL.

  6. 6

    Expand for the full header list

    Click Show all response headers on any result to see the complete raw header set for that URL.

About the HTTP Header & Status Code Checker

Checking a URL's response headers, status code, and redirect behavior usually means opening browser dev tools, and checking a whole batch of URLs that way means repeating that process one page at a time. This tool checks many URLs at once, follows each one's full redirect chain automatically, and flags the specific headers that actually matter for SEO and security, all with the option to check as a specific search engine crawler rather than a regular browser.

Why checking as Googlebot specifically matters

Some sites, intentionally or through a misconfigured caching or bot-detection layer, serve different content or headers to search engine crawlers than to a regular browser, a practice known as cloaking when done deliberately, and a real, damaging bug when done accidentally. Checking a page's response using a spoofed Googlebot or Bingbot User-Agent, exactly what this tool's User-Agent selector does, is standard, legitimate diagnostic practice for confirming your own site serves what you think it serves to crawlers specifically, not something exclusive to malicious use. If a page returns a 200 status to a browser but a 404 or an unexpected redirect to Googlebot's user-agent, that is a real, otherwise invisible indexing problem this comparison catches directly.

The one header most people never check: X-Robots-Tag

A page can be told not to index in two different ways, a meta robots tag inside the HTML itself, or an X-Robots-Tag HTTP header set at the server level, invisible in the page's visible HTML entirely. This second method is especially easy to miss, since it doesn't show up when viewing page source, only in the raw response headers, and it applies with equal force, a page with X-Robots-Tag: noindex is excluded from search results just as effectively as one with a meta noindex tag, even if every visible SEO element on the page looks perfectly optimized. This tool checks for exactly this header on every URL and flags it prominently when found, since it is one of the most consequential, and most overlooked, checks in a technical SEO audit.

Checking canonical and redirect consistency

Enabling the canonical and redirect consistency check compares each checked URL against where it actually ends up after following every redirect, flagging any protocol change, http upgrading to https, a host change, www being added or removed, or a path change along the way. This is particularly useful for auditing a list of URLs from an old sitemap, a backlink profile, or an internal link inventory, confirming they consistently resolve to the exact canonical form of each page rather than an inconsistent mix of www and non-www, or http and https, versions that could otherwise dilute ranking signals across duplicate variations of the same page.

Checking a competitor, or your own site, at scale

Because this tool accepts a full list of URLs at once, one per line, and processes them concurrently, it works just as well for auditing a competitor's key pages, checking their caching strategy, security header posture, and redirect hygiene, as it does for a full internal audit of your own site's top pages. Checking a competitor's public-facing response headers this way is no different from what a browser's own dev tools would show you visiting each page manually, this tool just does it for an entire list at once instead of one tab at a time.

Runs through a small server-side proxy

Since reading full response headers across domains isn't possible directly from a browser tab, checks run through a small server-side proxy that fetches each URL and reports its status, headers, and redirect behavior back to your browser. Nothing about the URLs checked is logged or stored beyond completing the request. If you specifically want to trace a longer redirect chain in more visual detail, our Redirect Chain Checker is built around that single-URL, hop-by-hop view, both part of the same Technical SEO Tools collection this tool belongs to.

Frequently asked questions

What headers does this show?

Key headers, Content-Type, Cache-Control, X-Robots-Tag, security headers, are highlighted automatically, and the full raw header set is available by expanding each result.

Can I check headers for a page that isn't live yet?

No, this checks a live, publicly accessible URL, since it performs a real HTTP request through the proxy.

Is it legitimate to spoof a Googlebot User-Agent?

Yes, checking your own or a public site's response as a specific crawler is standard, legitimate diagnostic practice for catching cloaking bugs or bot-specific misconfigurations, not something exclusive to malicious use.

Why is X-Robots-Tag flagged specially?

It's an HTTP header level noindex directive, invisible in a page's visible HTML source, that excludes a page from search results just as effectively as a meta robots tag would, making it one of the most consequential and easy to overlook checks in a technical audit.

What does the canonical consistency check actually compare?

It compares the URL you entered against where it finally resolves after following every redirect, flagging any protocol, host (including www), or path change along the way.

Can I check a competitor's site with this tool?

Yes, checking a publicly accessible site's response headers is no different from what a browser's dev tools would show visiting the page manually, this tool just does it in bulk.

How many URLs can I check at once?

There's no hard limit set by the tool, URLs are processed concurrently in small batches to keep checks reasonably fast without overwhelming the proxy.

Is my checked URL list logged or stored anywhere?

No, URLs are only used to complete the checks through the proxy, nothing is logged or stored afterward.