This site uses cookies and other tracking technologies to make possible your usage of the website, assist with navigation and your ability to provide feedback, analyse your use of our products and services, assist with our promotional and marketing efforts, and provide better user experience.

By using the website, you agree to our Privacy policy

Accept and continue

Report a bug

Cancel
20862   59   4
SEO 20 min read June 7, 2017

HTML Tables as Google Rich Snippets — Breakdown, Takeaways, Achieving The Snippet


Yulian Alinski
Head of SEO at
Lucky Labz
Ever since the inception of featured snippets in Google, tables have played a major role as one of those snippets capable of drawing huge amounts of traffic away from adjacent competitors, effectively starving them from the power of first page results. That is if you can earn a snippet.

In this post, I'll cover necessary steps and actions you can take to massively increase your chances in earning an HTML table featured snippet.
In late 1993, Dave Raggett proposed the digital markup display of complex material and data, using rolls & columns. In October 1994, W3C was established as a standard, thanks to a collaboration between MIT and CERN, with the help of DARPA and the European Commission.

Fast-forward to the year 2007, and we see the first appearance of additional elements in Google's search results. As of 2017, this practice has been further developed to now include a large variety of rich snippets, such as information regarding flights, sporting events, videos, recipes, movies, news and much more.

For Google, ever since 2007, HTML tables have been treated as a standalone element, worthy of displaying enriched SERP results. But how do you tell a good table from a bad and misleading one? Several years back, Google started experimenting with "machine learning," and it was eventually incorporated into their algorithms. Through efforts of trial and error, the developers have found a way to teach the algorithm how to depict the worthy tables on its own with ever increasing accuracy. This helped sieve through the billions of HTML tables with bad layouts.

Right now, the purpose of an HTML table can be associated with a certain search query, which is what we see as "featured snippets." Although nowadays CSS provides far superior layout capabilities and where tables are considered a caveman's practice, many websites heavily rely on them to stay competitive.


Anatomy of a table

Essentially, there are 3 types of tables:

  • Horizontal tables;
  • Vertical tables;
  • Fusion tables.
Ideally, a good table will have its first row acting as a header, describing the data below it. This is a good thing because it gives search engines something to work with. Just as articles have titles, HTML tables have captions. Depending on quantity and complexity of the data below the caption, different types of tables may be used.

So let us examine the code. Using the W3C standard, this is what the skeleton of an HTML table looks like:
<table> Indicates that the data will be contained within a table instead of a <div>;

<caption> — The table's title. This is read and used by search engines;

<tr> Table row. A tag for generating horizontal table rows. Each new tag generates an extra horizontal row;

<th> — Table heading. A tag for generating bold headings within the data;

<td> — Table data. This is the data container of the table. It can contain all sorts of HTML elements: text, images, lists, other tables, etc.
It is good to understand what each element of the table relates to because it is still in regular HTML. Therefore, it can be manipulated via CSS, which is convenient when designing a responsive table for mobile devices and apps.

So, why not divs, you would ask? Well, through observation of thousands of SERP results that trigger a featured snippet, we can observe an interesting pattern:

HTML tables > ordered lists = unordered lists > divs

It appears that Google favors the table element more than lists, and even more so than div containers. This makes sense, due to the nature of these tags. Tables are standalone elements that structure, contain and style sets of data. Lists are non-demanding elements which can either be casually used or enumerated. And finally, divs are literally universal containers for pretty much anything.


Earning the snippet

Before you get excited, we have to destroy your dreams. Unfortunately, there is no such thing as a set of rules that will 100% guarantee you getting a featured snippet. This was publicly announced by Google and is also mentioned in their documents. Rich snippets are now controlled by Google's self-sustaining machine learning algorithm, which is good at depicting queries but not that entirely accurate.

However, below we will discuss key takeaways that will highly increase your chances of earning that valuable snippet.
Please note that the following "rules" are based on experimental observations in the same manner that SEO professionals learn about the search engines. We can never say that a certain statement is 100% true. But by conducting enough experiments, the data will accumulate, eventually reaching 99+% accuracy.
#1:

Only select queries trigger a featured snippet

The first order of business is to find out which search queries trigger a featured snippet. Even if you have done your work flawlessly, following the advice below, this by no means guarantees the trigger.

Observations show that if the first 3-4 search results are all eligible for a featured snippet, then the algorithm will allow it. This automatically means you will have competition, no matter what you do.

Furthermore, the original purpose of rich snippets was to quickly answer a question or give the user access to what he/she is looking for.
Takeaway: Look for search queries that represent a question being asked or some type of textual or numerical data being sought. Look at the first 2-3 results. Do they have tables similar to yours?
#2:

Google only generates featured snippet tables
from first page results

