Good tool, Yoast SEO not compatible

Hi @yashjain27

Sorry to hear you had a bad experience with Page Builder. If you were still using Page Builder we’d have been happy to assist.

What known issue are you referring to?

I have checked bunch of forms starting on 2015, and SiteOrigin told its user they will fix the issue in few weeks. Its been 3 years and no fix has been provided.

Yoast SEO doesn’t pick up images in the site builders, headings, focus keywords, internal links, external links. Please help

Thanks for your feedback.

Unfortunately, referencing issues on the forum from 2015 still doesn’t get us any closer to discussing specifics. I’d be more than happy to if you want to send individual problems or links.

With regards to Yoast, we can definitely take a look at that.

There is currently an open issue with Yoast SEO. We’ve investigated the problem and it lies within Yoast, not Page Builder. As a result, it’s out of our hands. Here is the issue report logged on Yoast’s repo on GitHub. We’ve contributed as much as we’re able to: https://github.com/Yoast/YoastSEO.js/issues/1346#issuecomment-363706282

It’s worth noting that if Yoast isn’t detecting content count, for example, that’s in no way a reflection of whether search engines are reading that same content. They’re entirely different tools.

If you’d like to open a support topic, either here on www.remarpro.com or on the SiteOrigin forum, I’d be happy to Alex to dive in first thing tomorrow and assist as much as we’re able to. If you’d like to do that, please send me the link once the support topic has been opened. Thanks.

• This reply was modified 6 years, 5 months ago by Andrew Misplon.

OH okay, if it’s on their part I will change my review. So are you saying if they aren’t detecting my contents, Google still might? And how can you help otherwise?

Correct. An issue with Yoast SEO not reading word count within Page Builder (for example) is completely separate from search engines being able to crawl your site.

I don’t want to immediately say that the GitHub issue I’ve referenced above is the problem you’re facing. Ideally, we’d take a look first before making that conclusion. If you’d be willing to open a support issue on either forum, we’d assist ASAP and help confirm exactly where the issue lies and what can be done to move forward.

But haven’t you guys already done this before? I can show so many people asking for fix for the same issue but nothing has happened yet.

Here you can look at various forums: https://www.google.com/search?q=page+builder+by+siteorigin+seo+problems&rlz=1C1CHBF_enUS790US790&oq=page&aqs=chrome.0.69i59j69i60l3j69i57j0.2049j0j7&sourceid=chrome&ie=UTF-8

And I start a thread

Super, thanks. Alex will attend ASAP.

Yes, unfortunately, if you are encountering the error: “An error occurred in the ‘fleschReadingEase’ assessment” then it’s the bug I’ve linked above on Yoast SEO GitHub.