tdainat01

SBG AI Layer gives your WordPress site a lightweight AI discovery layer using machine-readable endpoints and structured outputs.
The free version focuses on foundational discovery and indexing support so AI systems, search tools, and language models can better interpret your site.
Features include:
<ul>
<li>AI discovery endpoint</li>
<li>LLM index output</li>
<li>llms.txt support</li>
<li>AI sitemap output</li>
<li>Entities output</li>
<li>Knowledge graph output</li>
<li>Lightweight admin interface</li>
</ul>
The plugin works on its own and does not require an external service in the free version.
SBG AI Layer Pro is available separately for sites that need advanced AI enrichment, remote analysis, automation, and expanded optimization features.

SBG AI Layer

SBG AI Layer adds AI discovery endpoints and machine-readable structured outputs to help modern crawlers understand your WordPress site.

Matthias Pfefferle

This plugin enables “Well-Known URIs” support for WordPress (RFC 5785: http://tools.ietf.org/html/rfc5785).
From the RFC:
It is increasingly common for Web-based protocols to require the 
 discovery of policy or other information about a host (“site-wide 
 metadata”) before making a request. For example, the Robots 
 Exclusion Protocol <a href="http://www.robotstxt.org/" rel="nofollow ugc">http://www.robotstxt.org/</a> specifies a way for 
 automated processes to obtain permission to access resources; 
 likewise, the Platform for Privacy Preferences 
 tells user-agents how to discover privacy policy beforehand.
While there are several ways to access per-resource metadata (e.g., 
 HTTP headers, WebDAV’s PROPFIND [RFC4918]), the perceived overhead 
 (either in terms of client-perceived latency and/or deployment 
 difficulties) associated with them often precludes their use in these 
 scenarios.
When this happens, it is common to designate a “well-known location” 
 for such data, so that it can be easily located. However, this 
 approach has the drawback of risking collisions, both with other such 
 designated “well-known locations” and with pre-existing resources.
To address this, this memo defines a path prefix in HTTP(S) URIs for 
 these “well-known locations”, “/.well-known/”. Future specifications 
 that need to define a resource for such site-wide metadata can 
 register their use to avoid collisions and minimise impingement upon 
 sites’ URI space.

/.well-known/

This plugin enables "Well-Known URIs" support for WordPress

SBG AI Layer vs /.well-known/