Meta Refresh

A meta refresh is an HTML tag placed in a page’s head that tells the browser to reload the page or move to a different URL after a set number of seconds. It works in the browser rather than on the server, so it is a weaker and slower alternative to a proper HTTP redirect.

Written by Paul Hoda, SEO consultant since 2005. Last updated 8 November 2026.

How a meta refresh works

The tag looks like this:

<meta http-equiv="refresh" content="0; url=https://example.com/new-page/">

The number is the delay in seconds. A value of 0 redirects immediately; a value such as 5 shows the page for five seconds first. Without a URL, the tag simply reloads the current page, which some news and live score sites once used to keep content updated.

Because the browser must first download and read the HTML before acting on the tag, a meta refresh is slower than a server-side redirect, which happens before any page content is sent.

How Google treats meta refresh

Google’s documentation says it understands meta refresh redirects. An instant meta refresh is treated as a permanent redirect, similar to a 301 redirect.

A delayed meta refresh is treated as a temporary redirect, more like a 302 redirect. Google still recommends server-side redirects where possible, and other search engines and tools may handle meta refresh less reliably.

Why server-side redirects are better

  • Speed: the visitor does not wait for a page to load before moving on.
  • Clarity: the status code clearly says whether a move is permanent or temporary, as explained under HTTP status codes.
  • User experience: delayed refreshes can be confusing, and the back button may bounce users forward again.
  • Accessibility: automatic refreshes can disorient people using screen readers, and accessibility guidelines advise against timed refreshes users cannot control.

When a meta refresh is acceptable

Sometimes you cannot change server settings, for example on some hosted platforms or static hosting with no redirect support. In those cases an instant meta refresh is a reasonable fallback, ideally combined with a canonical tag pointing to the new URL and a visible link for users. It is a better option than a JavaScript redirect if the page might not render scripts reliably.

How to find meta refresh tags

  1. Crawl the site with an SEO crawler; most report meta refresh tags and their targets.
  2. Check the source of suspect pages for http-equiv="refresh".
  3. Replace them with server-side redirects where you can.
  4. Update internal links to point straight at the final URL, avoiding redirect chains.

A note on old tactics

Delayed meta refresh tags were once used to show search engines one page and send users somewhere else. Google’s spam policies call this a sneaky redirect and treat it much like cloaking: both can lead to penalties.

Key Takeaways

  • A meta refresh redirects or reloads a page from inside the HTML.
  • Google treats an instant meta refresh as permanent and a delayed one as temporary.
  • Server-side 301 or 302 redirects are faster and clearer.
  • Use meta refresh only when server redirects are not possible.
  • Timed refreshes can harm accessibility and user experience.

Related Terms

Need a second opinion on your website? Ask for a free website SEO check, or keep learning in the SEO Encyclopedia.