Meta refresh

Quick win

Found on 1% of audited stores.

Remove or disable the `<meta http-equiv="refresh">` tag that forces an automatic page reload, or replace any redirect use-case with a server-side redirect instead.

What it is

A `<meta http-equiv="refresh">` tag in the `<head>` of a page tells the browser to automatically reload the current page — or jump to a different URL — after a set number of seconds, without the visitor doing anything. For example, `<meta http-equiv="refresh" content="10">` reloads the page every 10 seconds. WCAG Success Criterion 2.2.1 (Timing Adjustable) requires that any time limit on content can be turned off, adjusted, or extended by the user — and an automatic meta-refresh gives visitors no such control.

Why it matters

Automatic page refreshes are disorienting and harmful for people with disabilities. Screen-reader users lose their place in the page; people with cognitive or motor disabilities may not finish reading or complete a form before the page reloads or redirects them. Failing WCAG 2.2.1 exposes your store to legal risk under accessibility laws such as the ADA (US), EAA (EU), and AODA (Canada). Search engines also flag unexpected client-side refreshes as a poor signal — a proper server-side redirect is faster and more reliable for SEO. Removing this tag improves user experience, reduces legal exposure, and can marginally improve crawl efficiency for your product pages.

How to fix it

  1. Audit every page's HTML `<head>` section for a tag matching `<meta http-equiv="refresh" content="...">`. This tag may be hard-coded in a theme file or injected by an app/plugin.
  2. Determine the intent: (a) periodic self-reload (e.g. to refresh a countdown or live stock level) or (b) redirect to another URL after a delay.
  3. If the intent is a periodic self-reload, replace the meta-refresh with a JavaScript-based solution that can be paused by the user, or use server-sent events / AJAX polling so the page content updates without a full reload — and gives users control.
  4. If the intent is to redirect visitors to another page, remove the meta-refresh entirely and implement a proper HTTP 301 (permanent) or 302 (temporary) server-side redirect instead — this is faster, inaccessible-proof, and better for SEO.
  5. If a meta-refresh cannot be eliminated for a legacy reason, ensure the delay is set to 0 seconds (an instant redirect) — WCAG allows a 0-second redirect because the user has no time limit imposed on them — AND simultaneously implement the server-side redirect so the meta-refresh becomes redundant.
  6. Test the page with a screen reader (NVDA + Firefox or VoiceOver + Safari) and re-run your accessibility scanner to confirm the axe `meta-refresh` rule no longer flags the page.

Fix it on your platform

Pick your platform for the exact steps.

How to fix meta refresh on Shopify
  1. Go to Online Store → Themes → click the three-dot menu beside your active theme → Edit code.
  2. Open the file `layout/theme.liquid` (this wraps every storefront page).
  3. Use Cmd/Ctrl+F to search for `http-equiv` or `meta.*refresh`. Remove the entire `<meta http-equiv="refresh" ...>` line.
  4. If the tag appears in a section or snippet file (check snippets/ and sections/), search each file the same way.
  5. If you need a redirect, use Shopify's built-in URL redirect tool: Online Store → Navigation → URL Redirects → Add URL Redirect. This creates a proper 301.
  6. Save the theme file, then preview and re-scan to confirm the tag is gone.
Full Shopify guide →Official Shopify docs ↗
How to fix meta refresh on WooCommerce
  1. In WordPress admin go to Appearance → Theme File Editor (or use a code editor via FTP/SSH).
  2. Open your active theme's `header.php` (or `functions.php` if the tag is injected programmatically). Search for `http-equiv` or `meta.*refresh` and delete the line.
  3. If the tag comes from a plugin, go to Plugins → Installed Plugins, deactivate plugins one at a time while re-checking the page source, until the responsible plugin is identified — then check that plugin's settings to disable the redirect/refresh feature.
  4. For URL redirects, install the free 'Redirection' plugin (johngodley.com) and create a 301 redirect there instead of using a meta-refresh.
  5. Save changes, clear any caching plugin (e.g. WP Rocket, W3 Total Cache), and re-scan.
Full WooCommerce guide →Official WooCommerce docs ↗
How to fix meta refresh on BigCommerce
  1. Go to Storefront → My Themes → click Customize on your active theme → then Edit Theme Files (requires the Stencil CLI or the in-browser editor).
  2. Open `templates/layout/base.html` (Stencil themes) and search for `http-equiv`. Remove the matching `<meta>` tag.
  3. If the tag is not in the layout file, search all template and partial files for `refresh`.
  4. For redirects, use BigCommerce's built-in redirect manager: Server Settings → 301 Redirects (or via the API) — never use meta-refresh for redirects.
  5. Save, publish the theme, and re-scan the affected page.
