-
-
Notifications
You must be signed in to change notification settings - Fork 150
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 Verbesserungen für Doku | Camp 2023 #1196
Comments
Bsp.: --- in der Ist wahrscheinlich über die Links in den |
Diese Frage müsstet ihr uns beantworten. |
ich denke das ist eher ein Marker für das TODO gewesen und die Frage, ob das generell befürwortet wird oder eher nicht. In einer späteren Session haben wir noch entdeckt, daß man über das Icon links oben ein Inhaltsverzeichnis anzeigen kann. Das ist keinem der Anwesenden jemals aufgefallen und damit vielleicht ein Indiz dafür, daß man es optisch besser gestalten kann. Auch glaube @JanoschOltmanns hat noch kurz eine andre Darstellungsidee gezeigt und macht vielleicht dafür noch einen PR. Das Aufsplittern der Seiten wäre damit wahrscheinlich hinfällig. |
Die Grundlage für die Doku liegt im Hugo Learn Theme. |
Lange SeitenBeispiel: Die Seite "Einstellungen" ist extrem umfangreich. InhaltsverzeichnisGut zu wissen, dass es da ist. Ich hab es allerdings heute das erste mal gesehen :-) |
That's already possible - or what exactly is meant by that?
What does that mean?
imho not relevant for SEO |
As far as I understand, google does not index hash url´s like As reference I found this: So how might this information be helpful? While the docu already habe a dropdown anchor nav, a persistent anchor nav would be better. |
What is a "persistent anchor nav"? |
https://docs.contao.org/robots.txt is now added |
The meta-title for the browser should be able to be set custom if necessary. Currently, it looks like it is generated automatically |
See https://github.com/contao/docs/blob/main/CONTRIBUTING.md#the-hugo-front-matter-variables and https://learn.netlify.app/en/cont/pages/#front-matter-configuration
|
At the moment the docs have the parameters |
Ah I see, got it. |
Oh sorry, I meant to say always visible and expanded. So it should help, theoretically, if the anchor nav would stay open. On the other hand, I don't think It would be "nice" to have such long anchor link menus always visible. |
Its visibility is not relevant for a crawler. |
True google crawler will see and understand the anchor nav, even it is collapsed. However, as long as there is no better way to implement this anchor nav, this does not matter anyway. |
For what exactly? This issue is for "SEO improvements". The visibility of a menu is not relevant for that. The existence for a menu is helpful for "SEO" so that the crawler can find relevant pages more easily - but since there is a sitemap anyway, it's not hugely important. |
Presumably @leofeyer has access to the |
As far as I know, that is not exactly true. |
A myriad of websites have their menus behind menu buttons, especially for mobile views. I very much doubt Google would penalize that in any way. |
Please also post some examples. |
Nobody was talking about a google penalty. Maybe those people can say better, what I am failing at:
but this becomes now offtopic. sorry. |
Even their example hides the jump link menu behind a menu button on mobile. |
As far a I can recall, a google search for the email smtp setting did not show the https://docs.contao.org/ page at all on the first page. @contaoacademy do you recall, what we where searching for? If I check now, I get correct SERPs at least for the search: "contao email smtp". Still this result is on rank 3 ... while it should be 1 or even a "Featured snippet". |
Likely not, since that page has no description. |
Wir haben einen Test mit FAQ gemacht: |
In this case the page https://docs.contao.org/manual/de/layout/templates/php/data/ is at least missing the word "variablen". |
But the exact wording is on the page https://docs.contao.org/manual/de/faq/#template: |
I suspect that the one line is not relevant enough for Google to display it in the search results. I am currently asking myself to what extent the topic should be treated further. It does tie up massive resources and currently brings too little. I would suggest: If it doesn't work that way, then I would arrange a doku-call and clarify it there. What do you think? |
thats a good idea. |
Sounds good to me :) |
I have added the three sitemaps to the Google Search Console property. |
Just had another look and have an idea, why FAQs are not reanking.
And on the linked answer on https://docs.contao.org/manual/de/layout/templates/php/data/ the keyword If you support that idea, I could prepare an PR for improved headline and text. |
Regarding the content, sure, go ahead.
Is there any real evidence for that? Besides, we are surely not gonna change this, are we? Don't the collapsibles provide a better user experience? We could however change it to But this shouldn't matter at all anyway, since the FAQs are also provided a JSON-LD meta data. |
ok, its on my ToDo list ;)
Google search and evidence ;). I could not find any statement on that from google.
Yes but maybe there is a more SEO friendly way: Most FAQs that I see nowadays have the questions gathered at the top. If you click those questions you follow an anchor link down the page to where the same question is repeated with its not collapsed answer. Like its done here: https://granvogl.com/Infos But as long as the FAQs do not have real content, but only links to the pages withe the actual content, its hard to make them rank itself. But it helps to push the target pages (internal link building).
JSON LD helps google to understand the content. All this text in short: |
Then I would disregard that.
We won't make any changes based on opinions ;)
There already is: JSON-LD
That's a content issue though and unrelated to JSON-LD. |
I also think it’s a content issue. For the mentioned example “Wie kann ich alle Variablen meines Templates anzeigen?” a better answer might look something like: |
text change suggestion to address on SEO issue: |
Im Meeting vom 28.09.2023 haben wir besprochen, welche Punkte umgesetzt werden und welche nicht. |
Wie im Meeting vom 28.09.2023 beschlossen, wollen wir hier nichts zu. Wir sehen hier keine große Auswirkung für SEO, die den Aufwand rechtfertigt. |
Auf dem Contao Camp 2023 haben wir festgestellt, dass von Google viele Einträge in der Doku nicht entsprechend gefunden werden.
Folgende Verbesserungsvorschläge:
The text was updated successfully, but these errors were encountered: