Seoxpert.io
Get started
mediumOn-Page SEO

`<meta http-equiv="refresh">` With Short Delay (<5s)

Pages use <meta http-equiv="refresh"> with a delay under 5 seconds, causing accessibility and SEO problems.

By Seoxpert Editorial · Published

Why it matters

Short-delay meta-refresh redirects violate WCAG 2.1 accessibility guidelines, making content unreadable for some users. They also confuse search engines, potentially splitting ranking signals and harming SEO. Users may get stuck in redirect loops, impacting usability.

Impact

Leaving this unresolved can harm accessibility, SEO rankings, and user experience.

How it's detected

An automated crawler scans for <meta http-equiv="refresh"> tags with a delay value less than 5 seconds in the HTML head.

Common causes

  • •Using meta-refresh for quick client-side redirects instead of HTTP redirects
  • •Legacy code or templates with outdated redirect methods
  • •Attempting to force page reloads after form submissions
  • •Misunderstanding of SEO and accessibility implications

How to fix it

Replace the meta-refresh tag with an HTTP 301 or 302 redirect at the server or CDN level for proper SEO and accessibility. If a client-side redirect is necessary, set the delay to at least 10 seconds and provide a visible link for users to proceed manually. Avoid using meta-refresh for automatic navigation whenever possible.

Code examples

Problematic meta-refresh (delay <5s)

<meta http-equiv="refresh" content="1;url=/">

Recommended HTTP 301 redirect (server-side)

HTTP/1.1 301 Moved Permanently
Location: /

Accessible client-side redirect (delay ≥10s with manual link

<p>Thank you for subscribing! You will be redirected in 10 seconds. <a href="/">Click here to continue immediately.</a></p>
<meta http-equiv="refresh" content="10;url=/">

FAQ

Why is a meta-refresh delay under 5 seconds a problem?

It doesn't give users enough time to read the content, violates accessibility guidelines, and can confuse search engines.

How should I implement redirects for SEO and accessibility?

Use HTTP 301 or 302 redirects at the server or CDN level instead of meta-refresh for automatic navigation.

Is it ever acceptable to use meta-refresh?

Only for non-critical, user-initiated flows with a delay of 10 seconds or more and a visible manual link to the target page.

Can meta-refresh affect my site's SEO rankings?

Yes, improper use can split ranking signals and confuse search engines, potentially harming your site's SEO.

Found this issue on your site?

Run a scan to see if `<meta http-equiv="refresh">` With Short Delay (<5s) affects your pages.

Scan my website →