Tagged: schema, validation
-
AuthorPosts
-
February 4, 2020 at 6:31 pm #1181438
Hi,
I find some validation errors related to hProduct and “missing FN” (private link).
The issue occurs in class “avia-testimonial-name”:<div class='avia-testimonial_inner'><div class='avia-testimonial-content ' ><p><span id="hproduct-2" class="item hproduct">[Content]</span></p> </div><div class='avia-testimonial-meta'><div class='avia-testimonial-arrow-wrap'><div class='avia-arrow'></div></div><div class='avia-testimonial-meta-mini'><strong class='avia-testimonial-name' >[Content]</strong><span class='avia-testimonial-subtitle ' itemprop="jobTitle" >[Content]</span></div></div></div></div>
Could this be fixed for further releases? Theoretically,
class='fn avia-testimonial-name'
should work…
Thank you!February 6, 2020 at 7:15 pm #1182132Hey Ricard,
Τhank you for pointing this out!
We have asked our developer to look into this and get it sorted out over a next release.Best regards,
BasilisFebruary 6, 2020 at 8:02 pm #1182148Welcome! Happy to contribute
February 7, 2020 at 10:16 am #1182259Hi,
I cannot find the class hproduct in Enfold nor in WooCommerce. How did you add the content of the testimonial?
Best regards,
GünterFebruary 7, 2020 at 1:40 pm #1182306Hi Günter,
I made a mistake and need to reformulate my thread subject. The FN microformat issue is not Enfold native, but from plugin WP Customer Reviews Lite.
However, the present Testimonial in Enfold can be improved. Please let me propose the following:1) Fix present Enfold testimonial element to properly display all Schema value, namely PERSON + CREATIVEWORK (it is only showing PERSON on Google Schema Validation tool).
At present Enfold’s testimonial tags these items as PERSON+CREATIVEWORK, but the latter is not showing up.
IMO element CREATIVEWORK should contain element PERSON, not the other way round.
This is the code producing this PERSON+(not visible)CREATIVEWORK:<section class="avia-testimonial-row" style="padding: 0px; height: 105px;"> <div class="avia-testimonial av_one_half flex_column no_margin avia-testimonial-row-1 avia-first-testimonial avia_start_animation active-slide" itemscope="itemscope" itemtype="https://schema.org/Person" style=""> <div class="avia-testimonial_inner"> <div class="avia-testimonial-content " itemscope="itemscope" itemtype="https://schema.org/CreativeWork"> <p>This is Tina’s testimonial content</p> </div> <div class="avia-testimonial-meta"> <div class="avia-testimonial-arrow-wrap"><div class="avia-arrow"></div></div> <div class="avia-testimonial-meta-mini"> <strong class="avia-testimonial-name" itemprop="name">Tina</strong> <span class="avia-testimonial-subtitle " itemprop="jobTitle">CMO</span> <span class="hidden avia-testimonial-markup-link" itemprop="url">http://www.tinasplace.io</span> – <a class="aviablank avia-testimonial-link" href="http://www.tinasplace.io" target="_blank">Tina’s Place</a> </div></div></div></div> </section>
This next code produces the valid semantics we expect from the previous code.
If you screen this through Google Schema validator tool, you should get 2 instances of CreativeWork, one (Microformat) is enfolding PERSON within CREATIVEWORK (as “author”) and second is a plain example of CREATIVEWORK using RDFa.
Validated 100%.<section class="avia-testimonial-row" style="padding: 0px; height: 105px;"> <div class="avia-testimonial av_one_half flex_column no_margin avia-testimonial-row-1 avia-first-testimonial avia_start_animation active-slide"> <div class="avia-testimonial_inner"> <div class="avia-testimonial-content " itemscope="" itemtype="https://schema.org/CreativeWork"> <p itemprop="text">This is Tina’s testimonial content in Microformat</p> <!-- again the same, expressed in RDFa which is much more suitable for extending adding ontologies like FOAF or DC--> <div class="avia-testimonial-content " vocab="http://schema.org" typeof="CreativeWork"> <p property="text">This is Tina’s testimonial content in RDFa</p> </div> <!-- end RDFa sample --> <div class="avia-testimonial-meta"> <div class="avia-testimonial-arrow-wrap"><div class="avia-arrow"></div></div> <div class="avia-testimonial-meta-mini" itemprop="author" itemscope="" itemtype="https://schema.org/Person"> <strong class="avia-testimonial-name" itemprop="name">Tina</strong> <span class="avia-testimonial-subtitle " itemprop="jobTitle">CMO</span> <span class="hidden avia-testimonial-markup-link" itemprop="url">http://www.tinasplace.io</span> – <a class="aviablank avia-testimonial-link" href="http://www.tinasplace.io" target="_blank">Tina’s Place</a> </div> </div> </div> </div> </section>
This time I have no link for any live code, but I tested all the snippets previous to sending.
I hope this helps making a better Enfold theme :)
Thanks for reading.February 9, 2020 at 4:01 pm #1182769Hi,
Thanks for the input.
I’m not an expert on this, but IMO adding the RDFa …. only to one element does not make too much sense at the moment -it would need to redesign all other elements also.
For the moment I only changed the markup to show up in the structured data under CreativeWork (next release).
Hope this also helps you.
Best regards,
GünterFebruary 10, 2020 at 10:24 am #1182976Hi Günter,
I fully understand and -as an Enfold user- I rather have the dev team focussing on solid output.
However, just as a heads-up, RDFa can live together with Microformat and even JSON-LD scripts, Google will eat it up just as any standalone Schema markup. Even old timer GoodRelations can do. Just mind the namespaces :)
Have a nice week!February 13, 2020 at 2:57 am #1184031 -
AuthorPosts
- The topic ‘Goog eSearch Console – Microformat validation error FN – Testimonials’ is closed to new replies.