RankpediaA plain-English encyclopedia of search

Meta Refresh SEO

Tells a browser to reload or redirect to another URL after a set delay, acting as a client-side redirect signal for search engines.

If you have ever used meta refresh for a permanent site move and lost rankings, you know it is weaker than a server-side 301 redirect, especially when paired with on site seo and infographics SEO.

Key points

  • Use a 301 redirect for permanent URL changes, not meta refresh.
  • Set delay to zero seconds if using meta refresh for redirects.
  • Support meta refresh with internal links, canonicals, and XML sitemaps pointing to the destination.
  • Avoid delayed meta refresh on pages you want indexed; it confuses crawlers and users.
  • Treat meta refresh as a fallback, not a primary migration method.

Publisher loses 380 of 500 product pages after move

A publisher moved 500 product pages using a 3-second meta refresh. After three months, Google had indexed only 120 of the new URLs, treating the old URLs as canonical. The site lost 90% of organic traffic. Switching to 301 redirects recovered 90% of traffic within two weeks. The meta refresh was largely ignored because internal links still pointed to the old addresses.

Three ways meta refresh differs from a 301 redirect

  • Client-side vs server-side Meta refresh runs in the browser; search engines may not always execute it when crawling. A 301 redirect is server-sent and always seen.
  • Delay affects interpretation Google treats instant meta refresh (0 seconds) as permanent, similar to a 301 redirect, while delayed refreshes are interpreted as temporary, like a 302, affecting how link equity and ranking signals are passed.
  • No link equity transfer Unlike a 301 redirect, meta refresh may not transfer link equity reliably, especially with a nonzero delay, because search engines may not fully process the redirect or may treat it as a temporary signal.

Three common mistakes with meta refresh

  • Using it for permanent moves Replacing a 301 redirect with meta refresh for a permanent URL change often causes indexing problems and traffic loss.
  • Leaving old signals in place If internal links, canonicals, and XML sitemaps still point to the old URL, search engines may ignore the meta refresh and keep the old page canonical, undermining your on site seo efforts.
  • Setting a nonzero delay on indexed pages A delayed refresh confuses crawlers and users, making the page seen as a redirect rather than content, harming ranking chances.

Common questions

Is meta refresh bad for SEO?

It is not inherently bad, but less reliable than a 301 redirect and can cause indexing issues if used incorrectly.

Does Google treat instant and delayed meta refresh differently?

Yes, Google interprets instant meta refresh as permanent and delayed as temporary, affecting link equity and indexing.

Sources

  1. Google Search Central: Redirects and site moves Guidance on using redirects for site migrations.
  2. Google Search Central: JavaScript redirects and meta refresh How Google handles meta refresh and other client-side redirects.
↑