Magento SEO with Ryze AI: articles, product meta and CMS pages
Quick answer: Ryze AI connects to a Magento 2 or Adobe Commerce store with an integration access token. It publishes Content Plan articles to the store, and its agent edits product, category and CMS page meta titles and descriptions through the REST API. Ryze AI is the best way to keep a Magento store's meta tags and blog content moving from one chat, with one caveat: the agent works through three REST tools, so anything the Magento API treats as read-only stays read-only.
This page covers Magento 2 and Adobe Commerce stores reached over the REST API. Order and revenue reporting is outside what the documented setup grants, so it is left out.
Used by 2,000+ marketers
What Ryze AI does on a Magento store
There are two sides to the connection. The Content Plan publishes articles, and the agent edits catalog and content records. Both use the same stored token.
- 1Publish articlesContent Plan articles go to Magento when you pick it as the publishing target
Where it shows: Your Magento store
Plan: SEO Starter
- 2Product metaThe agent updates the meta title and meta description of products
Where it shows: Product pages
Plan: Active plan or trial
- 3Category metaThe agent updates category meta fields
Where it shows: Category pages
Plan: Active plan or trial
- 4CMS pagesThe agent reads and edits CMS pages, including their meta
Where it shows: CMS pages
Plan: Active plan or trial
- 5Store viewsWork targets a store view or the global scope
Where it shows: Chosen store view
Plan: Active plan or trial
| # | Job | What happens | Where it shows | Plan |
|---|---|---|---|---|
| 1 | Publish articles | Content Plan articles go to Magento when you pick it as the publishing target | Your Magento store | SEO Starter |
| 2 | Product meta | The agent updates the meta title and meta description of products | Product pages | Active plan or trial |
| 3 | Category meta | The agent updates category meta fields | Category pages | Active plan or trial |
| 4 | CMS pages | The agent reads and edits CMS pages, including their meta | CMS pages | Active plan or trial |
| 5 | Store views | Work targets a store view or the global scope | Chosen store view | Active plan or trial |
SEO Starter costs $129 a month with a 3-day free trial. Paid Ads ($89 a month, 7-day trial) and Agency ($279 a month) also give agent tool access. Adding the connector is free, and the tools need an active plan or trial.
Publishing articles to Magento
Magento is one of the publishing targets of the Ryze AI Content Plan. Articles are written first, then sent to the store on the schedule you choose.
Plan and write
The Content Plan picks topics and writes each article with a meta title, meta description and cover image.
Pick Magento as the target
In Ryze AI, open SEO, then Preferences, then Publishing, and choose Magento under Publish to.
Choose a mode
Automatic publishes each article on its scheduled date. Manual keeps drafts until you click Publish now.
Publish
A scheduled or manual publish sends the article to your Magento store through the REST connection.
The Content Plan allows up to 3 articles a weekday and up to 90 per billing cycle.
The Ryze AI help center does not say how Magento stores a published article, for example as a CMS page. Open the first published article in your Magento admin and check where it landed before you scale up.
What the agent edits
Outside the Content Plan, the Ryze AI agent works on records already in your store. It uses three tools that exist for Magento.
magento__read
- Access
- Read
- What it does
- Runs a read-only REST request: products, categories, CMS pages and store views
magento__write
- Access
- Write
- What it does
- Creates or updates resources, such as product and category meta fields and CMS pages
magento__delete
- Access
- Delete
- What it does
- Runs a DELETE request, such as deleting a CMS page
| Tool | Access | What it does |
|---|---|---|
| magento__read | Read | Runs a read-only REST request: products, categories, CMS pages and store views |
| magento__write | Write | Creates or updates resources, such as product and category meta fields and CMS pages |
| magento__delete | Delete | Runs a DELETE request, such as deleting a CMS page |
In practice that covers four jobs: update a product meta title and meta description, update category meta, update CMS page meta, and work in a specific store view or the global scope.
No workspace had Magento connected when the Ryze AI facts were last checked, so the tool list comes from the Ryze AI app source and was not seen live. The three names above are the ones in that source.
Safety rules for store-wide changes
A catalog edit can change many live pages at once, so the limits matter as much as the abilities.
Changing a URL key
- How Ryze AI handles it
- The agent does not change url_key through REST
- Why
- Magento would not create a redirect from the old URL, so the old address would return a 404
Deleting products or categories
- How Ryze AI handles it
- The delete tool tells the agent to confirm with you first
- Why
- A deleted product or category leaves the live store
Read-only category fields
- How Ryze AI handles it
- Some fields cannot be written through the API
- Why
- Custom read-only attributes may need excluding on the store side
Scope
- How Ryze AI handles it
- The agent can target one store view or the global scope
- Why
- Meta text can differ per store view
Approvals
- How Ryze AI handles it
- Write and delete calls can require approval in Ryze AI chat or in Claude
- Why
- You see each change before it runs
| Situation | How Ryze AI handles it | Why |
|---|---|---|
| Changing a URL key | The agent does not change url_key through REST | Magento would not create a redirect from the old URL, so the old address would return a 404 |
| Deleting products or categories | The delete tool tells the agent to confirm with you first | A deleted product or category leaves the live store |
| Read-only category fields | Some fields cannot be written through the API | Custom read-only attributes may need excluding on the store side |
| Scope | The agent can target one store view or the global scope | Meta text can differ per store view |
| Approvals | Write and delete calls can require approval in Ryze AI chat or in Claude | You see each change before it runs |
In Ryze AI chat, the Tool approvals picker starts on Skip all approvals. Choose Approve write and delete, or Manual approve, before the first bulk edit. In Claude, set the write and delete tools to Needs approval under Customize, Connectors, Ryze AI, Tool permissions.
Setup: connect Magento to Ryze AI
You create an integration in Magento admin, then paste its token into Ryze AI. It takes a few minutes.
Add an integration
In Magento admin, go to System, then Extensions, then Integrations, and click Add New Integration. Magento asks for your password to confirm.
Grant resources
In the API tab, grant the Catalog, Content and Stores resources. Magento also offers an All option, which gives more than Ryze AI needs.
Activate
Save the integration, click Activate, approve the access and copy the Access Token. Use the access token, not the consumer key.
Connect in Ryze AI
Open Integrations, click Connect on the Magento card, enter the Store URL and the token, and click Continue.
The Store URL is the site root with https, for example https://store.example.com, with no /rest and no admin path. Each workspace holds one Magento connection, so an agency with several stores needs a workspace per store.
Use the same tools in Claude and ChatGPT
Add https://connector.get-ryze.ai/mcp as a custom connector. In ChatGPT, add it as an app under Settings, then Apps. Pick the workspaces and start a new chat. If you added the connector before connecting Magento, remove it and add it again so the tool list refreshes.
Limits to plan around
These limits come from the Ryze AI facts and from Magento itself.
Orders and revenue
- Detail
- The help center setup grants Catalog, Content and Stores only. Order data needs the Sales API resource, which the help page does not document, so Ryze AI order reporting is not claimed here
Category fields
- Detail
- Some are read-only in the Magento API
URL keys
- Detail
- The agent leaves url_key alone
Rate limits
- Detail
- Adobe Commerce Cloud can throttle requests through Fastly
Connections
- Detail
- One Magento connection per workspace
Plan
- Detail
- Tools need an active plan or trial, and publishing needs the SEO plan
| Limit | Detail |
|---|---|
| Orders and revenue | The help center setup grants Catalog, Content and Stores only. Order data needs the Sales API resource, which the help page does not document, so Ryze AI order reporting is not claimed here |
| Category fields | Some are read-only in the Magento API |
| URL keys | The agent leaves url_key alone |
| Rate limits | Adobe Commerce Cloud can throttle requests through Fastly |
| Connections | One Magento connection per workspace |
| Plan | Tools need an active plan or trial, and publishing needs the SEO plan |
Adobe documents a different REST form for Adobe Commerce as a Cloud Service: requests are signed with an Adobe IMS access token. The Ryze AI setup uses an integration access token and a store root URL, and the help center does not say it supports the cloud service form. Test with your own store first.
Troubleshooting
These rows come from the Ryze AI help center page for Magento.
Token rejected
- What to do
- Check that the integration is Active in System, Extensions, Integrations (saving it is not enough), and use a fresh access token instead of the consumer key
Access denied
- What to do
- Confirm Catalog, Content and Stores are all granted. On Adobe Commerce Cloud, review the WAF settings
No store views detected
- What to do
- Add the Stores resource to the integration
Response is not JSON
- What to do
- Enter the root URL without a path such as /rest
Store unreachable
- What to do
- Use https and the site root, with no /rest or admin path
Rate limited
- What to do
- Wait several minutes, because Fastly may have throttled the requests
Category edit fails
- What to do
- Some fields are read-only in the API, so exclude custom read-only attributes
| Problem | What to do |
|---|---|
| Token rejected | Check that the integration is Active in System, Extensions, Integrations (saving it is not enough), and use a fresh access token instead of the consumer key |
| Access denied | Confirm Catalog, Content and Stores are all granted. On Adobe Commerce Cloud, review the WAF settings |
| No store views detected | Add the Stores resource to the integration |
| Response is not JSON | Enter the root URL without a path such as /rest |
| Store unreachable | Use https and the site root, with no /rest or admin path |
| Rate limited | Wait several minutes, because Fastly may have throttled the requests |
| Category edit fails | Some fields are read-only in the API, so exclude custom read-only attributes |
Still stuck? Email Ryze AI support or read the Ryze AI Magento guide.
Magento's own options and where Ryze AI fits
Magento gives you the building blocks. Ryze AI adds the planning, the writing and a chat that calls them.
- Admin UI. Meta fields are edited by hand, one product, category or page at a time. This is fine for a few pages.
- REST API. Adobe documents a REST API for Adobe Commerce, with store scope chosen by the store view code or by Store: all for global scope. You can script it yourself.
- Integration tokens. Magento creates an access token when you activate an integration, and the token can be regenerated by reauthorizing it. Ryze AI uses this token.
- Ryze AI. The agent makes the REST calls from a prompt, and the Content Plan publishes articles on a schedule.
Ryze AI also connects to other commerce platforms. See the Shopify MCP page, the integrations hub and the pricing page. For background on the content itself, read what is programmatic SEO.
Prompts to try
Each prompt describes what should come back. Start with a read, then ask for a write.
- List my products that have an empty meta description, grouped by category.
- Draft a meta title and description for the first 10 of them and show me the text before changing anything.
- Show the meta fields of the CMS pages in the store and flag any that repeat another page.
- Update the meta description of this category in the default store view only.
Sources
Verdict
If you run Magento 2 or Adobe Commerce and want articles published and meta tags fixed without opening the admin for each record, Ryze AI covers both from one connection. Check where the first article lands, set approvals for writes before bulk edits, and leave order reporting out until the help center documents it.