AI Project Showcase: SEO Assistant with LLM

Section 1 — Product Overview

1.1 Product name and tagline

Name: SEO Assistant with LLM
Tagline: Generate SEO-optimized focus keyphrases and meta descriptions using AI
Current status: Version 1.0.0 — functional WordPress plugin supporting three LLM providers
First commit / project start: Pre-migration commit March 27, 2026 (e65fdaf2); file creation dates not available

1.2 What it is

SEO Assistant with LLM is a WordPress plugin that generates AI-powered SEO recommendations — specifically focus keyphrases and meta descriptions — for any post or page. It works across all three major WordPress editing experiences (Classic Editor, Gutenberg Block Editor, and Elementor) by injecting a “Generate SEO” button into each editor’s toolbar. When triggered, the plugin sends the page title and body content alongside a built-in SEO best practices knowledge base to a user-selected LLM (OpenAI, Anthropic, or Google), and presents recommendations in a modal overlay with one-click copy functionality.

1.3 What makes it meaningfully different

• Triple-editor support: Works in Classic, Gutenberg, and Elementor — most SEO plugins only support one or two
• Multi-provider AI: Supports OpenAI (GPT-4o family), Anthropic (Claude Sonnet/Haiku), and Google (Gemini) from a single settings page
• Editable knowledge base: Ships with a comprehensive SEO best practices document (~2000+ words) that administrators can customize through a WordPress editor interface
• ITI Workflow Adapter integration: When the ITI Shared Library is present, Anthropic requests can route through n8n for centralized orchestration

1.4 Platform and deployment context

Platform: WordPress plugin
Deployment: Self-hosted WordPress (5.0+, PHP 7.4+)
Primary interface: In-editor button → modal popup with results and copy buttons

---

Section 2 — User Needs and Problem Statement

2.1 Target user

Primary user: WordPress site owners and content creators who need SEO optimization but lack SEO expertise
Secondary users: Elementor-based site builders
User environment: WordPress admin dashboard (post/page editor)

2.2 The problem being solved

Creating effective SEO focus keyphrases and meta descriptions requires specialized knowledge that most content creators don’t have. Existing SEO plugins (Yoast, Rank Math) tell you what’s wrong but don’t generate recommendations. This plugin generates the actual recommended keyphrase and meta description using AI, applying SEO best practices automatically.

2.3 Unmet needs this addresses

Need	How the product addresses it	Source of evidence
SEO guidance without expertise	AI generates recommendations using embedded best practices KB	class-seo-assistant-api.php prepare_prompt()
Editor-agnostic workflow	Separate JS integrations for Classic, Gutenberg, and Elementor	classic-editor.js, gutenberg-editor.js, elementor-editor.js
Provider flexibility	Three AI providers with configurable model selection	class-seo-assistant-settings.php
Customizable SEO rules	Admin-editable knowledge base shipped with comprehensive defaults	class-seo-assistant-knowledge-base.php

2.4 What users were doing before this existed

Manually writing keyphrases and meta descriptions based on personal judgment, or using Yoast/Rank Math’s analysis tools that critique but don’t generate content. Some users used separate AI tools (ChatGPT) and copy-pasted results back into WordPress.

---

Section 3 — Market Context and Competitive Landscape

3.1 Market category

Primary category: WordPress SEO plugins with AI content generation
Market maturity: Established (SEO plugins) but emerging (AI-powered SEO recommendation) [CLAUDE NOTE: inferred]
Key dynamics: Yoast and Rank Math dominate WordPress SEO; AI-powered generation is a differentiator [CLAUDE NOTE: inferred]

3.2 Competitive landscape

Product / Company	Approach	Strengths	Key gap this project addresses	Source
⚡ Yoast SEO	Analysis + scoring	Market leader, comprehensive analysis	Doesn’t generate keyphrases or descriptions	General knowledge
⚡ Rank Math	Analysis + suggestions	Feature-rich, schema markup	AI features locked behind premium tier	General knowledge
⚡ All in One SEO	Analysis + sitemap	Beginner-friendly	No AI generation in free tier	General knowledge
⚡ SEOPress	Lightweight analysis	Performance-focused	No AI content generation	General knowledge

3.3 Market positioning

