The goal is to insert the code schema markup on the page html code of the blog is that search engines such as yahoo or google bing easier to understand the purpose contained in a blog page, not just writing it, so that search engines can provide a more informative search results to the user. Rules of writing data structure or schema markup to a page of the site has the standard of writing special code schema markup that is used today is the result of cooperation enterprise collaboration most popular search engine in the world, google, yandex, yahoo and bing with Communitas open, reference legkap about ways of writing and command writing is published on the site  schema.org

How to Fix Error in data structures blog: Complete

Nowadays blogs have a lot involving schema markup to the structure of the code, even not only used for reference only search engines, social media facebook twitter and google + uses schema markup information data structures for information when users share on social media.

Org schema in order to function properly, then you should be able to ensure that the data structure schema markup on your blog page code error and its structure is not organized properly.

How to Check Data Structure schema markup blog 

How mengencek whether the data structure schema markup your blog in good condition or error, you can use a special tool provided by Google, go to the website https://search.google.com/structured-data/testing-tool,

then enter the address of your blog, homepage or address could address the article, then please run the test.


You will be presented information data structure schema markup owned by your blog page, or less probably would like to see the figure below:

chema markup errors in data structures blog

For my blog pribdi ditemuka BlogPosting and error on the Website, we try clicks on the blogposting, then discovered the error as shown below:


That means the data structure schema markup to the blog pages need to be repaired.

How to Fix Error (Error) The data structure schema markup on blog

You can find a lot of error data structures, error that appears may be different from one blog to other blogs, some of which are often found like appearance on, if you happen to find errors like the above, you can fix it with the steps below this:

1. Solve Error on the item type "WebSite" 

