Webmasters are optimizing their images, videos, blog posts, etc. to gain better rankings for the content in search engines like the Big G or social sites like Facebook. Using some behind the scenes magic (or more realistically, basic markup) we can hint to these sites what our content is about so that they can display and categorize it appropriately.

Well, just like there are image, news and video results sometimes mixed in with the regular Google search results, in some cases there are also “in-depth” article results to satisfy the ~10% of searchers that need more than a quick answer. These folks want in-depth answers to broad topics like “censorship” for example. Well, as we know, Google aims to please (arguably of course).

in-depth Google search results

How Do You Indicate To Google That Your Content Is Timeless Or Worthy As Research Material?

I actually just started using video schema yesterday on one of my main blogs to give Google a better indication about the videos embedded into my articles. Well, article schema is what we need for articles. Once we start marking up our content in that way, it will provide better clues to other sites what the individual pieces of content are about.

Think of the “pieces of content” on a web page as field values in a database. Just like we can display field values from a record in a database in any way that we wish (when programming) in relation to eachother, the same can be done for the “pieces” of our content.

By “pieces” I mean: thumbnail, title, publish date, article body, word count, etc.

Clearly labelling each (or the most important) pieces helps engines like Google display and categorize our content in specific ways (as mentioned above).

Let’s Breakdown A WordPress Blog Post Into Pieces, Shall We?

Let’s look at WordPress for example. WordPress does a great job of putting our content into “pieces” so for example, it separates publish date from title, which is separate from body, and so on. They are all stored in their own little place in the database separately (in fields) but are still tied together (in records).

And well, this is a common way to do things. This allows certain fields to be used independently. For example, a title can be used in a list of posts (archives) and can be linked to the post’s individual web page. Or, posts can be sorted by date in either chronological, reverse chronological, or random order using the publish date. You get the idea I think.

I’m going to close things off here and call this a part 1. But stay tuned for the exciting conclusion in part 2. Ok, cheesy hype aside, I do get a lot deeper into Schema, even with an analogy, plus I talk about some HTML elements and make it seem less dorky than it is (I think). OK, until next time.