cubicweb #693670 ajax content not seen by google bot [validation pending]

All the content served using ajax requests is not seen by the google bot, and therefore not indexed by google.

Important content missed :

  • all the tabs
  • the tickets on logilab.org

We should probably include something which detects the various bots and redirect them to more static views of our content (or at least provides direct link to some of that content). As a side effect this could allow browsing CW sites with non-js-enabled browsers and still be able to retrieve some data.

Maybe a per-site implementation is needed in which case individual tickets on the relevant projects should be filed.

prioritynormal
typebug
appeared in<not specified>
done in3.15.2
load0.100
load left0.000
closed by<not specified>

Workflow history

from state (6)to statecommentdateUser
donevalidation pending2012/07/24 08:20sthenault
opendone

please don't unvalidate because you're unsure. Either take the time to validate or don't do anything.

2012/07/19 09:24sthenault
validation pendingopen

lynx users are happy but I am very unsure about google

2010/05/10 11:19acampeas
donevalidation pending

version publiée

2010/02/26 18:21sthenault
in-progressdone

let's try with a <noscript> element

2010/02/26 15:25acampeas
openin-progress2010/02/26 15:10acampeas

Comments

  • 2010/02/12 16:52, written by acampeas

    we could maybe have a few discreet direct url/links to the tabs contents

    I suspect blind readers suffer a bit when browsing these things, too.

  • 2010/05/10 12:24, written by anon

    It would also allow one to stay on the "ticket list" or "documentation" page and refresh it. Useful if you keep tabs open between sessions.

    • 2010/05/10 12:26, written by jcboggio

      Is "anon" supposed to post comments on tickets ? If not, I can reproduce the "problem".

  • 2012/02/09 08:55, written by alutz

    The noscript has a better view but there is missing navigation and all information is spread across various pages.

    Generating all the content on the page and hiding it is probably too costly. Maybe with varnish in front, it could be an option.

    To complete this ticket we should check how the content has been indexed.