diff --git a/content/2015-12.md b/content/2015-12.md
index 4840c01c4..b26a4176a 100644
--- a/content/2015-12.md
+++ b/content/2015-12.md
@@ -147,3 +147,4 @@ $ curl -o /dev/null -s -w %{time_total}\\n https://cgspace.cgiar.org/rest/handle
## 2015-12-08
- Switch CGSpace log compression cron jobs from using lzop to xz—the compression isn't as good, but it's much faster and causes less IO/CPU load
+- Since we figured out (and fixed) the cause of the performance issue, I reverted Google Bot's crawl rate to the "Let Google optimize" setting
diff --git a/public/2015-12/index.html b/public/2015-12/index.html
index 61283ab77..57e5ab046 100644
--- a/public/2015-12/index.html
+++ b/public/2015-12/index.html
@@ -236,6 +236,7 @@ $ curl -o /dev/null -s -w %{time_total}\\n https://cgspace.cgiar.org/rest/handle
- Switch CGSpace log compression cron jobs from using lzop to xz—the compression isn’t as good, but it’s much faster and causes less IO/CPU load
+- Since we figured out (and fixed) the cause of the performance issue, I reverted Google Bot’s crawl rate to the “Let Google optimize” setting
diff --git a/public/index.xml b/public/index.xml
index b0f517b16..d762d11c6 100644
--- a/public/index.xml
+++ b/public/index.xml
@@ -174,6 +174,7 @@ $ curl -o /dev/null -s -w %{time_total}\\n https://cgspace.cgiar.org/rest/handle
<ul>
<li>Switch CGSpace log compression cron jobs from using lzop to xz—the compression isn’t as good, but it’s much faster and causes less IO/CPU load</li>
+<li>Since we figured out (and fixed) the cause of the performance issue, I reverted Google Bot’s crawl rate to the “Let Google optimize” setting</li>
</ul>
diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml
index e82900bc9..28573dedb 100644
--- a/public/tags/notes/index.xml
+++ b/public/tags/notes/index.xml
@@ -174,6 +174,7 @@ $ curl -o /dev/null -s -w %{time_total}\\n https://cgspace.cgiar.org/rest/handle
<ul>
<li>Switch CGSpace log compression cron jobs from using lzop to xz—the compression isn’t as good, but it’s much faster and causes less IO/CPU load</li>
+<li>Since we figured out (and fixed) the cause of the performance issue, I reverted Google Bot’s crawl rate to the “Let Google optimize” setting</li>
</ul>