Change:
color: #fff; background: #326de6; } <ins> // Adjust Bing search result page #bing-results-container { padding: 1em; } #bing-pagination-container { padding: 1em; margin-bottom: 1em; a.bing-page-anchor { padding: 0.5em; margin: 0.25em; } } </ins>

Discussion:
In Kubernetes docs when you search, search results page number displays as "". There is no space between page numbers. The commit message appears at the bottom of the page which is irrelevant. Also, the hyperlink appears in each search results which is not needed. eg: Expected Output. Search results in a proper way.
/language en Sounds like 3 different issues, :)
Can you clarify the issue(s) you're reporting If you can include a screenshot that's helpful; if you can open a new issue for each separate defect that's even better.
This problem happens when using Bing search. Here is the screenshot: !
/area web-development For context, the website uses Google Search unless corporate filtering / state-level censorship / similar restrictions prevent using Google, and for those readers there is a fallback to Bing search.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten I'm going to create a PR to fix this styling issue.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
/triage accepted /lifecycle frozen
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions 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
It took a long time but I made a PR to fix this issue.