Description
Laudia Connect is the companion plugin for Laudia, the AI search visibility service. After you approve a fix in your Laudia dashboard, Laudia publishes it to your site through this plugin’s small REST surface:
- JSON-LD schema and an FAQ block, printed in your site’s head. Theme-independent and reversible.
- A virtual llms.txt served at
/llms.txt. No file is written to your server. - Additive robots.txt lines (
Sitemap:,Allow:) appended to the robots.txt WordPress generates. The plugin refuses anyDisallow:orNoindex:line, so it can never block a crawler. If a physical robots.txt file exists, the plugin reports that honestly instead of pretending to deploy.
Readable by your own AI tools
The plugin registers its two READ-ONLY operations with the WordPress Abilities API (WordPress 6.9 and later), so the AI tooling on your own site can answer “is Laudia connected?” and “what has Laudia published here?” without you opening a dashboard. Publishing is not offered as an ability, and cannot be: an agent on your site can read what Laudia published, never add to it.
Deliberate non-goals: the plugin writes no files, edits no themes, manages no users, and has no settings screen. Everything it serves lives in four options rows and is removed when you delete the plugin.
Least-privilege access
The plugin registers a dedicated Laudia Connect role carrying only its own capability (plus read). You create one user with that role and issue a WordPress Application Password for it. Laudia refuses to operate with an administrator account.
Every REST request must carry that capability. All content is pinned by hash: the plugin recomputes the checksum of every payload and refuses a mismatch.
Installation
- Install and activate the plugin.
- Create a new user (for example
laudia-connect) with the Laudia Connect role. - On that user’s profile, create an Application Password.
- In your Laudia dashboard, connect your site with the username and Application Password.
FAQ
-
What can Laudia change on my site?
-
Only the five artifacts above (schema, FAQ, llms.txt, additive robots lines, and your homepage meta description), and only after you approve the exact content in your dashboard. The plugin refuses everything else.
-
Does deactivating the plugin delete anything?
-
No. Deactivation only stops serving; the role and stored content are kept. Deleting the plugin removes its options and the role.
-
Can an AI agent change my site through this plugin?
-
No. The two abilities the plugin registers with WordPress are read-only, and the publishing route is not exposed to them. Content still reaches your site only through the approval step in your Laudia dashboard, over an authenticated connection you can revoke. Calling either ability requires the Laudia Connect capability or an administrator account.
-
Can this block search engines or AI crawlers?
-
No. The robots surface is additive-only and the plugin rejects any
Disallow:orNoindex:line at the API and again at serve time.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Laudia Connect” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Laudia Connect” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.1.0
- Registers the plugin’s read-only surface with the WordPress Abilities API (6.9+), so AI tooling on your site can read the connection status and the published content. Publishing is deliberately not exposed: an agent can read what Laudia published, never publish.
- Tested against WordPress 7.1.
1.0.2
- Adds the meta-description artifact: Laudia can now publish the business description you confirmed as your homepage meta description. Front page only, so per-page descriptions set by an SEO plugin are left alone.
1.0.1
- Packaging fix: the distributed archive is now a valid zip (the 1.0.0 download was mispackaged).
1.0.0
- Initial release: the laudia/v1 REST surface (status, artifacts), JSON-LD head embeds, virtual /llms.txt, additive robots.txt filter, dedicated minimal role.