In a situation when you are doing a major code release and/or database schema change to a production environment is it detrimental to SEO to put up a "Gone Fishin'" page while the upgrade happening?
在您正在进行主要代码发布和/或数据库架构更改到生产环境的情况下,在升级发生时,SEO是否有害于建立“Gone Fishin”页面?
Assume that using the old code/database schema during the upgrade could put the post-upgrade DB into an undesirable/unknown state.
假设在升级期间使用旧代码/数据库模式可能会使升级后的DB进入不合需要/未知状态。
6 个解决方案
#1
10
No, not if you make sure to send the proper HTTP-headers. Do not send 200 OK, as this will make the search engines index your error message.
不,如果您确保发送正确的HTTP标头,请不要这样做。不要发送200 OK,因为这会使搜索引擎索引您的错误消息。
I would suggest sending "503 Service Unavailable" together with a text explaining why and how long you will be down..
我建议发送“503 Service Unavailable”和一条文字,说明你将失败的原因和时间。
#2
2
For a list of HTTP status codes see:
有关HTTP状态代码的列表,请参阅:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Specially for maintenance:
特别用于维护:
10.5.4 503 Service Unavailable
10.5.4 503服务不可用
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
由于服务器的临时过载或维护,服务器当前无法处理请求。这意味着这是一个暂时的条件,经过一段时间的延迟后会得到缓解。如果已知,延迟的长度可以在Retry-After报头中指示。如果没有给出Retry-After,客户端应该像处理500响应一样处理响应。
#3
1
How long will the “Site Down for Maintenance” page be live? If only a day, then it would be fine.
“网站停机维护”页面会有多长时间生效?如果只有一天,那就没关系了。
#4
0
Typically this is done for short periods of time (under 6-12 hours). I have never noticed a situation where this is an issue, as the google bot sees the dramatic change in content and it appears to essentially come back later like visitors. Now this isn't an official remark, just what I have noticed on my sites.
通常这是在短时间内(6-12小时)完成的。我从来没有注意到这是一个问题,因为谷歌机器人看到了内容的巨大变化,它似乎基本上像访客一样回来。现在这不是官方评论,只是我在网站上注意到的。
#5
0
It would either have to:
它要么必须:
- be a really long upgrade, or
- you'd be seriously unlucky to have a spider try your site while upgrading
是一个很长的升级,或
在升级时让蜘蛛尝试你的网站是非常不幸的
But if you are going to be longer than half a day to a day, consider this:
但如果你要超过半天到一天,请考虑这个:
I would seriously suggest chucking out something other than a 200 response code. If the spider hits and your server blerts out a 503 (service unavailable) code, chances are it will come back later on or another day.
我会认真地建议除了200响应代码之外的东西。如果蜘蛛命中并且您的服务器发出503(服务不可用)代码,则可能会在稍后或其他日期返回。
If it gets a 200 it might assume your site has changed and change its index.
如果它获得200,它可能会假设您的网站已更改并更改其索引。
#6
0
Like others said, return an appropriate error code. Either return a 40x (not 404) or 50x code. Don't redirect to a "maintenance" page, or return a 200 with a static maintenance page.
像其他人说的那样,返回适当的错误代码。返回40x(不是404)或50x代码。不要重定向到“维护”页面,也不要返回带有静态维护页面的200页面。
I've seen a few pages from time to time on Google which are cached as "down for maintenance" or something.
我在Google上不时看到几页被缓存为“维护”的页面。
#1
10
No, not if you make sure to send the proper HTTP-headers. Do not send 200 OK, as this will make the search engines index your error message.
不,如果您确保发送正确的HTTP标头,请不要这样做。不要发送200 OK,因为这会使搜索引擎索引您的错误消息。
I would suggest sending "503 Service Unavailable" together with a text explaining why and how long you will be down..
我建议发送“503 Service Unavailable”和一条文字,说明你将失败的原因和时间。
#2
2
For a list of HTTP status codes see:
有关HTTP状态代码的列表,请参阅:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Specially for maintenance:
特别用于维护:
10.5.4 503 Service Unavailable
10.5.4 503服务不可用
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
由于服务器的临时过载或维护,服务器当前无法处理请求。这意味着这是一个暂时的条件,经过一段时间的延迟后会得到缓解。如果已知,延迟的长度可以在Retry-After报头中指示。如果没有给出Retry-After,客户端应该像处理500响应一样处理响应。
#3
1
How long will the “Site Down for Maintenance” page be live? If only a day, then it would be fine.
“网站停机维护”页面会有多长时间生效?如果只有一天,那就没关系了。
#4
0
Typically this is done for short periods of time (under 6-12 hours). I have never noticed a situation where this is an issue, as the google bot sees the dramatic change in content and it appears to essentially come back later like visitors. Now this isn't an official remark, just what I have noticed on my sites.
通常这是在短时间内(6-12小时)完成的。我从来没有注意到这是一个问题,因为谷歌机器人看到了内容的巨大变化,它似乎基本上像访客一样回来。现在这不是官方评论,只是我在网站上注意到的。
#5
0
It would either have to:
它要么必须:
- be a really long upgrade, or
- you'd be seriously unlucky to have a spider try your site while upgrading
是一个很长的升级,或
在升级时让蜘蛛尝试你的网站是非常不幸的
But if you are going to be longer than half a day to a day, consider this:
但如果你要超过半天到一天,请考虑这个:
I would seriously suggest chucking out something other than a 200 response code. If the spider hits and your server blerts out a 503 (service unavailable) code, chances are it will come back later on or another day.
我会认真地建议除了200响应代码之外的东西。如果蜘蛛命中并且您的服务器发出503(服务不可用)代码,则可能会在稍后或其他日期返回。
If it gets a 200 it might assume your site has changed and change its index.
如果它获得200,它可能会假设您的网站已更改并更改其索引。
#6
0
Like others said, return an appropriate error code. Either return a 40x (not 404) or 50x code. Don't redirect to a "maintenance" page, or return a 200 with a static maintenance page.
像其他人说的那样,返回适当的错误代码。返回40x(不是404)或50x代码。不要重定向到“维护”页面,也不要返回带有静态维护页面的200页面。
I've seen a few pages from time to time on Google which are cached as "down for maintenance" or something.
我在Google上不时看到几页被缓存为“维护”的页面。