Meta refresh redirects and crawlers
A meta refresh redirect uses an HTML meta tag to send the browser to another URL after a delay. Google can follow meta refreshes, but its guidance is to prefer server-side HTTP redirects (301/302) because they are clearer, faster, and unambiguous. An instant (zero-delay) meta refresh is treated more like a redirect, while a delayed one is weaker and can confuse users and crawlers.
What this means
A meta refresh redirect is written in HTML, typically as a meta tag in the document head that instructs the browser to navigate to another URL, optionally after a delay in seconds. Because it lives in the page body, the client must download and parse the HTML before the redirect happens.
This makes it a client-side redirect, in contrast to an HTTP 301 or 302 which is delivered in the response headers before any HTML. Google supports meta refresh redirects but recommends server-side HTTP redirects when you control the server.
Instant versus delayed
Google distinguishes an instant meta refresh (zero delay) from a delayed one. An instant meta refresh is treated similarly to a redirect and Google generally follows it to the target. A delayed meta refresh — for example a 'you will be redirected in 5 seconds' page — is a weaker signal and can be a poor user experience.
Where possible, replace meta refreshes with HTTP redirects. Reserve meta refresh for cases where you genuinely cannot set server headers, and even then prefer an instant refresh over a delayed one.
- Meta refresh is client-side; the HTML must load first
- Google can follow it but prefers server HTTP 301/302
- Instant (0s) meta refresh is treated more like a redirect
- Delayed meta refresh is a weaker, more confusing signal
Migration guidance
For permanent moves, a server-side 301 is the clearest signal and consolidates ranking signals to the destination. For temporary moves, use 302/307. A meta refresh should be a last resort when server configuration is impossible.
If you must use meta refresh, point it directly at the final destination to avoid a client-side redirect chain, and verify in logs that crawlers reach the destination URL rather than getting stuck on the intermediate page.
How it appears in analytics and logs
A meta refresh in the HTML means the redirect happens client-side after the page loads, not at the HTTP layer. Crawlers can follow it but treat it as a weaker, slower signal than a server-side 301 or 302.
Diagnostic use case
Replace meta refresh redirects with proper HTTP redirects where possible, and understand how Google interprets instant versus delayed meta refreshes when you cannot change server config.
What WebmasterID can help detect
WebmasterID records crawler requests to both the source and destination URLs server-side, so you can see whether crawlers actually followed a meta refresh to the intended target.
Common mistakes
- Using meta refresh when a server-side 301 is available and clearer.
- Adding a multi-second delay that worsens user experience and weakens the signal.
- Chaining meta refresh through several intermediate URLs.
- Assuming a meta refresh consolidates ranking signals as strongly as a 301.
Privacy and accuracy notes
Meta refresh detection inspects your own page markup, not visitors. WebmasterID treats redirects as a crawl-routing topic and never ties them to visitor identity.
Related pages
- JavaScript redirects and crawling
A JavaScript redirect changes the location in script (for example via window.location) and only executes after the page is fetched and rendered. Google can follow JavaScript redirects once it renders the page, but its guidance is to prefer server-side HTTP redirects because they are processed immediately and unambiguously. JavaScript redirects add latency and depend on successful rendering.
- Redirect best practices for crawlers
Good redirects keep crawlers and link equity flowing to the right destination. The essentials: use 301 or 308 for permanent moves and 302 or 307 only for genuinely temporary ones, redirect each old URL directly to its final target in a single hop, map to the closest equivalent page rather than dumping everything on the homepage, and avoid loops. These choices preserve indexing signals and conserve crawl budget.
- HTTP 301 Moved Permanently for crawlers
301 Moved Permanently tells clients and crawlers that a resource has permanently moved to a new URL. It is the standard signal for migrations and URL changes: crawlers follow it, update their index over time, and consolidate ranking signals onto the new location. Use it whenever content has a stable new home.
- Website observability
See whether crawlers followed a redirect to the intended target.
Sources and verification notes
- Google Search Central — Redirects and Google SearchMeta refresh support; server-side HTTP redirects preferred.
- MDN — meta http-equiv refresh
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.