-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
BaseUrl banner: make the message configurable please Google/SEO/indexers #4028
Comments
Thanks for reporting this. Can you explain how this affects your site exactly? I mean, no one is googling for "Your Docusaurus site did not load properly.", so how did you find it was a problem, and how customizing the message will solve it? Maybe we should also add an opt-in option to remove it? |
I see a lot of docusaurus doc sites be indexed by google that way, probably since it is hosted as static only. I was just offering you to search for that exact string so you can see the scale of the problem. Maybe crawlers can be told to ONLY index meta description instead of that message, but I am not very deep into html specs any more... |
I do agree that these Docusaurus 2 sites get indexed in an unexpected way, and we should likely offer a way to disable that. I just wonder why specifically it is a problem for you and your users? It is very unlikely that a user will type such a string on Google, and when searching for "Docusaurus 2" I'm just trying to understand better your motivations to figure out the best way to do something about it. Maybe by default we could write "your site www.xyz.com did not load properly" or something? Does a new config option really solve the problem? As many site owners wouldn't even be aware of that option? |
Look, I really don't care what REAL people see that have javascript turned off (I regard them as weirdos and not part of our target population), so I'd rather cater to the CRAWLERS, and get a nice message on google et al. |
I found our site to be indexed with that message, so it's not about how and via what route I found out about that. Only then did I do an extra search for that string, to reveal the scale of this. |
I have to say I am not aware anymore of what I searched for, but it was the day of a media announcement and was generating some keyword combos and then saw it indexed like that. I just tried some again but can't reproduce. |
I understand. |
Thanks for being so sweet. Sorry about my hammering. It's no prio. |
Hey, Totally forgot about this, but it's already possible to disable this message 😅 https://v2.docusaurus.io/docs/next/docusaurus.config.js/#baseurlissuebanner Still trying to find a solution, will attempt a few things to make the message not indexed by default, but not sure about the Google Crawler behavior : |
This PR will ensure that the help banner is not server-rendered anymore. This should prevent the google indexation. As it is possible to disable this banner with config, and it should normally not be indexed anymore, I don't think it's worth it to be able to customize that message. Going to close this for now, but we'll check if the message is still indexed or not soon. |
The message is a helpful pointer for new users but in general I think it
could be omitted. By searching online for the exact message, there is a
number of docusaurus pages that have the issue so my opinion is that it
creates more problems that the problems it solves.
An idea could be to disable it by default on anything except localhost.
Anyway, thanks a lot for your response!
…On Fri, 29 Jan 2021 at 18:44, Sébastien Lorber ***@***.***> wrote:
#4125 <#4125>
This PR will ensure that the help banner is not server-rendered anymore.
This should prevent the google indexation.
As it is possible to disable this banner with config, and it should
normally not be indexed anymore, I don't think it's worth it to be able to
customize that message.
Going to close this for now, but we'll check if the message is still
indexed or not soon.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4028 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AL4R4HGEGJAUG5VRL5FTE3TS4LQXBANCNFSM4V7E3VYQ>
.
|
But if it was disabled by default it would not have any effect 😅 users
generally have this problem when they first try to deploy their site in
production.
Not sure what to do if my latest attempt does not work. Hope it will work!
😄
Le ven. 29 janv. 2021 à 20:42, kkhoury38 <notifications@github.com> a
écrit :
… The message is a helpful pointer for new users but in general I think it
could be omitted. By searching online for the exact message, there is a
number of docusaurus pages that have the issue so my opinion is that it
creates more problems that the problems it solves.
An idea could be to disable it by default on anything except localhost.
Anyway, thanks a lot for your response!
On Fri, 29 Jan 2021 at 18:44, Sébastien Lorber ***@***.***>
wrote:
> #4125 <#4125>
>
> This PR will ensure that the help banner is not server-rendered anymore.
> This should prevent the google indexation.
>
> As it is possible to disable this banner with config, and it should
> normally not be indexed anymore, I don't think it's worth it to be able
to
> customize that message.
>
> Going to close this for now, but we'll check if the message is still
> indexed or not soon.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <
#4028 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AL4R4HGEGJAUG5VRL5FTE3TS4LQXBANCNFSM4V7E3VYQ
>
> .
>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#4028 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFW6PVJZO3S6EXGVYYRL7TS4MFSXANCNFSM4V7E3VYQ>
.
|
Searching for |
🚀 Feature
Currently this message is indexed (google it) on ALL sites using docusaurus:
"Your Docusaurus site did not load properly."
It would be nice to let us configure that message so that we at least have some control over our crawl presence on the web.
Have you read the [Contributing Guidelines on issues]
yes
The text was updated successfully, but these errors were encountered: