Looking at our site in Lynx, we discovered books with 6 and sometimes even 10 rel=prev, rel=next links embedded in the header. These hidden links in the header must have a very wierd effect on search spiders, and was not navigation we wanted to be providing.
Also saw on non-book nodes, (blog posts and web links node types specifically) that were getting header rel=prev, rel=next added as if they had been added to be part of an outline, when they had not been.
Removed the three calls to drupal_add_link from theme_book_navigation to resolve this. Hidden header nav should be a admin settings option in my opinion. And should be looked into, I don't think it is functioning as it was intended since so many rel=prev/next were being added into the header.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | books_in_lynx_garland.jpg | 34.35 KB | greg@beargroup.com |
| #3 | books_in_lynx.jpg | 36.43 KB | greg@beargroup.com |
Comments
Comment #1
gregglesCan you confirm whether this is still happening int he 5.x version of Drupal? At this point most fixes happen in the 5.x series and are then backported as appropriate.
It seems to me that multiple "next/prev" links should not appear in the header, but that could be wrong.
Comment #2
gregglesOne more question - are you using a default theme or a custom theme?
If you are using a custom theme - does the problem still happen when you switch to a default theme (like bluemarine)?
Comment #3
greg@beargroup.com commentedHi - still seeing it in drup 5.0 on our dev server, lynx screenshot attached.
A very custom theme... www. realself.com
Comment #4
greg@beargroup.com commentedgood call on the theme - same page in Garland, don't get the repeating next | prev links hidden on the page. Same page in garland attached.
We found this in an SEO sweep... not sure how search would favor those hidden links.
Comment #5
gregglesIf it only happens in your custom theme then it seems like it is probably related specificaly to your theme or to the way that your theme is interacting with Drupal functions.
I'm tempted to mark this as "won't fix" because it's basically impossible for anyone but you to fix this with the current information, but I leave it as active (needs more info) so that you can continue to provide investigation and possible solutions.
Comment #6
Conditi0n commented