I noticed that, sometimes, instead of using a "redirect" header, some are rendering an HTML page with the meta tag "refresh" (client side).
Why is that?
Is there an advantage of the "refresh" method ?
Thanks,
keyplyr
9:44 pm on May 31, 2017 (gmt 0)
They are different tasks purposed for different objectives. The refresh is often misused & should not be done where a redirect is needed.
tangor
8:48 am on Jun 1, 2017 (gmt 0)
Depends on how much js or user input is involved. Most times it is not needed, ie, overkill.
Peter_S
9:12 am on Jun 1, 2017 (gmt 0)
Thank you for your answers.
keyplyr
9:21 am on Jun 1, 2017 (gmt 0)
BTW - forcing someone's browser to refresh may irritate some users. I try to leave their browser alone.
My end is the web page; their's is the browser.
not2easy
2:59 pm on Jun 1, 2017 (gmt 0)
About 12 years ago I thought it would be handy/helpful to send traffic on to the "new" page for an old product via meta-refresh. No. Google did not like it at all, and told me about it. I have not used it since. :(
Peter_S
3:06 pm on Jun 1, 2017 (gmt 0)
@not2easy It sounds like cloaking since a crawler will see the "old page", while a human being redirected to somewhere else.
engine
3:22 pm on Jun 1, 2017 (gmt 0)
I stopped using meta refresh many, many years back when I realised I didn't like it happen to me. I cant' think of why it might be useful, today. Having said that, someone might have a suggestion.