Operator Guide
Operator Guide: Every Tab Explained
This guide walks through every setting in the Rootz AI Discovery plugin. Each tab in your WordPress admin (Settings → AI Discovery) controls a different aspect of how AI agents see and interact with your site.
Tip: Every setting has an (i) icon next to it. Click or hover to see a plain-language explanation of what it does and how to set it.
Quick Start Tab
The Quick Start tab runs when you first activate the plugin. It auto-populates your AI Discovery settings by reading your existing WordPress content:
- Organization name pulled from your site title
- Domain detected automatically
- AI Summary generated from your About page or site description
- Core Concepts extracted from your most-used categories
- Policy pages auto-discovered (privacy, terms, GDPR, etc.)
You can re-run Quick Start at any time from the tab. It won’t overwrite fields you’ve already customized.
Identity Tab
This is how AI introduces your organization. Every field here appears in the /.well-known/ai manifest.
| Setting | What It Does | How to Set It |
|---|---|---|
| Organization Name | The name AI uses when referring to you | Your company or brand name |
| Legal Name | Registered business name for formal contexts | “Acme Corp, Inc.” — include the entity type |
| Domain | Auto-detected from WordPress | Usually leave as-is |
| Sector | Industry classification | e.g., “Healthcare”, “SaaS”, “E-commerce” |
| Tagline | One-line positioning statement | Your elevator pitch for AI |
| AI Summary | 2-3 sentence description for AI agents | What do you do, who do you serve, what makes you different? |
| Core Concepts | Glossary of terms specific to your business | Define industry jargon that AI might misunderstand |
| Contact Fields | Operator email, AI support, privacy contact | Separate from your public contact — these are for agent-to-operator communication |
Best practice: Write your AI Summary as if you were explaining your business to a new employee who knows nothing about your industry. Be specific. “We make software” is not useful. “We build compliance automation tools for mid-market healthcare providers” is.
Content Tab
Controls what content AI agents can access and how it’s formatted.
llms.txt Settings
| Setting | What It Does | Recommended |
|---|---|---|
| Enable llms.txt | Generates a concise, link-based overview at /llms.txt |
On (default) |
| Enable llms-full.txt | Generates full-content version with inline markdown | Off for small context windows, On for comprehensive access |
| Include Excerpts | Adds one-sentence descriptions under each page link in llms.txt | On — gives AI agents context without reading every page |
Limits
| Setting | Default | What It Controls |
|---|---|---|
| Pages Limit | 30 | Maximum pages in llms.txt. Set lower if you have many draft or utility pages. |
| Posts Limit (llms.txt) | 10 | Recent posts in the concise version. 10 is usually enough for a blog snapshot. |
| Posts Limit (llms-full) | 50 | Posts with full content inline. Watch your file size — 50 long posts can be very large. |
| Media Limit | 20 | Media items in the content endpoint. Includes EXIF data for images. |
Content Types
Choose which WordPress post types are included in AI-facing endpoints. Pages and Posts are enabled by default. You can add Custom Post Types if your theme or plugins use them (e.g., “Products” from WooCommerce, “Testimonials” from a review plugin).
Both llms.txt files are cryptographically signed with your plugin wallet. This is unique to Rootz — no other llms.txt plugin signs its output.
Policies Tab
Defines the rules AI agents must follow when using your content.
| Setting | What It Does |
|---|---|
| Content License | The license under which AI can use your content. Options: All Rights Reserved (most restrictive), CC-BY-4.0 (attribution required), CC0 (public domain), or custom. |
| Allow Quoting | Can AI agents quote excerpts from your content? “Yes” means an AI summarizing your blog can include direct quotes. |
| Allow Training | Can your content be used to train AI models? Most sites say “No.” This is the AI equivalent of robots.txt for training data. |
The plugin also auto-discovers your policy pages. It scans for privacy policies, terms of service, GDPR notices, cookie policies, AI usage policies, accessibility statements, and DMCA pages using 30+ common URL slug patterns. These appear automatically in the policies endpoint.
Why this matters: In our testing, 2 out of 3 major websites could not tell an AI agent whether quoting their content was allowed. This tab makes your answer explicit.
Tools Tab
Controls which AI tools are available on your site and whether WebMCP is enabled.
Your site offers 9 tools in 3 categories:
Discovery Tools (always on)
- getOrganizationInfo — Main identity manifest
- getPolicies — Content license and permissions
- getKnowledge — Organizational encyclopedia
- getFeed — AI-optimized blog feed
Action Tools
- searchContent — Full-text search with pagination
- getPage — Read any page as structured markdown
- verifyPageHash — Verify content integrity via SHA-256
Meta Tools
- getStatus — Self-scoring AI readiness report
- getContext — Plugin documentation for AI assistants helping with setup
WebMCP: When enabled, your site emits WebMCP-compatible tool definitions that Chrome 146+ browsers can register automatically. Visitors with AI-enabled browsers can use your tools without any additional setup.
Analytics Tab
Shows which AI agents visit your site, how often, and what they access.
- Traffic overview — Total AI requests in the last 24 hours and 7 days
- Agent breakdown — Which AI services are visiting (Claude, ChatGPT, Perplexity, Google, etc.)
- Top endpoints — Which tools are most used
Agents are classified by User-Agent string. The metrics table uses a custom WordPress database table for performance.
What AI Sees Tab
A live preview of your /.well-known/ai manifest as AI agents would see it. Use this to verify that your identity, pages, core concepts, and signature are all correct before going live.
The preview updates in real-time as you change settings on other tabs.
Account & Signing Tab
Manages your plugin wallet and cryptographic signing.
| Setting | What It Does |
|---|---|
| Wallet Address | Your plugin’s unique blockchain address (0x…). Auto-generated on first activation. This becomes your site’s digital identity for AI. |
| Signing Status | Shows whether ECDSA signing is active. Requires the PHP GMP extension. If GMP is unavailable, the plugin falls back to hash-only attestation (content hashes without signatures). |
| Re-sign Manifest | Button to regenerate the signed manifest after content changes. The plugin shows a notice when re-signing is needed. |
| Adoption Registry | Opt-in checkbox to share your domain with the AI Discovery Standard registry at rootz.global. Helps build the network of AI-ready sites. |
Troubleshooting
GMP Extension Not Installed
The plugin needs PHP’s GMP extension for ECDSA cryptographic signing. Without it, your endpoints still work but responses use hash-only attestation instead of full signatures.
Fix: Ask your hosting provider to enable php-gmp, or on Linux: sudo apt install php-gmp && sudo systemctl restart apache2
404 on /.well-known/ai
WordPress rewrite rules may need flushing. Go to Settings → Permalinks and click “Save Changes” (even without changing anything). This regenerates the .htaccess rules.
“No Wallet” Warning
The wallet generates automatically on plugin activation. If it shows “none,” try deactivating and reactivating the plugin. The wallet requires GMP for generation but the address is always displayable once created.
Score Below 50
Check the status endpoint (/wp-json/rootz/v1/status) for a category breakdown. Common missing items:
- Identity: Add Legal Name, Sector, and Tagline on the Identity tab
- Contacts: Add operator email and AI support email
- Content: Enable the Content endpoint on the Content tab
- Signing: Install GMP and re-sign the manifest
Content Changes Not Reflected
The plugin caches manifests and llms.txt for 1 hour. After making content changes:
- Go to the Account & Signing tab
- Click “Re-sign Manifest” to regenerate with fresh page hashes
- The cache clears automatically when you save settings or publish posts