November 26, 2020 at 12:37 am #1263137
When switching a Blog Post from Default Editor to ALB, the markup that remains on Enfold is incorrect. And therefore, it throws errors (in this case, 35 errors and 25 warnings) Now I remember why I had to disable your markup. I would like to have it back but without errors.
This is just one of the posts that I switched to ALB:
And the Structured Schema test:
November 30, 2020 at 12:58 pm #1263949
- This topic was modified 3 years ago by havi. Reason: Switched URL to Staging URL so I can Disable Schema on the Live Site
Thank you for the inquiry.
When you switch from the default editor to ALB, the theme will just convert the text or the content of the posts to a Text Block, but this element does not contain the necessary schema or markup by default. You will have to use a third party plugin such as the following to recreate the schema markup in JSON-LD format.
We recommend using the default editor for the posts if you are after the basic schema markup from the theme.
IsmaelNovember 30, 2020 at 5:45 pm #1264037
Could you please submit this as a bug? I have been turning blog articles to pages by using ALB for years (as recommended a long time ago by Kriesi) and this error never happened. I first noticed it when Yoast changed their Schema and you guys added the SEO deferring to the SEO plugin.
Something has gone awry. I suggest looking into why there are two “blog” markups created, one is good and without errors and the other one has the errors. This never happened before.
I would not appreciate having to use another plugin for Schema to replace what the theme should provide by default. Switching to ALB is really wonderful for a blog boost as I can turn it to Evergreen while still remaining on the blog. It worked perfectly with no issues (as that information is still there, I can still see the date, author, and thumbnail) but now it fails. I am sure that you did not design allowing switching to ALB to create a markup issue.
Besides, Enfold has a pretty large CSS and JS file that impacts LCP (last contentful paint) and no matter how little code I use for the page, these are large files. Adding more plugins is not recommended.
Please keep me posted of the fix.
December 1, 2020 at 5:05 pm #1264281
- This reply was modified 2 years, 12 months ago by havi. Reason: Found duplicate markup when checking for more info. Added info to help solve it
I first noticed it when Yoast changed their Schema and you guys added the SEO deferring to the SEO plugin.
What happens when you disable the schema markup from the theme? If you are using the Yoast SEO plugin, enabling the built in schema option should be enough. It is also much more preferable because it is already in JSON-LD format.
I would not appreciate having to use another plugin for Schema to replace what the theme should provide by default.
The theme provides basic schema for the posts but you have to use the default editor.
IsmaelSeptember 22, 2021 at 11:24 am #1321884
Im having the asme issues as Havi, and agree with him that you should have this fixed within Enfold. Else we are not able to use the ALB, which is the ‘power’ of Enfold.
I think it would be a great addition if you add schema markup options (like adding FAQ, etc) form within Enfold itself, so we can use the enfold framework, the ALB and also be able to add schema without having to use extra plugin that will slow down the website. The enfold code is very large and it’s 2021, this kind of functionality is a must if you are serious in SEO.
Please add this as an urgent request. We are using Enfold since day 1, developed dozen of websites. But SEO limitations and the large code / speed is really becoming an issue.
Love to hear from youSeptember 24, 2021 at 6:29 am #1322113
As we mentioned above, the default templates and the builder elements contain basic schema markup. If you add a special heading element for example, the theme will automatically add an itemprop attribute, which contains the value “headline”.
<div style="padding-bottom:10px; " class="av-special-heading av-special-heading-h3 avia-builder-el-0 avia-builder-el-no-sibling "> <h3 class="av-special-heading-tag " itemprop="headline">Hello</h3> <div class="special-heading-border"> <div class="special-heading-inner-border"></div> </div> </div>
The accordion element if used as FAQ element will contain the following schema structure.
<div itemscope="itemscope" itemtype="https://schema.org/FAQPage" class="togglecontainer toggle_close_all avia-builder-el-0 el_before_av_heading avia-builder-el-first enable_toggles"> <section class="av_toggle_section" itemscope="itemscope" itemprop="mainEntity" itemtype="https://schema.org/Question"></div> </section></div>
Only basic structure is added because the theme is used for a wide variety of sites, which is why we cannot add complex schema structures that focused on specific niches (e.g recipes, books etc) or structures that can only cater specific sites. So if you need a more complex schema structure, you will have to use a third party plugin such as Yoast or Markup (JSON-LD), which creates json-ld schema structures automatically.
- You must be logged in to reply to this topic.