Pages Using Meta Refresh Redirects
Meta refresh redirects are used on 2 pages, causing SEO and performance issues.
By Seoxpert Editorial · Published
Why it matters
Meta refresh redirects delay user navigation and can be ignored by some search engine crawlers, leading to poor indexing and loss of link equity. They also negatively impact accessibility and user experience compared to server-side redirects.
Impact
Leaving meta refresh redirects in place can harm SEO rankings and degrade user experience.
How it's detected
The crawler scans page HTML for <meta http-equiv="refresh"> tags that trigger redirects or auto-reloads.
Common causes
- Using meta refresh for page redirection instead of server-side redirects
- Legacy code or outdated redirect practices
- Lack of access to server configuration for proper redirects
- Attempting to auto-refresh content for updates
How to fix it
Code examples
Problem: Meta Refresh Redirect
<meta http-equiv="refresh" content="0; url=https://example.com/new-page">Fix: Apache .htaccess 301 Redirect
Redirect 301 /old-page https://example.com/new-pageFix: Nginx 301 Redirect
rewrite ^/old-page$ https://example.com/new-page permanent;FAQ
Why are meta refresh redirects bad for SEO?
They delay navigation, may be ignored by search engines, and do not transfer link equity as effectively as server-side redirects.
Can I use meta refresh for temporary redirects?
It's not recommended. Use HTTP 302 server-side redirects for temporary redirection to ensure proper SEO handling.
Do all browsers and crawlers support meta refresh redirects?
No, some crawlers and browsers may ignore meta refresh, leading to missed redirects and indexing issues.
How do I replace a meta refresh redirect with a server-side redirect?
Remove the meta tag and configure your server (e.g., Apache, Nginx) to issue a 301 or 302 HTTP redirect.
Found this issue on your site?
Run a scan to see if Pages Using Meta Refresh Redirects affects your pages.
Scan my website →