How it works, from catalog to published article

Generating PrestaShop blog articles in three steps is the promise. Here is what actually happens behind it.

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 license key in the app and paste it into the module's configuration. Pairing is automatic: the module and the app swap secrets that sign every call between them (HMAC, timestamp, replay protection). Nobody needs your back-office credentials, which matters to agencies and cautious merchants alike.

The app then syncs your catalog: products, categories, CMS pages, images, and the colors and fonts of your theme, from which it derives the design system used to dress the articles.

Step 2: pick a keyword

The app reads your catalog and suggests keywords: long-tail queries drawn from your own 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. 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: raw Markdown, plain text, bare semantic HTML for a theme that styles everything itself, or HTML styled to the theme detected in step 1, adjustable by hand from the store page.

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

What about product descriptions?

Same circuit. The Products tab lists your synced items, and the AI writes the description, title tag and meta description around a target keyword, from the product data or from the photo when the catalog is silent. Google result preview, character counters, optimization checks, and publishing straight to the product page once you approve.

What if I only want to centralize the writing?

That's a supported use, and more common than you'd think. You already have a publishing route (an integrator, a CMS you drive by hand, a client who approves before anything goes live); what you're missing is one place where the content gets made. You take the production and leave the publishing:

• Briefs and catalog sit in one place. Topics come out of your real products rather than a blank page, and keyword, tone and products to link to 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 is the work everyone forgets 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 as is.
• The history stays: every version, your corrections included, so you know what went out and when.

Automatic publishing is a convenience, not a condition of entry. Start this way and wire up publishing the day the back and forth wears you out.

The questions we get at this stage

How long until it's running? The module installs in under five minutes, then pairing and the first sync.

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. Only generation stops.

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

The rest (quotas, languages, multi-store) is in the full FAQ, and the prices are on the pricing page.