A meta redirect uses an HTML meta tag to automatically send visitors from one page to another after a specified delay. While .htaccess redirects are preferred for SEO and performance, meta redirects are useful when you don't have access to server configuration or need a client-side redirect with a delay message.
Add this to the <head> section
<meta http-equiv="refresh" content="0;url=https://yourdomain.com/new-page">
The content="0" means redirect immediately (0 seconds). Change the number to add a delay (e.g., content="5" for 5 seconds). Change the URL to your destination.
01. The Meta Redirect Tag
The meta refresh tag goes inside the <head> section of an HTML page. When a browser loads the page, it reads the meta tag and automatically navigates to the specified URL after the delay.
Immediate redirect (0 seconds):
<meta http-equiv="refresh" content="0;url=https://yourdomain.com/new-page">
Delayed redirect (5 seconds):
<meta http-equiv="refresh" content="5;url=https://yourdomain.com/new-page">
The delay is useful when you want to show a message like "This page has moved. You will be redirected in 5 seconds..." before sending the visitor to the new location.
02. Full HTML Example
Here's a complete page with a meta redirect and a fallback link for users who aren't redirected automatically:
<!DOCTYPE html>
<html>
<head>
<title>Page Moved</title>
<meta http-equiv="refresh" content="3;url=https://yourdomain.com/new-page">
</head>
<body>
<p>This page has moved. You will be redirected in 3 seconds.</p>
<p>If not redirected, <a href="https://yourdomain.com/new-page">click here</a>.</p>
</body>
</html>
Save this as the old page's filename (e.g., old-page.html) and upload it to the same location as the original file.
03. JavaScript Redirect Alternative
JavaScript redirects are another client-side option. They work similarly to meta redirects but give you more control (like conditional logic):
<script>
window.location.href = "https://yourdomain.com/new-page";
</script>
Or with a delay:
<script>
setTimeout(function() {
window.location.href = "https://yourdomain.com/new-page";
}, 3000); // 3000ms = 3 seconds
</script>
JavaScript redirects have the same SEO limitations as meta redirects. Use them only when server-side redirects aren't available.
04. Meta vs .htaccess Redirects
On Ultra Web Hosting, always use .htaccess redirects instead of meta redirects when possible. They're faster (the redirect happens before any HTML loads), better for SEO (Google treats 301s as permanent moves), and don't require the old page to exist.
The .htaccess equivalent of a meta redirect:
# 301 permanent redirect
Redirect 301 /old-page.html https://yourdomain.com/new-page
# Or with mod_rewrite
RewriteRule ^old-page\.html$ https://yourdomain.com/new-page [R=301,L]
Use meta redirects only when you cannot access .htaccess (like on a free hosting platform or a static page served by a third party). For a complete redirect reference, see our .htaccess guide and 302 Redirect Guide.
Need Help With Redirects?
If you need to set up redirects for a site migration or domain change, open a ticket and we can help configure the .htaccess rules.
Open a Support TicketQuick Recap: Meta Redirects
- Meta redirect:
<meta http-equiv="refresh" content="0;url=..."> - Place it in the <head> section of the HTML page
- Change content="0" to add a delay in seconds
- .htaccess 301 is better for SEO and performance
- Use meta/JS redirects only when server-side redirects are not available
Last updated March 2026 · Browse all General articles
