Free Meta Refresh Redirect Page Generator
Generate a standalone HTML redirect page with meta refresh, a JavaScript fallback, and a canonical tag. Redirect without server access. Free, copy-paste, no signup.
When to use this
A meta refresh page redirects without server access - host it on static hosting, GitHub Pages, or any CMS where you can add an HTML page. For SEO-critical moves, a server 301 (see the .htaccess or Nginx generators) is preferred.
Enter a destination URL to generate a standalone HTML redirect page. Save it as index.html in the folder you want to redirect.
Quick Answer
A meta refresh redirect generator builds a complete HTML page that sends visitors from one URL to another using a <meta http-equiv="refresh"> tag, with a JavaScript fallback and a canonical link. Enter the destination, copy the page, and host it anywhere - no server config needed. The U2L Meta Refresh Redirect Generator runs in your browser. Free, no signup.
Quick Facts
- A meta refresh redirect lives in the HTML itself: <meta http-equiv="refresh" content="0; url=https://example.com">.
- It needs no server access - host the HTML page on static hosting, GitHub Pages, S3, or any CMS that lets you add a page.
- A delay of 0 redirects immediately; a positive delay shows the page briefly before redirecting.
- The generator adds a JavaScript window.location fallback and a clickable link for environments where meta refresh is slow or blocked.
- A rel=canonical tag points search engines at the destination; an optional noindex keeps the redirect page out of search.
- For SEO-critical moves, a server-side 301 is preferred - meta refresh is the right tool when you cannot edit server config.
- Browser-only and instant - the page is built locally and never sent to U2L servers.
How to make an HTML redirect page
Set the destination, copy the page, host it.
- 1
Enter the destination URL
Type the full URL you want visitors sent to, including https://. The redirect page builds instantly with that destination.
- 2
Set the delay and options
Choose a delay (0 for an instant redirect), a page title, and whether to add noindex and a JavaScript fallback for maximum reliability.
- 3
Save and host the HTML
Copy the generated HTML, save it as index.html (or any page name) in the folder you want to redirect, and upload it to your host.
What is a Meta Refresh Redirect Generator?
Meta Refresh Redirect Generator is a tool that builds a complete, standalone HTML page whose only job is to redirect visitors to another URL. It uses a meta refresh tag - the HTML mechanism for client-side redirects - plus a JavaScript fallback and a canonical tag, so you can move visitors from one address to another without touching server configuration.
A meta refresh redirect is an instruction placed in a page's HTML head: <meta http-equiv="refresh" content="0; url=...">. When a browser loads the page, it reads the tag and navigates to the target URL after the specified number of seconds. Because the redirect lives in the HTML rather than the server, it works anywhere you can publish an HTML file.
That portability is the whole point. Server-side redirects (a 301 in Apache's .htaccess or an Nginx config) are the gold standard, but they require access to server configuration that many people simply do not have - on static hosts, GitHub Pages, an old CMS, or a shared host where you can only upload pages. A meta refresh page fills that gap, letting anyone create a working redirect with nothing but an HTML file.
Bloggers moving a post, developers retiring a page on static hosting, marketers pointing a vanity path at a campaign, and anyone who needs a quick redirect without server access use this generator to produce a reliable redirect page in seconds.
How does a Meta Refresh Redirect Generator work?
You enter a destination URL and the generator assembles a small, complete HTML document. The core is the meta refresh tag in the head, which carries your delay and the target URL. With a delay of 0 the browser redirects as soon as it parses the head; with a positive delay it renders the page first, which is useful for showing a brief 'redirecting…' message.
To make the redirect robust, the tool layers in fallbacks. A JavaScript line calls window.location.replace(target), which fires immediately in any browser with scripting enabled and, by using replace, keeps the redirect page out of the back-button history. A visible link to the destination is always included, so even a browser that ignores both meta refresh and JavaScript leaves the visitor one click from the right place.
For SEO, the page includes a rel=canonical tag pointing at the destination, signaling to search engines that the real content lives at the target URL. An optional robots noindex tag keeps the throwaway redirect page itself out of search results. The URL is HTML-escaped in attributes and JSON-encoded in the JavaScript so special characters cannot break the markup or the script.
Everything runs in your browser - the page is generated locally and never sent to U2L. The output is a plain HTML file you save (typically as index.html) in the directory you want to redirect, then upload to your host. Where you can edit server config instead, a 301 redirect passes SEO value more cleanly; this tool is for the many cases where you cannot.
Use Cases
How marketers, businesses, and developers use meta refresh redirect generator.
Redirecting on static hosting
On GitHub Pages, Netlify drops, S3, or any static host without redirect rules, an HTML redirect page is the simplest way to move a URL to a new location.
Moving a blog post or page
When a post's URL changes and you cannot edit server config, drop an HTML redirect at the old path so existing links and bookmarks keep working.
Vanity paths to a campaign
Point a memorable path like /promo at a long campaign URL by hosting a small redirect page, no server rules required.
Retiring a page gracefully
Send visitors from a discontinued page to the best replacement with a short delay and a friendly message instead of leaving a dead end.
Redirecting from a CMS page
In a CMS where you can add a page but not server rules, paste the generated HTML into a raw-HTML block to redirect from that page.
Placeholder redirects during a migration
While a site move is underway, use HTML redirect pages as quick stopgaps until proper server-side 301s can be configured.
Linking a parked path to your main site
Host a redirect page on a secondary path or microsite so it forwards to your primary domain without standing up server infrastructure.
Short delay with a branded interstitial
Use a few seconds of delay to show a branded 'taking you there' page before forwarding, useful for sponsorships or disclosures.
Quick redirect for testing or demos
Spin up a throwaway redirect page to test a flow or demo a forwarding behavior without changing any real server configuration.
Meta Refresh Redirect Generator vs Alternatives
Side-by-side feature and pricing comparison with the top alternatives.
| Feature | U2L | Server 301 | Hand-written HTML | JS-only redirect |
|---|---|---|---|---|
| Free, no signup | ||||
| Works without server access | ||||
| JS fallback + canonical included | N/A | Manual | ||
| Works without JavaScript | Depends | |||
| Escapes the URL safely | N/A | Varies | ||
| Best for SEO-critical moves | Use 301 |
Meta Refresh Redirect Generator vs A server-side 301 redirect
A 301 redirect configured on the server (via .htaccess on Apache or a server block on Nginx) is the SEO gold standard: it passes ranking value cleanly and is the correct choice whenever you can edit server config.
The catch is access - many hosts, static platforms, and CMSs do not let you set server redirects. A meta refresh page works in all of those cases. Use a 301 when you can; reach for this generator when server config is off the table.
Meta Refresh Redirect Generator vs A JavaScript-only redirect
A redirect using only window.location in a script is simple and fast for users with JavaScript enabled.
If scripting is disabled or blocked, a JS-only redirect strands the visitor. This generator combines a meta refresh (which works without JavaScript), a JS fallback, and a visible link - so the redirect succeeds across the widest range of environments, not just script-enabled ones.
Best Practices
Use a server 301 when you can
If you have access to server config, a 301 passes SEO value better. Use the meta refresh page specifically when you cannot edit server rules.
Set the delay to 0 for true redirects
A 0-second delay forwards immediately, which is what most redirects want. Reserve a positive delay for cases where you intend to show a brief message.
Keep the JavaScript fallback on
The JS window.location.replace fires instantly and keeps the redirect page out of browser history. Leaving it enabled makes the redirect faster and cleaner.
Include the canonical tag
Pointing rel=canonical at the destination tells search engines where the real content lives, helping consolidate signals on the target page.
Add noindex to the redirect page
The redirect page has no content of its own. Marking it noindex keeps it out of search results so only the destination is indexed.
Save it as index.html to redirect a folder
Placing the file as index.html in a directory redirects requests for that folder. Name it after a specific page to redirect just that URL.
Always use an absolute destination URL
Include the full https:// URL so the redirect works regardless of where the page is hosted. Relative paths can resolve unexpectedly.
Show a message on a delayed redirect
If you use a delay, the visible 'redirecting…' line reassures visitors and gives them a manual link in case the automatic redirect is slow.
Common Mistakes to Avoid
Using meta refresh for SEO-critical moves
For permanent moves where rankings matter, a server 301 is better. Relying on meta refresh when you could use a 301 can weaken how cleanly SEO value transfers.
Setting a long delay by accident
A non-zero delay makes visitors wait on a blank page before redirecting. Unless you intend an interstitial, set the delay to 0.
Relying on JavaScript alone
A JS-only redirect fails when scripting is disabled. The meta refresh tag works without JavaScript, so keep it as the primary mechanism.
Using a relative destination URL
A relative path can resolve to the wrong place depending on where the page is hosted. Always use the absolute https:// URL for the destination.
Forgetting noindex on the redirect page
Without noindex, the empty redirect page can get indexed and show up in search instead of the destination. Add it to keep search clean.
Not providing a manual link
If both meta refresh and JS fail, a visitor with no clickable link is stuck. The generated page always includes a link so there is a way forward.
Technical Specifications
| Mechanism | <meta http-equiv="refresh" content="DELAY; url=TARGET"> |
| Fallbacks | JavaScript window.location.replace + visible link |
| Delay | 0 for instant; positive seconds for an interstitial |
| SEO tags | rel=canonical to destination; optional robots noindex |
| Hosting | Any static host or CMS that serves an HTML file |
| Escaping | URL HTML-escaped in attributes, JSON-encoded in script |
| Best for | Redirects without server config access |
| Privacy | Built in your browser. No data sent to U2L. |
Frequently Asked Questions
What is a meta refresh redirect?
When should I use a meta refresh instead of a 301?
How do I host the redirect page?
Does a meta refresh redirect work without JavaScript?
What delay should I set?
Is a meta refresh bad for SEO?
Why does the page include a canonical tag?
What does the noindex option do?
Why is there a JavaScript redirect too?
Can I redirect a whole folder?
Will the back button get stuck on the redirect page?
Do I need to include https:// in the destination?
Is my destination URL sent to a server?
Can I customize the redirect message?
Does it escape special characters in the URL?
Is the tool free?
Related Free Tools
Whois Lookup
Look up registrar, owner, creation date, expiry, and DNS for any domain. Free Whois data, no API key.
Free QR Code API
REST API for generating SVG and GIF QR codes. WiFi, vCard, URL, and text. Free, no API key, edge-cached.
DNS / CNAME Checker
Look up A, AAAA, CNAME, MX, TXT, NS records for any domain. Verify global DNS propagation in seconds.
SSL Certificate Checker
Inspect any SSL certificate: validity, issuer, chain, expiry, and protocol. Spot issues before users do.
HTTP Header Inspector
Inspect HTTP request and response headers for any URL. Cache, security, CORS, and server details.
URL Shortener Speed Test
Compare redirect response times across 10+ URL shorteners. Real measurements in your browser.
Key Terms
- Meta refresh
- An HTML meta tag (http-equiv="refresh") that tells the browser to navigate to a URL after a set number of seconds.
- 301 redirect
- A permanent server-side redirect status code that passes SEO value to the destination. Preferred when you can edit server config.
- Canonical tag
- A rel=canonical link telling search engines the preferred URL for content, used here to point at the redirect destination.
- noindex
- A robots meta directive that asks search engines not to index a page, used to keep the empty redirect page out of search.
- Interstitial
- A brief in-between page shown before forwarding a visitor, created by setting a positive meta refresh delay.
Want redirects you can edit and track?
Instead of hosting redirect pages, create branded u2l.ai short links that you can re-point any time and track with full click analytics - no files to upload. Sign up free to manage redirects the easy way.
Sign up free