RankWiki

Technical SEO

Meta Refresh SEO

A meta refresh is an HTML meta tag that directs a browser to reload the current page or navigate to another URL after a specified delay, functioning as a client-side redirect mechanism.

Also called
Meta refresh redirect
Applies to
HTML pages, client-side navigation
Commonly confused with
Server-side redirect (301/302)

Key points

  • Meta refresh operates on the client side, not the server side, making it less reliable than server-side redirects.
  • Google treats an instant (0-second) meta refresh differently from a delayed one, often interpreting the instant version as a permanent redirect.
  • Using meta refresh for permanent URL changes is weaker than a 301 redirect and should not be the primary migration method.
  • If meta refresh is used, supporting signals such as the canonical tag and internal links must point to the destination URL.
  • Delayed meta refresh on pages intended for indexing can confuse search engine crawlers and harm indexing.

Why it matters

Meta refresh matters for SEO because it can act as a redirect signal, but it is less reliable and weaker than server-side alternatives. A 301 redirect is the preferred method for permanent URL changes because it passes link equity cleanly and is understood by search engines as a definitive move. Meta refresh, by contrast, runs in the browser and can be interpreted inconsistently. Google distinguishes between instant (0-second) and delayed meta refresh: instant redirects are often treated like permanent redirects, while delayed ones are treated as temporary. This distinction means that using a non-zero delay can signal to search engines that the redirect is not permanent, potentially diluting ranking signals. Furthermore, if a page with a meta refresh is indexed, search engines may index the wrong URL or fail to index the destination at all, especially if other signals like internal links or the canonical tag are not aligned.

Where it changes your decision

The choice to use meta refresh over server-side redirects affects three concrete situations:

  • Permanent URL migration: A 301 redirect is far more reliable than meta refresh. Meta refresh should only be a fallback if server-side redirects are impossible, and even then, supporting signals like the canonical tag must point to the destination.
  • Delayed navigation on indexed pages: Setting a non-zero meta refresh on a page you want indexed can cause crawlers to treat the page as a temporary redirect, reducing the chance of the page appearing in search results.
  • User experience on timed reloads: For scenarios like landing pages that automatically refresh after a few seconds, a zero-second meta refresh behaves more like a redirect, while any delay may frustrate users and lead to higher bounce rates.
Read next Meta Description After understanding meta refresh, reading about the meta description helps you control how search results display snippets, which is a separate but complementary on-page signal.

Sources

  1. Google Search Central Most authoritative source for how Google interprets redirects, indexing signals, and site moves.
  2. Google Search Central: Redirects and site moves Best source for replacement guidance when a page or site changes URLs.
  3. Google Search Central: JavaScript redirects and meta refresh Relevant to how Google handles redirect mechanisms outside standard server-side redirects.
  4. Google Search Central: Consolidate duplicate URLs Useful for canonicalization and related signals when a refresh or redirect is involved.