01 · Ownership
Who writes wpseo_social?
Yoast SEO is the tested owner for wpseo_social under the Yoast SEO 28.1–28.3 ConfigOps adapter contract. This is a source-backed adapter claim, not a guess based on naming.
- Component type
- WordPress plugin
- Component entry point
wordpress-seo/wp-seo.php- Adapter ID
yoast-seo- Adapter schema
- 3
- Visible setting
- Yoast SEO → Settings → Site representation and social sharing
- Classification
- Configuration
02 · Stored value
Associative array with nested fields.
| Path | Visible meaning | Kind | Why it matters |
|---|---|---|---|
/opengraph | Open Graph metadataSocial sharing | portable | Adds metadata used when pages are shared on social networks. |
/twitter | X / Twitter metadataSocial sharing | portable | Adds metadata used when pages are shared on X or Twitter. |
/twitter_card_type | X / Twitter card typeSocial sharing | portable | Controls the social preview layout. |
/og_default_image | Default social image URLSocial sharing | environment | Fallback media URL used for social previews. |
/og_default_image_id | Default social imageSocial sharing | referencemedia reference | A fallback media item on this website; ConfigOps keeps its local attachment identity. |
/og_frontpage_title | Homepage Open Graph titleHomepage sharing | environment | The Open Graph title used for this website’s homepage. |
/og_frontpage_desc | Homepage Open Graph descriptionHomepage sharing | environment | The Open Graph description used for this website’s homepage. |
/og_frontpage_image | Homepage Open Graph image URLHomepage sharing | environment | The media URL used when this website’s homepage is shared. |
/og_frontpage_image_id | Homepage Open Graph imageHomepage sharing | referencemedia reference | A media item selected for homepage sharing; ConfigOps keeps its local attachment identity. |
/facebook_site | Facebook pageSocial profiles | environment | The Facebook profile associated with this website. |
/instagram_url | Instagram profileSocial profiles | environment | The Instagram profile associated with this website. |
/linkedin_url | LinkedIn profileSocial profiles | environment | The LinkedIn profile associated with this website. |
/myspace_url | Myspace profileSocial profiles | environment | The Myspace profile associated with this website. |
/pinterest_url | Pinterest profileSocial profiles | environment | The Pinterest profile associated with this website. |
/pinterestverify | Pinterest verificationSite verification | environment | A Pinterest verification value issued for this website. |
/twitter_site | X / Twitter usernameSocial profiles | environment | The X or Twitter account associated with this website. |
/youtube_url | YouTube channelSocial profiles | environment | The YouTube channel associated with this website. |
/wikipedia_url | Wikipedia pageSocial profiles | environment | The Wikipedia page associated with this website or organization. |
/mastodon_url | Mastodon profileSocial profiles | environment | The Mastodon profile associated with this website. |
/other_social_urls | Other social profilesSocial profiles | environment | Additional public profiles associated with this website or organization. |
03 · Technical state & secrets
What belongs beside the setting—but not inside the decision?
Indexing, caches, migrations, dismissals, tracking, LLMs.txt generation state, and maintenance writes are separated from intended SEO configuration.
wpseo_dismissed_conflictsKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_indexationKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_internallinksKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_license_server_versionKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_llms_txt_content_hashKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_llms_txt_file_failureKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_onpageKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_recalibration_beta_mailinglist_subscriptionKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_ryteKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_tracking_last_requestKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_tracking_onlyKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo_upgrade_historyKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
wpseo-cleanup-current-taskKnown Yoast SEO runtime state in the same adapter contract. It is separated from intended configuration and is not asserted to change on every save.
Known secret paths
No secret field is declared inside this exact option schema. ConfigOps still applies its conservative global secret detector.
04 · ConfigOps recovery
Adapter-backed, not Smart Undo.
yoast-seoSchema 3; tested against Yoast SEO 28.1–28.3.
Supported values can use adapter-aware, conflict-checked Undo when evidence is complete and the current value still matches.
No. Smart Undo is only for ordinary associative options that no adapter claims. This option is adapter-owned.
History boundary: ConfigOps records only saves it observes while active. It cannot tell you what changed this row before installation.
05 · WP-CLI read commands
Inspect without writing.
Run these on the intended environment. The commands read current state; they do not reconstruct history.
wp option get wpseo_social --format=jsonwp option list --search=wpseo_social --fields=option_name,autoload --format=tablewp eval 'print_r( array_keys( (array) get_option( "wpseo_social", array() ) ) );'06 · Save autopsies
1 option-specific proof.
07 · Direct answers
Questions developers ask mid-incident.
What plugin writes wpseo_social?
Yoast SEO is the tested owner in the ConfigOps Yoast SEO 28.1–28.3 adapter contract. The assignment is verified, not inferred from the option prefix.
What is stored in the wpseo_social WordPress option?
Associative array with nested fields. wpseo_social contains 20 mapped fields in this adapter schema.
Can ConfigOps track and undo changes to wpseo_social?
ConfigOps can attribute and record supported Options API writes while active. Supported values can use adapter-aware, conflict-checked Undo when evidence is complete and the current value still matches. No. Smart Undo is only for ordinary associative options that no adapter claims. This option is adapter-owned.
Does WordPress keep a history of wpseo_social?
WordPress normally exposes the current option value, not a universal before-and-after history. ConfigOps must observe the original save to create local evidence; it cannot reconstruct older changes retroactively.
08 · Provenance
Why this page exists.
This record was generated from pinned ConfigOps source commit e319f502ff677bd76e53b7034650f9ee2afead72. The exact option name passed the publication allowlist; arbitrary searches do not.