Skip to content
SEO Madmanby Adam Hafez
Free tool

Meta refresh vs. 301 redirect checker

Parse a meta refresh tag's delay and target, and see which redirect signal Google actually reads from it: permanent at 0 seconds, temporary above 0.

Runs entirely in your browser. Nothing you enter is uploaded, logged or stored.

Redirect method ranking

Google's documentation orders redirect methods "by how likely Google is able to interpret correctly": a server-side HTTP redirect (301 or 308 for permanent, 302, 303 or 307 for temporary) first, meta refresh second, a JavaScript location change third, and a crypto redirect last. Use a server-side redirect when you can set one; reach for meta refresh only when you cannot.

This tool parses the delay and target with a regular expression matched against the documentedcontent="<seconds>; url=<url>" syntax. It cannot see how your server responds, so it cannot check an actual HTTP redirect for you.

Key takeaways

  • Google's documentation places a 0-second meta refresh in the same permanent-redirect category as an HTTP 301, using it as a signal the target should be canonical.
  • A meta refresh with any delay above 0 seconds is read as a temporary redirect signal instead, so the original page, not the target, stays eligible to be treated as canonical.
  • Google's documentation ranks redirect methods by how reliably it can interpret them, with server-side HTTP redirects first and meta refresh second.
  • A JavaScript redirect and a crypto redirect are both named as less reliable than meta refresh, and Google recommends using them only when a server-side redirect is not possible.
  • This tool only parses the tag's text; it cannot check what your server actually returns for a real HTTP redirect.

What it takes

  • A meta refresh content value, or a full meta http-equiv="refresh" tag

More tools

All of them free, all of them browser-only.

Browse the tools

How to use it

  1. 1Paste the tag or its content valueEither the bare content string, such as "0; url=https://example.com/new", or the full HTML tag works.
  2. 2Read the parsed delayThe number before the semicolon is the wait in seconds before the browser follows the redirect.
  3. 3Read which signal Google readsThis is the part most people get backwards. Zero seconds reads as permanent; anything more reads as temporary, regardless of how long the actual wait is.
  4. 4Check the target is an absolute URLA relative target can still work, but an absolute one removes any ambiguity about which host it resolves against.
  5. 5Compare against the redirect method rankingGoogle's documentation orders redirect methods by how reliably it can interpret them; use this to decide whether a server-side redirect is worth setting up instead.

Paste a meta refresh tag or just its content value, and this tool tells you which of Google’s two redirect signal categories, permanent or temporary, it actually falls into. Everything runs against a regular expression matched to the documented syntax, in your browser only.

The part almost everyone gets backwards

A meta refresh with a delay feels like the gentler option: give the visitor a moment before sending them along, rather than an instant, jarring server-side redirect. Google’s own documentation flips that intuition entirely. It groups “meta refresh (0 seconds)” alongside HTTP 301 and 308 under permanent redirects, stating the indexing pipeline treats it “as a signal that the redirect target should be canonical.” Any delay above 0 seconds moves the same tag into the temporary category instead, alongside HTTP 302, 303 and 307, where “the indexing pipeline doesn’t use the redirect as a signal that the redirect target should be canonical.” Adding a delay to be polite to visitors quietly tells Google the move might not be permanent, which can leave the old URL sitting in search results longer than intended.

Where meta refresh sits in Google’s own ranking

The same documentation orders every redirect method “by how likely Google is able to interpret correctly.” Server-side HTTP redirects sit at the top of both the permanent and temporary lists, meta refresh sits second in each, a JavaScript location change third, and a crypto redirect last, with the explicit caution not to rely on it “unless you have no other choice.” None of this makes meta refresh invalid: it is a real, documented, supported method. It is simply a fallback for situations where a server-side redirect genuinely is not available, such as a static host with no server-side scripting, rather than a first choice on a stack that can set real HTTP status codes.

Sources

  1. 1.Redirects and Google Search - Google Search CentralPrimary
  2. 2.How to specify a canonical URL with rel="canonical" and other methods - Google Search Central
Tools

Hreflang XML sitemap generator

Build a sitemap with xhtml:link hreflang annotations for localized pages, with every alternate listed on every URL as Google's documentation requires.