Sitelinks in Google disappearing

Over the past few months, my Sitelinks within google search have slowly disappeared (see graph below). Anyone else experiencing same? We’ve not touched the site other than updates for a long while.


You forgot to post the graph. :slight_smile:




Same for me. I think Google is reporting ‘No Rich Results Detected’ - finding only the searchbox on each page.

Perhaps see here:


I see that the falloff of valid pages dates from mid-November or so. There were two releases in that time: 2.9.0.beta11 about Nov 1, and 2.9.0.beta12 about Nov 14. I usually update within three days of a release.

This is my graph:

It seems possible to me the HTML structure of a Discourse page changed in some significant-to-Google way in one or other of those releases.


And one similar more:

Smaller forum so those drops are more clear. And I have tendency update/upgrade at leat once every week,


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">
    <meta charset="utf-8">
    <title>One bit-flipping NIC took down Amazon&#39;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&amp;hellip;">
    <meta name="discourse_theme_id" content="3">
    <meta name="discourse_current_homepage" content="latest">

    <meta name="generator" content="Discourse 2.9.0.beta14 - version fb2507c6ce80a1f4fc3a68a23342e5eca765a13f">
<link rel="icon" type="image/png" href="">
<link rel="apple-touch-icon" type="image/png" href="">
<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="" />

<link rel="search" type="application/opensearchdescription+xml" href="" 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 &#39;One bit-flipping NIC took down Amazon&#39;s cloud storage (2008)&#39;" href="" />
    <meta property="og:site_name" content="Postmortems" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary" />
<meta name="twitter:image" content="" />
<meta property="og:image" content="" />
<meta property="og:url" content="" />
<meta name="twitter:url" content="" />
<meta property="og:title" content="One bit-flipping NIC took down Amazon&#39;s cloud storage (2008)" />
<meta name="twitter:title" content="One bit-flipping NIC took down Amazon&#39;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="" 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/" data-svg-sprite-path="/svg-sprite/" 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" />

  <body class="">


In my case it decreased quite a lot many months ago.
In the picture there is only the last period.

Indexed pages have also dropped a lot…

1 Like

I’m having a similar issue but it’s likely a site-specific issue in my case (unless others are also experiencing this?)

Sitelinks also fell off for me around the beginning of November. Seems like the homepage is the only one left

1 Like

Site One:

Site Two (much newer):


1 Like

No no, it’s not just your case…
I have the decrease in indexed pages in two different discourse sites and only with this software.
It’s been going on for months and getting worse and worse, now I’m trying to migrate to something else.

1 Like

Don’t just focus on sitelinks, indexed pages also have the same problem.


Yes, seems so, though decline is slower and less dramatic …


Is googlebot falling in class of unsupported browser?


what does an unsupported browser see? A page with a single link to a list of supported browsers? :wink:

Then again, how would that explain a decline and not a cliff edge?

1 Like

running latest 3.1.0.beta2

1 Like

I don’t know. You tell me :wink:

I know same as everybody: structure of a site is the base what google is using when it makes decision what and how to show. But the structure is only base and everything else comes from algorithms of Google.

Because this is happening to virtually every discourse site, there is just two options:

  • something has happened in discourse
  • google has changed the algorithm

And the result is that forums aren’t ”worthy” to show sitelinks. But, most of forums actually don’t need search results with sitelinks. It doesn’t serve any real value to users.

It could show categories. But even here is too many and those would fill/expand resultpages. If any of you haven’t noticed Google tries to keep lenght of seach result page quite same all the time.

I really don’t know. Anyone here doesn’t. But I know so much that even my WordPress-sites are acting totally similar.

SEO is still good, though (edit: I ment say ranking). But, my Discourse is not even close to something I would achieve using WordPress and that is something I’ve wondered quite long time now.


I would worry a lot less about indexed pages - forums like discourse have lots of redundant links which lead to the same page. We could be seeing deduplication, which is good, because otherwise a forum looks like a giant SEO web farm.

1 Like

This topic title says “Site links disappearing” but that graph you linked says “Sitelinks searchbox”.

I googled some hosted sites of us and Sitelinks are still present in all. What is gone is the searchbox part of it.

So something changed somewhere and Discourse search results, when Sitelinks are rendered, are lacking a search input field. That’s a correct description of the problem?


These graphs are of the results of page indexing. Can someone share what the reasons Google gives for their pages not being indexed?

For example, if I look here on meta, 66% of our non-indexed pages are due to “Alternate page with proper canonical tag”. What are others seeing?

1 Like