In Neova Runs from the crawl itself: nothing to set up.
Rule last reviewed October 17, 2026 · Guide updated September 28, 2026
Use server-side 301 or 308 redirects. Use meta refresh only when server redirects are impossible, and then with a 0 second delay.
How Neova Finds It
Neova requests every address and reads what the server answers.
Why It Matters
Redirect issues can break user journeys and waste crawl budget.
The Ticket It Writes
RE-010 · Redirects Using a Meta Refresh
How to Check the Fix: 1. Run the check again in Neova 2. Spot-check sample URLs across affected templates 3. Record the re-check date and period label next to the baseline
Neova writes this ticket for every affected page group and sends it to Jira, Linear, Asana and the rest, after you approve it.
The Full Guide
TL;DR: A meta refresh is a client-side redirect written into the HTML, like <meta http-equiv="refresh" content="0;url=...">. It works, but it is a weaker, slower, less reliable way to redirect than a proper server-side 301. If this check flagged one, replace it with a real HTTP redirect wherever you can.
Type
Client-side redirect
Severity
Low to medium
Better option
301 / 302 header
Best tool
Screaming Frog
Fix
Swap for server redirect
The meta refresh is one of the oldest tricks in web history, older than the CSS box model. You drop a tag in the head of a page and the browser reloads to a new URL after a set number of seconds. It still works in every browser today. That is exactly why it survives in codebases: it needs no server access, no config file, no htaccess. Anyone who can edit HTML can write one. The problem is that "it works" and "it is the right way to redirect for SEO" are two different claims, and the meta refresh only satisfies the first.
The content attribute holds two things: a delay in seconds, then a URL to send the browser to. A delay of 0 means redirect immediately. Any number higher than that means the current page shows for that many seconds first, then the browser navigates away. You have seen the delayed version on "you are being redirected, click here if nothing happens" pages.
The critical distinction: this is a client-side redirect. The server sends back a normal 200 OK with a full HTML page, and the browser reads the tag and decides to navigate somewhere else. Compare that to a server-side 301 or 302, where the server never sends page content at all, it just returns a redirect status code and a Location header, and the browser follows it before rendering anything.
Server-Side Versus Meta Refresh
301 server redirect (preferred)Meta refresh (client-side)Browser requests old URLServer returns 301 + LocationBrowser goes straight to new URLNo page rendered. Full signal passed.Browser requests old URLServer returns 200 + full pageBrowser reads tag, thennavigates after delayExtra hop. Weaker, slower signal.
Why It Matters for SEO
Google can and does follow meta refreshes. John Mueller has said an instant meta refresh, delay zero, is treated similarly to a 301. So this is not a catastrophe. But "similar to" is not "the same as," and the meta refresh loses on several practical fronts:
It is slower. The browser has to download the whole page, parse the head, and then navigate. A server redirect happens before any content is sent. On a slow connection the user sees a flash of the wrong page, or worse, sits on it for the delay you set.
The signal is ambiguous. A 301 is an unambiguous "permanent, pass the equity." A meta refresh has no permanence code. Google has to infer intent from the delay value. Zero delay reads like a redirect, a non-zero delay reads more like a temporary interstitial.
It does not exist for non-HTML. You cannot meta refresh a PDF or an image. Server redirects handle everything.
It is a known spam pattern. Delayed meta refreshes and JavaScript redirects were long abused for cloaking and doorway pages, so search engines scrutinize them more than a clean 301.
It can break the back button. A user who lands on the refreshing page and hits back gets bounced forward again, trapping them.
When a Meta Refresh Is Acceptable
There are legitimate cases. If you have zero server access, no htaccess, no redirect plugin, no CDN rules, and you need to move one page, a delay-zero meta refresh is a reasonable stopgap. Some payment and OAuth flows use short delayed refreshes to show a "processing" state. And a genuinely informational "your download is starting" page with a visible delay is a real UX pattern, not an SEO redirect at all. The check flags meta refreshes because most of them are lazy substitutes for a proper redirect, not because every single one is wrong.
How to Detect Them
Tool
How
Screaming Frog
Crawl the site, open the Response Codes tab, filter by "Redirection (Meta Refresh)". It lists every page with the tag and its target.
Sitebulb
Flags meta refresh redirects in its indexability and redirect reports alongside the delay value.
View source
Search the raw HTML head for http-equiv="refresh". Quick spot check for a single page.
curl
curl -s https://example.com/page | grep -i refresh shows the tag from the raw response.
GSC URL Inspection
Shows how Google resolved the URL and whether it treated it as a redirect.
How to Fix It
Confirm the intent. Is this meant to be a permanent redirect? Then it wants a 301. Temporary? A 302. A real interstitial? Then it might be fine as is.
Replace with a server-side redirect. On Apache, an htaccess rule: Redirect 301 /old-page https://example.com/new-page. On Nginx, a return 301 in the server block. On WordPress, a redirect plugin. On a CDN, an edge redirect rule.
Remove the meta tag from the old page once the server redirect is live, so you do not stack two redirects on top of each other.
Test the response.curl -sI https://example.com/old-page should now return 301 and a Location header, with no page body.
Recrawl in Screaming Frog to confirm the meta refresh count is zero and every redirect resolves in a single hop.
DO
Use a server-side 301 for permanent moves
Reserve meta refresh for cases with no server access
Set delay to 0 if you must use one for a redirect
Point the target directly at the final URL, no chains
Verify with a curl of the response headers after the fix
DON'T
Use a delayed meta refresh to move real pages
Stack a meta refresh on top of a server redirect
Chain a meta refresh into another redirect
Use it for anything that is not HTML
Assume it passes equity exactly like a clean 301
What Good Looks Like
Zero meta refresh redirects in your crawl. Every intentional redirect is a single-hop server-side 301 or 302 that returns the right status code with a Location header and no page body. The only http-equiv="refresh" tags left, if any, are genuine user-facing interstitials with a visible delay and a manual click-through link, not silent SEO redirects.
FAQ
Does Google Follow Meta Refresh Redirects?
Yes. Google follows them and treats an instant, delay-zero refresh much like a 301. Delayed refreshes are treated more like a temporary redirect. It works, but a real 301 is clearer and faster.
Does a Meta Refresh Pass Link Equity?
A zero-delay refresh generally passes equity similar to a 301, but the behavior is less predictable than a server redirect because there is no explicit permanence signal. If ranking equity matters, use a 301.
Is a Meta Refresh the Same as a JavaScript Redirect?
Both are client-side, so they share the same downsides: slower, weaker signal, more scrutiny. Google can follow both, but a server-side redirect beats either for SEO.
Are Meta Refreshes Ever Fine to Keep?
Yes, for genuine interstitials: a visible "your download is starting" or "redirecting to our partner" page with a real delay and a manual link. Those are UX patterns, not SEO redirects, and the check is really aimed at the silent kind.
Redirects tangled up?
Meta refreshes, chains, loops, and mismatched status codes quietly leak crawl budget and ranking signal. Our audit maps every redirect on your site and shows you exactly which ones to rewrite as clean single-hop 301s.