An HTML redirect uses a meta refresh tag on a page to tell the browser to send visitors automatically from the original URL to another URL. It is suitable when you cannot change server settings but need to forward visitors quickly. If you can configure a server-side redirect, that should generally be your first choice. An HTML redirect requires the browser to load the original page before proceeding to the destination, which may make the wait feel longer. It also makes it harder to control which HTTP status codes are used.
How it works: Set the wait time and destination on the original page
The meta refresh tag goes in the head section of the original page’s HTML and specifies a wait time in seconds and a destination URL. Setting the time to zero means an immediate redirect; setting it to five means redirecting after five seconds. Here, “immediate” does not mean skipping the original page: the browser still needs to load that page and process the tag before navigating to the new location.
Choosing between an immediate and a delayed redirect is therefore not just about how long visitors should wait. You should also consider whether they need time to read an explanation of the redirect.
When to use it: An alternative when you cannot change server settings
Semrush’s 2023 article lists uses such as page migrations, content consolidation, and limited-time campaigns. Specific examples include:
- Moving an article to a new URL and directing visitors from the old URL to its new location.
- Combining several pages into one and directing visitors from each old page to the consolidated content.
- Displaying an explanation on a simple introductory page, then waiting a few seconds before sending visitors to the main content.
HTML redirects can be used in these situations, but that does not make them the best choice. If you have permission to configure the server, compare server-side options first. Being able to edit the HTML is not a reason to overlook differences in loading speed and redirect control.
Search implications: The delay affects more than user experience
Semrush’s 2023 article stated that Google at the time treated immediate meta refresh redirects as permanent and delayed redirects as temporary. That describes how redirects were treated at the time; it should not be assumed to reflect current search rules. If your choice of redirect depends on how search engines interpret it, check the latest official guidance.
The same article also advises avoiding redirect chains. For example, redirecting visitors from an old page to an intermediate page, then on to a new page, adds extra steps. Set the redirect to point directly to the final destination so visitors do not have to go through multiple redirects.
User experience: Explain the redirect and provide a fallback link
If visitors need to wait on the original page, briefly explain the redirect—for example, “This content has been updated. You will be taken to the new version shortly.” The destination page should also meet their original needs: when a product page is temporarily unavailable, related products will generally provide a more relevant next step than an unrelated category page.
Some older browsers may also ignore meta refresh or handle it differently, so the original page should provide a fallback link that visitors can use to reach the destination manually if the redirect fails. The delay should match the length of the explanation. The five-second delay suggested by the author of the Semrush article is not a universal standard, nor does it guarantee that visitors will stay until the redirect occurs.
HTML redirects: perspectives from across the web
Can HTML redirects be used for A/B testing?
Semrush lists A/B testing as a possible use for HTML redirects, but randomly splitting traffic requires a separate implementation plan. The article gives the example of randomly directing some traffic to another version. However, its basic meta refresh example specifies only the wait time and destination URL; it does not explain how to split traffic randomly.
What security concerns come with using meta refresh?
Semrush states that meta refresh is easier for malicious actors to manipulate than server-side redirects and is often used for phishing, so some browsers may flag pages using this type of redirect as suspicious. This does not mean that all meta refresh redirects are malicious, but security is worth considering when choosing an approach.
Do you have to use .htaccess to configure redirects in Apache?
Not necessarily. One opinion on Stack Exchange suggests that using Apache’s .htaccess or main configuration file generally works better. However, Semrush cites Apache’s official documentation as saying that .htaccess can sometimes reduce server performance and should be used only when necessary. If you can edit the main configuration file, consider that approach first rather than always choosing .htaccess.
References
- what redirect do i use?webmasters.stackexchange.com — Discusses: Do you have to use .htaccess to configure redirects in Apache?
- List of .htaccess Redirect Rules & What They Dowww.semrush.com · 2021-10-14T19:27:00Z — Discusses: Do you have to use .htaccess to configure redirects in Apache?
- How to Set Up an HTML Redirect (+ Alternatives)www.semrush.com · 2023-07-24T08:57:00Z — Discusses: Can HTML redirects be used for A/B testing?; What security concerns come with using meta refresh?




