diff --git a/docs/google-search-console-integration.md b/docs/google-search-console-integration.md
index 15db835a..5fb3d628 100644
--- a/docs/google-search-console-integration.md
+++ b/docs/google-search-console-integration.md
@@ -12,6 +12,8 @@ However, you can still access your search terms by setting up your site on Googl
 
 This integration is privacy-friendly and requires no Google code to be placed on your site. Google is basically just sending us the information they’ve already collected on their search results.
 
+Plausible doesn't store this Search Console data. We fetch search query, clicks, impressions, CTR and position data from the Google Search Console API whenever you view the report, and don't save any of it in our database. We only store the authorization details and the property you've selected, which is what's needed to keep the integration running.
+
 <CtaBox
   headline="See SEO queries and website analytics in one dashboard"
   link="https://plausible.io/register"
@@ -123,6 +125,8 @@ You can check if Plausible Analytics is integrated with and has the right permis
 
 If you'd like to remove the Google Search Console integration, click on the **Unlink Google account** button in the **Google Search Console Integration** module within the **Integrations** section of your website settings.
 
+Since Plausible doesn't store any Search Console data, disconnecting means the search query stats immediately stop appearing in your dashboard. They'll come back once you reconnect the integration.
+
 P.S. If you want to learn more about analyzing organic search traffic in Plausible, visit our [blog post](https://plausible.io/blog/seo-dead#analyzing-organic-search-traffic).
 
 ## What's next?
diff --git a/src/css/custom.css b/src/css/custom.css
index ffd98369..c658e767 100644
--- a/src/css/custom.css
+++ b/src/css/custom.css
@@ -257,6 +257,15 @@ html[data-theme='dark'] {
   font-weight: 500;
 }
 
+/* Give anchor-linked headings clearance from the sticky navbar.
+   Docusaurus's default scroll-margin-top (navbar height + 0.5rem) leaves
+   headings flush against the navbar, which reads as landing on the wrong
+   section for short chapters. Needs .markdown prefix to out-specificity
+   the theme's own anchorTargetStickyNavbar_* rule regardless of CSS order. */
+.markdown .anchor {
+  scroll-margin-top: calc(var(--ifm-navbar-height) + 1.5rem);
+}
+
 @media (min-width: 997px) {
   .col.docItemCol_VOVn {
     max-width: calc(75% - var(--ifm-spacing-horizontal)) !important;