#1272 new

Search Does Not Go To Tabbed Content

Reported by Peter | February 20th, 2015 @ 08:28 AM | in User issues

When I do a search, and find the argument on a tabbed page, the link only takes me to the first tab as there's no #tabN (or #ctabN in my case) on the search result.

So the use goes to the page but the hit does not appear to be there as it's on one of the other tabs.

Comments and changes to this ticket

  • dleffler

    dleffler February 20th, 2015 @ 07:12 PM

    • Tag set to search
    • Assigned user cleared.

    Sorry, we don't manage tabs/history at this point. The search index is only based on the 'page'. Perhaps in the future, we'll be able to implement a more strategic 'history' which would include tabs, once we rename all the tabs in the system to be unique (most are now named 'tab1, tab2, etc...'

  • Peter

    Peter February 21st, 2015 @ 08:51 AM

    • Assigned user set to “expNinja”

    Thanks for the feedback, I understand. Sadly it may mean a last minute rethink. I may need for now to emulate the tabbed pages with a top graphic and separate pages in order to make the search engine actually find things that you can click to get to. The tabbed pages are such an excellent feature.

  • dleffler

    dleffler February 21st, 2015 @ 03:02 PM

    • Assigned user cleared.

    To be honest I'm not sure any cms/package deals with tabbed content that way. Since we are dealing with ALL the text on a page and not some of the 'meta' data like title, description, etc...I'm not an SEO expert, but I'm pretty sure search engines like Google, etc... only 'index' the meta data, but store the page, meaning, even if you have the word on a page, if it doesn't appear in the meta data it won't be 'hit'.

  • dleffler

    dleffler December 26th, 2015 @ 05:59 AM

    • Milestone set to 2.3.7
  • dleffler

    dleffler January 1st, 2016 @ 04:18 AM

    • Milestone changed from 2.3.7 to 2.3.8
  • dleffler

    dleffler January 26th, 2016 @ 11:36 AM

    • Milestone changed from 2.3.8 to User issues

    This would be a difficult/complex fix since the content is on the page, but hidden through the use of css/javascript

  • dleffler
  • dleffler

    dleffler July 26th, 2016 @ 11:08 AM

    • Milestone set to User issues

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Bug Tracker for Exponent CMS

Shared Ticket Bins

People watching this ticket