Three access modes
Choose open, answers-only or restricted behavior depending on your AI crawl strategy.
Products / LemonX AEO / AI Access
AI Search Visibility Crawler policyAI Access Control for WordPress inside WordPress.
AI Access gives WordPress teams a policy layer for AI crawler behavior. The plugin supports open, answers-only and restricted modes, applies effective access by site or content context, filters robots directives and can send policy headers.
AI Access visualized
Purpose-built SVG scene for this module.
Version OKPurpose-built SVG scene for this module.
Key features
LemonX AEO v1.0.0AI Access turns AEO signals into repeatable actions.
Every block below is based on a practical WordPress use case: review the signal, understand the evidence, improve the page, and monitor the next change.
Effective content policy
Resolve access at the content level so important source pages can behave differently from low-value pages.
Robots integration
Adjust robots directives to align with AI discovery and protection goals.
Policy headers
Send policy headers that make intended access clearer to compatible crawlers.
Citation strategy alignment
Use access settings together with llms.txt, AI Crawlers and citation monitoring.
Publishing safeguards
Help editors understand how new content will be exposed to AI crawlers.
Designed around the real WordPress admin workflow for AI Access.
WordPress scenario
Built for actual site operations, not just a dashboard mockup.
A documentation-heavy company wants AI systems to reference public docs but not low-quality archives or private-style landing pages. The operator sets the global policy, adjusts sensitive content, and verifies the effective mode before publishing.
Why it matters: AEO work becomes useful only when teams can turn answer visibility, content gaps, technical signals and integrations into WordPress actions.
- Choose a global AI access philosophy
- Map which content should be cite-worthy source material
- Set access mode and verify effective output
- Update robots and policy behavior
- Monitor AI crawler activity
Plugin data model
Page content is grounded in the actual AEO plugin structure.
Site mode, effective post mode, queried mode, robots filter output, policy headers, open / answers_only / restricted.
The page is written to match how a WordPress user would see and use the feature: inside the LemonX AEO admin menu, connected with related modules, and reported through the same AEO operating system.
| Capability | Operational value | Area |
|---|---|---|
| Three access modes | Choose open, answers-only or restricted behavior depending on your AI crawl strategy. | AI Search Visibility |
| Effective content policy | Resolve access at the content level so important source pages can behave differently from low-value pages. | AI Search Visibility |
| Robots integration | Adjust robots directives to align with AI discovery and protection goals. | AI Search Visibility |
| Policy headers | Send policy headers that make intended access clearer to compatible crawlers. | AI Search Visibility |
Recommended workflow
Use a consistent operating process.
The best AEO results come from a loop: define the opportunity, verify the signal, improve the page, submit or expose the URL, then measure change again.
01
Choose a global AI access philosophyThis step keeps the workflow repeatable inside WordPress and connected to LemonX AEO reporting.02
Map which content should be cite-worthy source materialThis step keeps the workflow repeatable inside WordPress and connected to LemonX AEO reporting.03
Set access mode and verify effective outputThis step keeps the workflow repeatable inside WordPress and connected to LemonX AEO reporting.04
Update robots and policy behaviorThis step keeps the workflow repeatable inside WordPress and connected to LemonX AEO reporting.05
Monitor AI crawler activityThis step keeps the workflow repeatable inside WordPress and connected to LemonX AEO reporting.06
Review citations and adjust page-level strategyThis step keeps the workflow repeatable inside WordPress and connected to LemonX AEO reporting.Use the page as a source asset: clear definitions, strong schema, internal links and current facts.
SEO and AEO best practices
Make the page easy to crawl, understand, cite and recommend.
For Google SEO, the page needs a clear title, focused H1, helpful headings, internal links, indexable content and structured data. For AEO, it also needs direct answers, entity consistency, source-worthy explanations, FAQs and a relationship with other trusted pages.
- Use one clear H1 and descriptive H2 sections aligned with real questions.
- Add FAQ structured data and breadcrumb structured data for machine-readable context.
- Connect related AEO modules with internal links so the topic cluster is obvious.
- Keep claims specific to what the plugin actually supports and avoid empty marketing language.
- Use SVG scenes to show the WordPress workflow rather than decorative icons.
FAQ
Questions users and AI systems should be able to answer from this page.
What are the AI Access modes?
The plugin supports open, answers_only and restricted modes.
Should every site be fully open?
Not always. Public source pages may benefit from openness, while thin archives, duplicate sections or sensitive content may need restrictions.
Does AI Access replace robots.txt?
No. It complements robots behavior with AEO-specific policy handling and headers.
How should I choose a mode?
Start from business goals: maximum discoverability, answer-only access, or stricter protection, then validate with crawler analytics.
Use AI Access as part of the full LemonX AEO workflow.
Connect this feature with Query Lab, AI Citations, AI Visibility, Content Optimizer, Schema Center, llms.txt, AI Crawlers and Reports to create a complete WordPress AEO operating system.