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

DuckDuckGo: SEO Description broken mostly for stable class pages #10470

Closed
jcommander opened this issue Jan 4, 2025 · 2 comments
Closed

DuckDuckGo: SEO Description broken mostly for stable class pages #10470

jcommander opened this issue Jan 4, 2025 · 2 comments
Labels
archived bug content:website Issues related to adding website features and fixing bugs, whether on the front or back-end

Comments

@jcommander
Copy link

Well, I'm not sure if this Issue can be fixed with the Docs or if it resides on DuckDuckGo's Side but I thought it would make sense to track since there are some interesting observations:

I've noticed the SEO description being all messed up on DuckDuckGo for a while.
I have basically only seen it on the Class Reference pages... it doesn't seem to be completely consistent though

But I remember it not being like this, so I searched for 3.2 docs, and to my surprise, they're still fine

Google
Image

DuckDuckGo (stable)
Image

DuckDuckGo (3.2)
Image

Maybe someone has an idea what is happening here.

@hsvfan-jan
Copy link

Doesn't seem to be version specific

Image

@tetrapod00 tetrapod00 added the content:website Issues related to adding website features and fixing bugs, whether on the front or back-end label Jan 5, 2025
@mhilbrunner
Copy link
Member

mhilbrunner commented Jan 6, 2025

Thanks for reporting! After a brief Google (😉), this appears to be a Bing (and thus DDG) issue, unrelated to Godot specifically.

For example, here is someone encountering it on another website:
canonical/microk8s.io#628 (and yes, Godot's Docs do contain <meta charset="utf-8" />)

There are more, similar results around the web, like https://answers.netlify.com/t/bing-indexed-a-scrambled-version-wrong-encoding/54751.

For now, I'm going to close this, as I don't think there is anything we can do to fix this. Some of the results suggest it cleared up after a while (probably on re-indexing), so let's hope for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
archived bug content:website Issues related to adding website features and fixing bugs, whether on the front or back-end
Projects
None yet
Development

No branches or pull requests

4 participants