That makes sense, right? The first SERP contains the most helpful and highly accurate results for the user. Thus, if a featured snippet is to be shown, with the intent to facilitate the user, it would have to be taken from those first 10 results. This is true for all types of featured snippets.
Takeaway: Get your page ranked in the first 10 results, otherwise you will not qualify for the featured snippet.
#3:

Featured snippets are being updated roughly
on a quarterly basis

Of course, we cannot say for sure. Some snippets move in a matter of weeks. Others take up to 6 months to update. The important thing to recognize is that the frequency is likely to get shorter, as Google's algorithms become ever so effective.

Remember, back in the days when major updates such as Panda and Penguin were periodic updates, each targeting a specific issue with searches? Right now, those updates are part of the core algorithm. It is expected that rich snippets will follow the same path eventually.
Takeaway: Even if you change something now, results do not come right away. That, combined with the fact that your changes may or may not be effective, leaves one to wonder exactly how long it would take to achieve the results. So instead, use the time to research and work on the quality.
#4:

Google's hidden table index

Did you know that Google actually has a separate index for HTML tables? Check it out:

https://research.google.com/tables

It looks like this:
We see an index for web tables and fusion tables. It appears that horizontal and vertical tables fall under the category of web tables, whereas hybrid tables are classified as fusion tables.

You will notice that the URL of the index only exists as:

https://research.google.com/tables

It does not look like local results are being supported. Also, it says that this index is experimental.
Takeaway: It could be an interesting tool to check if your table is indexed, or in other words — read by Google as such.
#5:

Caption tag does help

Although not mandatory, the <caption> tag, as explained earlier, acts as the title of the table. In the absence of this tag, Google will look for the next best thing - the surrounding headings. They can be anything from <h1> to <h4>. <h5> and <h6> are quite rare, as these tags are typically used to entitle very specific portions of content deep down in the page, usually not very semantic with the topic of the page.
Takeaway: You are advised to introduce a caption tag to your table so that your table can be treated in a similar way to articles. Do not allow Google to guess by looking at the surrounding headings, although we do recommend having both.
#6:

Table headings

By using the <th> tag, you indicate to search engines that your table has order in its data that is topic-related and patterned all the way from the beginning to the end.
Takeaway: Use the <th> tag head and order sets of data. This helps the search engines understand the relationship between the sets of data in your table.
#7:

Semantic relation

You also have to take a look at the role of the table. What is it about? How big is it? Can it be used as a substitute to describe the purpose of the entire page? What is its relation to the topic of the page?

Of course, Google will look to pick only tables that are the best possible answer to the search query. Therefore, breaking down your topics can actually favor you in some cases. For example, we have an article about a very popular inspirational motto: "Improvise. Adapt. Overcome."

Each of those single-word sentences can be treated as a topic of their own. Thus, all of the following search queries are prime candidates for triggering a list or table featured snippet:

  • How to improvise?
  • Improvisation techniques
  • How to adapt?
  • Overcoming obstacles
  • Steps for overcoming obstacle
In each of those topics, it is possible to work in a table with <th> fields, such as:
Takeaway: A great asset when working on SEO tasks is to be able to put yourself in the position of the searcher and think as if you were him. So, when creating your tables, think about how people may search for it and start from there.
#8:

Content quality

Not much to say here. Obviously, only the highest content quality will be chosen among the many.
Takeaway: Work on the quality. Remember, shiny buttons, and flashy text are not always the right approach. Always, the best content is the one that is the easiest to understand/consume. For example, some articles from .edu websites, that have only text and zero HTML/CSS/script styling, do in fact outperform all others.
#9:

Surrounding content

Take note that tables on their own mean nothing. The way Google's algorithms work is by looking at the content that surrounds the table - headings, paragraphs, images etc. The best practice is to sort of wrap the table around relevant content, like so:
<h?>Heading</h?>

<p>Paragraph</p>

. . .

<table>...</table> // Your table is here

. . .

<p>Paragraph</p>

<h?>Next heading</h?>
Takeaway: Surround your table by relevant content. Use long tail or broadly related keywords in the paragraphs above and below the table, even in the headings(if it makes sense).
#10:

Duplicating content or data is a no-no

Having similar or exact data in the table as well as somewhere else on that same page creates confusion. Typically, if the algorithm isn't sure what to choose, it will usually choose nothing.
Takeaway: Make sure that whatever content is found in your table is absolutely unique data to the entire page. Do not recite already existing data.
#11:

Bold subject column

Text written in bold is historically used to highlight important pieces of text or to style headings.
Takeaway: Let us help out the search engines a little by bolding our subject column. This is easily achievable via CSS styling.
#12:

Table size/proportions

Although still read, tables with weird proportions, irregular symmetry, tables that are too wide or too long on a X x Y axis may be bypassed.
Takeaway: Think of a way to structure your table data proportionally. Otherwise, split the table into two tables or think of only including the most important data, so the sizes are kept reasonable.
#13:

Data character count proportions