Full BigCommerce guide →Official BigCommerce docs ↗
How to fix meta refresh on Wix
  1. Wix does not expose raw `<head>` HTML directly for most pages, but custom code can be added via Settings → Custom Code (Wix Business & eCommerce plans) or via the Velo (Dev Mode) `<head>` code area.
  2. Open the Wix Editor → click the page in question → go to Settings → Advanced → Custom Code (or in Velo: open `masterPage.js` or the page's code panel).
  3. Search for any snippet containing `http-equiv` or `meta.*refresh` and delete it.
  4. For redirects, use Wix's URL Redirect Manager: go to Marketing & SEO → SEO Tools → URL Redirect Manager → Add Redirect, and create a 301 redirect there.
  5. Publish the site and verify the page source no longer contains the meta-refresh tag.
Full Wix guide →Official Wix docs ↗
How to fix meta refresh on Squarespace
  1. Go to Website → Pages → select the affected page → click the gear icon (Page Settings) → Advanced → Page Header Code Injection.
  2. Remove any `<meta http-equiv="refresh" ...>` tag pasted there.
  3. Also check Settings → Advanced → Code Injection (site-wide header) for the same tag.
  4. For redirects, use Squarespace's URL Mapping tool: Settings → Advanced → URL Mappings. Add a line like `/ -> /new-page 301` following Squarespace's syntax.
  5. Save and publish, then verify via View Source that the meta-refresh is gone.
Full Squarespace guide →Official Squarespace docs ↗
How to fix meta refresh on Webflow
  1. Open your Webflow project in the Designer. Go to Project Settings → Custom Code → Head Code (for site-wide injection) or open the specific page → Page Settings → Custom Code → Inside <head> tag.
  2. Find and delete any `<meta http-equiv="refresh" ...>` snippet.
  3. For redirects, use Webflow's built-in 301 redirect tool: Project Settings → Hosting → 301 Redirects → Add Redirect.
  4. Publish the site and confirm via browser View Source that the tag is absent.
Full Webflow guide →Official Webflow docs ↗
How to fix meta refresh on Adobe Commerce (Magento)
  1. SSH into the server or use your IDE to open the theme's root layout file, typically `app/design/frontend/<Vendor>/<theme>/Magento_Theme/layout/default_head_blocks.xml` or the base theme's `default.xml`.
  2. Search all layout XML files and `.phtml` templates for `http-equiv` and remove the relevant `<block>` or inline `<meta>` tag.
  3. If the redirect is set via a CMS page's 'Custom Layout Update' XML field, go to Content → Pages → Edit the page → Design → Layout Update XML and remove the meta tag there.
  4. For proper redirects, use Stores → Configuration → Web → URL Options, or add a server-level redirect in your `.htaccess` / Nginx config (e.g., `Redirect 301 /old-path /new-path`).
  5. Run `bin/magento cache:flush` and re-scan the page.
Full Adobe Commerce (Magento) guide →Official Adobe Commerce (Magento) docs ↗
How to fix meta refresh on WordPress.org
  1. Go to Appearance → Theme File Editor and open `header.php` for your active theme. Search for `http-equiv` and delete the meta tag if found.
  2. If using a child theme, check the child theme's `header.php` and `functions.php` as well.
  3. Search active plugins: some SEO or caching plugins can inject meta-refresh tags — check each plugin's settings and disable the feature, or deactivate plugins to isolate the source.
  4. For redirects, use the free 'Redirection' plugin to manage 301/302 redirects without touching code.
  5. Clear caches (plugin cache, server cache, CDN cache) and re-test.
Full WordPress.org guide →Official WordPress.org docs ↗
How to fix meta refresh on Wix Studio
  1. Open Wix Studio Editor → select the page → open the Velo panel (enable Dev Mode if not already on).
  2. In the page's `<head>` code block or `masterPage.js`, search for `http-equiv` or `refresh` and remove the tag or script.
  3. For site-wide head injection, go to Site → Settings → Custom Code and inspect any head code snippets.
  4. Use the URL Redirect Manager (Marketing & SEO → SEO Tools → URL Redirect Manager) for any needed redirects.
  5. Publish and verify via browser View Source.
Full Wix Studio guide →Official Wix Studio docs ↗
How to fix meta refresh on PrestaShop
  1. Access your server via FTP/SSH and open your active theme folder at `/themes/<your-theme>/`.
  2. Open `templates/_partials/head.tpl` (or `header.tpl` for older themes) and search for `http-equiv`. Remove the matching line.
  3. If injected by a module, go to Modules → Module Manager, identify the module, and disable the meta-refresh feature in its configuration.
  4. For redirects, configure a `.htaccess` 301 redirect or use a dedicated redirect module from the PrestaShop marketplace.
  5. Clear the PrestaShop cache under Advanced Parameters → Performance → Clear Cache, then re-scan.
Full PrestaShop guide →Official PrestaShop docs ↗

Does your site have this issue?

Run a free SEOLZ scan to find meta refresh — and every other issue — across your whole site in minutes.

Scan my site free

Frequently asked questions

What is Meta refresh?

A `<meta http-equiv="refresh">` tag in the `<head>` of a page tells the browser to automatically reload the current page — or jump to a different URL — after a set number of seconds, without the visitor doing anything. For example, `<meta http-equiv="refresh" content="10">` reloads the page every 10 seconds. WCAG Success Criterion 2.2.1 (Timing Adjustable) requires that any time limit on content can be turned off, adjusted, or extended by the user — and an automatic meta-refresh gives visitors no such control.

Why does meta refresh matter?

Automatic page refreshes are disorienting and harmful for people with disabilities. Screen-reader users lose their place in the page; people with cognitive or motor disabilities may not finish reading or complete a form before the page reloads or redirects them. Failing WCAG 2.2.1 exposes your store to legal risk under accessibility laws such as the ADA (US), EAA (EU), and AODA (Canada). Search engines also flag unexpected client-side refreshes as a poor signal — a proper server-side redirect is faster and more reliable for SEO. Removing this tag improves user experience, reduces legal exposure, and can marginally improve crawl efficiency for your product pages.

How do I fix meta refresh?

Remove or disable the `<meta http-equiv="refresh">` tag that forces an automatic page reload, or replace any redirect use-case with a server-side redirect instead.

Authoritative references

Related Accessibility (WCAG) issues