Focused AI generation tool that complements (not replaces) existing SEO analysis plugins. Lightweight, single-purpose, multi-provider, and works across all WordPress editors. [CLAUDE NOTE: inferred]

3.4 Defensibility assessment

Limited defensibility as a standalone plugin — the concept is straightforward. Value comes from the curated knowledge base, triple-editor support, multi-provider architecture, and ITI ecosystem integration. The n8n adapter path provides enterprise-grade orchestration when deployed with the ITI stack. [CLAUDE NOTE: inferred]

---

Section 4 — Requirements Framing

4.1 How requirements were approached

Requirements were documented in a single Requirements.md file using a hierarchical bullet format. The spec is concise (12 lines) and covers the complete product scope.

4.2 Core requirements

1. WordPress plugin supporting Classic, Gutenberg, and Elementor editors
2. Generate recommended SEO focus keyphrase and meta description per post/page
3. Action triggered by button in editor toolbar
4. Send headline + body + knowledge base hints to LLM as context
5. Recommendations based on SEO best practices
6. Editable SEO best practices knowledge base through admin dashboard
7. Results displayed in modal popup with copy functionality
8. Administrator settings for LLM provider and API key selection
9. Deliverable as downloadable .zip file

4.3 Constraints and non-goals

Hard constraints: WordPress 5.0+, PHP 7.4+ (per README)
Explicit non-goals: NOT FOUND — add manually

4.4 Key design decisions and their rationale

Decision	Alternatives considered	Rationale	Evidence source
Multi-provider (OpenAI + Anthropic + Google)	Single provider	Flexibility; no vendor lock-in	class-seo-assistant-settings.php
Editable knowledge base in WordPress	Hard-coded prompts	Admin customization without code changes	Requirements.md line 8
Modal popup for results	Sidebar panel, inline insertion	Non-intrusive, universal across editors	Requirements.md line 10
JSON-only output contract	Free-form text	Reliable parsing for keyphrase + description	class-seo-assistant-api.php
Body truncation to 4000 chars	Full content	Token budget management	class-seo-assistant-api.php prepare_prompt()

---

Section 5 — Knowledge System Architecture

5.1 Knowledge system overview

KB type: Editable text document stored as WordPress option (seo_assistant_knowledge_base)
Location in repo: includes/class-seo-assistant-knowledge-base.php (default content in get_default_content())
Estimated size: ~2000+ words of SEO best practices (shipped default)

5.2 Knowledge system structure

The knowledge base is a single document (not a file tree) stored in the WordPress wp_options table. Default content covers:

SEO Best Practices Knowledge Base (default)
├── Focus Keyphrase Guidelines
│   ├── Length: 2-5 words
│   ├── Specificity rules
│   └── Intent matching
├── Meta Description Guidelines
│   ├── Length: 150-160 characters
│   ├── Formulas and patterns
│   └── Compelling copy rules
├── Content-Type Specific Guidelines
├── Quality Checklist (10 items)
├── Five Worked Examples
└── Notes for AI Generation (10 bullets)

5.3 Knowledge categories

Category	Files / format	Purpose	Update frequency
SEO best practices	Single WordPress option (HTML/Markdown)	Injected into every LLM request as context	Admin-editable at any time

5.4 How the knowledge system was built

The default knowledge base was authored as part of the plugin development, containing comprehensive SEO best practices, formulas for meta descriptions, content-type-specific guidelines, a quality checklist, and five worked examples. It ships as a PHP heredoc string and is stored in WordPress options on plugin activation. Administrators can edit it through a TinyMCE editor in the admin dashboard.

5.5 System prompt and agent configuration

System prompt approach: Single prompt constructed in prepare_prompt() — instructs the model as an “SEO expert” with:

• Task: analyze title + body content
• Constraints: keyphrase 2–5 words, meta description 150–160 chars
• Context: full knowledge base text injected as “SEO BEST PRACTICES:”
• Content: “CONTENT TO ANALYZE:” with title + body (truncated to 4000 chars)
• Output contract: JSON only — {"focus_keyphrase":"...","meta_description":"..."}

Key behavioural guardrails: JSON-only output enforcement (parsed via regex)
Persona / tone configuration: “SEO expert” role instruction
Tool use / function calling: None — single-turn generation only

---

Section 6 — Build Methodology

6.1 Development approach

