The NGFB plugin provide HTML Meta tags for web page headers as well as optional social sharing buttons. The Google Structured Data Testing Tool checks this header HTML Meta tags, along with Schema as well as Microdata HTML markup. The Schema plus Microdata markup must be included all through the document’s body to recognize sections plus specific info for Google and additional search engines.
The adding up of Schema as well as Microdata HTML markup is managed by the WordPress theme template. Some themes template might give actions plus filters for diverse sections of the template – that might be used by plugins to add Schema as well as Microdata – however usually Schema plus Microdata markup is hard-coded straight in the templates. To add or adapt the HTML markup in this case, you usually have to edit the applicable theme template or theme functions.
The Google Structured Data Testing Tool breaks downward the analyzed content in to several sections. You’ll discover utmost of the HTML Meta tag added by NGFB in the rdfa-node / possessions section.
As an instance, you could view as well as compare an study of this page in Google’s Structured Data Testing Tool and Facebook’s Object Debugger.
Google announced improvement to their rich snippet testing tool late previous week, including a new moniker: the Structured Data Testing Tool.
There are three main changes, says Google:
- We have improved how we display rich snippets in the testing tool to improved match how they emerge in search results.
- The brand new image design makes it clearer whatever structured data we could extract from the page, and how that might be shown in our explore results.
- The tool is now accessible in languages other than English to aid webmasters from around the world construct structured-data-enabled web sites.
The tool is still situated in the similar place, at the rich snippets tool address. It is still called the Rich Snippets Testing Tool in Google Web master Tools, though that might change.
Another puzzling caveat is that the WMT Help resource has been restructured to reflect the new tool name, however it still says this is accessible in English merely, despite the statement of new language. It seems the tool certification may be a few days behind the real announcement.
One complaint that has sprung up as the announcement is the new boundary of 1,500 characters for HTML testing. Published pages could be tested by the URL tool, however those in growth require to use the HTML tester. It is almost certainly a good idea to bookmark this novel tool in order that you could access it easily.
Search Engine Watch writer Thom Craver offers a solution. The majority basic form of verification for HTTP could be done by using a username as well as password in the URL, he said. Make your dev. surroundings publicly online, however behind a username/password combo using normal basic HTTP verification. The username plus password could be incorporated in the URL, so the tool could crawl using the correct credentials.