Change:
{{ if .Page.Param "announcement" }} <section lang="en" id="fp-announcement" style="background-color:{{ .Page.Param "announcement_bg" }}"> <del> <main> <div class="content announcement main-section"> </del> <ins> <aside > <div class="content announcement main-section" data-nosnippet> </ins> <h3> {{ T "announcement_title" |  markdownify }}

Discussion:
The announcement banner text (merged in ) is being used as the Google search snippet for docs pages. This may not have been your intention. !
SIG Docs doesn't have a good way to improve Google's indexing algorithm. The text is in an HTML element which should mark it as an aside: content only indirectly related to the main content. I'd characterize this as a Google bug. There are a lot of Google people in the Kubernetes ecosystem but probably not from the web search side. Do you agree with that characterization? /triage awaiting-more-evidence
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : SIG Docs doesn't have a good way to improve Google's indexing algorithm. The text is in an HTML element which should mark it as an aside: content only indirectly related to the main content. /triage awaiting-more-evidence Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/priority awaiting-more-evidence
I can't find anything suggesting Google has ever ignored elements, and I can find a comment from someone at Google saying they explicitly ignore them ( via ). The supported way to mark something not to go in a snippet is the attribute: , . I can raise a feature request with the search team to ask them to treat like but from a Kubernetes users perspective, changing the site will get to a better outcome quicker.
It sounds useful to add to the announcements.
I would adjust to "fix now"
Yikes, sorry guys! I would also mark as fix now
/priority fix-now
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /priority fix-now Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-priority awaiting-more-evidence /priority critical-urgent

This is a Feature Request The HTML partials, and frontpage-, contain a element which duplicates the element found in the body of the page. This became an issue as the docsy theme updates page anchors in the script . This script depends upon the element and failed to find the H1 - H6 level headings on the page to udpate. What would you like to be Investigate how to include the announcement banner on the docs pages (front page, docs, blog, and so on) without the element. Investigate changes to the corresponding stylesheet. Why is this needed Clean up or adjust the preexisting, related code as well as the current templates and stylesheet. Provide a flexible way to add and remove content such as announcement or banners on the pages. Comments For additional information, see PR .
/assign
/kind cleanup /priority important-soon
/reopen There might be more to do here.
Reopened this issue. <detailsIn response to : /reopen There might be more to do here. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I don't think there's any more work that needs doing here! you can close this off :)
Good. The only thing noted is some different styling per main section (docs vs case studies). /close
Closing this issue. <detailsIn response to : Good. The only thing noted is some different styling per main section (docs vs case studies). /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details