Governed ability
Get post SEO head (Yoast)
aafm/yoast-get-head Read only
Reads the rendered SEO head markup for a post from Yoast, best-effort: the returned head string is empty when Yoast exposes no head API for that post. Requires the edit-posts capability and edit access to that post.
How it is governed
The same model as every ability in the plugin, stated for this one.
- Off until you enable it
Like every ability, Get post SEO head (Yoast) ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Reads only
It reads data and returns it to your client. Nothing on your site is created, changed, or removed.
- Capability gated
A connection only sees Get post SEO head (Yoast) if the user you connected can run it, and the plugin checks that capability again before it executes.
- Every call audited
The call is written to the log in your own database, denials included, with the argument keys but never the values.
See it in action
An illustrative run. Your real calls and data stay on your own site.
Try it with a prompt
Example requests you could paste to your agent.
Get the rendered SEO head markup Yoast outputs for post 142.
Show me the head tags Yoast would render for this post.
Fetch the Yoast head output for post 512 so I can check the meta tags.
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Frequently asked
Short answers for Get post SEO head (Yoast).
Why might the head come back empty?
It reads the rendered SEO head markup for a post from Yoast on a best-effort basis. The returned head is empty when Yoast exposes no head API for that post.
When is it available?
Only while Yoast SEO is active. It requires the edit-posts capability plus edit access to that post.
Is it audited?
Yes. It is off by default and every call is recorded in the plugin's audit log.
Governed by default, from the first call.
Get post SEO head (Yoast) is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Every ability off until you enable it, capability-gated on every call.