Skip to main content
miji.be

Meta Refresh

An HTML meta tag that instructs the browser to automatically redirect to a different URL after a specified delay.

Sep 6, 2026 / About 1 min read

Redirect

A meta refresh is an HTML-based redirect mechanism that uses a meta tag in the page's head section to instruct the browser to navigate to a different URL after a specified delay. The syntax is straightforward: a meta tag with http-equiv="refresh" and a content attribute specifying the delay in seconds and the target URL.

Meta refresh redirects operate at the HTML level rather than the HTTP level, which means the browser must first download and begin parsing the HTML document before the redirect is triggered. This makes meta refresh slower than server-side redirects (301, 302) and is generally considered a less desirable approach.

From an SEO perspective, Google Search Central documentation states that Google Search interprets a meta refresh with a zero-second delay as a permanent redirect, and a meta refresh with a delay greater than zero as a temporary redirect (as of August 2026). The same documentation positions meta refresh as an alternative for platforms where server-side redirects cannot be implemented, so server-side redirects remain the first choice for permanent URL changes.

Meta refresh is sometimes used as a fallback when server-side redirects are not available, such as on static hosting platforms that do not support HTTP redirect configuration. In URL shortening, meta refresh may appear in splash pages that display a countdown before redirecting to the destination.

Was this article helpful?

Related Terms

301 Redirect

A permanent HTTP redirect that tells browsers and search engines the resource has moved permanently to a new URL.

JavaScript Redirect

A client-side redirect implemented using JavaScript code to navigate the browser to a different URL.

Redirect Chain

A sequence of multiple redirects between the initial URL and the final destination, where each redirect points to another redirect.

Client-Side Redirect

A redirect executed by the browser using HTML meta tags or JavaScript, after the initial page has been partially loaded.

Server-Side Redirect

A redirect handled by the web server before any page content is sent to the browser, using HTTP status codes like 301 or 302.

Redirect Caching

A mechanism in which browsers and CDNs store redirect responses for a certain period and skip querying the origin server on later visits.

Related Articles

301 vs 302 Redirects - Choosing the Right Type for Short URLs

Understand the differences between 301 and 302 HTTP redirects. Learn how each type affects SEO, analytics, and performance for short URLs.

URL Shorteners and SEO - How Short Links Affect Search Rankings and Link Equity

Analyze the impact of short URLs on search engine optimization. Covers 301 redirect link equity, crawl budget effects, and SEO best practices.

How URL Shorteners Work - The Technical Side of Redirects

Discover the technical mechanics behind URL shortening: hash generation, database lookups, HTTP redirects, and more. Includes HTTP response examples and base-62 encoding calculations.

FAQ

Why is meta refresh discouraged for SEO?
Google Search Central documentation positions meta refresh as an alternative for platforms where server-side redirects cannot be implemented (as of August 2026). Because the browser has to download and parse the HTML before the redirect starts, it is slower than a server-side redirect and the user experience is worse.
Are there appropriate use cases for meta refresh?
It is used when the server configuration can't be modified and the redirect has to be implemented with static HTML alone, such as page migration notices on static hosting. Google Search interprets a meta refresh with a zero-second delay as a permanent redirect and one with a delay greater than zero as a temporary redirect (as of August 2026).

Put the terms to work

Shorten a URL for Free