AI-assisted development using Cursor IDE. The plugin was built to spec from the 12-line Requirements.md document. The architecture follows standard WordPress plugin patterns (singleton, hooks, AJAX).

6.2 Build phases

Phase	Approximate timeframe	What was built	Key commits or milestones
Initial build	Pre-Mar 2026	Complete v1.0.0 plugin with all three editor integrations	Files in repository
Pre-migration commit	Mar 27, 2026	Full workspace committed to ITI monorepo	e65fdaf2
Chat/API handler updates	Mar 31, 2026	Updates to chat and API handlers	69ea8003

6.3 Claude Code / AI-assisted development patterns

• Plugin scaffolded via AI-assisted development in Cursor
• Multi-editor JS integration generated with editor-specific API knowledge
• SEO knowledge base content generated and curated via AI
• Default content includes worked examples written by AI

6.4 Key technical challenges and how they were resolved

Challenge	How resolved	Evidence
Triple-editor integration	Separate JS files for Classic (jQuery), Gutenberg (wp-plugins API), and Elementor (panel API)	Three dedicated JS files in assets/js/
JSON extraction from LLM output	Regex-based extraction: /\{[^\}]"focus_keyphrase"[^\}]\}/s	class-seo-assistant-api.php process_response()
Multi-provider API differences	Provider switch with separate HTTP call logic and response parsing per provider	class-seo-assistant-api.php call_*_api() methods
n8n adapter return format mismatch	When adapter returns text, raw text is returned without JSON parsing — may need normalization	class-seo-assistant-api.php Anthropic path [CLAUDE NOTE: potential issue noted]

---

Section 7 — AI Tools and Techniques

7.1 AI models and APIs used

Model / API	Provider	Role in product	Integration method
GPT-4o	OpenAI	SEO recommendation generation (default option)	POST https://api.openai.com/v1/chat/completions
GPT-4o-mini	OpenAI	Lighter/cheaper alternative	Same endpoint
GPT-4-turbo	OpenAI	Higher-quality alternative	Same endpoint
GPT-3.5-turbo	OpenAI	Budget option	Same endpoint
Claude Sonnet 4.5 (claude-sonnet-4-5-20250929)	Anthropic	Default Anthropic model	POST https://api.anthropic.com/v1/messages
Claude Sonnet 4 (claude-sonnet-4-20250514)	Anthropic	Alternative	Same endpoint
Claude Haiku 4.5 (claude-haiku-4-5-20251001)	Anthropic	Lightweight option	Same endpoint
Claude 3.5 Sonnet (claude-3-5-sonnet-20241022)	Anthropic	Legacy option	Same endpoint
Gemini Pro	Google	Default Google model	Generative Language API
Gemini 2.0 Flash	Google	Fast alternative	Same endpoint
Gemini 1.5 Pro / Flash	Google	Additional options	Same endpoint
ITI Workflow Adapter (optional)	ITI / n8n	Anthropic requests routed through n8n when shared library present	ITI_Workflow_Adapter::run_agent('seo-assistant', ...)

7.2 AI orchestration and tooling

Tool	Category	Purpose
ITI Workflow Adapter (optional)	Orchestration	Routes Anthropic calls through n8n when ITI shared library is present
WordPress AJAX	Transport	Frontend-to-backend communication for generation requests

7.3 Prompting techniques used

• [x] Role assignment (“SEO expert”)
• [x] Knowledge base context injection (full editable KB prepended to prompt)
• [x] Structured JSON output contract
• [x] Content truncation for token budget management (4000 char body limit)
• [x] HTML stripping for clean content extraction
• [ ] Multi-turn conversation (not used — single-turn only)
• [ ] Chain-of-thought (not used)
• [ ] Tool/function calling (not used)

7.4 AI development tools used to build this

Tool	How used in build
Cursor IDE	Primary development — plugin code, JS integrations, knowledge base authoring

---

Section 8 — Version History and Evolution

8.1 Version timeline

Version / Phase	Date	Summary of changes	Significance
v1.0.0	Pre-Mar 2026	Initial release: three editors, three providers, editable KB, modal UI	Full feature set
API handler update	Mar 31, 2026	Chat and API handler updates across products	69ea8003

8.2 Notable pivots or scope changes

NOT FOUND — the product appears to have been built to spec from Requirements.md without significant pivots.

