Structured data and Google

-

Domain-specific markup for fun and profit

It doesn’t come as a surprise to Dull Old Web Farts (DOWFs) like me to learn last month that Google gives a search boost to sites that use structured data (as well as rewarding sites for being performant and mobile-friendly). Google has brilliant heuristics for analysing the content of sites, but developers being explicit and marking up their content using subject-specific vocabularies means more robust results.

For the first time (to my knowledge), Google has published some numbers on how structured data affects business. The headlines:

  • Jobrapido’s overall organic traffic grew by 115%, and they have seen a 270% increase in new user registrations from organic traffic
  • After the launch of job posting structured data, Google organic traffic to ZipRecruiter job pages converted at a rate three times higher than organic traffic from other search engines. The Google organic conversion rate on job pages was also more than 4.5 times higher than it had been previously, and the bounce rate for Google visitors to job pages dropped by over 10%.
  • In the month following implementation, Eventbrite saw roughly a 100-percent increase in the typical year-over-year growth of traffic from Google Search
  • Traffic to all Rakuten Recipe pages from search engines soared 2.7 times, and the average session duration was now 1.5 times longer than before.

Impressive, indeed. So how do you do it? For this site, I chose a vocabulary from schema.org:

These vocabularies cover entities, relationships between entities and actions, and can easily be extended through a well-documented extension model. Over 10 million sites use Schema.org to markup their web pages and email messages. Many applications from Google, Microsoft, Pinterest, Yandex and others already use these vocabularies to power rich, extensible experiences.

Because this is a blog, I chose the BlogPosting schema, and I use the HTML5 microdata syntax. So each article is marked up like this:

<article itemscope itemtype="http://schema.org/BlogPosting">
  <header>
  <h2 itemprop="title" id="post-11378">The HTML Treasure Hunt</h2>
  <time itemprop="dateCreated pubdate datePublished" 
    datetime="2019-05-20">Monday 20 May 2019</time>
  </header>
    ...
</article>

The pubdate value on itemprop isn’t from schema.org, but it’s required by Apple for WatchOS because, well, Apple likes to be different. And that’s basically it. All of this, of course, is taken care of by one WordPress template, so it’s automatic.

Metadata partial copy-paste necrosis for misery and loss

One thing puzzles me, however; Google documentation says that Google Search supports structured data in any of three formats: JSON-LD, RDFa and microdata formats, but notes “Google recommends using JSON-LD for structured data whenever possible”.

However, no reason is given for preferring JSON-LD except “Google can read JSON-LD data when it is dynamically injected into the page’s contents, such as by JavaScript code or embedded widgets in your content management system”. I guess this could be an advantage, but one of the other “features” of JSON-LD is, in my opinion, a bug:

The markup is not interleaved with the user-visible text

I strongly feel that metadata that is separated from the user-visible data associated with it highly susceptible to metadata partial copy-paste necrosis. User-visible text is also developer-visible text. When devs copy/ paste that, it’s very easy to forget to copy any associated metadata that’s not interleaved, leading to errors. (And Google will penalise errors: structured data will not show up in search results if “The structured data is not representative of the main content of the page, or is potentially misleading”.)

An example of metadata partial copy-paste necrosis can be seen in the commonly-recommended accessible form pattern:

<label for="my-input">Your name:</label>
<input id="my-input"/>

As Thomas Caspars wrote

I’ve contacted chums in Google to ask why JSON-LD is preferred, but had no reply. (I may go as far as trying to “reach out” next time.)

Andrew wrote

I’m pretty sure Google prefers JSON-LD over microdata because it’s easier for them to stealborrow the data for their own use in that format. When I was working on a screen-scraping project a few years ago, I found that to be the case. Since then, I’ve come to believe that schema.org is really about making it easier for the big guys to profit from data collection instead of helping site owners improve their SEO. But I’m probably just being a conspiracy theorist.

Speculation and conspiracy theories aside, until there’s a clear reason why I should use JSON-LD over interleaved microdata, I’m keeping it as it is.



from Bruce Lawson's personal site /2019/structured-data-and-google/

Comments

Post a Comment

Popular posts from this blog

20 Free Professional Resume Cover Letter Format Templates for Jobs 2020

-
Image
Are you getting ready to apply to jobs and want to make a cover letter? Using a professional cover letter template will save you time and ensure that you've got a professional design. This cover letter template and hundreds more can be found on Envato Elements. Using a premium cover letter template can not only save you time, but you'll have a high-quality template for your letter. All you need to do is add the information you'd like to and customize the template and you're done. In this article, we'll explore some of the best premium and free cover letter templates available online. Find the Best Premium Resume Cover Letter Templates on Envato Elements (With Unlimited Use)  Envato Elements is an all-you-can-download resources for professionals and creatives, including good cover letter templates . With Elements, you pay a low monthly fee to get access to: resume and CV letter templates stock photos and royalty free music WordPress themes and more
Read more

How to Effectively Manage a Remote Team

-
Image
According to Flexjobs , remote work has grown by 44% in the last five years. And that statistic was published  before  the remote work boom of 2020. Remote work is here to stay.  Managing remote teams requires planning, and you'll see the best tools and techniques in this article. (Image source: Envato Elements. ) If your team is navigating the switch to working together while apart, you might be facing challenges that you didn't encounter while sharing an office. Learning how to manage a remote team is a must in 2020. Working remotely can unlock your team's full potential. But it takes a conscious effort to ensure that everyone stays connected. In this article, we're going to share the top tips, tools, and techniques so that you never miss a beat while managing remote workers. Three Top Benefits of Working Remotely Too many workplaces see managing remote workers as purely a challenge. In reality, working remotely lends itself to benefits that lead to a happier a
Read more

How to Create Gantt Charts in PowerPoint With PPT Templates

-
Image
You might not think of Microsoft PowerPoint as a project management tool. But there's a reason it's used for project updates and by project teams. The ease-of-use and flexibility of PowerPoint work for any project management professional.  It's easy to create a Gantt Chart in PowerPoint (PPT) once you know how. When it comes to managing projects, you need tools to make them manageable. That includes process charts to help your team collaborate efficiently. Project management professionals often turn to  Gantt charts  to visualize the parts of the project. In this tutorial, you'll learn how to create a Gantt chart in PowerPoint . You'll learn how to use an impressive template to build a Gantt chart that ensures that every member of your project team knows how their part in the project fits into the bigger picture. Let's dive in! What's a Gantt Chart? Imagine you're building something that requires collaboration with others. That could be a website,
Read more