Does the Alt Tags module handle images I add in the future?

Yes. That is exactly how it works. Automatic SEO Images Alt Tags does not write alt text into your database when you install it. It sets the alt (legend) on the fly, every time a product, listing or category page is rendered, by hooking into PrestaShop's presenter layer. Upload a new product image and it is covered automatically. No re-run, no batch job.

Templates combine tokens like {product_name}, {category}, {category_name}, {manufacturer}, {image_position} and product identifiers ({reference}, {ean13}, {isbn}, {upc}, {mpn}), with a separate template per shop language so each storefront gets a localised alt tag.

One safety rule: by default the module never overwrites alt text you typed by hand, it only fills empty fields. You can switch on override if you want every image driven by the template. The default max length is 125 characters.

The module registers presenter hooks for product pages, product listings and category pages. On a product page it updates the cover image, default image and gallery images. On listings it updates the presented product cover/default image and image list. On category pages it updates the category image legend. Because this happens in the presented data, it stays compatible with cache and does not require scanning or rewriting rendered HTML.

The default templates are simple and safe: product pages use {product_name} - {manufacturer}, listing pages use {product_name} - {category}, and category pages use {category_name}. You can change them to include references or identifiers, but keep the result readable. Search engines and screen readers both prefer useful text over a stuffed list of attributes.

The builder cleans the generated alt text before returning it: it replaces variables, strips HTML, decodes entities, collapses repeated spaces and trims separators left empty by missing variables. It then truncates to the configured maximum length at a word boundary where possible. That means a missing manufacturer should not leave an ugly dangling template, and a very long product name should not produce an oversized alt attribute.

The practical workflow is to set a product template, listing template and category template once, leave override off unless you want to replace hand-written legends, then check a product page and a listing page in the browser source. Future images follow the same rules automatically because the hook runs every time the page is presented.