8.3 What has been cut or deferred

• Plugin URI and Author URI remain as placeholders (yourusername, yourwebsite.com)
• No automated testing found in the product directory
• AI Engine integration available as architecture pattern but not activated in this plugin

---

Section 9 — Product Artifacts

9.1 Design and UX artifacts

Artifact	Path	Type	What it shows
Admin CSS	assets/css/admin.css	Stylesheet	Full modal, spinner, results, copy buttons, responsive rules
Gutenberg panel	assets/js/gutenberg-editor.js	JS	DocumentSettingPanel “SEO Assistant” in block editor sidebar

9.2 Documentation artifacts

Document	Path	Type	Status
README.md	README.md	User documentation	Complete — install, configure, usage, FAQ, changelog
Requirements.md	Requirements.md	Product spec	Complete — 12-line hierarchical bullet spec

9.3 Data and output artifacts

Artifact	Path	Description
Default SEO knowledge base	includes/class-seo-assistant-knowledge-base.php (heredoc)	~2000+ word SEO best practices document
Nested plugin copy	seo-assistant-plugin/	Duplicate directory for zip packaging

---

Section 10 — Product Ideation Story

10.1 Origin of the idea

The plugin addresses a gap between SEO analysis tools (which tell you what’s wrong) and AI tools (which can generate content but aren’t integrated into the editor workflow). The requirement to support all three WordPress editor types (Classic, Gutenberg, Elementor) suggests targeting the broadest possible WordPress user base. [CLAUDE NOTE: inferred from Requirements.md and product design]

10.2 How the market was assessed

NOT FOUND — add manually. The product fills an obvious gap in the WordPress plugin ecosystem where SEO analysis exists but AI-powered generation is typically locked behind premium tiers.

10.3 The core product bet

That a lightweight, focused WordPress plugin for AI-generated SEO recommendations — working across all editors and supporting multiple AI providers — is more useful than adding AI features to a monolithic SEO plugin. [CLAUDE NOTE: inferred]

10.4 How the idea evolved

Requirements → single-purpose plugin → multi-editor support → multi-provider architecture → editable knowledge base → ITI ecosystem integration (Workflow Adapter).

---

Section 11 — Lessons and Next Steps

11.1 Current state assessment

What works well: Clean single-purpose architecture; triple-editor support; multi-provider flexibility; editable knowledge base with comprehensive defaults
Current limitations: Placeholder author/URI metadata; no automated tests; JSON extraction via regex (fragile); n8n adapter path may not fully normalize output for modal display
Estimated completeness: 85% — functional product, needs polish and testing [CLAUDE NOTE: inferred]

11.2 Visible next steps

