Title: Great Plugin. Microdata Support?
Last modified: September 3, 2016
---
# Great Plugin. Microdata Support?
* [Preston](https://wordpress.org/support/users/pkdsleeper/)
* (@pkdsleeper)
* [11 years, 7 months ago](https://wordpress.org/support/topic/great-plugin-microdata-support/)
* Love this plugin. Started adding microdata to the theme title which caused check
to fail.
* > “REQUIRED: The theme needs to have tags, ideally in the header.php
> file.”
* This fails theme check:
`<title itemprop="name"><?php wp_title( '|', true, '
right' ); ?>`
* This passes:
`<?php wp_title( '|', true, 'right' ); ?>`
* I guess it does not recognize microdata.
* sleeper
Viewing 2 replies - 1 through 2 (of 2 total)
* Plugin Author [Samuel Wood (Otto)](https://wordpress.org/support/users/otto42/)
* (@otto42)
* WordPress.org Admin
* [11 years, 7 months ago](https://wordpress.org/support/topic/great-plugin-microdata-support/#post-7899922)
* At this time, it does not recognize those. It may be more lenient in the future,
especially with the changed support for titles which may be in WordPress 4.1.
* However, on a general note, putting itemprop=”name” on a title tag really makes
no sense. What would the itemscope be on in such a case? It could not be on the
head element, so it would need to be on the HTML element. And making the whole
HTML into an “item” is generally a bad idea. You would ideally want the itemscope
to be on the body for a whole page scenario.
* I realize that putting itemscope onto the main html element isn’t technically
incorrect, but it’s definitely not what any of the examples on schema.org show.
On the WebPage example, they show the itemscope covering the body, for example:
[http://schema.org/WebPage](http://schema.org/WebPage)
* The purpose of schema microdata is to allow things like search engines to better
understand the underlying structure of the document, by identifying specific
elements as having special meanings. Things such as the title and other elements
in the head already have well-defined meanings. Adding microdata to them doesn’t
really give you any benefits. It would be more effective to limit microdata to
the body and other elements in the page which have less-specific markup, such
as things in headers or generic div’s and span’s.
* Basically, the “name” is a generic property from the “Thing” schema, so it would
be better to put that on something such as the title of the blog post on a single-
page markup. Blog posts have their own titles, which might not be the same as
the title of the webpage as a whole.
* Thread Starter [Preston](https://wordpress.org/support/users/pkdsleeper/)
* (@pkdsleeper)
* [11 years, 7 months ago](https://wordpress.org/support/topic/great-plugin-microdata-support/#post-7899923)
* Greetings Otto,
* > At this time, it does not recognize those. It may be more lenient in the future,
> especially with the changed support for titles which may be in WordPress 4.1.
* Cool! I look forward to any update you may decide to provide. As I said, this
tool is awesome!
* > You would ideally want the itemscope to be on the body for a whole page scenario.
* **_Agreed!_** At the time of the post I was in the early stages, still trying
to grok what “all the fuss” was about (esp. from Google). I’ve since updated
my code, but thanks for the pointers 🙂
* sleeper
Viewing 2 replies - 1 through 2 (of 2 total)
The topic ‘Great Plugin. Microdata Support?’ is closed to new replies.
* 
* [Theme Check](https://wordpress.org/plugins/theme-check/)
* [Frequently Asked Questions](https://wordpress.org/plugins/theme-check/#faq)
* [Support Threads](https://wordpress.org/support/plugin/theme-check/)
* [Active Topics](https://wordpress.org/support/plugin/theme-check/active/)
* [Unresolved Topics](https://wordpress.org/support/plugin/theme-check/unresolved/)
* [Reviews](https://wordpress.org/support/plugin/theme-check/reviews/)
* 2 replies
* 2 participants
* Last reply from: [Preston](https://wordpress.org/support/users/pkdsleeper/)
* Last activity: [11 years, 7 months ago](https://wordpress.org/support/topic/great-plugin-microdata-support/#post-7899923)