Hi,

the project page referred me to this website and the discussion about avoiding duplicate content:

http://2bits.com/bing/how-google-and-bing-crawlers-was-confused-quicktab...

If I use robots.txt to disallow the pages such as /page-name?qt-tab_set=0#tab_set it causes a real problem, unless I am missing something obvious.

By disallowing the messy quicktabs url variants in search engines, Google will never index the pages that actually have the tab instance at the top, and therefore search results will lead site visitors to the correct node, but they will never see the tabs.

So my question is: how do I use quicktabs so that I do NOT get duplicate content on Google, AND so that Google indexes the pages which actually display the tabs to the user? Once a node is placed in a tab, a user should never see the original node via the original url, as it will not have the tab set displayed. The user can only ever see the long quicktab url to ensure that they get the tab set presented to them, but this is the exact urls that have been blocked from search engines.

Why do I seem to be the only person hitting this very obvious problem in such a popular module?

Please help.

Comments

smustgrave’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

With D7 EOL approaching in a month I'm starting to triage the D7 side of quicktabs queue.

If still an issue or needed for 4.0.x (latest branch) feel free to reopen