Governed ability
Get post SEO (All in One SEO)
aafm/aioseo-get-post Read only
Reads a post's SEO fields (title, description, canonical, social, and robots) from All in One SEO's own data store, not post meta. Requires 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 (All in One SEO) 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 (All in One SEO) 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.
Read the All in One SEO title and description for post 142.
Show me the canonical URL and social settings All in One SEO has for this post.
What robots settings does All in One SEO store for post 512?
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 (All in One SEO).
Where does it read from?
It reads a post's SEO fields (title, description, canonical, social, and robots) from All in One SEO's own data store, not from post meta.
When is the ability present?
Only while All in One SEO is active on the site. It is registered by that integration and is absent when the plugin is not running.
What access does it need?
It requires edit access to that post, is off by default, and each read is captured in the audit log.
Governed by default, from the first call.
Get post SEO (All in One SEO) 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.