Meta Refresh Redirect Generator
FREE TOOL · NO SIGN-UP
This meta refresh redirect generator creates the HTML you need to send visitors from one page to another when you can’t set up a server redirect. Enter the destination URL and a delay, and it gives you a single meta refresh tag plus a complete, ready-to-upload redirect page with a canonical link, a noindex tag, a JavaScript fallback and a “click here” link. It’s free, needs no sign-up and runs in your browser, which makes it handy for static hosts, old HTML pages and platforms where you can’t touch server settings.
How to Use the Meta Refresh Redirect Generator
Step 1 – Enter or paste your input
Paste the full destination address into Redirect to URL, including https://. Set the Delay in seconds. Leave it at 0 for an instant redirect, which is the best choice in almost every case. Change the Page title if you like; it shows briefly in the browser tab.
Step 2 – Choose your options
Under Include, decide what goes into the full page. JavaScript fallback adds a script that redirects after the same delay, in case the meta tag is ignored. Canonical link to target points search engines at the new URL. noindex this page asks search engines not to index the redirect page itself. All three are on by default.
Step 3 – Copy, download or apply the result
Use Meta tag only if you’re adding the tag to an existing page’s <head>, or Full HTML redirect page if you’re replacing the old page entirely. Click Copy or Download, upload it to the old URL’s location and test it in a private browser window.
How a Meta Refresh Redirect Works
A meta refresh redirect is an HTML tag, <meta http-equiv="refresh" content="0; url=https://example.com/new/">, placed in a page’s head that tells the browser to load a different URL after a set number of seconds. It’s a client-side redirect: the browser does the work, not the server.
The content value has two parts. The number is the delay in seconds, and the url= part is the destination. When the browser reads the tag, it waits for the delay and then loads the new address.
Because the old page has to load first, the server returns a normal 200 status for the old URL, not a 301 or 302. That’s the key difference from a server redirect. Search engines that process the page can still see and follow the meta refresh, and the fallback link in the generated page gives visitors a way through if refresh is blocked.
Instant vs Delayed Refresh and SEO Impact
| Delay | How Google treats it | When to use it |
|---|---|---|
| 0 seconds (instant) | Interpreted as a permanent redirect | Page has moved and you can’t use a server 301 |
| Any delay above 0 | Interpreted as a temporary redirect | Rarely; a short notice before moving on |
| Server 301 or 308 | Permanent redirect, the strongest signal | Whenever you have server or host access |
| Server 302 or 307 | Temporary redirect | Short-term moves, testing, maintenance |
Google’s redirect documentation says an instant meta refresh is treated as permanent and a delayed one as temporary. So if a page has moved for good and a server redirect isn’t possible, use a delay of 0. The generator shows a note for whichever case you choose.
Meta Refresh vs 301, 302 and JavaScript Redirects
Server-side 301 and 308 redirects are the gold standard for permanent moves. The server answers before any page loads, every browser and crawler understands them, and they’re the clearest signal for moving links and rankings to the new URL. Use the .htaccess Redirect Generator or Nginx Redirect Generator if you have server access.
302 and 307 redirects are temporary. Search engines usually keep the original URL indexed.
JavaScript redirects, using location.replace() or similar, only work once the browser runs the script. Google can process them when it renders the page, but they’re less reliable than server redirects for other crawlers and tools.
Meta refresh sits between the two. It doesn’t need JavaScript and Google treats an instant one as permanent, but it’s still slower and less universal than a server redirect. It’s a good fallback, not a first choice. That’s why the generated page includes both a meta refresh and a JavaScript fallback: if one is blocked, the other usually works.
Accessibility Concerns With Timed Refresh
Timed redirects can be a real problem for some users. If a page changes after a few seconds, someone using a screen reader may lose their place mid-sentence, and people who read slowly may not finish the message before it disappears. Users with cognitive disabilities can find unexpected page changes disorienting.
The Web Content Accessibility Guidelines treat a timed meta refresh as a failure of success criteria such as 2.2.1 Timing Adjustable, because the user can’t stop or extend it. An instant redirect, with a delay of 0, doesn’t have this problem, because nothing appears before the page changes.
If you need to show a message first, such as “This page has moved”, consider a normal page with a clear link to the new location instead of a countdown.
Key Features of Our Meta Refresh Redirect Generator
- Free, with no sign-up: fill in a URL and copy.
- Private: runs in your browser; nothing is uploaded or stored.
- Two outputs: the meta tag alone, or a complete redirect page.
- Custom delay: with guidance on how Google treats it.
- JavaScript fallback: a second redirect method in the same page.
- Canonical and noindex options: included by default and easy to switch off.
- Visible fallback link: “If you are not redirected, click here” for every visitor.
When a Meta Refresh Makes Sense
- Static hosting without redirect rules, such as basic file hosting.
- Hosted platforms that don’t let you edit server settings.
- Old HTML files on a site you’re retiring or moving.
- Short links or landing pages that should forward to another site.
- Temporary forwarding during a migration while server rules are set up.
- Documentation or file servers where only HTML can be uploaded.
Pro Tips and Mistakes to Avoid
Checklist of best practices
- Use a server 301 whenever you can; treat meta refresh as the fallback.
- Set the delay to 0 for permanent moves.
- Use the full absolute destination URL.
- Point the redirect straight to the final page, not to another redirect.
- Update internal links and your sitemap to use the new URL.
Common mistakes and quick fixes
- Long countdown delays: they’re treated as temporary and hurt accessibility. Use 0.
- Redirect chains: if the destination redirects again, update the target.
- Mixed signals: a noindex tag and a canonical on the same page can send search engines conflicting hints. If passing signals to the new URL is your main goal, try unticking noindex and relying on the instant redirect plus canonical.
- Forgetting to test: check the old URL in a private window after uploading.
Redirect Visitors Without Server Access
When you can’t change server settings, a well-built meta refresh page still gets visitors and search engines to the right place. Create one with the meta refresh redirect generator, and when you do have access, set up proper rules with the .htaccess Redirect Generator, the Nginx Redirect Generator or the YAML Redirect Generator for static sites. Explore more technical SEO tools in the FHSEO Hub free SEO tools collection.