How browsers and Google read a meta refresh
Google Search treats an instant (0-second) meta refresh as a permanent redirect. It treats a delayed meta refresh, more than 0 seconds, as a temporary redirect. Google presents meta refresh as a fallback for platforms where server-side redirects cannot be set up. It accepts the refresh instruction either as a meta tag in the HTML head or as a Refresh HTTP header sent by server-side code. MDN states that the two forms are equivalent.
Syntax. For a redirect, the
contentattribute is a non-negative integer (seconds) followed by;url=and a valid URL. MDN's examplecontent="3;url=https://www.mozilla.org"sends the browser to that URL after 3 seconds.A number alone. When the
contentattribute holds only a number, the browser reloads the same page after that many seconds instead of redirecting.Timing. The refresh timer starts only after the page has fully loaded.
HTTP redirects. MDN defines an HTTP redirect as a server response with a status code that starts with 3, and lists the HTML meta redirect as one alternative.
Order. Browsers apply HTTP redirects first and JavaScript redirects next, so a meta refresh runs last: an HTTP redirect exists even when no page is transmitted, while a meta redirect needs the delivered page.
For server-side redirects in a site move, see domain migration without losing SEO.
Accessibility and the HTML-only limit
A meta refresh works only in HTML documents, so it cannot redirect images, PDFs or other non-HTML files.
The delay value also matters for accessibility. MDN recommends a 0-second delay for accessibility compliance, and WCAG technique H76 requires a zero time-out so that no content is shown before the new page loads. WCAG lists a short, uncontrollable meta refresh as an accessibility failure because screen reader users lose their place when the page changes.
Server-side redirects editors can manage
Pagepro builds the redirect map from a URL inventory drawn from several sources, because a sitemap alone misses URLs. It pairs the map with a redirect manager in Sanity that content editors use, so they can add redirects without a deploy, as part of headless CMS development for marketing teams.
Sources
- HTML Living Standard: 4.2.5.3 Pragma directives (Refresh state)WHATWG · html.spec.whatwg.org
- Redirections in HTTPMDN · developer.mozilla.org
- Redirects and Google SearchGoogle · developers.google.com
- <meta> http-equiv attributeMDN · developer.mozilla.org
- Technique H76: Using meta refresh to create an instant client-side redirectW3C · w3.org
- Technique F41: Failure due to using meta refresh to reload the pageW3C · w3.org