Fix guides · Accessibility
How to fix “The document uses <meta http-equiv="refresh">”
Pages that reload or redirect themselves after a delay pull visitors away mid-read. How to replace a meta refresh with a proper redirect.
- Time to fix
- 10–20 minutes
- Skill needed
- Developer
- Who notices
- Screen reader users and slow readers
Why it matters
A meta refresh tag tells the browser to reload the page, or go to another one, after a set number of seconds. Visitors don't control when it happens.
Screen reader users lose their place when the page reloads, and anyone who reads slowly may be moved on before they finish.
“Since users do not expect a page to refresh automatically, such refreshing can be disorienting.”
Before you start
- If the tag redirects to another address, replace it with a server-side 301 redirect, which is also better for search engines.
- If it reloads the page to show fresh content, update that content with a script instead, or let visitors refresh themselves.
- A delay of 0 seconds (an instant redirect) isn't flagged, but a server redirect is still better.
Fix it on your platform
Shopify
- Search your theme code for http-equiv="refresh" and remove it. For addresses that moved, create a URL redirect in your Shopify admin instead (search the admin for "URL redirects").
WordPress
- Search your theme and custom HTML blocks for http-equiv="refresh". Use a redirection plugin or your host's redirects for addresses that moved.
Webflow
- Remove the meta tag from your custom code, and set up the redirect in Site settings → Publishing → 301 redirects.
Wix
- Remove the tag from your Custom Code settings, and set up a 301 redirect with Wix's URL Redirect Manager in your dashboard's SEO tools.
Squarespace
- Remove the tag from code injection, and add the redirect in the URL Mappings panel.
Next.js
- Use redirects in next.config, or redirect() in a server component, instead of a meta tag.
async redirects() {
return [{ source: "/old-page", destination: "/new-page", permanent: true }];
},Any other site
- Remove the meta refresh tag and configure a 301 redirect on the server.
<meta http-equiv="refresh" content="5; url=/new-page">Check that it's fixed
- View the page source and search for "refresh": the tag should be gone.
- Re-run your StudioLNC audit: the issue should be gone.
Find every issue like this on your site
Free audit of performance, accessibility, SEO and security, with fixes for your platform.