1. Replace placeholder Plugin URI and Author fields
2. Add automated tests (PHPUnit, JS unit tests)
3. Fix potential n8n adapter output normalization
4. Harden JSON extraction (consider native JSON mode flags per provider)
5. Add support for bulk generation across multiple posts
6. Character count validation in meta description results

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 git log where available
• [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
README.md	Product description, features, installation, configuration, FAQ, changelog
Requirements.md	Original 12-line product specification
seo-assistant.php	Plugin header (v1.0.0), singleton bootstrap, AJAX handler, admin menu
includes/class-seo-assistant-api.php	Multi-provider API calls, prompt construction, JSON parsing, ITI Workflow Adapter path
includes/class-seo-assistant-settings.php	Provider/model configuration, available models list, test connection
includes/class-seo-assistant-knowledge-base.php	Default KB content (~2000+ words), CRUD methods
admin/settings-page.php	Settings UI with provider/model/key configuration
admin/knowledge-base-page.php	TinyMCE editor for KB, save/reset, tips
assets/js/admin.js	Modal UI, generation workflow, copy functionality, character counting
assets/js/classic-editor.js	Classic Editor toolbar button integration
assets/js/gutenberg-editor.js	Gutenberg DocumentSettingPanel registration
assets/js/elementor-editor.js	Elementor panel footer integration
assets/css/admin.css	Full UI styling
.gitignore	Standard WordPress/Node/env exclusions
Git log (2 path-specific commits)	Commit history

---

Addendum — April 2026 Competitive Landscape and Roadmap Update

1. Industry Context

The WordPress SEO plugin category sits at the center of two colliding forces: the vibe coding explosion and the convergence of frontier LLM capabilities. With 82% of developers now using or planning to use AI coding tools, and platforms like Bolt.new and Lovable enabling non-technical builders to ship functional applications in hours, the barrier to creating an “AI-powered SEO plugin” has dropped to near zero. Any developer — or motivated marketer with Cursor open — can build a plugin that sends content to Claude or GPT and returns a keyphrase and meta description. That’s essentially what SEO Assistant v1.0.0 does, and it’s no longer a differentiating capability.

The more significant shift is what’s happening to the AI models themselves. Claude 4, GPT-5, and Gemini 2.5 now score within 10% of each other on production tasks, and pricing has compressed dramatically (Gemini 2.5 offers roughly 80% of frontier capability at 8% of competitor cost). Multi-provider support — which SEO Assistant listed as a differentiator — is now a configuration toggle in most frameworks. The “uses AI” or “powered by Claude” positioning that worked in early 2025 has lost its force. When every competitor integrates the same models at similar cost, differentiation has to come from the domain expertise embedded in the product, the workflow integration, and the judgment about where AI helps versus where it misleads.

The third dynamic is the emergence of Generative Engine Optimization (GEO) as a distinct discipline from traditional SEO. Content optimization is no longer just about ranking in Google’s blue links — it’s about being cited by ChatGPT, Perplexity, and Google AI Overviews. Surfer SEO pivoted explicitly to “AI Search Guidelines” in early 2026, and Clearscope added AEO-specific content grading. This shift changes what an SEO plugin needs to do: it’s no longer enough to generate a good keyphrase and meta description. The plugin needs to evaluate whether content is structured for AI extraction — entity clarity, factual density, question-answer formatting, source citations. SEO Assistant doesn’t do any of that yet.

2. Competitive Landscape Changes

Since SEO Assistant v1.0.0 shipped, the competitive environment has changed materially:

Competitor	What Changed	Direct Impact
Rank Math	Content AI v2.0 with real-time NLP suggestions on free tier; AI Link Genius (v3.0.108, March 2026) for automated internal linking; llms.txt support and AI search traffic tracking	Our core keyphrase generation is now a free feature in Rank Math
Yoast SEO	AI Optimize button rewrites meta descriptions and titles via GPT (Premium, $99-119/year); AI-assisted internal linking workouts	Direct competition for our primary use case
AIOSEO	Full AI Suite (v4.9.4, Feb 2026) including AI content generator, FAQ blocks, social posts, E-E-A-T author profiles, and Writing Assistant via SEOBoost integration	Far broader AI scope than our single-feature generation
Surfer SEO	AI Search Guidelines for optimizing AI citation; Workspaces + Brand Kit per domain ($89-219/mo)	GEO/AEO capabilities we entirely lack
Clearscope	AEO optimization with content grading for AI platform citations ($129-399/mo)	Addresses the GEO shift we haven’t responded to
SEOPress	Now supports 5 AI providers	Matches our multi-provider approach

Eroded differentiators:

Feature We Claimed as Unique	Current Status
AI keyphrase generation	Available free in Rank Math, in Yoast Premium, and in AIOSEO AI Suite
AI meta description generation	Yoast AI Optimize, AIOSEO AI Content Generator, and Rank Math Content AI all do this
Multi-provider LLM support	SEOPress offers 5 providers
Editable knowledge base	Still somewhat unique — AIOSEO’s SEOBoost provides similar customization, but no competitor has our admin-editable KB approach

What remains ours:

• Triple-editor support (Classic + Gutenberg + Elementor) — most competitors focus on Gutenberg only
• ITI Workflow Adapter / n8n routing — no competitor routes AI calls through workflow orchestration
• Lightweight complementary positioning — works alongside Yoast/Rank Math rather than replacing them

3. Our Competitive Response: Product Roadmap

The roadmap is organized in four tiers, prioritized by competitive urgency.

Tier 1 (next build cycle) closes the gaps that matter most. AI SEO title generation (S effort) extends our existing prompt and modal to produce titles alongside keyphrases — minimal code change for a feature every competitor now has. Content SEO scoring (L) adds a 0-100 score against keyphrase usage, readability, heading structure, and meta completeness. GEO/AEO readiness scoring (L) is the strategic move: scoring content for AI citation likelihood — entity clarity, factual density, question-answer formatting, structured data presence. This cross-pollinates with the AEO Optimizer product, sharing scoring methodology rather than duplicating effort. Real-time keyword/NLP suggestions (L) responds directly to Rank Math Content AI v2.0. JSON extraction hardening (S) replaces our fragile regex parsing with provider-specific JSON mode flags.

Tier 2 builds on the scoring foundation. Internal linking suggestions (L) — Rank Math shipped AI Link Genius in March 2026 and we have nothing comparable. Section-level rewrite suggestions (L) go beyond scoring to generate specific, actionable improvements using Claude’s reasoning. Yoast/Rank Math integration (M) reads their existing SEO data and enhances it with AI generation, reinforcing the complement-not-replace positioning. Bulk generation (M) handles multiple posts from a dashboard view.

Tier 3 adds strategic differentiation: AI-powered schema recommendation and JSON-LD generation (L), iterative multi-turn refinement (M), E-E-A-T content guidance (M), content gap analysis via Claude (L), and SEO performance tracking (XL).

Tier 4 explores llms.txt generation, AI visibility monitoring, multi-language generation, content briefs, WordPress.com compatibility, and WooCommerce product SEO.

The sequencing logic: Tier 1 items come first because without content scoring and GEO readiness, we’re a single-feature plugin in a market where that feature is now free. Scoring is the prerequisite for everything downstream — internal linking, section rewrites, and schema all require content analysis infrastructure.

4. New Capabilities Added Since Last Build

Several Skills created as part of the April 2026 roadmap cycle are directly relevant to SEO Assistant’s development:

• generative-engine-optimization — GEO/AEO methodology covering content optimization for AI citation, entity clarity, factual density assessment, and llms.txt generation. This is the knowledge backbone for the Tier 1 GEO/AEO readiness scoring feature.
• answer-engine-optimization-strategy — Covers content structuring for AI extraction, E-E-A-T signal placement, LLMS.txt configuration, and AI crawler management. Complements the GEO skill with implementation strategy.
• wordpress-seo-plugin-integration — Integration patterns for reading from and writing to Yoast, Rank Math, AIOSEO, and SEOPress data stores. Directly enables the Tier 2 Yoast/Rank Math integration feature.
• schema-markup-generation — JSON-LD generation for FAQ, HowTo, Speakable, Article, Product, and Review schemas with WordPress integration patterns. Supports the Tier 3 schema recommendation feature.
• ai-citation-tracking — Monitoring content visibility across ChatGPT, Perplexity, and Google AI Overviews. Relevant to the Tier 4 AI visibility monitoring feature.
• seo-optimization (existing, updated) — Traditional SEO methodology that underpins the core keyphrase and meta description generation.

5. Honest Assessment

Current strengths: SEO Assistant does one thing and does it well within a clean, lightweight architecture. The triple-editor support (Classic, Gutenberg, Elementor) is genuinely rare. The editable knowledge base gives administrators control over the SEO best practices that inform generation. The n8n Workflow Adapter integration demonstrates enterprise-grade orchestration. And the complement-not-replace positioning is smart — users don’t want to rip out Yoast or Rank Math.

Acknowledged gaps: The product’s core feature — generating a keyphrase and meta description via AI — is now available for free in Rank Math and in Yoast Premium. We have no content scoring, no internal linking suggestions, no GEO/AEO readiness evaluation, no schema generation, no readability analysis, and no bulk capabilities. The JSON extraction via regex is fragile and needs hardening. The plugin is a v1.0.0 single-feature tool in a market that moved to multi-feature AI SEO suites in Q1 2026.

What we’re watching: The GEO/AEO shift is the most consequential market change. Whether content is “good for SEO” is increasingly secondary to whether content is structured for AI extraction and citation. We’re also watching the pricing compression in AI APIs — as model costs drop, the cost barrier to offering AI-powered features in free-tier plugins disappears, further commoditizing the generation capability.

This product demonstrates how we approach WordPress content optimization — with a focus on workflow integration across all editor types and a knowledge-base-driven architecture that can evolve as SEO best practices change. The roadmap reflects what we’ve learned about where the market moved while we built v1.0.0, and the shared Skills infrastructure means the next build cycle can move faster.