Skip to content

Stop leading with llms.txt - #15

Merged
henry-mosh merged 1 commit into
mainfrom
copy/deemphasise-llms-txt
Sep 3, 2026
Merged

Stop leading with llms.txt#15
henry-mosh merged 1 commit into
mainfrom
copy/deemphasise-llms-txt

Conversation

@henry-mosh

Copy link
Copy Markdown
Collaborator

Summary

llms.txt stays a feature; it stops being a headline. CiteCue writes that file and the plugin serves it — the least of what the plugin does — and AI crawlers don't meaningfully read it. Every placement that presented it as a headline capability now names something the plugin actually decides at request time.

Five placements, in descending order of prominence:

Where Was Now
Directory banner eyebrow AI CRAWLERS · LLMS.TXT · METADATA AI CRAWLERS · SEO METADATA
Plugin header description "…adds enriched SEO metadata…, publishes your llms.txt, and lets CiteCue push…" llms.txt clause dropped
readme feature bullets a dedicated **llms.txt** bullet removed
readme "What the plugin actually does" opened by explaining llms.txt before reaching the live-request work opens on the live-request work
Settings screen intro "…publishes your llms.txt…" "…adds CiteCue's enriched metadata to your live pages…"

The plugin header line is the one with the widest reach — it's what wp-admin's plugin list renders under the name.

Deliberately untouched

  • External Services — must document every request the plugin makes; a directory review requirement
  • The verification FAQ — llms.txt is literally the thing being requested there
  • The settings toggle and status row — they govern the feature, which still exists
  • The changelog — history, not positioning

Banner note

The eyebrow drops to two terms rather than padding back to three. Both are true of what's published today, and neither promises anything unreleased — worth keeping in mind because assets/ can be pushed to SVN independently of the held 1.2.0 release, so the banner may go live against 1.1.2.

Regenerated with assets-src/build-assets.sh; both PNG sizes updated.

Verification

  • 382 tests green across core, WooCommerce-stub and multisite
  • phpcs and composer lint clean
  • Asset build asserts all four output dimensions

🤖 Generated with Claude Code

It is a real feature and it stays one, but it was carrying more weight in the
positioning than it earns: CiteCue writes that file and the plugin serves it,
which is the least of what this plugin does, and AI crawlers do not meaningfully
read it. Every placement that presented it as a headline capability now names
something the plugin actually decides at request time.

Five placements, in descending prominence: the directory banner's eyebrow, the
plugin header description (which is what wp-admin's plugin list shows), the
readme's feature bullets, the paragraph that opened by explaining llms.txt
before getting to the live-request work, and the settings screen's intro. The
banner eyebrow drops to two terms rather than padding to three — both true
today, and neither promising anything unreleased.

What is deliberately untouched: the External Services section, which must
document every request the plugin makes and is a directory review requirement;
the verification FAQ, where llms.txt is the thing being requested; the settings
toggle and status row, which govern the feature; and the changelog, which is
history.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@henry-mosh
henry-mosh merged commit c3b4fb5 into main Sep 3, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant