Is a meta refresh redirect bad for SEO?
Rubric check: meta refresh redirect (check id redirect_meta_refresh)
It's a weak redirect. A meta refresh sends visitors on from inside the page instead of from the server. Google follows it, but it's slower for people and some crawlers and AI tools don't follow it at all.
Why it matters for SEO
Google treats an instant meta refresh as a permanent redirect and a delayed one as temporary. A server-side 301 is still the clearer signal, and it moves people on before the old page loads.
Meta refreshes are often left over from an old site, a hosting "parking" page or a quick fix where server redirects weren't available.
Does this matter for ChatGPT and AI Overviews?
AI crawlers that fetch the page may read the old page's HTML and stop there, without following the refresh. Then they see an empty or outdated page instead of your content.
A 301 works for every crawler, so switching costs little and removes the doubt.
How Rubric scores it
StandardStandard checks are the baseline every other tier is measured against.
Why this tier: Meta refresh is a weak redirect.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 12 points off. Even one failing page costs at least 6 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 1 of 300 sites where Rubric could judge it (0.3%). That is 1 of 287 judged sites in Rubric's 313-site test set and 0 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 1 of 1 times. (Engine build d17c9d9.)
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Find the meta refresh: view source and search for
http-equiv="refresh". It's usually in a theme file, a custom HTML block or an old plugin. - Remove it and add a 301 with a redirect plugin (Redirection, or the redirect manager in Rank Math or Yoast Premium).
- Update links to point straight at the new page.
Shopify
- Search Online Store > Themes > Edit code and page content for
http-equiv="refresh"and remove it. - Add a redirect instead: search for URL redirects in the admin and create one from the old path to the new page.
- Update menu links to the new URL.
Webflow
- Remove the meta refresh from the page's Custom code or from any Embed element.
- Go to Site settings > Publishing > 301 redirects and add the old path and the new page.
- Publish.
Custom code
Replace the tag with a server-side 301. Nginx:
location = /old-page { return 301 https://example.com/new-page; }Then remove <meta http-equiv="refresh" ...> from the old page and update internal links.
Related checks
More status codes and redirects checks · The full AI SEO glossary