FAQ — every answer about Publium

Short answers to the questions we really get asked — with no commercial detours. If yours isn't here, write to us: it will probably end up here.

The module and the versions

What does the module do, and what does the licence unlock?

The module installs a complete blog in your PrestaShop — articles, categories, tags, RSS feed, sitemap, friendly URLs, SEO tags. The licence unlocks the advanced functions (SEO assistant, structured data, internal linking) and the connection to the generation app, which writes from your catalog. The blog and its content stay in your store, whatever happens.

Which PrestaShop versions are supported?

From 1.6.1 to 9, with the same module and the same functions. That isn't a slogan but an architectural constraint we impose on ourselves — the detail per version is here.

Does the module slow my store down?

No. The blog front end is standard PrestaShop (Smarty, theme cache), and the API is only ever called by your app, with strict rate limiting. No external script is loaded on your store.

Generation

Who writes: the AI or me?

The AI writes a full draft from your brief (keyword, tone, length, products to link to) and from your synchronised catalog. You review, correct, publish — every version is kept.

Does Google penalise generated content?

Google demotes useless content, not generated content. An article anchored in your catalog, reviewed and published at a regular rhythm ticks the boxes of the "Helpful Content" algorithm. Generic filler, AI or not, does not.

Which languages does the AI write in?

The languages of your store: the brief states the writing language, and publishing targets the right PrestaShop language. French and English are the most road-tested.

Can I impose an outline, a tone, instructions?

Yes — it's recommended. The brief accepts an imposed heading outline, a tone (professional, friendly, expert…), a target length and free-form instructions. The more precise the brief, the shorter the review.

How do product descriptions work?

The Products tab lists your synchronised catalog. For each item: a structured description, title tag (70 characters) and meta description (160), written around a target keyword, with a Google result preview. Two sources to choose from: the product data, or its photo when the item is empty — the case with imported catalogs.

Does publishing overwrite my existing text?

For product descriptions: yes, after your explicit approval — a dialog warns you before any replacement. For the blog: articles are created, never overwritten; an update from the app modifies the matching article.

Quotas and plans

How do quotas work?

Each plan includes a number of generations per month — articles and product descriptions each have their own counter. Plans scale with connected stores and generation volume. To scope a plan for your case, see our pricing page or book a demo.

What happens if I cancel?

Nothing dramatic: the blog, the articles and the rewritten descriptions stay in your store — the content lives with you, not with us. Only generation stops.

Security and access

Do you need access to my back office?

No, never. The app only communicates with the module, over a signed API (HMAC, timestamp, replay protection). That's the decisive argument for agencies running several client stores: zero passwords exchanged.

Where does my catalog data go?

The module exposes to the app the data needed for writing: products, categories, pages, images, theme stylesheets. It serves to generate your content, full stop. No reselling, no cross-referencing between stores.

Odds and ends

Are multilingual and multistore setups handled?

Yes for multilingual (the module's blog and the generation handle the installed languages). PrestaShop's multistore mode is supported on the module side; on the app side, each paired store is driven separately.

Can I write my articles myself, in the module?

Of course: the module has its own classic admin interface inside PrestaShop. The app isn't required in order to blog — it's there to hold the rhythm, which is the real battleground.

I only want to centralise the writing, not publish from the app. Does that work?

Yes, and it's a supported use. You keep your own publishing route and take only the production: every piece is available as Markdown, plain text, bare semantic HTML or HTML styled with your theme, with the SEO framing already done. The detail is here.

How do I get started?

Install the module, create an account, pair with a licence key: under fifteen minutes. The full walk-through is on How it works.