Connect Magento to AltoRank

Magento authenticates with a admin bearer token that you create and can revoke yourself. Connecting it makes Magento an available destination — it does not give AltoRank permission to publish. That still takes a person approving the draft.

What you will need

Base URL
Your Magento install URL including https://
Admin token
The access token from an integration you activate
Store code
Optional
For multi-store installs. Left empty, the default store is used

Setup

  1. 1 Create the credential in Magento

    Go to Magento admin → System → Integrations. AltoRank never asks for your Magento login: you create a scoped credential there and paste it here, so revoking our access later is one click on your side and does not change how you sign in.

  2. 2 Add the connection in AltoRank

    In your workspace, open Integrations, choose Magento, and fill in base url, admin token. The connection is tested before it saves, so a wrong value fails here rather than silently at publish time.

  3. 3 Approve an article

    Nothing publishes on connection. Open a draft, read the fact-check verdict, and approve it. Only then does AltoRank call Magento. You can also turn on automatic publishing for the workspace, which ships after a hold you can veto; either way there is no agent route around the approval.

What approving does in Magento

On approve
Creates a CMS page (not a blog post: Magento has no blog without an extension) with the slug as its URL key, active, and the meta description set. It is reachable at /{slug} at once.
On unpublish
Deletes the CMS page.

Worth knowing

  • The integration has to be activated after it is created, or the token exists but authorises nothing.

The adapter behind this page is apps/web/lib/cms/magento.ts . If this page and that file disagree, the file is right and the page has a bug.

Common questions

Does AltoRank publish to Magento automatically?

Only after a person approves the specific draft. Connecting Magento removes the copy-and-paste step; it does not hand over the decision. The publish path requires an approval recorded under a person, by click or by the rule they set, and the MCP server exposes no publish tool, so this holds even when an AI agent is driving the product.

What Magento credentials does AltoRank need?

Base URL, Admin token, Store code (optional). Admin bearer token. Nothing else, and never your Magento account password.

Can I publish to Magento as a draft instead of live?

Not from AltoRank: the review happens here, before anything is sent, so approving is the act of publishing. On approve, Creates a CMS page (not a blog post: Magento has no blog without an extension) with the slug as its URL key, active, and the meta description set. It is reachable at /{slug} at once. If you want a staging destination, connect Notion as well and approve there first. Unpublishing is available afterwards: Deletes the CMS page.

Can I revoke access without breaking my site?

Yes. The credential is created in Magento and revoked there, independently of your login. Revoking it stops AltoRank publishing and changes nothing else. Articles already published stay where they are: they are ordinary content on your platform, not embeds pointed at us.

Can I use Magento on the self-hosted version?

Yes. Self-hosting is the same product under an open-source licence with no feature gates, so every connector works and your credentials never leave your own infrastructure. The adapter is apps/web/lib/cms/magento.ts in the repository.

Be the site the assistant names.

Add a domain and the first draft is written while you watch. Every publish is your decision, a click on the draft or a rule you set and can hold, and you can read the source or self-host it free.

Add a domain, it sets up your workspace