Meta Refresh SEO
A meta refresh is an HTML meta tag that tells a browser to reload the current page or open another URL after a set number of seconds, and it runs on the client side rather than the server.
Key takeaways
- Meta refresh is a client-side redirect; it is weaker than a 301 redirect.
- Instant (0-second) meta refresh is treated like a temporary redirect by Google.
- Delayed meta refresh can harm SEO and user experience.
- Always support meta refresh with proper internal links, canonicals, and sitemaps.
- For permanent URL changes, use a 301 redirect instead.
Meta refresh can act like a redirect signal, but it is usually weaker and less reliable than a server-side 301 or 302 redirect.
Example
A page at old-page.html contains <meta http-equiv="refresh" content="0; url=https://example.com/new-page">. When a user or crawler visits old-page.html, the browser immediately loads new-page.html. This is an instant meta refresh redirect.
When should I use this?
- For temporary, browser-driven navigation (e.g., a splash page that auto-redirects after a few seconds).
- When you have no server access to set up a 301 redirect.
- For time-sensitive content that needs a refresh (e.g., a live scoreboard).
- As a fallback when JavaScript redirects are not possible.
What it is not
- Not a server-side redirect: It runs in the browser, not on the server.
- Not a permanent redirect: Google treats instant meta refresh like a temporary redirect (302), not a permanent one (301).
- Not a replacement for canonical tags: It does not consolidate duplicate content signals.
- Not a reliable indexing signal: Delayed meta refresh can confuse crawlers and hurt indexation.
Quick start
- Identify the page you want to redirect from.
- Open the HTML file and locate the
<head>section. - Add the meta refresh tag:
<meta http-equiv="refresh" content="0; url=https://example.com/new-url">. - Set
content="0"for instant redirect; avoid delays >0 seconds for SEO. - Update internal links, canonical tags, and XML sitemaps to point to the new URL.
- Test the redirect in a browser and with Google Search Console.
Common mistakes
- Using meta refresh instead of a server-side 301 redirect for permanent URL changes.
- Assuming all meta refreshes are equivalent; Google distinguishes between instant and delayed refresh behavior.
- Leaving internal links, canonicals, and XML sitemaps pointing to the old URL after using meta refresh.
- Setting a delayed refresh on pages intended for indexing, which can confuse crawlers and users.
Next step
FAQ
Is meta refresh bad for SEO?
It depends. Instant meta refresh (0 seconds) is often treated like a temporary redirect by Google, but it is weaker than a 301 redirect. Delayed meta refresh can confuse users and crawlers, negatively impacting SEO. It is generally not recommended for permanent URL changes.
What is the difference between meta refresh and a 301 redirect?
A 301 redirect is a server-side HTTP status code that permanently points a browser and search engine to a new URL. A meta refresh is a client-side HTML tag that can introduce a delay and is less reliable for passing link equity and indexing signals.
Related topics
Sources
- Google Search Central — Most authoritative source for how Google interprets redirects, indexing signals, and site moves.
- Google Search Central: Redirects and site moves — Best source for replacement guidance when a page or site changes URLs.
- Google Search Central: JavaScript redirects and meta refresh — Relevant to how Google handles redirect mechanisms outside standard server-side redirects.
- Google Search Central: Consolidate duplicate URLs — Useful for canonicalization and related signals when a refresh or redirect is involved.
Reviewed by Lucía Marín, Founding editor.