Timed Refresh Exists

Element Code: PE-031

What "Timed Refresh Exists" actually means

This check fires when a page carries a meta refresh with a non zero delay, something like <meta http-equiv="refresh" content="5;url=https://example.com/new/">. The number before the semicolon is a countdown in seconds. When the timer hits zero, the browser reloads the current page or navigates to the URL you specified. It is a redirect that lives in the HTML instead of in the HTTP response, and it runs on a delay instead of instantly.

People reach for it for two reasons. Either they wanted a redirect and did not have server access to set up a real one, or they wanted a page to auto reload to show fresh data (a scoreboard, a dashboard, a "you will be redirected shortly" interstitial). Both use cases have better answers in 2026, and the timed refresh is the worst option in almost every case I run into during audits.

Why this matters for SEO and users

Google has said for years that it treats a meta refresh with a URL roughly like a redirect, and that an instant (zero second) refresh is treated closer to a 301 while a delayed one is treated more like a soft 302 or, worse, an unclear signal. The keyword is unclear. When you leave the destination ambiguous, you leave ranking consolidation on the table. Link equity that should flow cleanly to the destination gets diluted or delayed while Google figures out your intent.

The user experience side is blunt. A timed refresh yanks the page out from under someone mid read. It breaks the back button, because the browser can get stuck in a refresh loop where pressing back just fires the timer again. Screen reader users get no warning that the ground is about to move. The W3C accessibility guidelines (WCAG 2.2, success criterion 2.2.1) explicitly flag auto refreshing content that the user cannot pause or stop. So a timed refresh is not just an SEO smell, it can be a compliance problem on regulated sites.

How a timed refresh compares to the alternatives

The two paths, decided

How to detect it across a site

You do not want to eyeball view source page by page. Crawl for it:

• Screaming Frog SEO Spider: run a crawl, then open the Directives tab or filter the internal report. Meta refresh URLs surface under the "Meta Refresh" column, and you can bulk export every offender with its target.
• Sitebulb: flags meta refresh redirects as a dedicated hint under its redirect and indexability checks, with the delay value shown.
• Google Search Console: the URL Inspection tool will show a page redirecting when the refresh is zero second, and the Page Indexing report can bucket affected URLs as "Page with redirect."
• Server logs or a quick grep: if you have template access, grep the codebase for http-equiv="refresh". That finds the source, not just the symptom.

How to fix it, step by step

1. Confirm the intent. Redirect or live data? That single answer picks your fix.
2. For a redirect, add a server side rule. On Apache: Redirect 301 /old-path/ https://example.com/new-path/. On Nginx: return 301 https://example.com/new-path/;. In a CMS, use its redirect manager (Yoast, Rank Math, and Redirection all do this cleanly).
3. Delete the meta tag from the template or page body once the server redirect is confirmed working. Leaving both creates a double redirect.
4. For live data, replace the whole page reload with a fetch() call on an interval that updates only the changed elements. The URL stays put, the scroll position stays put, and crawlers see a stable page.
5. Retest. Recrawl the affected URLs and inspect them in Search Console to confirm the signal is now a clean 301 or no redirect at all.

Do vs Don't

What "good" looks like

Zero meta refresh tags in your HTML. Redirects handled at the server with the correct status code, so a crawler gets the answer in the HTTP response before it ever parses markup. Any live updating content driven by scripted polling that leaves the URL and scroll position alone and can be paused. When you recrawl, the "Meta Refresh" column in Screaming Frog is empty, and Search Console shows either a clean permanent redirect or an ordinary indexable page.

FAQ