Automatic SEO meta tags: titles, descriptions and keywords for your whole catalog - Module PrestaShop

A whole catalog of SEO tags, without writing them one by one

On a catalog of a few hundred products, writing a unique meta title and meta description by hand for every product, in every language, takes days. PrestaShop offers neither a template nor a mass edit: each page is edited on its own, and the theme leaves the basic tags as they are. The result is empty descriptions, titles copied from one product to the next, and pages that look the same to search engines.

Automatic SEO Meta Tags turns this into a routine: you describe once, in a template, what a good title and description contain, and the module proposes the value of every page — product, category, brand, CMS page and home page — in every language and every shop. You check it, correct it if needed, then write in batches. The module then keeps a record of what it wrote: a value typed by hand is never replaced without your consent.

Templates that know your catalog

A template combines fixed text and variables: name, category, brand, price, reference, EAN, attributes, features, short description, shop name, year, language and currency. Filters format the result — upper case, lower case, first letter in capitals, tag stripping, word-safe truncation, fallback value — and optional groups avoid dangling separators when a variable is empty. For example, {name}[ - {brand}] gives “Fox cushion - Studio Design”, and {short_description|or:name|truncate:160} uses the short description, or the name when it is empty.

Each page type has its own template, and each language can have its own. A language that inherits the default-language template does not translate its text: it applies it with its own variables. For genuinely native wording, write one template per language.

Nothing is written before you approve it

The module first analyses the selection, then shows a preview: old and new value side by side, a character counter against your minimum and maximum, a search-result preview and warnings — empty variable, value too short or too long, duplicate with another page, value cut at the field limit. Every proposal can be edited line by line, and every row can be excluded. Three modes decide what is replaced: fill empty fields only, replace the values written by the module, or replace every value after confirmation. A progress bar shows the work; if the browser closes, the application resumes where it stopped. The last application can be undone, and the timestamped history keeps the before, the after and the author of every write.

Find the tags that are missing

The audit walks the catalog and sorts the issues: empty field, title or description too short or too long, title or description shared by several pages, empty keywords, value changed outside the module. The table filters by type, language, issue, origin of the value and name; every row leads to the native edit page or to the module's editor, and the CSV export follows exactly the filter on screen. A “Generate for these pages” button opens the generation with the selection already made.

Import, export and keywords

The CSV export produces a UTF-8 file, one row per page and per language, with the title, description, keywords and canonical URL. The import starts with a dry run: every line is checked — type, identifier, shop, language, length, forbidden characters, canonical URL, duplicate — and the report gives the file, line, field and reason. An empty cell leaves the value in place; the {empty} token clears it. Keywords can be generated from the name, category, brand and feature values, with stop-word lists in English, French, Spanish, Italian and Polish, case- and accent-insensitive deduplication, and a length limit. Major search engines ignore the keywords tag: the module keeps it for the tools and shops that use it, without promising an effect on rankings.

Clean tags in the head

The module replaces the tags the theme prints with one configurable set, without adding anything visible to the page:

• Social tags Open Graph and Twitter Card, with a template per page type and an image fallback (product cover, then category image, then logo). The product:* tags of product pages are kept and the theme's duplicates removed.
• Hreflang for products, categories, brands, CMS pages and the home page, in every active language of the shop, with x-default, absolute URLs and only the translations that exist. One set of tags is printed, in place of the theme's set.
• Canonical URL customized per product, category or CMS page, with URL validation; when empty, the native canonical is kept, and only one canonical tag is served.
• Shop-name suffix in the title, optional, with the separator of your choice; the title length is counted with the suffix.
• Keywords tag on PrestaShop versions that no longer have a native field: the module stores the keywords and prints the tag itself.

The result is identical for every visitor, with no cookie, and no query is added on pages the module does not cover.

New pages fill themselves in

When a product, category, brand or CMS page is created, its empty fields receive their value. On update, empty fields are filled and, if you asked for it, the values written by the module are recalculated when the price or another template variable has changed. A value typed by hand, imported or changed outside the module is never touched by this automatic generation. Specific-price and combination changes queue the product; beyond 20 objects in one request, the rest is processed by the scheduled task. A daily recalculation keeps values that depend on the year, price rules, taxes or currencies up to date. Everything can be switched off per type, per language and per shop.

AI only if you want it

The module can ask an OpenAI-compatible API for title, description and keyword proposals, with your own key and the model of your choice. You choose the data sent (name, category, brand, features, short description), the languages and the fields; each object is one request, and the result arrives in the same preview, with no automatic write. The key is encrypted and masked. Without a key, every other feature keeps working.

Multistore and five languages

In a multistore, templates, settings and jobs are configured per shop, and one generation can target one or several shops. Products, categories, CMS pages and the home page keep a value per shop; brands, whose native fields are shared, are flagged as such. A new shop receives the templates of the default shop, and a button copies templates from one shop to another. The interface exists in English, French, Spanish, Italian and Polish.

What the module does not do

It does not create JSON-LD structured data or rich snippets, does not generate a sitemap, does not change robots.txt, does not manage redirects, does not rewrite URLs and does not write image alt texts. It does not track your rankings in search engines and does not replace Search Console. It prepares and checks tags; it guarantees neither a ranking nor traffic.

Move from a catalog with uneven tags to a consistent catalog: describe once, check every value and let the module write the rest.