If you find an error on the part itemtype website, how to fix it are as follows:
find the </ head on your blog template, and then enter the code below before the </ head
<b:if cond='data:blog.pageType != &quot;error_page&quot;'>
<script type='application/ld+json'>{ &quot;@context&quot;: &quot;http://schema.org&quot;, &quot;@type&quot;: &quot;WebSite&quot;, &quot;url&quot;: &quot;<data:blog.homepageUrl/>&quot;, &quot;potentialAction&quot;: { &quot;@type&quot;: &quot;SearchAction&quot;, &quot;target&quot;: &quot;<data:blog.homepageUrl/>?q={search_term}&quot;, &quot;query-input&quot;: &quot;required name=search_term&quot; } }</script>
</b:if>

 

2. Solve Error strukturdata the "author"

Propery value "author" we can fill in the name of the author or the author of the article's posting is concerned, if the inside pages of your blog article you display the author, then the HTML code to paste the code we can author markup schema for the author.

At the html code of your blog please find the code below:
<b:if cond='data:post.authorProfileUrl'>
    <a class='g-profile' expr:href='data:post.authorProfileUrl' rel='author' title='author profile'>
        <data:post.author/>
    </a>
<b:else/>
Then change it to:
<b:if cond='data:post.authorProfileUrl'>
    <span class='fn' itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'>
        <meta expr:content='data:post.authorProfileUrl' itemprop='url'/>

        <a class='g-profile' expr:href='data:post.authorProfileUrl' rel='author' title='author profile'>
            <span itemprop='name'><data:post.author/></span>
        </a>
    </span>
<b:else/>
If your page does not display the author then you can make your own:
Please find the code:
 <article class='post hentry' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>
then add the following code below:
 <article class='post hentry' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>
<span itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'>
     <meta expr:content='data:post.authorProfileUrl' itemprop='url'/>

     <meta expr:content='data:post.author' itemprop='name' />
</span> 

If the setting above is true then display the data structure for the "author" will look like the image below:
data structure to author

3. Overcoming Error In "DatePublished" and "DateModified"

The data structure for the item "DatePublished" should be filled with dates penerbitkan articles, while DateModified can be filled with the date of modification of the article, if it is within your blog page article featuring the article publication date then we can DatePublished and DateModified paste the HTML code to the date of the article.
<time class='timestamp-link' expr:content='data:post.timestampISO8601'><data:post.timestamp/></time>

Then change it to:
<time class='timestamp-link' expr:content='data:post.timestampISO8601'itemprop='datePublished dateModified'><data:post.timestamp/></time>

 

4. Solve Error In strukturdata "image"

Values ​​for the data structure property "image" must contain an image url, if in artiktikel pasted image, the image url that we can use for the property value "image".

Find the following code:
 <article class='post hentry' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>

Then add the code below right after the above code becomes:
<article class='post hentry' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>
<b:if cond='data:post.firstImageUrl'>
<div itemprop='image' itemscope='itemscope' itemtype='https://schema.org/ImageObject'>

<meta expr:content='data:post.firstImageUrl' itemprop='url'/>
<meta content='320' itemprop='width'/>
<meta content='172' itemprop='height'/>
</div>
</b:if>
Actually the above code you can add anywhere inside part of the article but should be in the scope of HTML tags with  itemtype = 'http: //schema.org/BlogPosting'

The above code will assign the value "image" with the url of the first image that you insert on your blog articles, Value for itempprop = 'widht' and itemprop = 'height' you can customize to change the value of the image size you normally use on articles postinga.

If it works then strukturdata schema for the above code will look like the image below:

schema markup to the item image

5. Solve Error data structure "name" and "headline"

item property "name" and "headline" for itemtype = 'http: //schema.org/BlogPosting', we can fill with posting the article title is concerned, I fix is ​​as follows:

Search HTML tag used to wrap the article title of your blog posts, such as title tags on my blog is:
<h1 class='post-title entry-title'>
    <b:if cond='data:post.link or (data:post.url and data:blog.url != data:post.url)'>
        <a expr:href='data:post.link ? data:post.link : data:post.url'><data:post.title/></a>
    <b:else/>
        <data:post.title/>
    </b:if>
</h1>

then we change it to:
<h1 class='post-title entry-title' itemprop='headline name'>
    <b:if cond='data:post.link or (data:post.url and data:blog.url != data:post.url)'>
        <a expr:href='data:post.link ? data:post.link : data:post.url'><data:post.title/></a>
    <b:else/>
        <data:post.title/>
    </b:if>
</h1>
 If correct, then you will see the results like to see below:

markup schema name and headlines

6. Addressing Error data structure "publisher"

What the publisher and what is the difference with the author?, Publisher are patent holders and publishers all over the post while the author is the author of the posting.

item property "publisher" must use itemtype = 'https: //schema.org/Organization' or itemtype = 'https: //schema.org/Person', and this type of item has a sub item of property, name and logo.
To fill this property I usually use the name and logo blog blog.

How to fix it, find html tag that has  itemtype = 'http: //schema.org/BlogPosting'

Eg for my blog is:
<div class='post hentry' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>
Add at the bottom of the code becomes:
<div class='post hentry' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>
<span itemprop='publisher' itemscope='itemscope' itemtype='https://schema.org/Organization'>
    <meta expr:content='data:blog.title' itemprop='name'/>
    <span itemprop='logo' itemscope='itemscope' itemtype='https://schema.org/ImageObject'>
        <meta content='https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsz9Z74Y7CB0F5WIcXAO8fnyuwEnsK1bZqtxuvIEhSgKNBom0R5r5aJq9laHEExYlETeXMkAG34HPNTM-vb-jfVxZKZ1RTTD5IQiNu1OpVDXN4P41F7pMF3mYRr5BHMR1WPcnIue8SMw0/s1600/pasien-bpjs.jpg' itemprop='url'/>
        <meta content='146' itemprop='width'/>
        <meta content='146' itemprop='height'/>
    </span>
</span>
    

the blue is the blog url logo, please replace the logo image url for your blog.
numbers above 146 for itemprop = 'width' and itemprop = 'height' you can adjust the size of the logo of your blog.

The above code could be placed anywhere but should remain in the scope of html tags that have  itemtype = 'http: //schema.org/BlogPosting'

schema markup item property publisher

7. Solve Error Data Structure "mainEntityOfPage"

Item property "mainEntityOfPage" we can fill in with a url or  creativeWork (webpage, article, etc.)
If you choose url, we could fill it with the url of the blog article is concerned, if you choose creativeWork webpage, then we can use the itemtype = 'https: //schema.org/WebPage' for HTML tags used for items such property.

We will try to fill mainEntityOfPage with the url of the blog article in question.

If you do not use the link to the title of the article then please find the code:
<div class='post hentry' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>
and add them at the bottom into:
<div class='post hentry' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>
<meta expr:content='data:post.url' itemprop='mainEntityOfPage' />

If by chance your post using the article title link then you can add itemprop = 'mainEntityOfPage' tag in HTML for the link pattern would be:

<h1><a itemprop='mainEntityOfPage' href='xxx'>title</a></h1>

If successful it will look like the image below:

schema markup mainEntityOfPage

Is the influence of data structure for SEO?

According  Moz : If it is associated with seo until now the influence of schema markup on the ranking results pencaian still being debated, is still in the process of experiment and until now reportedly has been no evidence to assure that the presence of a marked-up data in the structure of the html page of your blog can increase your rankings in search result.


But there are indications that the search results snippets of information that is contained in the schema org blog page can increase click throught rate (CTR), it will be more attractive to more users click on a title in the search results.

If I do not terlambar get the latest information about the schema markup is the same statement on the strengthening of the google that to date schema org has not been used as the google ranking factors, but most likely I think personally schema org there will likely be used as the google ranking factors later.

So What advantage involving data structure schema markup to the code page of the blog?

Although not affect the seo, Presence schema markup I think this should still be involved in the structure HTLM blog page, Google recommends the blog to have a data structure schema markup to the goal of keeping the search engine more easily capture the intent contained in the blog page so that is understood not only writing course, remains the search engine will understand what the purpose of each part of the text.

By involving the structure of the data is good, then google index will be faster and better, and the search engine will be able to provide results with better information, and that means the blog will be more easily recognized, although its effects are not instant we can feel

Especially for adsense publishers We know that sometimes a rejection not google adsense is not clear navigation, there is a likely cause is that the blog is still new and the data structure schema markup template that is used does not provide presence information blog navigation on the page.



Cover

Repairs errors in the schema markup is difficult to serve because it would depend on the structure of the HTML used in the template of your blog, and may be structures htmlnya different, understanding the rules of the code schema markup actually very easy to make the structure of the blog supports schema markup good and correct.

Articles on  Free How to Fix Error in data structures blog , at least be able to provide additional insight and guidance to you to correct errors in the data structure of your blog template.