Local AI Search readiness
Review robots.txt, sitemap, llms.txt, and eligible public content without turning the plugin into mandatory cloud onboarding.
WORDPRESS · WOOCOMMERCE · AI SEARCHBuilding · 0.5.0-dev
AI Search Optimizer
Prepare WordPress and WooCommerce for AI Search with a local-first workflow: analyze public signals, select content, generate deterministic llms.txt, and publish only when the administrator chooses to.
The current version is 0.5.0-dev. The code is public and verifiable, but it is not yet presented as a stable release or as available on WordPress.org.
WHAT IT DOES
AI Search readiness without turning the Free plugin into a trial.
Accepted local capabilities remain available without a Kairoseth account. External support is optional, explicit, and separate from the Free product.
Source-grounded llms.txt
Generate a deterministic proposal from selected public content and inspect exactly what will be published before any write occurs.
WordPress + WooCommerce
Include public WordPress content and supported public WooCommerce product awareness in the accepted local workflow.
Explicit, verifiable publishing
Compare before writing, avoid unnecessary changes, and verify the public result and its SHA-256 after publication.
Multisite isolation
Keep state and operations scoped per site so a Multisite installation does not mix context across tenants.
Optional Kairoseth support
The Free product works locally. Kairoseth receives bounded context only after an administrator explicitly starts a request.
LOCAL WORKFLOW
From public signals to a verifiable llms.txt in five steps.
The workflow prioritizes human control, determinism, compare-before-write behavior, and idempotence.
Analyze
Check public readiness signals and eligible site content.
Select
Choose which public content belongs in the proposal.
Preview
Review deterministic llms.txt output and its hash before publishing.
Publish
Write only after an explicit administrator action.
Verify
Read the public result back and confirm it matches the expected content.
PRIVACY AND CONTROL
No silent telemetry or automatic site-content sharing.
Loading the support surface does not contact Kairoseth. An external request starts only after an explicit click, automatic context is limited to bounded technical metadata, and the user chooses what additional information to send.
TRUST & CONTROL
Authority stays explicit as the platform grows.
Kairoseth separates identity, organization scope, product roles and product capabilities. A login route, browser state or AI response never becomes an authorization boundary by itself.
KAIROSETH PLATFORMCONTROL PLANE
- Identity
- Shared account
- Verified
- Organization
- Tenant scope
- Required
- Product
- RBAC assignment
- Explicit
- Sensitive actions
- Policy gate
- Controlled
Organization scope
Customer resources and access are resolved inside an active organization context rather than treated as global account state.
Product-scoped roles
Owner, Admin and Member authority is assigned per product. Organization membership alone does not automatically grant every product.
Server authority
Sensitive access, policy and capability decisions remain authoritative on the server instead of trusting client UI state or model output.
Controlled execution
Capabilities that can act are introduced behind explicit grants, staged gates and audit rather than implied autonomy.
Public trust evidence
Review the customer-facing policies that define privacy, security reporting, acceptable use and the current legal operating framework.
AI SEARCH OPTIMIZER
Public code today; stable release after its gates pass.
Extensions catalog integration does not change distribution status: 0.5.0-dev remains in development until release and WordPress.org gates are complete.