Info

A page redirects with a meta refresh

The short version

Use an HTTP redirect instead; it is faster and clearer to search engines.

What it means

One step of the chain isn't an HTTP redirect: the page answered 200 and then sent the browser on with <meta http-equiv="refresh"> or a JavaScript line such as window.location = "...". We read the page to find this; we never run its scripts.

Why it matters

The browser has to download and start rendering the page before it moves on, which is slower and often flashes an empty page. Search engines treat these as weaker signals than a 301 and may keep the intermediate page in results. Link checkers, previews in chat apps and scripts that don't run JavaScript stop at the intermediate page entirely.

How to fix it

  1. Find the page in the chain that moves visitors on.
  2. Replace it with a server redirect: in Nginx return 301 https://example.com/new;, in Apache Redirect 301 /old https://example.com/new, or in your hosting panel's redirect settings.
  3. If the page decides where to go based on the visitor, such as language, do it on the server and send a 302 or 307 there.
  4. Keep a plain link on the old page as a fallback while the change rolls out.

Check it worked

Run the redirect tracer again. Each hop should show an HTTP redirect status, and the finding should be gone.