It is quite common to get Node is Empty warning in WordPress when tested in Structured Data Testing Tool. There should be a property inside. Previously, we have discussed about how to Fix WordPress mainContentOfPage Schema Error in Genesis. Despite WordPress is a Free Software, these Themes are not Free Softwares. Due to the closed source model of software distribution, it is very difficult for the community to participate and fix them.
Why Node is Empty Warning Comes in WordPress Structured Data Testing
These Themes gradually proving one basic thing – Google demands highly specialized persons in Theme development and the current developers has too much superficial knowledge. Mix and Match, Trial and Error methods used to add micro data; which now are failing. We have fixed the major error ourselves but we can not distribute it as it is a closed source software. Node is Empty Warning in WordPress in Google Structured Data Testing is not exactly harmful but it does indicate a kind of automated common method used while crafting the webpage. Which can lower down the SERP in near future.
These are not only problem of Genesis, these are problems of most of the paid Themes. Red marked Errors must be fixed to avoid penalty. These errors can decrease the number of site links and other variables on SERP. The developers lack the idea about HTML5 Vocabulary and Interfaces, so about the hierarchy of the represented data.
---
Fix Node is Empty Warning in WordPress Structured Data Testing
The basic thing is that, you need to fill data :
1 2 3 4 5 6 7 8 9 10 11 12 13 | <aside class="sidebar sidebar-primary widget-area" role="complementary" itemscope="itemscope" itemtype="http://schema.org/WPSideBar"> <section id="text-2" class="widget widget_text"> <div class="widget-wrap"> .... <div class="text widget"> <span itemprop="text" itemscope itemtype="https://schema.org/Text"> ... <p>Copyright © 2015 · <a href="https://jima.in/" itemprop="creator" itemscope itemtype="http://schema.org/Person"><span itemprop="name">Abhishek Ghosh</span></a> ... </div> |
The above will throw error but we have shown two things :
Adding the Item Type Text and Item Prop text. Text and text are not same. After you add these inside a Widget, WPSideBar itself will not itself show as Node is Empty. It will give error against the Text Item.
As basically this way of editing is meaningless, it is better to remove them to the full. We have fixed our major elements of the webpages in this way :
We have removed some default function and used JSON-LD, Page Map etc. to fix them. If we can not mark where from the Article starts and where it ends, it becomes difficult and misleading for Google. Relevant information can be found here :
1 | https://developers.google.com/custom-search/docs/structured_data |
All fields on the Widgets have to filled up properly, our knows Item is within Widget, adding one Item will not work. These are arising due to the Theme developers desperate trials to over optimize.
