Note that there are some explanatory texts on larger screens.

plurals
  1. PODoes google and/or bing crawler penalize content inside hidden twitter bootstrap tabs
    primarykey
    data
    text
    <p>I have pages that will be crawled by the google and bing crawlers. One of the pages uses twitter bootstrap 2.3.2 <a href="http://getbootstrap.com/2.3.2/components.html#navs" rel="nofollow">Tabbable nav</a>:</p> <pre><code>&lt;div class="tabbable"&gt; &lt;ul class="nav nav-tabs"&gt; &lt;li class="active"&gt;&lt;a href="#tab1" data-toggle="tab"&gt;Section 1&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="#tab2" data-toggle="tab"&gt;Section 2&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt; &lt;div class="tab-content"&gt; &lt;div class="tab-pane active" id="tab1"&gt; &lt;p&gt;I'm in Section 1&lt;/p&gt; &lt;/div&gt; &lt;div class="tab-pane" id="tab2"&gt; &lt;p&gt;Howdy, I'm in Section 2 and not currently visible. Will search engines ignore me?&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </code></pre> <p>Since the content on the non active tabs is hidden I could see the search engines applying a significant penalty or discounting that content entirely when they crawl the site--not good news for the tabs since they will need to be removed.</p> <p><a href="https://support.google.com/webmasters/answer/66353?hl=en" rel="nofollow">In this link</a> google warns about hiding text. and Matt Cutts says <a href="http://www.mattcutts.com/blog/seo-mistakes-unwise-comments/" rel="nofollow">"I don’t recommend that people use CSS to hide text"</a> so clearly you <em>can</em> get penalized for hiding text. However, engines may be smart enough to distinguish valid and invalid hiding. </p> <p>Is my concern on hidden tabs warranted or do the search engines distinguish?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload