What a meta refresh redirect actually is
A meta refresh is a single line in the head of a page. Its content attribute says how many seconds to wait and which address to open. A value of zero means an instant jump; a larger value creates the old-style page that says you will be redirected in a few seconds.
The key difference from a server redirect is that the server answers with a normal 200 status and sends the whole page. The browser performs the jump after it reads the HTML. A customer tapping a link in Instagram or Telegram sees no difference. Only the crawler does.
How Google and Yandex treat meta refresh
Google has said it interprets an instant meta refresh as a permanent redirect and a delayed one as temporary. So the signal does arrive, but the crawler must first download and parse the document. A server 301 is visible in the response header, before any content loads.
Yandex also processes these jumps, though a zero-delay version is safer there too. Accessibility matters as well: automatic, delayed page changes disorient people who use screen readers. For a site move or URL consolidation, a meta redirect is a compromise, not a standard.
JavaScript redirects share the same weakness
A script changes the address after the page has loaded, usually through the location object. Google can run JavaScript and will usually notice the jump, but only at the rendering stage, which is sometimes delayed. If the script throws an error or loads slowly, the redirect can go unnoticed. Yandex handles scripts less predictably.
In short, both client-side methods depend on how the crawler processes the page. A server 301 does not.
When a meta refresh redirect is the only option
Some situations leave you without server access, or the jump has to follow a user action:
- a website builder that does not expose server configuration
- plain static hosting with no per-page rules
- a thank-you page after a Click or Payme payment
- a temporary placeholder set up by someone without technical rights
How to switch to a server-side 301
Before settling for a meta tag, check three places. First, the builder or hosting panel often has a redirects section that issues a real 301. Second, if the site runs on a CMS, a redirect plugin or built-in module will do. Third, you can put a service such as Cloudflare in front of the site and define redirect rules there.
Afterwards, update internal links so they point straight to the new address, and keep only final URLs in your sitemap.
If you must keep a meta refresh
Make it as safe as possible:
- set the delay to 0
- use the full destination URL with protocol
- add a canonical tag pointing to the new address
- keep a plain link to the new page in case the jump fails
- never chain several such pages together
How to check your site and what to watch for
Open the old URL in your browser's developer tools on the Network tab. If the first entry is a 301 or 302, the redirect is server-side. If it is a 200 followed by a request for another address, a meta refresh or script is at work, and the page source will show which. SEO crawlers usually list pages with meta refresh separately.
Also look for unexpected jumps, especially on mobile devices. Hidden redirects to third-party sites are sometimes injected after a hack, and owners can go a long time without noticing. Showing a crawler one thing and sending people elsewhere is treated by search engines as deception.
If you are unsure which redirects your site uses and how they affect search visibility, the markdev team can run an SEO audit and prepare a plan to replace them with server-side ones. Describe your task and we will suggest where to start.
FAQ
Is a meta refresh the same as a 301 redirect?
No. A 301 is sent by the server in the response header, while a meta refresh is a tag inside the HTML that the browser acts on after loading the page. For SEO the server version is faster and more reliable.
Does a meta refresh lose link value?
Google treats an instant meta refresh as a permanent redirect, so the signal is usually counted. It is processed later and less reliably than a 301, so a server redirect is better for any real move.
Should I use a meta refresh with a delay?
Better not. Google reads it as temporary, and visitors may leave or get confused. If a zero-delay version is impossible, add a canonical tag and a plain link to the new page.
How can I find every meta refresh on my site?
Run a crawler for a technical audit. It lists pages containing the tag separately, and you can then replace them with server redirects wherever possible.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.