seo/update-knowledge-graph sets who the site represents — a person or an organisation — and the details search engines attach to that entity: name, alternate name, logo, and for a person the linked user.
This drives Yoast’s schema output and the site’s identity in search results.
At a glance
| Ability | seo/update-knowledge-graph |
| Toolset | Yoast SEO — toolset/yoast-seo |
| Group | Yoast SEO › Settings |
| Requires | Yoast SEO, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
The entity everything else points at
Every piece of structured data Yoast emits references this entity. An article has a publisher; a product has a seller; a breadcrumb belongs to a site. If the entity is incomplete, all of them are incomplete in the same way.
Incomplete is the common state rather than the exception, because this is configured during Yoast’s first-time setup and that setup is frequently abandoned halfway. seo/get-first-time-config reports whether it was finished.
The person-or-organisation choice is not cosmetic. An Organization entity supports a logo and a set of social profiles; a Person entity links to a WordPress user and behaves differently in search features. Choosing the wrong one produces schema that validates and describes the wrong kind of thing.
The logo has requirements — dimensions and aspect ratio — and one that fails them is dropped from the output rather than flagged, which is why a site can have a logo configured and no logo in its structured data.
The social profiles that complete the entity are set separately, in seo/update-social-profiles.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
settings | object | Yes | A map of setting key to new value. Keys outside this area are refused. |
What comes back
| Name | Type | What it is |
|---|---|---|
updated | array | The keys that changed. |
settings | object | The area after the write. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Set the site to represent our organisation, with our logo.
It resolves to one call:
{
"ability": "seo/update-knowledge-graph",
"parameters": {
"settings": { "company_or_person": "company", "company_name": "Example Ltd" }
}
}Worth knowing
- Every other piece of structured data references this entity.
- A logo failing the size requirements is dropped silently.
- Person and Organization are genuinely different entities, not a label.
- Social profiles are set separately and complete the entity.
Related abilities
- Update Social Profile URLs — the sameAs links
- Get Configuration Status — whether this was ever finished
- Update Schema Defaults — what each content type claims to be
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category