Yoast update 21st Sept has broken plugin?

Hi @markyz89,

Unfortunately, your message does not provide enough information for us to be able to reproduce the problem you experienced. Could you please describe in detail what doesn’t work anymore, and how it used to work before?

If you can add screenshots to clarify your description, that’d be highly appreciated!

Thanks!

Same issue here.

Error:
“ACF Content Analysis for Yoast SEO vereist Yoast SEO for WordPress 14.9 of hoger, update de plugin alsjeblieft.” (dutch)

Translation:
“ACF Content Analysis for Yoast SEO requires Yoast SEO for WordPress 14.9 or higher, please update the plugin.”

@angelomusch Which version of Yoast SEO for WordPress are you running on your site?

If it’s lower than 17.3, can you please update it to the latest version and try again?

Please let us know if that resolved the issue for you. Thanks!

Solved by renewing my license. Thank you Taco.

Hi @tacoverdo, thanks for getting back to me.

I can’t really give you a lot more detail. This problem (that content in custom fields wasn’t being analysed by Yoast) was reported to me as the developer for our organisation by one of our departments who had their site built externally. I was going to install your plugin as a solution but then saw it was already installed. I can’t see any evidence of this plugin doing anything, so there’s not really anything to take a screenshot of, but I’ve been told it was working before.

The timeline matched up with a Yoast update so I suggested in this question that might have been the reason for this issue.

Our debug log has the following error:
[05-Oct-2021 14:40:15 UTC] PHP Notice: Trying to get property ‘post_type’ of non-object in /kunden/328878_10247/webseiten/provegincubator.com10082021/wp-content/plugins/wordpress-seo/src/integrations/third-party/elementor.php on line 156

So that suggests there is a conflict between Yoast and Elementor that has a knock-on effect on this plugin? Both plugins (and yours) are up-to-date.

We don’t have Yoast premium like @angelomusch. Do you think upgrading to premium would solve the issue?

Thanks,
Mark

I’m happy to hear that @angelomusch! Thanks for being a Yoast customer!

—-

Thanks for your reply @markyz89.

To be fair, I don’t think upgrading to Yoast SEO Premium in itself will resolve the problem. However, doing so will give you access to our 24/7 support team. They can help you investigate and (usually) resolve this potential conflict as they can dive much deeper into your site than I can on the forums.

A great start could be to check for a plugin conflict following this guide btw: https://yoast.com/help/how-to-check-for-plugin-conflicts/.

I have this issue also, of Yoast not analyzing the ACF fields correctly.
I am using:
Yoast SEO (free): Version 17.5
ACF Content Analysis for Yoast SEO: Version 3.0.1
Wordpress: Version 5.8.1

What didn’t help:
– turning off all plugins except Yoast and ACF content analysis
– reverting to a wordpress default theme (like twentyseventeen)
– re?nstalling both Yoast and ACF content analysis

Example:
The page: https://www.mindfulness-op-maat.nl/wp/anja/
This oage contains over 500 words, yet Yoast reports:

“Text length: The text contains 89 words. This is far below the recommended minimum of 300 words. Add more content.”

I also use Elementor Pro, which could be a problem maybe?

Any pointers or tips would be greatly appreciated!

• This reply was modified 3 years, 4 months ago by Anonymous User.
• This reply was modified 3 years, 4 months ago by Anonymous User. Reason: adding example + fixing a typo

Hi @hansvannoord,

To be fair, without taking a look at the backend of your site this is just a guessing game.

That said, if this were directly related to your page builder, I wouldn’t expect to see the 89 words still being reported. What we usually see then is 0 words are reported.

Should you be unable to figure this one out here, I think this would be a good case to present to Yoast’s support team. Obviously, this would require the purchase of Yoast SEO Premium at https://yoast.com/shop/.

Thank you for your reply Taco,

odd then that it gives me a count, which it does on most pages, often incorrect.

I will search on then, I also posted at the ACF content analysis github page, maybe it yields a result. When it does I will report back here.

Thanks!