AEO Optimizer Product Showcase
AI Project Showcase: AEO Optimizer
Section 1 — Product Overview
1.1 Product name and tagline
Name: AEO Optimizer
Tagline: A WordPress plugin that scores and optimizes content for AI-powered answer engines — Google AI Overviews, Microsoft Copilot, ChatGPT, and Perplexity.
Current status: Live
First commit / project start: January 2026 (v1.0.0); current version 1.1.0 released January 2026
1.2 What it is
AEO Optimizer is a WordPress plugin that analyzes post and page content against eight Answer Engine Optimization dimensions and produces a 0–100 scorecard with actionable recommendations. It works inside both the Classic Editor and Gutenberg Block Editor, analyzing selected text or entire posts without sending any content to external servers. The plugin includes a customizable system prompt that codifies AEO best practices drawn from Google Search Central, Bing Webmaster Guidelines, and emerging AI-search research.
1.3 What makes it meaningfully different
Unlike traditional SEO plugins that focus on keyword density and meta tags for search-result-page rankings, AEO Optimizer focuses entirely on whether content is extractable by AI answer engines — whether it leads with direct answers, uses structured data patterns, demonstrates E-E-A-T signals, and maintains entity consistency. All analysis runs server-side on the WordPress host; no content leaves the site, addressing privacy concerns that limit adoption of cloud-based SEO tools.
1.4 Platform and deployment context
Platform: WordPress plugin (PHP)
Deployment: Self-hosted WordPress installation (5.8+, PHP 7.4+)
Primary interface: In-editor toolbar buttons (Classic + Gutenberg), popup scorecard dialog, admin settings page
Section 2 — User Needs and Problem Statement
2.1 Target user
Primary user: WordPress content creators, editors, and content strategists who publish long-form content
Secondary users: SEO managers evaluating content quality across teams
User environment: WordPress post/page editor during content creation and revision workflows
2.2 The problem being solved
Content creators need their articles to appear in AI-generated answer summaries (Google AI Overviews, Copilot, ChatGPT citations, Perplexity answers), but traditional SEO tools do not evaluate whether content is structured for AI extraction. Writers lack a feedback loop that tells them, in real time, whether their content follows answer-first structure, has proper E-E-A-T signals, and uses patterns that AI crawlers can parse.
2.3 Unmet needs this addresses
| Need | How the product addresses it | Source of evidence |
|---|---|---|
| Real-time AEO scoring during writing | Inline editor buttons analyze content and return an 8-dimension scorecard with 0–100 scoring | documentation/README.md, aeo-optimizer.php |
| Specific, actionable rewriting suggestions | Returns personalized heading rewrites, E-E-A-T template insertions, and structural fixes tied to actual content | documentation/cursor_aeo_optimizer_requirements.md |
| Privacy-first analysis (no data leaving the site) | All analysis runs server-side via WordPress AJAX; FAQ explicitly states no external communication | documentation/README.md FAQ section |
2.4 What users were doing before this existed
Content teams relied on general SEO plugins (Yoast, Rank Math) that score keyword density and readability but do not evaluate AI-extraction readiness. Some teams manually compared content against Google’s AEO documentation, a time-consuming process with no scoring consistency.
Section 3 — Market Context and Competitive Landscape
3.1 Market category
Primary category: WordPress content optimization / SEO tooling
Market maturity: Emerging (AEO-specific tooling is nascent as of early 2026)
Key dynamics: Google AI Overviews launched widely in 2024–2025, creating a new optimization surface. Traditional SEO vendors have not yet released dedicated AEO scoring modules. ⚡
3.2 Competitive landscape
| Product / Company | Approach | Strengths | Key gap this project addresses | Source |
|---|---|---|---|---|
| Yoast SEO ⚡ | Keyword-density and readability scoring in WP editor | Large user base, mature product | No AEO dimension scoring; does not evaluate answer-first structure or E-E-A-T signals | ⚡ Public product page |
| Rank Math ⚡ | SEO scoring with schema markup helpers | Good schema integration | Schema generation without content-structure scoring for AI extraction | ⚡ Public product page |
| Semrush / Ahrefs ⚡ | Cloud-based SEO suites with content graders | Comprehensive keyword and SERP tools | Cloud-only; content must be uploaded; no in-editor AEO scoring | ⚡ Public product page |
3.3 Market positioning
AEO Optimizer occupies the emerging space between traditional SEO plugins and AI-search readiness tools. It is the first WordPress-native plugin focused exclusively on optimizing content for AI answer engines, positioned as a complementary tool to existing SEO plugins rather than a replacement. [CLAUDE NOTE: inferred from product documentation; no explicit positioning statement found]
3.4 Defensibility assessment
The plugin’s defensibility rests on its deep AEO scoring taxonomy (8 dimensions derived from Google Search Central and AI-search research), its customizable system prompt architecture that allows the evaluation criteria to evolve as AI-search behavior changes, and its privacy-first, server-side-only approach. The knowledge embedded in the default prompt represents curated expertise that is non-trivial to replicate.
Section 4 — Requirements Framing
4.1 How requirements were approached
Requirements were defined through iterative Cursor AI sessions (exported January 9, 2026 in cursor_aeo_optimizer_requirements.md) and refined through documentation iterations. The eight AEO dimensions were derived from published AEO research and Google/Bing guidelines referenced in the system prompt.
4.2 Core requirements (what it must do)
- Analyze WordPress content against 8 AEO dimensions and produce a 0–100 score with color-coded ratings
- Provide specific, actionable suggestions tailored to the actual content (heading rewrites, E-E-A-T templates, structure improvements)
- Work in both Classic Editor and Block Editor (Gutenberg) with keyboard shortcuts and copy-results functionality
- Run entirely server-side with no external API calls — content never leaves the WordPress installation
- Provide administrator settings with a customizable system prompt for evaluation criteria
4.3 Constraints and non-goals
Hard constraints:
- WordPress 5.8+, PHP 7.4+
- Content size limit: 500KB maximum
- Analysis timeout: 60 seconds
- No impact on public-facing site performance
Explicit non-goals:
- Not a replacement for traditional SEO plugins (complementary tool)
- Not a content generator — analyzes and recommends, does not write
- No external server communication or cloud dependency
4.4 Key design decisions and their rationale
| Decision | Alternatives considered | Rationale | Evidence source |
|---|---|---|---|
| Server-side rule-based analysis (no LLM API calls) | Cloud LLM analysis via Claude API | Privacy: content never leaves the site; no API cost per analysis; works offline | CLAUDE.md mentions Claude integration but code confirms local analysis |
| 8-dimension scoring taxonomy | Simpler pass/fail or single-score model | Granularity helps writers understand which specific aspects need improvement | documentation/cursor_aeo_optimizer_requirements.md |
| Editable system prompt in admin settings | Hardcoded evaluation criteria | Allows criteria to evolve as AEO best practices change without plugin updates | aeo-optimizer.php settings page, includes/default-prompt.txt |
| Dual editor support (Classic + Gutenberg) | Gutenberg-only | WordPress ecosystem still has significant Classic Editor usage | documentation/README.md installation section |
Section 5 — Knowledge System Architecture
5.1 Knowledge system overview
KB type: Embedded system prompt (AEO evaluation criteria document)
Location in repo: includes/default-prompt.txt (289 lines), documentation/# AEO RECOMMENDATION TOOL - SYSTEM PROMP.md (318 lines, extended version)
Estimated size: ~12,000 tokens across both prompt documents
5.2 Knowledge system structure
includes/
└── default-prompt.txt # Core AEO evaluation criteria (289 lines)
documentation/
├── # AEO RECOMMENDATION TOOL - SYSTEM PROMP.md # Extended prompt with metrics section (318 lines)
├── README.md # Full user guide with AEO education (566 lines)
├── USER-GUIDE.md # Comprehensive guide (1,769 lines)
├── QUICK-START.md # 5-minute getting started (120 lines)
├── DOCUMENTATION-SUMMARY.md # Documentation overview (481 lines)
└── cursor_aeo_optimizer_requirements.md # Requirements export (99 lines)
5.3 Knowledge categories
| Category | Files / format | Purpose | Update frequency |
|---|---|---|---|
| AEO evaluation criteria | default-prompt.txt (.txt) |
Defines the 8 scoring dimensions, weighting, recommendation structure | Updated with each version |
| Extended metrics prompt | # AEO RECOMMENDATION TOOL - SYSTEM PROMP.md (.md) |
Adds KEY METRICS TO TRACK section and expanded final reminders | Supplementary to core prompt |
| User documentation | README.md, USER-GUIDE.md, QUICK-START.md (.md) |
End-user education on AEO concepts and plugin usage | Per release |
| Requirements specification | cursor_aeo_optimizer_requirements.md (.md) |
Original requirements from Cursor AI session | One-time capture (Jan 2026) |
5.4 How the knowledge system was built
The system prompt was developed by synthesizing published AEO guidelines from Google Search Central, Bing Webmaster Guidelines, Search Engine Journal, and Semrush research. It was iteratively refined through Cursor AI development sessions. The prompt defines 8 evaluation dimensions, each with specific scoring criteria, and a recommendation taxonomy (Priority Actions, Content Optimizations, Technical Requirements, Authority Building, What to Avoid).
5.5 System prompt and agent configuration
System prompt approach: A long-form evaluation criteria document stored in includes/default-prompt.txt, editable via Settings → AEO Optimizer. Defines the AEO consultant persona, 8 dimensions with scoring rubrics, and recommendation structure.
Key behavioural guardrails: Recommendations must be specific to the analyzed content (not generic); suggestions include actual heading rewrites and E-E-A-T text templates; scores must follow defined color-coding bands.
Persona / tone configuration: “Expert AEO consultant” persona defined in the system prompt, focused on actionable, educational guidance.
Tool use / function calling: None — the plugin uses server-side PHP regex/heuristic analysis, not LLM function calling. The system prompt is stored for reference/education but is not consumed by an LLM at runtime in the current architecture.
Section 6 — Build Methodology
6.1 Development approach
Developed using Cursor AI-assisted iterative sessions, with requirements captured in conversation exports. The plugin was built in a rapid two-version cycle: v1.0.0 established core analysis functionality, and v1.1.0 added Gutenberg support, keyboard shortcuts, enhanced CSS, and documentation.
6.2 Build phases
| Phase | Approximate timeframe | What was built | Key commits or milestones |
|---|---|---|---|
| v1.0.0 | January 2026 | Core 8-dimension analysis engine, Classic Editor integration, admin settings, system prompt | Initial release |
| v1.1.0 | January 2026 | Gutenberg Block Editor support, keyboard shortcuts, copy results, editor CSS, comprehensive documentation | Current release |
6.3 Claude Code / AI-assisted development patterns
Development was conducted primarily through Cursor AI sessions (exported January 9, 2026 from Cursor 2.3.29). The CLAUDE.md file provides project context for AI development tools including directory structure, feature overview, and links to ITI Shared Library components. Documentation was also generated through AI-assisted workflows.
6.4 Key technical challenges and how they were resolved
| Challenge | How resolved | Evidence |
|---|---|---|
| Supporting both Classic Editor and Gutenberg with consistent UX | Separate JavaScript files (editor.js for Classic, gutenberg.js for Gutenberg) with shared analysis AJAX endpoint |
assets/js/editor.js (853 lines), assets/js/gutenberg.js (645 lines) |
| Content extraction from Gutenberg block structure | Dedicated block content extraction logic in gutenberg.js that handles different block types |
assets/js/gutenberg.js |
| Analysis timeout for large content | 60-second timeout with 500KB content size limit; AJAX request with timeout handling | aeo-optimizer.php analyze_content() method |
Section 7 — AI Tools and Techniques
7.1 AI models and APIs used
| Model / API | Provider | Role in product | Integration method |
|---|---|---|---|
| None (rule-based) | N/A | Content analysis is performed via PHP regex/heuristic engine — no LLM API calls at runtime | Server-side PHP analyze_content() method |
Note: CLAUDE.md references Claude API, Tavily, and Pinecone as available ITI shared-library components, but the current codebase does not make runtime calls to any external AI API. The system prompt is stored and editable but serves as a reference document / evaluation criteria definition, not as an LLM system prompt.
7.2 AI orchestration and tooling
| Tool | Category | Purpose |
|---|---|---|
| Cursor AI | Development IDE | Primary development environment for iterative code generation |
| Claude (via Cursor) | AI pair programming | Code generation, requirements refinement, documentation writing |
7.3 Prompting techniques used
- [x] System prompt persona/role setting (AEO consultant persona in
default-prompt.txt— used as evaluation criteria reference) - [x] Structured / JSON output prompting (scoring structure defined in prompt)
- [ ] Chain-of-thought reasoning
- [ ] Few-shot examples in prompts
- [ ] Tool use / function calling
- [ ] RAG context injection
- [ ] Multi-turn conversation management
- [ ] Output guardrails / content filtering
- [ ] Fallback / error recovery prompting
7.4 AI development tools used to build this
| Tool | How used in build |
|---|---|
| Cursor | Primary development IDE; requirements sessions exported as documentation; iterative code generation for PHP, JS, CSS |
| Claude (via Cursor) | AI pair programming for plugin architecture, scoring logic, editor integration, and comprehensive documentation |
| Antigravity | Autonomous test execution, browser QA, visual regression testing — used per global CLAUDE.md tool lane |
Section 8 — Version History and Evolution
8.1 Version timeline
| Version / Phase | Date | Summary of changes | Significance |
|---|---|---|---|
| 1.0.0 | January 2026 | Initial release: 8-dimension AEO analysis, Classic Editor integration, admin settings, customizable system prompt | Foundation release with core scoring engine |
| 1.1.0 | January 2026 | Gutenberg Block Editor support, keyboard shortcuts (Ctrl/Cmd+Shift+A/S), copy results, enhanced editor CSS, comprehensive documentation suite | Full WordPress editor coverage; production-ready documentation |
8.2 Notable pivots or scope changes
The CLAUDE.md describes integration with Claude API for AI-powered recommendations, and references knowledgebase directories (disambiguations, guardrails, embeddings) that exist on disk but are empty. This suggests the product may have been initially scoped for LLM-powered analysis but was simplified to server-side rule-based analysis, with the knowledgebase scaffolding left in place for a future re-expansion. [CLAUDE NOTE: inferred from CLAUDE.md vs. actual code architecture]
8.3 What has been cut or deferred
- LLM-powered analysis via Claude API (referenced in CLAUDE.md but not implemented in
aeo-optimizer.php— nowp_remote_*calls to Anthropic/OpenAI) - Knowledgebase content for disambiguations, guardrails, and embeddings directories (directories exist under
knowledgebase/but are empty as of April 2026) - Marketing materials directory (
marketing/exists but is empty) - Plugin install pipeline contains a single
plugin-installs/aeo-optimizer.zipbut no automated build script is documented
Section 9 — Product Artifacts
9.1 Design and UX artifacts
| Artifact | Path | Type | What it shows |
|---|---|---|---|
| Editor CSS | assets/css/editor.css (884 lines) |
Stylesheet | Scorecard popup, progress bars, color-coded scores, recommendation categories |
| Admin CSS | assets/css/admin.css (205 lines) |
Stylesheet | Settings page layout and system prompt editor |
| VS Code theme | AEO Optimizer/.vscode/settings.json |
IDE config | Purple (#9015c1) brand color for development environment |
9.2 Documentation artifacts
| Document | Path | Type | Status |
|---|---|---|---|
| README | documentation/README.md (566 lines) |
User guide | Complete (v1.1.0) |
| User Guide | documentation/USER-GUIDE.md (1,769 lines) |
Comprehensive guide | Complete (v1.1.0) |
| Quick Start | documentation/QUICK-START.md (120 lines) |
Getting started | Complete |
| Documentation Summary | documentation/DOCUMENTATION-SUMMARY.md (481 lines) |
Overview | Complete (v1.1.0) |
| Requirements | documentation/cursor_aeo_optimizer_requirements.md (99 lines) |
Requirements capture | Complete (Jan 2026) |
| HTML exports | documentation/*.html (5 files) |
Web-ready docs | Complete |
9.3 Data and output artifacts
| Artifact | Path | Description |
|---|---|---|
| Default system prompt | includes/default-prompt.txt |
289-line AEO evaluation criteria document |
| Extended system prompt | documentation/# AEO RECOMMENDATION TOOL - SYSTEM PROMP.md |
318-line version with KEY METRICS TO TRACK section |
| O’Reilly Style Guide | documentation/O'Reilly Style Guide.html |
Editorial reference (not AEO-specific; supplementary) |
Section 10 — Product Ideation Story
10.1 Origin of the idea
AEO Optimizer was born from the observation that AI-powered answer engines (Google AI Overviews, Microsoft Copilot, ChatGPT, Perplexity) were rapidly changing how content gets discovered — but content creators had no tools to evaluate whether their content was optimized for AI extraction. Traditional SEO plugins focused on keyword rankings, not on the structural and credibility signals that AI systems use to select source content for answers. [CLAUDE NOTE: inferred from product documentation and system prompt context]
10.2 How the market was assessed
Research approach used: Analysis of published AEO guidelines from Google Search Central, Bing Webmaster Guidelines, Search Engine Journal, and Semrush; review of existing WordPress SEO plugin capabilities.
Key market observations:
- Google AI Overviews launched at scale, creating a new optimization surface that existing tools ignore
- No WordPress plugin offered dedicated AEO scoring — the gap was entirely unaddressed
- Content creators expressed confusion about how to optimize for AI answer engines vs. traditional search
What existing products got wrong:
Existing SEO tools treat AI-search optimization as an extension of keyword SEO rather than a fundamentally different content-structure challenge. They focus on meta tags and keyword density while ignoring answer-first structure, E-E-A-T signals, and entity consistency — the factors that determine whether AI systems extract and cite content.
10.3 The core product bet
If content creators get real-time, dimension-specific feedback on how well their content is structured for AI extraction, they will produce content that is more likely to be cited by answer engines — creating measurable value in a market where no competing WordPress tool exists.
10.4 How the idea evolved
The product started as a concept for LLM-powered content analysis (CLAUDE.md references Claude API integration) but was refined to use server-side rule-based scoring. This pivot preserved the privacy advantage (content never leaves the site), eliminated per-analysis API costs, and ensured the plugin works without external dependencies. The 8-dimension scoring taxonomy and recommendation structure were defined in a comprehensive system prompt document that serves as both the evaluation criteria and as exportable AEO education content. [CLAUDE NOTE: evolution from LLM to rule-based is inferred from CLAUDE.md vs. code discrepancy]
Section 11 — Lessons and Next Steps
11.1 Current state assessment
What works well: Complete 8-dimension scoring engine with specific recommendations; dual editor support (Classic + Gutenberg); privacy-first architecture; comprehensive documentation suite; keyboard shortcuts for power users.
Current limitations: No LLM-powered analysis (system prompt is stored but not consumed by an AI at runtime); knowledge system directories referenced in CLAUDE.md (embeddings, disambiguations, guardrails) exist but are empty; no automated testing suite visible in repo.
Estimated completeness: v1.1.0 — functional product with documentation; ~70% of CLAUDE.md’s described architecture implemented (knowledgebase scaffolding unpopulated).
11.2 Visible next steps
- Implement Claude API integration for LLM-powered analysis (bridging the gap between CLAUDE.md’s described architecture and current implementation)
- Build out the knowledgebase directories (disambiguations, guardrails, embeddings) for deeper analysis
- Create plugin-install ZIP packaging and distribution pipeline
- Add automated testing (PHPUnit for analysis logic)
- Develop marketing materials
11.3 Lessons learned
_Manual input required — this section cannot be populated automatically._
Section 12 — Claude Code Validation Checklist
- [x] Every placeholder has been replaced or marked NOT FOUND
- [x] All externally-sourced competitive data is marked with ⚡
- [x] All inferences are marked with [CLAUDE NOTE]
- [x] Version history is derived from actual documentation version references
- [x] Knowledge system paths reflect real directory structure
- [x] AI tools are confirmed from code/config, not guessed
- [x] Section 11.3 is left blank for manual input
- [x] Document header shows today’s date and files examined
Sources Examined
| File / Path | What it contributed |
|---|---|
CLAUDE.md |
Sections 1, 4, 5, 6, 7, 8 — project overview, directory structure, development context, shared library references |
CLAUDE.md.backup |
Section 8 — earlier version for comparison |
aeo-optimizer.php (1,305 lines) |
Sections 1, 4, 5, 7 — version numbers, analysis logic, AJAX endpoints, settings page |
includes/default-prompt.txt (289 lines) |
Section 5 — core evaluation criteria, 8 dimensions, recommendation taxonomy |
documentation/# AEO RECOMMENDATION TOOL - SYSTEM PROMP.md (318 lines) |
Section 5 — extended prompt with metrics tracking |
documentation/README.md (566 lines) |
Sections 1, 2, 3, 4, 8 — product description, AEO education, features, version history |
documentation/USER-GUIDE.md (1,769 lines) |
Section 9 — comprehensive documentation artifact |
documentation/QUICK-START.md (120 lines) |
Section 9 — getting-started documentation artifact |
documentation/DOCUMENTATION-SUMMARY.md (481 lines) |
Section 9 — documentation overview |
documentation/cursor_aeo_optimizer_requirements.md (99 lines) |
Section 4 — original requirements specification |
assets/js/editor.js (853 lines) |
Section 6 — Classic Editor integration |
assets/js/gutenberg.js (645 lines) |
Section 6 — Gutenberg integration |
assets/css/editor.css (884 lines) |
Section 9 — UI design artifact |
assets/css/admin.css (205 lines) |
Section 9 — admin UI artifact |
assets/js/admin.js (157 lines) |
Section 6 — admin settings JavaScript |
AEO Optimizer/.vscode/settings.json |
Section 9 — brand color / IDE config |
.gitignore |
Section 6 — project configuration |
Addendum — April 2026 Competitive Landscape and Roadmap Update
1. Industry Context
When AEO Optimizer shipped v1.1.0 in January 2026, Answer Engine Optimization was a nascent concept with no dedicated WordPress tooling. Three months later, the category has exploded. SE Ranking launched a dedicated AEO tracking tool. Surfer SEO shipped AI Tracker with citation monitoring across ChatGPT, AI Overviews, Perplexity, and Gemini at $95/month. Semrush added AI Visibility features with prompt-level insights. Two direct WordPress competitors — AnswerSEO and Answer Engine Optimization by Syed Tarikul Islam — appeared on WordPress.org. The market went from empty to contested while the product was at v1.1.0.
The vibe coding proliferation makes this category particularly vulnerable to commoditization. AEO Optimizer’s core functionality — analyzing content against scoring dimensions and producing recommendations — is exactly the kind of thing a motivated developer can build in a weekend with Cursor and a well-crafted prompt. The fact that two WordPress.org plugins already exist proves this. What’s harder to replicate is the 8-dimension scoring taxonomy derived from Google Search Central and Bing Webmaster Guidelines, the comprehensive 20,000-word user documentation, and the domain judgment about what actually makes content extractable by AI systems versus what merely looks well-formatted.
The LLM convergence dynamic creates both the product’s biggest opportunity and its most pressing problem. Claude 4, GPT-5, and Gemini 2.5 are all excellent at evaluating content quality — meaning the rule-based PHP regex/heuristic engine that currently powers AEO Optimizer is now its most significant limitation. Competitors like Surfer SEO and Frase use LLM-powered evaluation that understands context, nuance, and semantic relationships. AEO Optimizer’s system prompt was designed to be a Claude system prompt — the default-prompt.txt defines persona, scoring rubrics, and recommendation structure — but the LLM integration was never implemented. The Claude API client exists in the ITI Shared Library. Activating it is the single most important technical change for this product.
2. Competitive Landscape Changes
The competitive landscape shifted from “no WordPress AEO tools” to “multiple WordPress AEO tools plus enterprise SaaS” in three months.
New direct WordPress competitors:
| Competitor | Launched | Key Features |
|---|---|---|
| AnswerSEO (WordPress.org) | Oct 2025, updated Mar 2026 | 10-check AEO audit, FAQ/HowTo/Speakable schema generation, LLMS.txt management |
| Answer Engine Optimization (Syed Tarikul Islam, WordPress.org) | May 2025, updated Dec 2025 | Auto question detection, FAQ generation, structured data markup |
New SaaS competitors:
| Competitor | Launched | Key Features | Pricing |
|---|---|---|---|
| AEO Engine | 2025 | Full-service AEO: content creation, CMS publishing, Reddit/Quora seeding | $1,597/mo |
| Profound | 2025 | 10+ AI engine tracking, 400M+ prompt database, citation attribution | Enterprise |
| Otterly.AI | 2025 | GEO Audit (25+ factors), tracks 6 AI engines | $29/mo |
| AthenaHQ | 2025 | AI mention monitoring, sentiment analysis | SaaS |
Features competitors added (Jan–Apr 2026):
| Competitor | Feature | Impact |
|---|---|---|
| Surfer SEO | AI Tracker — citation tracking across ChatGPT, AI Overviews, Perplexity, Gemini ($95/mo add-on) | Sets user expectation for citation monitoring |
| Surfer SEO | Auto-Optimize — one-click entity/fact injection | Raises the bar for actionable optimization |
| Surfer SEO | Pre-Publish Review — readability, originality, AI-structure check | Directly competes with our pre-publish scoring |
| Semrush | AI Visibility suite — brand monitoring across ChatGPT, Gemini, AI Mode, AI Overviews | Enterprise citation tracking |
| Semrush | Prompt Research — discover AI prompts and topics for visibility | Capability no WordPress plugin offers |
| SE Ranking | Dedicated AEO Tool with competitor benchmarking and historical data | Mid-market AEO tracking |
| AnswerSEO (WP) | LLMS.txt generation and management; FAQ/HowTo/Speakable schema auto-generation | Features AEO Optimizer completely lacks |
| NeuronWriter | AEO content guide + semantic NLP scoring | Content optimization with explicit AEO awareness |
Eroded differentiators:
| Previous Differentiator | Current Status |
|---|---|
| “Only WordPress-native AEO plugin” | Eroded — AnswerSEO and Answer Engine Optimization now on WordPress.org |
| “8-dimension AEO scoring taxonomy” | Partially intact — no competitor matches the depth, but Otterly.AI offers 25+ factor GEO audits and AnswerSEO performs 10 checks |
| “Privacy-first, no external API calls” | Intact but double-edged — still unique, but competitors using LLMs deliver significantly richer recommendations |
| “Customizable evaluation criteria” | Intact — no WordPress competitor offers editable system prompts |
| “Comprehensive AEO education (20K-word guide)” | Intact — no competitor integrates this level of documentation |
3. Our Competitive Response: Product Roadmap
The roadmap’s central thesis: activate the dormant Claude API integration to transform AEO Optimizer from a pattern-matcher into a genuine AI analyst.
Tier 1 (next build cycle) has five items, prioritized by competitive urgency. Claude API integration for content analysis (L) is the most important change. The existing default-prompt.txt becomes the actual Claude system prompt, and the ITI Shared Library’s class-iti-claude-api.php handles the API calls. The plugin offers both modes: local-only (current regex/heuristic, privacy-first) and Claude-powered (richer analysis, requires API key). Schema markup generation (L) for FAQ, HowTo, Speakable, and Article JSON-LD — AnswerSEO already ships this. LLMS.txt file generation and management (M) — only 3.2% of websites have this file, making it an early-mover opportunity despite AnswerSEO offering it. AI crawler access controls (S) for managing GPTBot, PerplexityBot, and ClaudeBot directives. Score history and progress tracking (M) stores analysis results over time to demonstrate improvement.
The sequencing logic: Claude integration comes first because the regex/heuristic engine is the product’s ceiling. Without it, every feature downstream is limited to pattern-matching quality. Schema generation comes second because it’s the most visible parity gap with AnswerSEO. LLMS.txt and crawler controls address emerging AEO infrastructure needs. Score history provides the “before and after” evidence users need to justify continued use.
Tier 2 opens white-space differentiation: Claude-powered auto-rewrite suggestions with one-click accept (M), bulk site-wide content audit via wp_cron (L), WordPress-native AI citation tracker using Tavily (XL), content extractability preview showing exactly what an AI would extract (M), and Open Graph/social meta validation (S).
Tier 3 builds AI-native capabilities: competitive content comparison via Tavily + Claude (XL), Reddit/community citability scoring (M) — Reddit appears in 68% of AI responses — AI-answer simulation (L), multi-prompt variant testing (L), and personalized AEO coaching via chat (L).
Tier 4 explores entity graph visualization, knowledge base RAG integration, Gutenberg block-level scoring, WooCommerce product page AEO, multisite network dashboard, and REST API for headless CMS.
4. New Capabilities Added Since Last Build
These Skills from the April 2026 roadmap cycle are directly relevant to AEO Optimizer’s development:
- answer-engine-optimization-strategy — AEO methodology covering content structuring for AI extraction, E-E-A-T signal placement, entity consistency, LLMS.txt configuration, AI crawler management, and citation tracking. This is the strategic knowledge backbone for AEO Optimizer’s entire feature set — particularly the 8-dimension scoring taxonomy expansion and LLMS.txt management.
- generative-engine-optimization — GEO methodology covering content optimization for AI citation in ChatGPT, Google AI Overviews, and Perplexity. Complementary to the AEO strategy skill, focused on the content optimization techniques.
- ai-citation-tracking — Monitoring content visibility across AI answer engines using prompt-based tracking and competitive benchmarking. Directly supports the Tier 2 WordPress-native citation tracker.
- schema-markup-generation — JSON-LD generation for FAQ, HowTo, Speakable, Article, Product, and Review schemas with WordPress integration. Enables the Tier 1 schema generation feature.
- wordpress-seo-plugin-integration — Integration patterns for Yoast, Rank Math, AIOSEO, and SEOPress data stores. Enables AEO Optimizer to read existing SEO data as context for AEO analysis.
- content-gap-analysis — Methodology for identifying gaps in content coverage. Relevant to the competitive content comparison feature in Tier 3.
5. Honest Assessment
Current strengths: AEO Optimizer’s 8-dimension scoring taxonomy (Answer-First Structure, E-E-A-T Signals, Structured Data Readiness, Content Clarity, Originality, Technical Accessibility, Entity Consistency, Topic Authority) is the most granular AEO evaluation framework in any WordPress plugin. The privacy-first architecture — all analysis on the server, no content leaving the site — is a genuine advantage for organizations with data sensitivity requirements. The customizable system prompt lets administrators evolve evaluation criteria as AEO best practices change. The 20,000-word documentation suite is comprehensive enough to serve as AEO education, not just product documentation. And dual editor support (Classic + Gutenberg with keyboard shortcuts) covers the WordPress user base.
Acknowledged gaps: The product’s most significant limitation is that its system prompt — carefully designed to define AEO evaluation criteria for Claude — is not actually consumed by an LLM at runtime. The analysis runs on PHP regex and heuristics. This means the product cannot detect semantic issues, evaluate context-dependent quality, or generate specific rewrite suggestions. The knowledgebase directories (disambiguations, guardrails, embeddings) exist but are empty. There is no schema markup generation — AnswerSEO already ships this. No LLMS.txt management. No AI crawler controls. No score history tracking. No citation monitoring. No bulk auditing capability. The marketing materials directory is empty.
What we’re watching: The LLMS.txt adoption curve — currently at 3.2% of websites, with AI crawlers up 300%+ since January 2025. If LLMS.txt becomes as standard as robots.txt, every SEO/AEO plugin will need to manage it, and early movers will have an advantage. The pricing dynamics in AI citation tracking — Surfer charges $95/month, SE Ranking $129+/month, and Profound targets enterprise. If we can offer citation tracking within a WordPress plugin at plugin pricing, that’s a meaningful cost advantage. We’re also watching whether Google Search Central publishes explicit AEO guidelines — official guidance would validate the category and could reshape the scoring taxonomy.
This product demonstrates how we approach an emerging optimization category — with a structured scoring framework, comprehensive documentation, and honest acknowledgment that the initial rule-based approach needs to evolve to Claude-powered analysis. The system prompt architecture was designed for this upgrade; the implementation gap is the product’s most pressing strategic priority.
