Skip to content

The page redirects with a refresh, not an HTTP redirect

meta-refresh-redirectminor
On this page

Why it matters

  • Google's redirects guide reads an instant meta refresh as a permanent redirect and a delayed one as a temporary redirect, and asks for a permanent server-side redirect (301 or 308) whenever possible.
  • A delayed refresh shows the old page first: visitors wait, may act on it, and the back button returns them to it.
  • A refresh needs the page itself to load and be read, where an HTTP redirect is answered before any HTML.

Example

Wrong
<meta http-equiv="refresh" content="5; url=/" />
Right
<meta http-equiv="content-language" content="ar" />

How to fix

Answer the old address with a permanent redirect from the server:

nginx
location = /ar/offers-old/ { return 301 /ar/offers/; }
  • On Apache: Redirect 301 /ar/offers-old/ /ar/offers/. On a hosted platform, use its redirects setting.
  • Keep a refresh only where the server cannot redirect, and make it instant (content="0; url=…").
  • A page that reloads itself on a timer (no address) is not a redirect, and is not reported.

How we detect

  1. We read <meta http-equiv="refresh"> and the Refresh response header, as HTML reads them: a delay, then the address.
  2. A refresh with an address is reported, as instant (0 seconds) or delayed.
  3. A refresh without an address reloads the page and is left alone.

Redirects a script makes (location.href = …) are not read here.