Tabbed Content Might Just Be Hurting Your Rankings

You might be redesigning your website or refreshing page content and find that you have written a lot of great optimised content, that's great! But you might be wondering 'where am I going to put all of this content?' 'how will all of these words look on the page and how am I going to display them?'. So someone suggests sorting your content into tabs to clear up the page and keep it looking professional and organised, while you might think this is the answer you need to consider the SEO implications.

Tabbed content is usually created using div.tabs using JavaScript. Even though Google has been learning how JavaScript is becoming an essential component in web design since 2014, it's search engine crawlers might not be detecting your tabbed content. While search engine crawlers have no problem reading JavaScript they have no human reading ability, they are unable to click through the tabs and so typically only read the first tab. That means they are skipping a lot of important content that you spent a lot of time creating and optimising for your search engine rankings.

For the full in detail explanation check out the original article on Search Engine Journal below.

When a crawler reads your JS statements it will simply either be able to understand it or not. If it isn’t understood, any piece of content within that sector won’t be displayed or rendered. Meaning that your well-structured content may not be of any value to your search aspirations.

Recent posts from Lilac James

As a free user, you can follow Passle and like posts.

To repost this post to your own Passle blog, you will need to upgrade your account.

For plans and pricing, please contact our sales team at sales@passle.net

Sorry, you don't have permission to repost or create posts.

Repost successful!

View the repost

Repost successful!

Your repost is currently a draft. Review your repost and request approval.

Something went wrong whilst reposting - please try again.

Sorry - this is not an option. This post already exists in the Passle you have selected.

Try reposting to another Passle.