This article has been removed.
The content of this blog can be searched by keyword.
Use the search window in the sidebar or at the top. Alternatively, please translate the original article using Google or other means.
Please find alternative content.
Remnants of articles that had been published
Structured data errors and causes
Google Search Console> How it looks in search> Structured data
What is structured data?
Structured data is what tagged the search engines and other crawlers to understand what information written in HTML means.
The Awesome Inc. template of Blogger that we are using has the following description.
- class = 'hentry'
- http://schema.org/BlogPosting
This declares that the HTML syntax generated by the Awesome Inc. template conforms to the structured data standard: schema.org, syntax: microformats.org (hentry). Search engines and crawlers look for the corresponding field, meta tag and index.
schema.org
microformats.org
Cause of structured data error
The Awesome Inc. template is considered to be missing fields and meta tags that are required for schema.org, microformats.org.
What are the adverse effects of structured data errors?
Errors in structured data do not usually adversely affect Google crawling, indexing, ranking. You can leave it alone and ignore it.
Google Product Forum
Google is pursuing the following benefits.
In Google search, if you understand the content of the page or if you explicitly specify additional information in the page code using structured data, you can incorporate rich features into the search results.
Google Developers
Is repair necessary?
By writing the web page with the minimum HTML tag, the browser can understand the syntax and display it.
Structured data is a standard established for search engines and crawlers, and it is considered that there is no effect on SEO even if a structured data error has occurred, so the necessity of restoration is considered to be low I will.
Users of Awesome Inc. templates are all supposed to have structured errors, so it's a good idea to wait until the template is available.
As a practical matter, in order to repair the structured data error, we have to modify the template, taking the Awesome Inc. template as an example, from the HTML code with more than 3,000 lines we specify the location to be appended to the standard It is necessary to add corresponding field and markup. Hurdles are expensive for those who have never written HTML.
Example of repairing structured data errors
I attempted to repair as I was curious whether it could completely deter the detection of structured errors.
The following is a trial and error note.
Template backup
Back up the Awesome Inc. template before entering the repair work. The way to do is as follows.
- Blogger> Themes> HTML editing
- Click on HTML to activate it
- Use Ctrl + A to select the whole, then press Ctrl + c to copy
- Paste into text editor with Ctrl + v
- Save it after naming it
- end
Passive coping method
Specifically, searching hentry with Awesome Inc. template hits the following syntax, so delete all attributes related to schema.org and hentry.
<div class='post hentry uncustomized-post-template' itemprop='blogPost' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>Revised:
<div class='post uncustomized-post-template' >Field name to be excluded from detection
| Required field | author, datePublished, headline, publisher |
| Recommended Field | dateModified, mainEntityOfPage |
Google specific errors are handled individually
| image_url | For BlogPosting objects the property image_url is not recognized by Google. |
Workaround
<meta expr:content='data:post.thumbnailUrl' itemprop='image_url'/>
<meta expr:content='data:post.firstImageUrl' itemprop='image_url'/>
Revised:
<meta expr:content='data:post.thumbnailUrl' itemprop='image'/>
<meta expr:content='data:post.firstImageUrl' itemprop='image'/>
Aggressive repair methods
Schema.org, microformats.org (hentry) It is a way to add meta tags missing from the template, leaving the attribute as it is.
The following procedure is limited to the Awesome Inc. template, but there is a possibility that it can be applied to Blogger users.
Find places to add
Blogger> Themes> HTML editing
- Show template HTML
- Search with hentry
In our Awesome Inc. template it was found on line 2019. I think that you can find it with a slightly younger line number if you have an initial template.
Add structured data (schema) from the next line of tag with hentry attribute.
What tags will you add?
Additional example
<div class='post hentry uncustomized-post-template' itemprop='blogPost' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>
<!-- 追記ここから -->
<div style='display:none'>
<meta content='data:post.link : data:post.url' expr:itemid='data:post.link' itemType='https://schema.org/WebPage' itemprop='mainEntityOfPage' itemscope='itemscope'/>
<!-- 公開日の定義 -->
<span class='published' itemprop='datePublished'><data:post.timestampISO8601/></span>
<!-- 更新日の定義 -->
<span class='updated' itemprop='dateModified'><data:post.lastUpdatedISO8601/></span>
<!-- authorの定義 -->
<span itemprop='author'><data:post.author/></span>
<!-- nameの定義 -->
<span itemprop='name'><data:post.author/></span>
<!-- headlineの定義 -->
<span itemprop='headline'><data:post.title/></span>
<!-- publisherの定義 -->
<div itemprop='publisher' itemscope='itemscope' itemtype='https://schema.org/Organization'>
<span itemprop='name'><data:blog.title/></span>
<span itemprop='logo' itemscope='itemscope' itemtype='https://schema.org/ImageObject'>
<span itemprop='url'>https://kzstock.blogspot.com/</span>
<meta content='horizontal' itemprop='width'/>
<meta content='vertical' itemprop='width'/>
</span>
</div>
<!-- imageの定義 -->
<div itemprop='image' itemscope='' itemtype='https://schema.org/ImageObject'>
<img alt='3' height='3' src='https://kzstock.blogspot.com/' width='3'/>
<meta content='https://kzstock.blogspot.com/' itemprop='url'/>
<meta content='3' itemprop='width'/>
<meta content='3' itemprop='height'/>
</div>
</div>
<!-- 追記おわり -->What is schema.org?
Q: Why do I need to add markup? What will I get from then? How is the data used?
Search engines use markup on the page in various ways. With these projects, you can display the content more clearly in the search results. Not all types of information on schema.org are displayed in search results. You can find specific uses by referring to the documents of each company, but you can expect that more data will be used more over time. In addition, since markups are publicly accessible from your web page, other organizations can find new ways of interest as well.
Q: Do I need to mark up all the properties?
It is OK to mark up only some properties of the item. Markup is not a choice whether it's all or not. However, marking up as much content as possible helps the search engine use your information to present the page in the most useful way to the user. As a general rule, please mark up only the content that is displayed to the user who visited the web page, and not mark up the content on the hidden div or other hidden page elements.
FAQ - schema.org
- How to avoid the problem that Synaptics Mouse 19.0.19.13 is detected repeatedly by Windows Update
- Can I delete the MATS folder?
- If the uninstall process stops, try using Microsoft easy fix
- Delete unknown account in local user profile | Windows 7
- How to delete an unknown account
- Installing and using YouTube Video Downloader
- Summary of measures against videos that cannot be downloaded
- The Fukuoka University NTP server will stop!
- How to set up a public NTP server on your PC
- Tab Explorer with QTTabBar
- remnants ラベルの記事（要約付）
- Google が含まれる記事（要約付）
- 【2024年度総括】藤井七冠(最優秀棋士)、羽生九段現役続行と会長退任を表明
- 【バグ】TVerRec 3.4.2 のリネーム処理不具合とその原因を考察
- 【恐怖】ポンジスキームとは？歴史から学ぶ詐欺の仕組み
- 【終息】TVerRec 3.3.9（暫定）で機能制限ほぼ解除、3.4.0リリース！
- 【緊急】TVerRec 3.3.6緊急リリース！仕様変更に暫定対応
- 【未解決】TVerRecダウンロード不具合！TVerの仕様変更かも？
- 【昇級／降級】全棋士ランキング確定、伊藤匠叡王B1へ昇級、羽生九段B2へ降級
- 【将棋】なぜ藤井聡太は人々を魅了するのか？【2024年度振り返り】
- 【更新】Lhaz 2.5.4リリース！法人利用が有料化へ
- 【Pixel 3月／2025】カメラ、WebView 、Bluetooth、電話のバグ修正【Android 15】
このサイトを検索 | Search this site
ブロトピ：今日のブログ更新