Page uses meta refresh redirect — the fix
This page uses a <meta http-equiv="refresh"> tag to redirect users to another URL. Meta refresh redirects are slower than server-side redirects and may not pass full link equity.
Where this fits: crawlability in SEO
Crawlability is whether search engine bots can physically reach and read your pages. Before Google can rank anything, Googlebot has to fetch it: follow links to it, receive a successful response, and parse the HTML. Crawl problems are silent — the page looks fine in a browser while bots hit walls (robots rules, broken chains, server errors, infinite URL spaces). Because everything downstream depends on the crawl, fixing crawlability issues usually unlocks more value per hour than any other SEO work.
Why page uses meta refresh redirect hurts your rankings
Google treats meta refresh redirects with a delay of 0 as 301 redirects, but longer delays may be treated as soft redirects that do not pass full ranking signals. Meta refreshes also create a poor user experience with a visible flash of content before redirection. Server-side 301 redirects are always preferred.
This is a medium-severity issue: individually modest, but it compounds — dozens of medium issues across hundreds of pages add up to a real quality deficit in how search engines assess the site.
How to fix it
Replace the meta refresh redirect with a proper server-side 301 redirect. Configure the redirect in your web server (nginx, Apache) or application routing layer. If a server-side redirect is not possible, use JavaScript window.location as a fallback, but server-side is strongly preferred.
Crawlability best practices
- Keep robots.txt minimal and deliberate — block admin/duplicate spaces, never CSS/JS assets.
- Maintain an XML sitemap that lists only canonical, indexable, 200-status pages, and reference it in robots.txt.
- Keep every important page within 3 clicks of the homepage.
- Return proper status codes: 200 for content, 301 for permanent moves, 410 for gone — never soft-404s.
- Collapse redirect chains to a single hop; update internal links to point at final URLs.
- Keep URL parameters under control — infinite filter/sort combinations burn crawl budget.
The full library: SEO best practices, by category.
Frequently asked questions
What does "Page uses meta refresh redirect" mean?
This page uses a <meta http-equiv="refresh"> tag to redirect users to another URL. Meta refresh redirects are slower than server-side redirects and may not pass full link equity.
Why does page uses meta refresh redirect matter for SEO?
Google treats meta refresh redirects with a delay of 0 as 301 redirects, but longer delays may be treated as soft redirects that do not pass full ranking signals. Meta refreshes also create a poor user experience with a visible flash of content before redirection. Server-side 301 redirects are always preferred.
How do I fix page uses meta refresh redirect?
Replace the meta refresh redirect with a proper server-side 301 redirect. Configure the redirect in your web server (nginx, Apache) or application routing layer. If a server-side redirect is not possible, use JavaScript window.location as a fallback, but server-side is strongly preferred.
How serious is this issue?
This is a medium-severity issue: individually modest, but it compounds — dozens of medium issues across hundreds of pages add up to a real quality deficit in how search engines assess the site. It belongs to the crawlability family of checks.
How do I find every page affected by this on my site?
Run a free Dr Urls audit: it crawls your site, detects page uses meta refresh redirect on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by page uses meta refresh redirect, and hands you a ready-made fix task.
Check my site free