Verified option record · updated 2026-08-25

`wpseo_llmstxt`

Configuration

wpseo_llmstxt is owned by Yoast SEO in the tested Yoast SEO 28.1–28.3 ConfigOps contract. It is a structured option with 7 exact mapped fields in adapter schema 3.

Tested owner: Yoast SEOTested ConfigOps adapter assignment
Version contract: Yoast SEO 28.1–28.3Adapter schema 3
Stored shape: Associative array with nested fields7 mapped fields
ConfigOps recovery: Conditional UndoCurrent-state check required

01 · Ownership

Who writes `wpseo_llmstxt`?

Yoast SEO is the tested owner for wpseo_llmstxt 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
Classification: Configuration

02 · Stored value

Associative array with nested fields.

Mapped paths7

Secret paths0

Field kinds2

Exact fields mapped by ConfigOps adapter schema 3
Path	Visible meaning	Kind	Why it matters
`/llms_txt_selection_mode`	LLMs.txt page selectionAI discovery	portable	Controls whether pages are selected automatically or manually.
`/about_us_page`	About pageAI discovery	referencecontent reference	A page included in this website’s LLMs.txt file.
`/contact_page`	Contact pageAI discovery	referencecontent reference	A page included in this website’s LLMs.txt file.
`/terms_page`	Terms pageAI discovery	referencecontent reference	A page included in this website’s LLMs.txt file.
`/privacy_policy_page`	Privacy policy pageAI discovery	referencecontent reference	A page included in this website’s LLMs.txt file.
`/shop_page`	Shop pageAI discovery	referencecontent reference	A page included in this website’s LLMs.txt file.
`/other_included_pages`	Other included pagesAI discovery	referencecontent reference	Additional pages included in this website’s LLMs.txt file.

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_conflicts

Known 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_indexation

Known 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_internallinks

Known 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_version

Known 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_hash

Known 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_failure

Known 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_onpage

Known 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_subscription

Known 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_ryte

Known 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_request

Known 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_only

Known 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_history

Known 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-task

Known 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.

ConfigOps adapterYes · yoast-seo

Schema 3; tested against Yoast SEO 28.1–28.3.

Adapter-aware UndoConditionally supported

Supported values can use adapter-aware, conflict-checked Undo when evidence is complete and the current value still matches.

Smart Undo eligibilityNo

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.

Read the current value

wp option get wpseo_llmstxt --format=json

Inspect matching storage and autoload metadata

wp option list --search=wpseo_llmstxt --fields=option_name,autoload --format=table

List top-level keys without changing the value

wp eval 'print_r( array_keys( (array) get_option( "wpseo_llmstxt", array() ) ) );'

06 · Save autopsies

No option-specific autopsy published yet.

Contract coverage is not a save autopsy.

The owner and field map are verified by the adapter source, but this Atlas record does not claim an option-specific browser or integration save trace.

07 · Direct answers

Questions developers ask mid-incident.

What plugin writes wpseo_llmstxt?

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_llmstxt WordPress option?

Associative array with nested fields. wpseo_llmstxt contains 7 mapped fields in this adapter schema.

Can ConfigOps track and undo changes to wpseo_llmstxt?

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_llmstxt?

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.