ng to deal with a different
GitHub repo (hibernate.org).
--
View this message in context:
http://hibernate-development.74578.x6.nabble.com/hibernate-dev-Hibernate-site-SEO-optimization-tp839p1332.html
Sent from the Hibernate Development mailing list archive at
On 10 December 2015 at 15:26, Steve Ebersole wrote:
> I am not really sure what "have their headers patched to declare that the
> new guides are the canonical version" means in practical terms...
It means that the HTML pages of the documentation should have some
metadata within the header section
I am not really sure what "have their headers patched to declare that the
new guides are the canonical version" means in practical terms...
On Wed, Dec 9, 2015 at 10:55 AM Sanne Grinovero wrote:
> On 9 December 2015 at 16:36, Steve Ebersole wrote:
> > We could leave the ones that are on docs.jb
On 9 December 2015 at 16:36, Steve Ebersole wrote:
> We could leave the ones that are on docs.jboss.org in place and just move
> the current stable ones. I see no benefit to moving ORM 3.2 docs over e.g.
I'm ok to leave them there, but if we do they at least need to have
their headers patched to
We could leave the ones that are on docs.jboss.org in place and just move
the current stable ones. I see no benefit to moving ORM 3.2 docs over e.g.
On Wed, Dec 9, 2015 at 10:08 AM Sanne Grinovero wrote:
> On 9 December 2015 at 13:54, Hardy Ferentschik
> wrote:
> > Hi,
> >
> > On Wed, Dec 09,
On 9 December 2015 at 13:54, Hardy Ferentschik wrote:
> Hi,
>
> On Wed, Dec 09, 2015 at 03:12:54PM +0200, Vlad Mihalcea wrote:
>> Is there any change we host the docs on hibernate.org and simply redirect
>> the old pages from
>>
>> http://docs.jboss.org/hibernate
>>
>> to
>>
>> http://hibernate.or
Hi,
On Wed, Dec 09, 2015 at 03:12:54PM +0200, Vlad Mihalcea wrote:
> Is there any change we host the docs on hibernate.org and simply redirect
> the old pages from
>
> http://docs.jboss.org/hibernate
>
> to
>
> http://hibernate.org/orm/documentation
That would be an option I guess. Host the do
Related to this, the sitemap is limited to 50k entries and hosting multiple
projects, each one with tons of pages, is going to limit the number of
entries we get in the sitemap.
Is there any change we host the docs on hibernate.org and simply redirect
the old pages from
http://docs.jboss.org/hiber
Hi,
I think one thing not mentioned on this thread is the fact that we are not
controlling
the root of the webserver (afaik). The docs are hosted on docs.jboss.org and I
think we
only have write access to the hibernate sub-folder. And even if we had access
to the root
and could modify robots.t
I've started discussions about this in general wrt the hibernate.org
webpage. There is a lot of version-specific information there. Hosting
this specifically for documentation on the doc site would be one option.
Note however that we have limited forms of access to that docs site which
makes it l
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
indexe
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
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:
https://support.google.com/webmasters/answer/156184?hl=en
The sitemap.xml is important if:
- Your site is really large
- Your site has a large arch
Hi Vlad,
We already have something like this, at
http://docs.jboss.org/hibernate/stable/. The latest final version docs
are available there. It's only that results from there have not a good
search result ranking apparently.
--Gunnar
2015-12-04 20:42 GMT+01:00 Vlad Mihalcea :
> Hi,
>
> It seem
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 by
google, it will always render the latest version of the docs:
http://www.postgresql.org
15 matches
Mail list logo
