Meta refresh checker

What the meta refresh checker does

This tool checks whether a webpage contains a meta refresh directive and reports what it found. A meta refresh is an HTML instruction that tells the browser to reload the current page or navigate to another URL after a specified delay.

The directive looks like <meta http-equiv="refresh" content="5; url=https://example.com/">. The first number is the delay in seconds, and the optional URL is the destination. Without a URL, the page simply reloads itself.

Why meta refresh matters for SEO

Search engines generally prefer server-side redirects, such as 301 or 302 responses, over meta refresh. A meta refresh happens after the page has already loaded, so it can waste crawl budget, introduce delay, and behave inconsistently across clients. For permanent moves, a server-level redirect is the cleaner choice.

Meta refresh can also harm user experience. A short delay with an unexpected jump can confuse visitors, and some browsers or extensions block the behavior. When used as an automatic reload, it can disrupt reading or interfere with form entry.

How to interpret the result

If a meta refresh is detected, note the delay and the destination. A zero-second delay with a URL acts similarly to a redirect, though not identically. A longer delay gives users time to read but is still less reliable than a proper HTTP redirect. If the directive reloads the same page, consider whether the behavior is necessary at all.

If no meta refresh is found, the page does not use this mechanism. That is usually the desired state for modern sites, which handle redirects and updates at the server or application level.

Better alternatives

• Use 301 redirects for permanent URL changes, so link equity and signals transfer cleanly.
• Use 302 or 307 redirects for temporary moves.
• Update content dynamically with JavaScript when a page needs to refresh data without a full reload.
• Avoid refresh delays that interrupt users unexpectedly.

Practical workflow

Check pages that recently moved or were replaced. If a meta refresh is present, confirm whether a server-side redirect can replace it. Review legacy pages and landing pages for forgotten refresh directives, and test the user experience on both desktop and mobile before deciding to keep any refresh behavior.

Limitations

The checker reports meta refresh directives present in the HTML response. It does not detect JavaScript-based redirects or server-side redirects, which are separate mechanisms.