在过去的几个月里，我在谷歌搜索中的网站链接（Sitelinks）已逐渐消失（见下图）。还有其他人遇到同样的情况吗？我们除了长期更新外，并未对网站进行任何其他操作。
2 个赞
你忘了发图了。 
2 个赞
我也是。我认为 Google 报告“未检测到富媒体搜索结果”——每个页面只找到搜索框。
也许可以看看这里：
3 个赞
我注意到有效页面的下降可以追溯到 11 月中旬左右。在此期间有两个版本：2.9.0.beta11 大约在 11 月 1 日发布，2.9.0.beta12 大约在 11 月 14 日发布。我通常会在发布后三天内更新。
这是我的图表：
对我来说，似乎有可能 Discourse 页面的 HTML 结构在其中一个版本中发生了对 Google 来说很重要的变化。
2 个赞
I happen to use a Discourse forum which is obscure and not so frequently updated, and probably not crawled by Google very often.
If I search for
“One bit-flipping NIC took down Amazon’s cloud storage”
I get a result which includes an image from the target page:
I suspect this is what we’re now missing out on. Results for my updated and less obscure forums are just plain text snippets.
Here’s the header of that target page as seen by my browser - not sure if Google sees the same or not.
<!DOCTYPE html>
<html lang="en" class="desktop-view not-mobile-device text-size-normal">
<head>
<meta charset="utf-8">
<title>One bit-flipping NIC took down Amazon's cloud storage (2008) - cloud - Postmortems</title>
<meta name="description" content="Official statement:
Amazon S3 Availability Event: July 20, 2008
Peter Vosshall in the video below says
… it took down s3 completely. So one server, one NIC, one bit, took down our regional service and that was the on&hellip;">
<meta name="discourse_theme_id" content="3">
<meta name="discourse_current_homepage" content="latest">
<meta name="generator" content="Discourse 2.9.0.beta14 - https://github.com/discourse/discourse version fb2507c6ce80a1f4fc3a68a23342e5eca765a13f">
<link rel="icon" type="image/png" href="https://postmortems.info/uploads/default/optimized/1X/_129430568242d1b7f853bb13ebea28b3f6af4e7_2_32x32.png">
<link rel="apple-touch-icon" type="image/png" href="https://postmortems.info/uploads/default/optimized/1X/_129430568242d1b7f853bb13ebea28b3f6af4e7_2_180x180.png">
<meta name="theme-color" media="all" content="#ffffff">
<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, user-scalable=yes, viewport-fit=cover">
<link rel="canonical" href="https://postmortems.info/t/one-bit-flipping-nic-took-down-amazons-cloud-storage-2008/622" />
<link rel="search" type="application/opensearchdescription+xml" href="https://postmortems.info/opensearch.xml" title="Postmortems Search">
<meta name="csrf-param" content="authenticity_token" />
<meta name="csrf-token" content="HMY_f3K39gT7gyv1DSmPRW8zd7v29Z0kD55iyNR9C3zgwwBbbgXmhK9Euzuu0gpooN7LlzSSueWlIz4GawwPmw" />
<meta name="fragment" content="!">
<link rel="preload" href="/assets/start-discourse-f6e4e67026eabe0c9b84599087eb11ee33d8149f196b7439b0630ed5ab4d5f29.js" as="script">
<link rel="preload" href="/assets/browser-update-d7761004034ce1ea7686d586f5e8a8d216e6f67b609f9b4bcaba53b8b8d34729.js" as="script">
<link rel="preload" href="/assets/browser-detect-7af298cd000a967d2bdc01b04807eda2924a388584ea38ad84919b726283c2ed.js" as="script">
<script defer src="/assets/browser-detect-7af298cd000a967d2bdc01b04807eda2924a388584ea38ad84919b726283c2ed.js"></script>
<link rel="preload" href="/assets/locales/en-4632a4adf53ab69af31ccd61772e71da2b8d273a9238188b7322caa0beb9e231.js" as="script">
<script defer src="/assets/locales/en-4632a4adf53ab69af31ccd61772e71da2b8d273a9238188b7322caa0beb9e231.js"></script>
<link rel="preload" href="/assets/vendor-0086bb622ee0d0e4b902506c9c6b6e6da9dea80b09d9e2307a0e80ee8ae90cb5.js" as="script">
<script defer src="/assets/vendor-0086bb622ee0d0e4b902506c9c6b6e6da9dea80b09d9e2307a0e80ee8ae90cb5.js"></script>
<link rel="preload" href="/assets/chunk.857.91d4bdb47afe27a0b223-cc02271de56ef602d0fb03225b01336e39ea5e0e833131533d046d5f7fa0e9dd.js" as="script">
<script defer src="/assets/chunk.857.91d4bdb47afe27a0b223-cc02271de56ef602d0fb03225b01336e39ea5e0e833131533d046d5f7fa0e9dd.js"></script>
<link rel="preload" href="/assets/chunk.143.554dfbd1faa360aeb1d7-bbbe9995b2c8f62e4972b08bcea57ab4fbca241815fa3712c9c82bc3a692155e.js" as="script">
<script defer src="/assets/chunk.143.554dfbd1faa360aeb1d7-bbbe9995b2c8f62e4972b08bcea57ab4fbca241815fa3712c9c82bc3a692155e.js"></script>
<link rel="preload" href="/assets/discourse-5717caf5e6e015828843fb47d9b7fa86336c8c7a3f293f8ca41d572e4a458e96.js" as="script">
<script defer src="/assets/discourse-5717caf5e6e015828843fb47d9b7fa86336c8c7a3f293f8ca41d572e4a458e96.js"></script>
<link rel="preload" href="/assets/plugins/discourse-details-3262864f1b5a3f1b862422b3e2a0d3a296de258f13c70f25bd1f512e29ed1d97.js" as="script">
<script defer src="/assets/plugins/discourse-details-3262864f1b5a3f1b862422b3e2a0d3a296de258f13c70f25bd1f512e29ed1d97.js"></script>
<link rel="preload" href="/assets/plugins/discourse-local-dates-3d830b7216fd387586ab877d3474fd56fe7d1b58f7915636490c00baca46a3a9.js" as="script">
<script defer src="/assets/plugins/discourse-local-dates-3d830b7216fd387586ab877d3474fd56fe7d1b58f7915636490c00baca46a3a9.js"></script>
<link rel="preload" href="/assets/plugins/discourse-narrative-bot-cb6fa1c8b042328ccee9b135ef703e4c383d0595f1ee4d2f0cc2392a48ce485b.js" as="script">
<script defer src="/assets/plugins/discourse-narrative-bot-cb6fa1c8b042328ccee9b135ef703e4c383d0595f1ee4d2f0cc2392a48ce485b.js"></script>
<link rel="preload" href="/assets/plugins/discourse-presence-11bf773d7d34416ce01190e5c36e8d9e7c6ac78c5dc848f38402f82f05fc37b3.js" as="script">
<script defer src="/assets/plugins/discourse-presence-11bf773d7d34416ce01190e5c36e8d9e7c6ac78c5dc848f38402f82f05fc37b3.js"></script>
<link rel="preload" href="/assets/plugins/docker_manager-3d9182e7201f69426040bf2be635fa04454aa12b984610fab305ce6ae44689a3.js" as="script">
<script defer src="/assets/plugins/docker_manager-3d9182e7201f69426040bf2be635fa04454aa12b984610fab305ce6ae44689a3.js"></script>
<link rel="preload" href="/assets/plugins/lazy-yt-37ba46caad39a8d451e22030fac3ba0c04d3c2aa5cf73544b9c23ec143dcbf99.js" as="script">
<script defer src="/assets/plugins/lazy-yt-37ba46caad39a8d451e22030fac3ba0c04d3c2aa5cf73544b9c23ec143dcbf99.js"></script>
<link rel="preload" href="/assets/plugins/poll-3772958eb9b6ce2f5bbb0a90e9a2925586933212cc816daa749f2a6ff7c8d5cc.js" as="script">
<script defer src="/assets/plugins/poll-3772958eb9b6ce2f5bbb0a90e9a2925586933212cc816daa749f2a6ff7c8d5cc.js"></script>
<link rel="preload" href="/extra-locales/admin?v=5273f5b8ab23c0f09f8900c146f7dfbb" as="script">
<script defer src="/extra-locales/admin?v=5273f5b8ab23c0f09f8900c146f7dfbb"></script>
<link rel="preload" href="/assets/admin-3e297caed7810816d80e1d9564d31c87fd0e6d43133d12828144f485df3aa5a9.js" as="script">
<script defer src="/assets/admin-3e297caed7810816d80e1d9564d31c87fd0e6d43133d12828144f485df3aa5a9.js"></script>
<link id="manifest-link" rel="manifest" href=/manifest.webmanifest crossorigin="use-credentials">
<link rel="alternate nofollow" type="application/rss+xml" title="RSS feed of 'One bit-flipping NIC took down Amazon's cloud storage (2008)'" href="https://postmortems.info/t/one-bit-flipping-nic-took-down-amazons-cloud-storage-2008/622.rss" />
<meta property="og:site_name" content="Postmortems" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary" />
<meta name="twitter:image" content="https://postmortems.info/images/discourse-logo-sketch-small.png" />
<meta property="og:image" content="https://postmortems.info/images/discourse-logo-sketch-small.png" />
<meta property="og:url" content="https://postmortems.info/t/one-bit-flipping-nic-took-down-amazons-cloud-storage-2008/622" />
<meta name="twitter:url" content="https://postmortems.info/t/one-bit-flipping-nic-took-down-amazons-cloud-storage-2008/622" />
<meta property="og:title" content="One bit-flipping NIC took down Amazon's cloud storage (2008)" />
<meta name="twitter:title" content="One bit-flipping NIC took down Amazon's cloud storage (2008)" />
<meta property="og:description" content="Official statement: Amazon S3 Availability Event: July 20, 2008 Peter Vosshall in the video below says … it took down s3 completely. So one server, one NIC, one bit, took down our regional service and that was the only layer - we had checksumming all the way up and down the stack - that was the only layer that didn’t have the checksumming. As seen on HN: Reminds me of a rogue NIC, flipping a single bit every now and then, that took down S3: Ref: https://news.ycombinator...." />
<meta name="twitter:description" content="Official statement: Amazon S3 Availability Event: July 20, 2008 Peter Vosshall in the video below says … it took down s3 completely. So one server, one NIC, one bit, took down our regional service and that was the only layer - we had checksumming all the way up and down the stack - that was the only layer that didn’t have the checksumming. As seen on HN: Reminds me of a rogue NIC, flipping a single bit every now and then, that took down S3: Ref: https://news.ycombinator...." />
<meta property="article:published_time" content="2020-05-11T13:14:59+00:00" />
<meta property="og:ignore_canonical" content="true" />
<meta id="data-discourse-setup" data-base-url="https://postmortems.info" data-base-uri="" data-environment="production" data-letter-avatar-version="5_684b749d1c1eee86b31a584fa946fc1a" data-markdown-it-url="/assets/markdown-it-bundle-2cd81b202957f9fd91c706abaa4902ae44bb77e7b0ef6abcf5c18587dfa9c5b6.js" data-service-worker-url="service-worker.js" data-default-locale="en" data-asset-version="191356ca2533fd1871d60d97ca8dca2f" data-disable-custom-css="false" data-highlight-js-path="/highlight-js/postmortems.info/a5a82d5d9c93ba17b974dbe7408b61e64d7130b7.js" data-svg-sprite-path="/svg-sprite/postmortems.info/svg-3-69607f2c7bea253fd5873db55f6da14d4413a71b.js" data-enable-js-error-reporting="true" data-color-scheme-is-dark="false" data-user-color-scheme-id="2" data-user-dark-scheme-id="-1">
<meta name="discourse/config/environment" content="%7B%22modulePrefix%22%3A%22discourse%22%2C%22environment%22%3A%22production%22%2C%22rootURL%22%3A%22%22%2C%22locationType%22%3A%22history%22%2C%22historySupportMiddleware%22%3Afalse%2C%22EmberENV%22%3A%7B%22FEATURES%22%3A%7B%7D%2C%22EXTEND_PROTOTYPES%22%3A%7B%22Date%22%3Afalse%7D%2C%22_APPLICATION_TEMPLATE_WRAPPER%22%3Afalse%2C%22_DEFAULT_ASYNC_OBSERVERS%22%3Atrue%2C%22_JQUERY_INTEGRATION%22%3Atrue%7D%2C%22APP%22%3A%7B%22name%22%3A%22discourse%22%2C%22version%22%3A%222.9.0.beta14%20fb2507c6ce80a1f4fc3a68a23342e5eca765a13f%22%2C%22exportApplicationGlobal%22%3Atrue%7D%7D" />
</head>
<body class="">
5 个赞
不不，不只是你的情况……
我在两个不同的 Discourse 站点上都遇到了索引页面减少的问题，而且只使用这个软件。
这个问题已经持续了好几个月，而且越来越糟，我现在正试图迁移到别的东西上。
1 个赞
不要只关注网站链接，已编入索引的页面也存在同样的问题。
2 个赞
是的，似乎是这样，尽管下降速度较慢且不那么剧烈……
2 个赞
googlebot 是否属于不支持的浏览器类别？
2 个赞
不支持的浏览器会看到什么？一个带有指向支持的浏览器列表的单个链接的页面？
话又说回来，这如何解释下降而不是悬崖边缘？
2 个赞
我不知道。你告诉我吧
我知道的和大家一样：网站结构是谷歌做决定显示什么以及如何显示的根本依据。但结构只是基础，其他一切都来自谷歌的算法。
因为这几乎发生在每一个 Discourse 网站上，只有两种可能：
- Discourse 发生了什么事
- 谷歌改变了算法
结果是论坛不再“值得”显示站点链接。但是，大多数论坛实际上不需要带有站点链接的搜索结果。它对用户没有实际价值。
它可以显示分类。但即使是分类也太多了，而且它们会填满/扩展结果页面。如果你还没有注意到，谷歌会试图一直保持搜索结果页面的长度大致相同。
我真的不知道。这里的任何人也不知道。但我知道的是，即使是我的 WordPress 网站也表现出完全类似的情况。
SEO 仍然很好，尽管（编辑：我的意思是排名）。但是，我的 Discourse 远不及我使用 WordPress 所能达到的水平，这一点我一直很困惑。
2 个赞
我会少担心索引页面——像 Discourse 这样的论坛有很多重复的链接指向同一个页面。我们可以看到去重，这很好，因为否则论坛看起来就像一个巨大的 SEO 网站农场。
2 个赞
此主题标题为“站点链接消失”，但您链接的图表显示“站点链接搜索框”。
我搜索了一些我们托管的网站，站点链接仍然全部存在。消失的是其中的搜索框部分。
所以有些东西在某处发生了变化，并且 Discourse 的搜索结果在呈现站点链接时缺少搜索输入字段。这是对问题的正确描述吗？
3 个赞
这些图表显示的是页面索引结果。有人能分享一下 Google 给出页面未被索引的原因吗？
例如，如果我在这里查看元数据，我们 66% 的未索引页面是由于“具有正确规范标签的替代页面”造成的。你们看到了什么？
1 个赞