Meta refresh redirects are used on 2 pages, causing SEO and performance issues.
By Seoxpert Editorial · Published
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.
Leaving meta refresh redirects in place can harm SEO rankings and degrade user experience.
The crawler scans page HTML for <meta http-equiv="refresh"> tags that trigger redirects or auto-reloads.
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;They delay navigation, may be ignored by search engines, and do not transfer link equity as effectively as server-side redirects.
It's not recommended. Use HTTP 302 server-side redirects for temporary redirection to ensure proper SEO handling.
No, some crawlers and browsers may ignore meta refresh, leading to missed redirects and indexing issues.
Remove the meta tag and configure your server (e.g., Apache, Nginx) to issue a 301 or 302 HTTP redirect.
Run a scan to see if Pages Using Meta Refresh Redirects affects your pages.
Scan my website →