SquishPixel Blog · SEO · Front-end · Tools

Meta refresh delay decides whether Google reads a page move as permanent or temporary

DEV Community published a guide on auditing meta refresh redirects. A meta refresh is an instruction inside a page, or in a response header, that tells the browser to load another address after a set delay. The guide argues that a browser reaching the right page does not show the redirect says what you meant it to say.

It points to Google's redirect documentation. According to that documentation, an instant meta refresh with a delay of zero seconds is treated as permanent. A delayed refresh, with a delay above zero, is treated as temporary. The same timing rule applies to the HTTP Refresh equivalent. For a permanent move, Google recommends a permanent server-side redirect where possible, with a meta refresh as an alternative when the platform cannot do that.

The article uses a fictional example. A product called Harbor Manuals retires an old setup guide and replaces it with a new installation guide. If the platform shows a notice and refreshes after five seconds, a manual test reaches the right page. But the delay does not match a permanent move under Google's classification. The author stresses this is a review example, not a report of lost rankings.

For checking, the guide suggests keeping the network log in browser developer tools and recording the first response for the old URL. Note any refresh header or HTML refresh tag, the delay, the declared target and the final destination. If no refresh instruction can be found, leave the mechanism marked as unresolved instead of assuming a zero-second delay. After a fix, repeat the same checks on the public page, not just the preview or the CMS setting.

Why it matters

Page moves are often handled by a website builder or documentation template, and the person who sets a delay for readability may not be the person who owns the migration. The page works for visitors, so the release looks done. Yet the delay may tell Google the move is only temporary.

The guide also keeps its claims modest. It covers Google's documented behaviour only, and a successful test does not prove Google has recrawled the page or changed its results. Check what was actually delivered, then watch search behaviour separately.

Source: DEV Community. This brief summarises their reporting; read the original for the full detail.