Again, having data with a few characters in one cell and whole sentences in the adjacent cell counts as an irregularity. This is best avoided.
Takeaway: Summarize your text data so that each of the cells can be proportionally even in size, and thus the entire table.
#14:

Columns with single subjects

Unfortunately, two or more columns with competing subjects are not yet received well by search engines. Even though they may be legit within the entirety of the table, the algorithms are not yet advanced enough to tell internal subjects apart.
Takeaway: A table is best kept under a single subject from end to end.
#15:

Numerical units

It is not uncommon to see a table containing numerical values. However, lack of clarity about what unit these numbers are expressed in may hinder the table.
Takeaway: State the numerical unit, either within the <th> cells or the <td> cells. Example:

Cost in USD — $5
is better than
Cost — 5
#16:

Links in data

Contrary to what you may think, Google does tolerate the use of relevant links within HTML tables, and yes, it does display them in the featured snippet.
Takeaway: Be very careful when including links in your table. They need to be highly relevant.


Vertical tables and microformats

Surprise surprise… HTML tables generate yet another type of rich snippet. Above, you can see an example. We searched for "tesla model S". On page 1 we see a lot of results like this one. But on page 2… ?

Actually, this type of rich snippet is triggered by vertical tables and can be found as far back as page 8 or deeper. We know of other microformats that behave similarly, don't we?

  • Breadcrumbs;

  • Review ratings;

  • Events.
What makes vertical tables unique is that they contain multiple <tr> table rows with only one <th> and <td> per table row. The result is a loooooooong vertical list. Wikipedia actually uses this table style in its articles.

An interesting takeaway is how longer tables are actually cropped, based on the search query. Google will choose to display up to 6 of the most relevant table rows below the meta description. Yes, you heard me — 6.


The recent Google Project Owl

At the end of April - beginning of May 2017, Google announced they would be launching counter steps to combat inaccurate information, as well as hateful results in their search engine. The undertaking was dubbed Project Owl. For a full version detailed analysis of the project, take a look at Sarah's post.
Long story short - Google decided that taking into account user feedback has more value than downsides. And this is what Project Owl is. They have modified their SERP interface by adding extra functions.

One of those functions is the ability to user-rate featured snippets.

What!? Really?

Yup, take a look:
Clicking on the "feedback" option now prompts a window with extra user options. Notice how diverse they are? And then some! There is even a field to type in generic user feedback.

So, should you be worried?

Not necessarily. Take a look at what you get after providing input and clicking on "send":

Your responses help to improve the Google Search experience.

Note: Your feedback will not directly influence the ranking of any single page.
This is just another social experiment. If things get out of hand or turn out really bad — it's bye bye birdie.

Back to the feedback. We have on our hands two options:

  • marking the snippet as …

  • commenting on the snippet

The first option might be the dangerous one. Those are fixed options, which can be collected algorithmically in order to rate a certain snippet, similar to how it is done with review ratings (average from 0 - 5). Assuming that upon rating a snippet, the algorithm locks onto your IP and prevents you spamming negative options, this is still a knife with two edges, which is the reason why these new changes have not been received well by the communities.

The other manual option for commenting should be directed to Google's manual team, considering that the amount of queries that trigger a snippet are far from overwhelming.

In the end, it is hard to say how all of this will turn out. There are those that respect the competition by recognizing its collective value. And there are those that just do not bother playing by the rules and are happy to spam the featured snippet that you worked for so hard.

Which one are you going to be? Let me know in the comments.

Rate the article on a five-point scale

(The article has already been rated by 5 people on average 4 out of 5)
Found an error? Select it and press Ctrl + Enter to tell us

Recommended posts

Subscribe to our newsletter
Keep up to date with our latest news, events and blog posts!
Sign In Free Sign Up

You’ve reached your query limit.

Or email
Forgot password?
Or email
Back To Login

Don’t worry! Just fill in your email and we’ll send over your password.

Are you sure?
Please pick the project to work on

Personal demonstration

Serpstat is all about saving time, and we want to save yours! One of our specialists will contact you and discuss options going forward.

These may include a personal demonstration, a trial period, comprehensive training articles & webinar recordings, and custom advice from a Serpstat specialist. It is our goal to make you feel comfortable while using Serpstat.

Name
Email
Phone
We are glad of your comment

Upgrade your plan

Upgrade your plan

Export is not available for your account. Please upgrade to Plan A or higher to get access to the tool. Learn more

Sign Up Free

Спасибо, мы с вами свяжемся в ближайшее время

Invite
E-mail
Role
Message
Optional

You have run out of limits

You have reached the limit for the number of created projects. You cannot create new projects unless you increase the limits or delete existing projects.

I want more limits

Christmas is a time for miracles.

You are almost on the finish line of our Christmas quest. The last brick of your lego-promocode is left on the way up 55% discount.

Did not find previous lego-bricks? Fill the form anyway.

Name
Email
Phone