What is a meta refresh redirect?

Meta refresh redirect, explained

Meta refresh runs in the browser, not the server. The server returns 200 and a page, and the tag in the page head tells the browser to go somewhere else after a number of seconds. It's the fallback when you can't configure server redirects, which happens on some static hosts, legacy CMSs and page builders.

Google's redirect documentation lists how it reads them. A meta refresh with a 0-second delay, which fires as soon as the page loads, is treated as a permanent redirect, the same family as 301 and 308. A delayed meta refresh is treated as temporary. The same rules apply to the Refresh HTTP header. JavaScript location redirects are listed as a last resort, because they only work if Google renders the page.

Google still says server-side redirects are the best way to make sure Google Search and people get to the correct page. Meta refresh adds a page load before the real one, can be skipped by some bots, and can confuse users when the delay is visible. A delayed refresh on a page with content can also look like a doorway if the destination is unrelated.

Use it when server redirects truly aren't available, set the delay to 0, and add a canonical on the old page pointing to the new URL as a backup signal.

Why it matters for founders

Founders on no-code hosts sometimes can't set server redirects. Knowing that an instant meta refresh counts as permanent means you can still move pages without losing their signals.

Example

Your old landing page lives on a static host with no redirect rules. You replace its content with a head containing an instant meta refresh and a canonical to the new page, and Google swaps the URLs in results.

Common mistakes

• Using a delayed refresh for a permanent move.
• Using meta refresh when you could set a server redirect.
• Relying on JavaScript redirects as the only signal.
• Leaving the old page's content in place under the refresh tag.