Install
This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/danielk-am/alkamy-seo-agent-for-woocommerce/archive/refs/heads/main.zip
Draft product content, review SEO metadata, and record labelled AI-answer observations from your own API connection, inside WordPress.
For store teams who want help writing from their product facts, the plugin brings the draft into the place they already edit. You choose the provider and model, check the result, and control what is saved.
0.6.0 preview release. See release checks and testing limits before using it on a production store.
What you can do
| Your task | How the plugin helps |
|---|---|
| Write product search snippets | Draft a title and meta description from saved product facts, then review and explicitly save them. Revision checks reject stale saves. |
| Improve text where you edit | Configure up to 30 AI buttons for supported product, category and media fields. Give an optional instruction, generate into the field, and undo the latest generation. |
| Keep a repeatable record of model answers | Save questions, run observations, and retain labelled answers or failures. Optional daily runs use WordPress cron. |
| Work from an AI client | Expose 13 permission-checked WordPress abilities for compatible MCP clients through the WordPress MCP Adapter. |
Rank Math is optional. When active, reviewed metadata goes into its fields. Without a detected SEO plugin, Alkamy outputs its own product title and meta description. When a known competing SEO plugin is active, Alkamy disables metadata saves and output; copy drafts into that plugin instead. This is not a site-wide sitemap, redirect, schema, or indexing manager.
Requirements
- WordPress 6.6 or later, PHP 8.0 or later with OpenSSL, and active WooCommerce.
- An API token and model supporting OpenAI-compatible Chat Completions, at a public HTTPS endpoint reachable by WordPress. Provider charges apply.
- An administrator to configure the connection and buttons. Item editors need permission to edit the relevant product, category, or attachment.
- For MCP only: WordPress 6.9+ with its Abilities API, or a compatible Abilities API installation, plus an active compatible WordPress MCP Adapter. A numeric minimum Adapter version has not been established by this release's test matrix.
No n8n installation is required. The public plugin calls your configured API directly. A private connector is a separate, optional integration and is not included in this repository or required for BYOK use.
Install and make your first draft
- Install and activate WooCommerce. If migrating from Codex Bridge for Rank Math, deactivate that older plugin first; the shared namespace prevents both implementations from running together.
- Install the built plugin folder as
wp-content/plugins/alkamy-seo-agent-for-woocommerce, then activate it. A source checkout needs the build step below before installation. - Open WooCommerce → SEO/GEO Agent → Connection. Enter your provider's public HTTPS API base URL, model ID, and API token, then save.
- Test the saved connection. The test makes a small billable API request.
- Select a product in the SEO workflow, generate a draft, check every claim against your product facts, edit as needed, then save.
For example, begin with a product whose material, dimensions, and included parts are already recorded. Review whether the draft preserves those details. Remove any unsupported availability, delivery, or performance claim before saving.
AI buttons in editors
Open AI buttons to choose the label, target field, and prompt. {{context}} inserts saved item text, {{value}} inserts the current field, and {{instructions}} inserts the instructions supplied for that run. Reload open editors after saving the configuration.
| Editor surface | Supported fields | When generated text is saved |
|---|---|---|
| Classic WooCommerce product editor | Title, description, short description, purchase note | Use the normal Update button. |
| Existing product category's full edit screen | Name and description | Use the normal Update button. |
| Media Library attachment details | Title, alt text, caption, description | Applied changes save immediately through WordPress. |
Category creation, quick/bulk editing, and the newer WooCommerce product editor are outside the documented support scope. Prices, stock, identifiers, and arbitrary custom fields are excluded. The plugin does not generate images. Optional image input helps a vision-capable model draft media text; it does not verify product identity or specifications.
More screenshots
What GEO observations mean
GEO means generative engine optimisation. Here, it means drafting useful factual content and keeping samples of answers from your configured model. An observation can help you inspect whether that model mentions a brand or cites a domain for a question.
These samples do not measure consumer ChatGPT, Google AI Overviews, search rankings, search volume, or overall visibility. They cannot guarantee future mentions or citations. Provider and model changes can change results, and citation presence does not prove the source supports an answer.
The public API connection supports writing and observations with live search turned off. Verified live-search evidence requires a separate search-capable connector. A question can enable recurring paid calls; WordPress cron timing depends on your site's scheduling setup. Removing a question stops its schedule and retains history. Deactivation stops this plugin's cron hook; externally configured schedulers need separate management.
Data, credentials, and MCP
Generation sends the relevant prompt, item text, current field, and supplied facts to your configured provider. Optional media image input sends a local JPEG, PNG, or WebP preview of up to 2 MB. It is off by default. No order or customer-record collection is implemented by this plugin; avoid entering personal information in prompts or product text.
Tokens are encrypted in WordPress using the site's authentication salt and are not returned to the browser. Salt rotation requires re-entering the token. Changing the endpoint clears the previous token. Provider retention, charges, and terms apply separately. See data handling.
MCP discovery exposes drafting, reviewed metadata saves, question management, and observation operations. Every ability requires manage_options, with item permissions checked where relevant. Credentials and connection-setting mutations are not exposed. MCP field drafting returns text; it does not fill or save an open editor. See MCP setup and authority.
Development
Use a Node.js version supported by the pinned @wordpress/scripts package and npm, plus PHP 8.0+ for PHP checks. From this repository:
npm ci
npm run buildThe build produces the build/ JavaScript and asset manifests required by WordPress. Ship those files with the plugin; do not ship node_modules/, credentials, local configuration, or test-site content. See release checks for verification and contributing for a focused change workflow.
Support and security
For a reproducible bug, include plugin, WordPress, WooCommerce, PHP, and provider/model versions, the affected editor surface, and redacted steps. Never include an API token or private customer content. Follow security reporting guidance for sensitive findings.
See the changelog. Licensed under GPL-2.0-or-later.