Page redirects with a meta refresh
What it is
The page answers with status 200, but a <meta http-equiv="refresh"> tag in its HTML with a delay of 0 sends the browser straight on to another URL. It works as a redirect for visitors, yet the server never says the page has moved. It is common after a site move done in page templates, or on hosting that cannot set server redirects.
Why it matters
Google follows an instant meta refresh and treats it as a permanent redirect, but recommends a server-side redirect wherever you can set one. Crawlers that do not follow meta refresh, including some AI crawlers, see a near-empty page at the old address and may never reach the target. Each hop also costs visitors a page load before they see anything.
How Asky checks it
Asky reads the <meta http-equiv="refresh"> tags in the page’s raw HTML as a browser does: the first one it can read decides. The page is reported when its delay is 0 and its URL, after the first ; or , and an optional url=, is an http or https address of another page. The URL runs to the end of the value, commas included, or to its closing quote. Not reported: a refresh with no URL or to the page itself, a javascript: target, and a negative delay, which browsers ignore. The page gets no other finding. A delay above 0 is reported under accessibility, and redirects set by JavaScript are not seen.
Reported as a warning with medium severity.
How to fix it
- Open the page source (View Source) and find the
<meta http-equiv="refresh">tag and its target. - Replace it with a 301 redirect from the old URL to the target on the server, at your CDN, or in your CMS’s redirect settings (in WordPress a redirect plugin, in Webflow the 301 redirects in the site settings).
- Once the server redirect works, remove the old page or its refresh tag.
- Update internal links and your sitemap to use the target URL directly.
Example
https://example.com/old-pricing sent visitors on with a meta refresh:
<!-- Before: served with status 200 -->
<meta http-equiv="refresh" content="0; url=https://example.com/pricing">
<!-- After: the server answers 301 with Location: https://example.com/pricing -->