问题原文
原帖链接 · davidgo · CC BY-SA 4.0
Question Moving Pages to New URL's - Unable to Use 301 Redirects to Tell Search Engines The Pages Have Moved got me thinking - If there is only access to change the content of a page to affect redirection we can use
<meta http-equiv="REFRESH" content="0; url=XXXXXXX>
Of-course, this does not create a 30x status code, but on the other hand is very old (I remember using it with Netscape) and has a very low barrier as its just HTML.
How does Google treat http-equiv="REFRESH" to a new URL from a redirection/SEO POV?
已采纳解答
原帖链接 · Ryder Cragie · CC BY-SA 4.0
This might help:
https://developers.google.com/search/docs/crawling-indexing/301-redirects
meta refresh and its HTTP equivalent
If server side redirects aren't possible to implement on your platform, meta refresh redirects may be a viable alternative. Google differentiates between two kinds of meta refresh redirects:
Instant meta refresh redirect: Triggers as soon as the page is loaded in a browser. Google Search interprets instant meta refresh redirects as permanent redirects.
Delayed meta refresh redirect: Triggers only after an arbitrary number of seconds set by the site owner. Google Search interprets delayed meta refresh redirects as temporary redirects.
Place the meta refresh redirect either in the
<head>element in the HTML or in the HTTP header with server side code.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
