We could list the stable doc only in the sitemaps and exclude all the
others from the robots.txt.
This way Google will only index the stable docs.
To navigate between versions we need to add a selector somewhere on the
page to load a specific version of the docs, but that doesn't have to be
indexed by Google.
On Tue, Dec 8, 2015 at 1:05 PM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
Stefania (my girlfriend but also a professional SEO consultant) also
pointed out that we should make sure that indexing engines understand
that the documentation pages are intentionally similar, as you get
penalised for duplicate content.
So as you suggest we need to mark - for each guide - which one is the
"main" reference. I don't know if using a sitemap only is enough, I
was told that we need to add some headers in each webpage to refer it
to its canonical URL, I'll ask if we need both actions.
On 7 December 2015 at 08:12, Vlad Mihalcea <mihalcea.vlad(a)gmail.com>
> Thanks for pointing that out.
> The robots.txt is in place https://docs.jboss.org/robots.txt
> But I couldn't find the sitemap.xml
> According to Google:
> The sitemap.xml is important if:
> - Your site is really large
> - Your site has a large archive of content pages that are isolated or
> not linked to each other. If you site pages do not naturally reference
> other, you can list them in a sitemap to ensure that Google does not
> overlook some of your pages.
> So we meet both these two requirements.
> Maybe we need to add a sitemap.xml and reference the link to the "stable"
> docs only and the modification date.
> On Mon, Dec 7, 2015 at 9:46 AM, Gunnar Morling <gunnar(a)hibernate.org>
>> Hi Vlad,
>> We already have something like this, at
. The latest final version docs
>> are available there. It's only that results from there have not a good
>> search result ranking apparently.
>> 2015-12-04 20:42 GMT+01:00 Vlad Mihalcea <mihalcea.vlad(a)gmail.com>:
>> > Hi,
>> > It seems like a good step to tackle the SEO optimization problem is to
>> > offer a "curent" link in our site to point to the latest docs.
>> > That's how PostgreSQL and Spring do it and once this link is indexed
>> > google, it will always render the latest version of the docs:
>> > http://www.postgresql.org/docs/current/static/
>> > MySQL does not offer this option and when googling something about
>> > there's a big chance of getting a 5.0 page instead of 5.6 or 5.7.
>> > I think we should add a "current" "symbolic link" in
the docs folder:
>> > https://docs.jboss.org/hibernate/orm/
>> > and when we publish a new version, we need to go to Google Webmaster
>> > (at least that's how I do it on my blog) and ask google to reindex
>> > particular "current" link. I guess that could be automated too.
>> > Vlad
>> > _______________________________________________
>> > hibernate-dev mailing list
>> > hibernate-dev(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> hibernate-dev mailing list