Closed rviscomi closed 4 years ago
Google doesn't really let you change any of this. Setting the Meta Description is the best you can do, but it will use a quote from the page if it thinks it's more accurate/useful than that.
We do include breadcrumbs structured data from the year page to the section (see example here), but could enhance that to have base page, and language.
A bigger concern for me is that Google is being very slow to index some of our translations. See the Coverage section of Google Search Console. The sitemap has 69 pages, but Google only has 56 with the others being excluded due to redirects (3 pages now available and no longer redirecting), pages discovered and not indexing (8), pages not indexed (2 - including the French home page!) and pages not selected as canonical (3 Japanese pages recently translated). Tried a few things (manually resubmitting pages and whole sitemap and also temporarily removing lastmod
in sitemap as not accurate - before fixing it properly so I could bring it back), but no luck nudging it to do it properly...
@ymschaap , @rachellcostello , @AVGP and @AymenLoukil you got anything to add to this?
It's a well-known thing that Google often rewrites meta descriptions in the SERPs in response to the searcher's query, as it's pointed out in the SEO Chapter. So, as @bazzadp also pointed out, this action of plucking content is due to this matter.
While content updates (title/description/headings) can definitely improve the search appearance for most of these 2019 almanac pages, I found more interesting the search appearance strategy considering the upcoming 2020.
So, here's are my thoughts on that,
The root (https://almanac.httparchive.org/en/
) will contain the current Web Almanac, therefore the 2020 content. So, without the year in the URL.
All the previous years remain archived, in subdirectories, as it is now (https://almanac.httparchive.org/en/2019/
), so no redirects needed at first sight.
The 2019 pages will become "secondary/leaf" pages and each chapter will link to the latest (in this case, 2020), but not the other way around. This way, the signal sent to the search engines says which are the main website pages and which ones are less important when it comes to pages hierarchy.
@catalinred I've been thinking over your proposal, and can see the advantage of that in terms of boosting the signal of the current year.
However I would have big concerns about breaking any linking as soon as we archive the 2020 chapter into https://almanac.httparchive.org/en/2020/
when launching 2021 edition. The intention is to make this resource a quotable resources and we've worked hard to make it it deep linkable, so really would prefer to keep the current year structure and just change https://almanac.httparchive.org
to redirect to the best language and year available for that user - as we do now.
As always, while SEO is important, IMHO it shouldn't be prioritised over users and I fear this proposal may do that long term.
What do you think about that concern?
@rviscomi as discussed above we only have limited influence over how we appear in SERPs and when I search for an incognito window I get better results than you did previously:
I do think we should add the language and year to the breadcrumbs (see example of how we currently breadcrumb it here). Will raise a separate issue for that (edit - #885).
In regards to the missing chapters that I raised, we still have 11 chapters not indexed:
Google is aware of them but stubbornly doesn't seem to want to index them:
The canonical ones are old versions and resubmitting them doesn't seem to update them. Frustrating.
However I did discover that the French SEO chapter (for example) seems to be mapping to the app engine URL despite the canonical tag pointing to the real URL that should be used:
We could 301 redirect them when host is wrong to give another signal. Will raise a separate issue for that (edit - #884)
So if we close out above discussion with @catalinred and raise the other two issues as separate issues, then I think we can just close this issue. Let me know if you disagree.
We're in the top position for "web almanac" queries, which is perfect. The home page result contains a few secondary page results:
A few ways we could make this better:
Any other thoughts or ideas?