Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve search engine ranking for minikube.sigs.k8s.io #6763

Closed
blueelvis opened this issue Feb 23, 2020 · 10 comments
Closed

Improve search engine ranking for minikube.sigs.k8s.io #6763

blueelvis opened this issue Feb 23, 2020 · 10 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@blueelvis
Copy link
Contributor

I was searching for the documentation which is hosted as part of this repo at this link - https://minikube.sigs.k8s.io/ & surprisingly, I couldn't find it in any of the following search engines on the 1st page when just searching for minikube -

  1. Google
  2. DuckDuckGo
  3. Bing

I think that the docs website should come up. What do you guys think?

@medyagh
Copy link
Member

medyagh commented Feb 23, 2020

Any seo experts?

@medyagh
Copy link
Member

medyagh commented Feb 23, 2020

@blueelvis sorry irrelevant but any interest to help have windows tests for docker driver on GitHub actions? This PR is stuck we need some windows expert help #6580

@blueelvis
Copy link
Contributor Author

@medyagh - Yes sir. I have been out travelling quite a lot so just getting back in :( . Just joined as a reviewer on that PR.

Not an SEO expert over here. @tstromberg - Any chance you know someone?

@blueelvis
Copy link
Contributor Author

I just ran a Chrome Lighthouse audit and found the following -

image

@afbjorklund afbjorklund added the kind/documentation Categorizes issue or PR as related to documentation. label Feb 23, 2020
@afbjorklund
Copy link
Collaborator

@afbjorklund
Copy link
Collaborator

afbjorklund commented Feb 23, 2020

I think this part could need some improvement: https://minikube.sigs.k8s.io/blog/

Posts in 2019

v1.3.1 released
Tuesday, August 13, 2019 in Releases

https://github.com/kubernetes/minikube/tree/master/site/content/en/blog

@priyawadhwa priyawadhwa added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Feb 25, 2020
@tstromberg
Copy link
Contributor

Update:

Not great, but also not terrible.

@tstromberg tstromberg changed the title The Documentation website doesn't pop in any search results Improve search engine ranking for minikube.sigs.k8s.io Apr 20, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 18, 2020
@sharifelgamal sharifelgamal added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Aug 26, 2020
@sharifelgamal
Copy link
Collaborator

sharifelgamal commented Dec 16, 2020

There's not a whole lot for us to do here, if we come up with something, we can reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

8 participants