How it works — from your catalog to a published article

Generating PrestaShop blog articles in three steps is the promise. Here is what actually happens behind it, step by step — because a tool that touches your store deserves better than "it's magic".

Step 1 — Connect your store

You install the Publium module on your PrestaShop (any version from 1.6.1 to 9 — the detail per version is here). The module is a complete blog in its own right: categories, tags, RSS, sitemap, friendly URLs, structured data.

Then you create a licence key in the app and paste it into the module's configuration. Pairing is automatic: the module and the app exchange secrets that will sign every exchange between them (HMAC, timestamp, replay protection). One point that matters to agencies and cautious merchants alike: nobody needs your back-office credentials. The app only ever talks to the module, through a dedicated signed API.

As soon as the connection is up, the app synchronises your catalog: products, categories, CMS pages, images — and even the colours and fonts of your theme, from which it derives a design system reused later to dress the articles.

Step 2 — Pick a keyword

The app reads your catalog and suggests keywords: long-tail queries drawn from your products and categories, ranked by search intent and potential. You can bring your own too.

You choose a query, then frame the brief: language, tone, length, an imposed outline if you insist, and the catalog products to link to from the article. That brief is your steering wheel: the AI writes, but it writes what you framed.

Step 3 — Review, publish

Generation runs in the background (one to two minutes) and the article appears in your workspace: title, structured content, excerpt, title tag and meta description. Four output formats to choose from: raw Markdown, plain text, bare semantic HTML (no styling at all, for a theme that dresses everything itself), or HTML styled to your theme — the one detected in step 1, which you can adjust by hand from the store page.

You review, you correct what needs correcting (every version is kept, you can go back), then you publish: as a draft, immediately, or scheduled for the date you choose. The article travels to the module over the signed API and shows up on your store's blog, in your theme, with its structured data.

What about product descriptions?

The same circuit works for your catalog: the Products tab lists your synchronised items, and the AI writes the description, title tag and meta description around a target keyword — from the product data, or from its photo when the catalog is silent. Google result preview, character counters, optimisation checks, and publishing straight to the product page once you approve.

What if I only want to centralise the writing?

That's a supported use, and a more common one than you'd think: you already have a publishing route — an integrator, a CMS you'd rather drive by hand, a client who wants to approve before anything goes live — and what you're missing isn't a robot that publishes. It's one single place where the content gets made.

In that mode, you take the production and leave the publishing:

• Briefs and catalog in one place. Topics come out of your real products, not a blank page; target keyword, tone and products to link to all fit in a form.
• The SEO framing comes as standard. Title tag and meta description to spec, Google result preview before you approve, links to your product pages, structured data where the format allows. That's the work everyone forgets when writing in a word processor.
• The text leaves with you, in whichever format suits your chain: Markdown for a repository or a static site generator, plain text for any back office, bare HTML for a theme that styles everything itself, styled HTML to paste without touching it.
• The history stays. Every version is kept, your corrections included — you know what went out, and when.

In other words: automatic publishing is a convenience, not a condition of entry. And nothing stops you starting this way and wiring up publishing the day the back and forth starts to wear you out.

The questions we get at this stage

How long until it's running? Installing the module, pairing, and the first sync: under fifteen minutes on a standard store.

Do I need to know how to write a prompt? No. The brief is a form: keyword, tone, length, products. "Prompt engineering" is our job, not yours.

What happens if I stop? The blog and all your content stay in your store — they live with you, not with us. Only generation stops.

How often should I publish? Two to eight articles a month depending on your ambition. What matters is regularity, and scheduled publishing exists for exactly that.

The rest — quotas, languages, multi-store — is in the full FAQ. And if you'd rather judge for yourself, book a demo: we generate articles on your own store, in front of you. You'll know within the hour whether the tool suits you.