Hi, thanks for the report, and sorry for the confusion here.
I looked into your session on our side, and here is what actually happened: WPVibe did not block the write. Yoast’s _yoast_wpseo_metadesc is an underscore prefixed “protected” meta key in WordPress, so the first attempt without –force gets refused with a hint, and a retry with –force goes through. Your assistant’s update to that post completed successfully.
The confusing part is Yoast itself. Yoast does not render the front end from postmeta. It serves titles and descriptions from its own indexables cache table (wp_yoast_indexable), and a direct meta write does not always refresh that cache. So your new description is stored in the database, but the page keeps showing the old one, which looks exactly like “nothing was changed.” When you asked your AI about it again, it guessed at a permissions explanation instead of the real cause (that second session never actually reached WPVibe at all).
Two easy ways to fix it:
- Ask your AI to re-save the post after writing the meta (any small update, even re-saving the same title via the REST API). Re-saving triggers Yoast to rebuild its index for that post.
- Or in wp-admin go to Yoast SEO > Tools and click “Start SEO data optimization.” That rebuilds the whole table.
On your Abilities API question: Yoast added Abilities API support recently, but the abilities it registers are read only (SEO, readability, and inclusive language scores). There is no write ability for meta descriptions yet, so the meta write path above is the correct one.
I am also going to make WPVibe handle this automatically so a Yoast meta write refreshes that post’s indexable for you. Thanks for surfacing it.
John
