Meta refresh detected: the worst way to redirect a page

In brief

A meta refresh is a redirect inside the HTML: slower than a 301, passed less reliably by Google, and often invisible to tools. Replace it with a real server-side HTTP 301 redirect for a clean transfer of the signal.

WarningP2 — CTR / SERP

What is it?

A meta refresh redirect was detected.

Why it hurts SEO and AI

It is the worst way to redirect: slower than a 301, passed less reliably by Google, and invisible to many tools. It often signals an old mechanism or a template hack.

When it is NOT a problem

  • The meta refresh is an intentional reload of the same page (dashboard, status screen), not a redirect to another URL.
  • It is a temporary, non-indexed page (confirmation, internal app redirect) with no SEO stake.
  • You are on the very first crawl: Seogard sets a baseline before it alerts.
Before
<head>
  <meta http-equiv="refresh" content="0; url=/new-page">
</head>
After
# Server-side redirect (HTTP header)
HTTP/1.1 301 Moved Permanently
Location: /new-page

The meta refresh lives in the HTML and runs after load; the 301 is returned by the server first, and Google reads it as a true permanent move.

How to fix it

  1. Find the meta http-equiv="refresh" tag and the target URL it points to.
  2. Set up a server-side 301 redirect (server config, framework, or CDN) to that target.
  3. Remove the meta refresh from the template once the 301 is in place.
  4. Re-crawl to confirm the page returns a 301 and not a 200 with a meta refresh.

This scan checks the HTTP status, noindex and canonical of every page

Is this issue on your site?

Are old meta refresh redirects still lingering on your site? Enter a URL: Seogard analyzes the rendered HTML and detects meta refreshes that should be 301s. Free, no credit card.

By clicking Scan, I certify that I own this site or have permission to crawl it.

  • No credit card
  • Result in ~30 s

What you get back

The redirect passes the SEO signal cleanly and executes instantly.

Seogard catches this regression automatically — through its monitoring for your metas and canonicals.

Frequently asked questions

Does Google follow meta refresh redirects?

Google eventually follows them, especially at delay 0, but treats them worse than a 301 and passes the signal less reliably. A server-side 301 remains the reference.

What is the difference between meta refresh and 301?

A 301 is returned by the server in the HTTP header, before any page; a meta refresh is an instruction inside the HTML, run after load, so it is slower and less reliable.

Related rules

Temporary redirect on removed pageA page removed from the sitemap redirects with a 302/307 (temporary). Google keeps the old URL indexed and is slower to consolidate signals toward the target. If the removal is permanent, a 301 (permanent) redirect passes link equity cleanly. Removal without 410 or 301A page removed from the sitemap returns a bare 404. It works, but the signal is ambiguous: Google keeps re-crawling it for weeks. Permanent deletion — return 410 (faster deindexing); moved content — 301 (preserves backlink equity). Noindex page declared in sitemapThis page is declared in your sitemap but carries a noindex directive (meta tag or X-Robots-Tag header): you are asking Google to index it and ignore it at the same time. Wasted crawl budget and polluted GSC indexing reports. Remove it from the sitemap, or remove the noindex.

Updated July 10, 2026