Add agent discovery headers and Content-Signal to robots.txt - #1160
Merged
marco-s merged 6 commits intoAug 20, 2026
Merged
Conversation
Signed-off-by: Andrew Bringaze <abringaze@linuxfoundation.org>
LinuxAzzamean
force-pushed
the
agent-discovery-content-signals
branch
from
August 20, 2026 19:15
131c20b to
2f38980
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Adds agent-facing API discovery and AI content-use preferences.
Changes:
- Adds homepage API-catalog discovery headers.
- Serves an RFC 9727 API catalog.
- Adds Content Signals to
robots.txt.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
public/class-lfevents-public.php |
Adds the homepage discovery header. |
includes/class-lfevents.php |
Registers discovery and robots hooks. |
includes/class-lfevents-well-known.php |
Implements the API catalog endpoint. |
includes/class-lfevents-llms-txt.php |
Adds the Content-Signal directive. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+104
to
+107
| $sections['lfe_content_signal'] = array( | ||
| 'raw' => 'Content-Signal: ai-train=no, search=yes, ai-input=no' . "\n", | ||
| 'priority' => 900, | ||
| ); |
Per RFC 9264, link target objects only support defined members like title, not an arbitrary description field. This keeps the same text but represents it correctly so the document conforms to the declared RFC 9727 profile. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Andrew B. <137023659+LinuxAzzamean@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.
Suppressed comments (1)
web/wp-content/mu-plugins/custom/lfevents/includes/class-lfevents-llms-txt.php:107
- This section emits the directive without a
User-agentdeclaration. The SEO Framework appends raw sections after its generated groups, so the signal can be associated with whichever bot-specific group precedes it (or treated as orphaned) rather than applying to all agents. Emit a complete wildcard group so the intended site-wide policy has deterministic scope.
$sections['lfe_content_signal'] = array(
'raw' => 'Content-Signal: ai-train=no, search=yes, ai-input=no' . "\n",
'priority' => 900,
);
per Copilot suggestion Signed-off-by: Marco Schmoecker <dsw@gmx.net>
Clean up edit Signed-off-by: Marco Schmoecker <dsw@gmx.net>
Signed-off-by: Andrew Bringaze <abringaze@linuxfoundation.org>
Signed-off-by: Andrew Bringaze <abringaze@linuxfoundation.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal 1: Link headers for agent discovery
Adds a Link: </.well-known/api-catalog>; rel="api-catalog" header on the homepage
Adds a /.well-known/api-catalog endpoint (RFC 9727 Linkset format) so the header resolves to a real document instead of a 404
Goal 2: Content Signals in robots.txt
Adds Content-Signal: ai-train=no, search=yes, ai-input=no via the existing the_seo_framework_robots_txt_sections filter, alongside the current llms.txt pointer
Tested against dev (dev-lfeventsci.pantheonsite.io), all four checks (homepage headers, robots.txt, api-catalog endpoint) confirmed working.