Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the blank-slate domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/ezisellc/public_html/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /home/ezisellc/public_html/wp-includes/functions.php:6114) in /home/ezisellc/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/ezisellc/public_html/wp-includes/functions.php:6114) in /home/ezisellc/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/ezisellc/public_html/wp-includes/functions.php:6114) in /home/ezisellc/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/ezisellc/public_html/wp-includes/functions.php:6114) in /home/ezisellc/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/ezisellc/public_html/wp-includes/functions.php:6114) in /home/ezisellc/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/ezisellc/public_html/wp-includes/functions.php:6114) in /home/ezisellc/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/ezisellc/public_html/wp-includes/functions.php:6114) in /home/ezisellc/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/ezisellc/public_html/wp-includes/functions.php:6114) in /home/ezisellc/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":44819,"date":"2020-08-26T09:00:00","date_gmt":"2020-08-25T21:00:00","guid":{"rendered":"https:\/\/ezisell.com\/?p=44819"},"modified":"2020-08-26T09:00:00","modified_gmt":"2020-08-25T21:00:00","slug":"structured-data-seo-mythbusting-what-google-wants","status":"publish","type":"post","link":"https:\/\/ezisell.com\/structured-data-seo-mythbusting-what-google-wants\/","title":{"rendered":"Structured Data: SEO Mythbusting – What Google Wants"},"content":{"rendered":"

Structured data formats are rules that standardize the structure and content of a webpage.<\/p>\n

Google is asking all of us to surface structured data to their crawlers by marking up our HTML with RDFa and Microformats.<\/p>\n

Google’s John Mueller made it clear that Google preferred JSON-LD structured data.<\/p>\n

Wow unless you are super technical this is all mumbo jumbo. “schema markup” and “structured data” WTH….<\/p>\n

It sounds and looks complicated, but it is something anyone can learn to do.<\/p>\n

So what does this mean and why should you care?<\/p>\n

Basically Google wants this, and if you want your site to rank somewhere inside hte first 10 pages then, you has better do what Google wants.<\/p>\n

After all just doing this can give you a significant SEO boost and also increase your rankings.<\/p>\n

Most people simply put human readable dat on their site – this looks great but it makes it harder for Google to find and crawl.<\/p>\n

This markup makes it easier for Google to know what hte page is about without guessing<\/p>\n

Check out this code direct from Google<\/p>\n

You would do that by using this markup<\/a>:<\/p>\n

So for example you have a receipe page <\/p>\n

The markup you could use is<\/p>\n

———————————<\/p>\n

<html>
  <head>
    <title>Party Coffee Cake<\/title>
    <script type=\"application\/ld+json\">
    {
      \"@context\": \"https:\/\/schema.org\/\",
      \"@type\": \"Recipe\",
      \"name\": \"Party Coffee Cake\",
      \"author\": {
        \"@type\": \"Person\",
        \"name\": \"Mary Stone\"
      },
      \"datePublished\": \"2018-03-10\",
      \"description\": \"This coffee cake is awesome and perfect for parties.\",
      \"prepTime\": \"PT20M\"
    }
    <\/script>
  <\/head>
  <body>
  <h2>Party coffee cake recipe<\/h2>
  <p>
    This coffee cake is awesome and perfect for parties.
  <\/p>
  <\/body>
<\/html><\/pre>\n

—————————-<\/p>\n

 <\/p>\n

This looks complicated so to help you out Google has created the Structured Data Mark-up Helper<\/a> so web masters can add schema mark-up to their sites easier.<\/p>\n

 <\/p>\n

 <\/p>\n

SEO changes rapidly, what ranked a site quickly one day may not work the next. Especially if these are blackhat methods.<\/p>\n

Google recognizes this so have put together a channel to help webmasters find out What Google Wants.<\/p>\n

One of these channel that Google has created is called SEO Mythbusting. <\/div>\n
 <\/div>\n
Below is a video from this series<\/div>\n
 <\/div>\n
Under this video is the transcript from the video so you can follow it if needed.<\/div>\n
 <\/div>\n
 <\/div>\n
In this bonus material from the filming of last week’s episode (Googlebot: SEO Mythbusting), Martin Splitt (WebMaster Trends Analyst, Google) and his guest Suz Hinton (Cloud Developer Advocate, Microsoft) dive into the topic of “new microformats”: structured data! <\/span><\/div>\n
 <\/div>\n
Documentation mentioned in this episode: <\/span><\/div>\n
Intro to structured data → <\/span>https:\/\/goo.gle\/structured-data-intro<\/a><\/div>\n
Overview of supported structured data in Google Search → <\/span>https:\/\/goo.gle\/search-gallery<\/a><\/div>\n
Structured data testing tool → <\/span>https:\/\/goo.gle\/2K9rTo5<\/a><\/div>\n
Rich results rest → <\/span>https:\/\/goo.gle\/30SEWA3<\/a><\/div>\n
Rich result status reports → <\/span>https:\/\/goo.gle\/rich-results-report<\/a><\/div>\n
 <\/div>\n