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

SEO: Google search console: Server error (5xx) #8508

Closed
chrifro opened this issue Mar 1, 2022 · 2 comments · Fixed by #9622
Closed

SEO: Google search console: Server error (5xx) #8508

chrifro opened this issue Mar 1, 2022 · 2 comments · Fixed by #9622
Assignees
Labels

Comments

@chrifro
Copy link

chrifro commented Mar 1, 2022

According to Google Search Console, there are 64 pages that return a 5xx error. [1]

Most affected URLs are: https://gitpod.io/api/xyz
Bildschirmfoto 2022-03-01 um 11 30 21

@filiptronicek
Copy link
Member

@ChristinFrohne should these endpoints even be indexed? I am guessing they are not needed for SEO and shouldn't be in anyone's search results 😄, maybe we should add the /api/ route to https://github.com/gitpod-io/gitpod/blob/main/components/dashboard/public/robots.txt?

I'm not sure who to cc / mention here though, maybe @jankeromnes?

@chrifro
Copy link
Author

chrifro commented Mar 1, 2022

True, we should also have a general look at which pages of gitpod.io we want to be indexed.
e.g. workspace URL should be removed as well
https://imgur.com/b11BtRz
https://imgur.com/b11BtRz
related issue: https://github.com/gitpod-io/website/issues/1464

Here is the open task for de-indexing pages. Happy to snyc with someone on that [1]

@geropl geropl added component: dashboard type: bug Something isn't working labels Mar 14, 2022
@geropl geropl changed the title Google search console: Server error (5xx) SEO: Google search console: Server error (5xx) Apr 7, 2022
@jankeromnes jankeromnes self-assigned this Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

4 participants