Leonidas Milosis

Continuing the AT from [here](https://github.com/Yoast/wordpress-seo/pull/20944#pullrequestreview-1938392783). Verify our classic editor integration still works: Done and all good ✅ Verify our Elementor integration still works: Done and all good ✅

@thefrosty Just a heads up, we've scheduled an improvement on usermeta and while it doesn't touch specifically the afore-mentioned `_yoast_wpseo_profile_updated` meta, it does clean up other custom Yoast usermeta, when...

> once I noticed that we were using the hierarchy with the var name $indexable, so we should probably make tripple sure this is not done elsewhere. I'm actually not...

Without diving too much into the the issue and its potential culprits, I can say that we might consider completely moving the Squirrly import to the new way of import...

@monbauza it would be interesting to see if it happens with older versions of the Squirrly SEO plugin as well. I'm guessing that things started to break when they did...

Awesome, thanks for that really useful info 🎉 🙂

The PRs are ready for a review, but we have a couple of questions that need to be answered first from the product team before moving the ticket in `Needs...

Hi there @bmcpherson-malware and thank you for the report. Your caching proposal attempts to decrease the database queries with each page load, that are due to the get_all() function. But:...

CR: ✅ (aside from the fact that we named a non-public change (because of the feature flag) an `enhancement` and [an open question](https://github.com/Yoast/wordpress-seo/pull/21391#discussion_r1735788827))

🐛 A direct effect of us introducing this content parsing is that we now get OOM errors because of an infinite loop, whenever there's the `Yoast breadcrumbs` block in a...