Writing Product Titles That Work for Both Google and Humans

Last reviewed June 2026 — checked against PrestaShop 1.7, 8 and 9. The Name field, its ps_product_lang mapping, the SEO-tab Meta title and Friendly URL fields, and the Reference field for SKUs are all current. Important on PrestaShop 9: product URLs drop the category by default, so the slug derives from the Name alone — renaming a product changes the friendly URL more directly than on older versions.

In PrestaShop, the product title is not one piece of text doing one job — it's one field doing four jobs at once. The Name you type under Catalog → Products becomes the page's H1, the clickable link on every category and search-results listing, the anchor text in cross-sell and "you may also like" blocks, and the line item printed on the invoice. Out of the box it also seeds the page's <title> tag and the URL slug. So the same string has to read like a human wrote it for a shopper and carry the keyword Google ranks the page on. Get it wrong and you don't get a small problem in one place — you get the same wrong title repeated across your whole storefront and your SERP snippet. This guide is about that one field: where it lives in PrestaShop, what it feeds, and how to make it earn the click without reading like keyword soup.

Where the product title actually lives in PrestaShop — and what it feeds

Open any product in Catalog → Products and the first field on the Basic settings tab is Name. That field maps to the name column in the ps_product_lang table (one row per language), and PrestaShop reuses it in more places than most merchants realise:

• The H1 on the product page — rendered by the ProductController through the theme's product.tpl. This is the on-page heading Google weights heavily.
• The link text in listings — every product card (the product-miniature partial, typically catalog/_partials/miniatures/product.tpl, used by category listings, search results, the homepage featured block, and the new/best-seller modules) uses the Name as the anchor. That anchor text is also an internal-linking signal.
• The default <title> and URL slug — when you leave the SEO fields blank (more on that below), PrestaShop generates both from the Name.
• The cart, order summary and invoice line — the Name is what the customer sees at checkout and what prints on the PDF invoice. A title padded with "Best Quality Premium 2024" looks absurd on an invoice.

So what? A change to one field ripples to all of these surfaces simultaneously. That's the leverage — and the trap. You can't "SEO" the listing title without also changing the invoice line, unless you use PrestaShop's separate SEO fields deliberately.

The two fields most merchants don't know they have

The single most useful thing PrestaShop gives you here is buried in the SEO tab of the product editor. The Meta title field lets you override the browser-tab and SERP title independently of the visible product Name. This is the escape hatch from the classic SEO-vs-human tension:

• Name (visible): "Linear Shower Drain — 60 cm" — clean, scannable, looks right on a category card and an invoice.
• Meta title (SERP only): "Linear Shower Drain 60 cm — Stainless Steel 304, Tile Insert" — carries the extra keywords searchers actually type.

If the Meta title is empty, PrestaShop falls back to the Name — which is why stores that ignore this field end up with their listing title and their Google title locked together. Filling it deliberately is the difference between a clean storefront and a keyword-stuffed one. Aim for a meta title around 40–60 characters: long enough to carry the keyword and a differentiator, short enough that Google doesn't truncate it with an ellipsis. Where Meta title still feels too cramped to hold everything, the cleaner pattern is a dedicated SEO subtitle that sits beside the name rather than inside it — we cover that trade-off in Product SEO Subtitles.

The same SEO tab also exposes the Friendly URL field. By default PrestaShop slugifies the Name, so renaming a live product can regenerate the friendly URL — or tempt you to regenerate it yourself — and if the slug changes, unless you have redirects in place, that breaks every existing link and the page's accumulated ranking. On PrestaShop 9 this matters more, because the category is gone from the URL and the slug rests entirely on the Name. If you must rename, verify the friendly URL: keep the old slug (set it by hand) or, if it does change, make sure a 301 is in place. For doing that reliably across a catalogue — catching slug changes and keeping the redirects in step — our SEO Revolution module manages the meta fields and 301s from one screen, so a rename doesn't silently drop a ranking page.

The structure that works in a PrestaShop listing

Because the Name is the link text on every category card, the front-loaded words matter twice: once for SEO, once because that's what a scanning shopper reads before deciding to click. A reliable order:

[Primary keyword / product type] + [key differentiator] + [variant]

• "Linear Shower Drain — Stainless Steel 304, 60 cm"
• "Wall-Mounted Bathroom Cabinet — Oak, 60 cm"
• "Over-Ear Bluetooth Headphones — Noise-Cancelling, Black"

The product type leads because that's the search term and the word a browsing customer locks onto. The differentiator (material, certification, headline feature) earns the click against the product sitting next to it on the same category page. The variant comes last — and on PrestaShop that's a deliberate choice, because of how combinations work (see the next section).

If you keep the visible Name tight and put the keyword-rich version in the Meta title, a consistent pattern across a category looks like this — Name on the left for scannability, Meta title on the right for the SERP:

Name (H1, card, invoice)        Meta title (≤ 60 chars, SERP only)
─────────────────────────────   ──────────────────────────────────────────
Linear Shower Drain — 60 cm     Linear Shower Drain 60 cm — Stainless 304
Linear Shower Drain — 80 cm     Linear Shower Drain 80 cm — Stainless 304
Wall Cabinet — Oak, 60 cm       Oak Wall Bathroom Cabinet 60 cm | Soft-Close

The point of the pattern is repeatability: same word order, same separator, same capitalisation down the whole category, so the cards line up and the SERP titles read as one coherent shop rather than three.

One PrestaShop trap: titles and combinations

If a product has combinations (size, colour) managed under the Combinations tab, the Name stays the same for the whole product — the combinations are represented separately from the base product name (as selected options and as cart/order attributes), not baked into the title, depending on template and context. So putting "Navy Blue, Large" in the Name of a product that also has a colour/size combination gives you "T-Shirt Navy Blue, Large — Large, Navy" duplication on the page and in the cart. The rule: if an attribute is a real combination, leave it out of the Name and let PrestaShop render it. Only bake a variant into the Name when it's a standalone product, not a combination. If you're unsure which model your catalogue should use, that decision is its own topic — see product combinations and variants.

What to leave out of a PrestaShop product Name

• Marketing adjectives. "Best", "Premium", "Top Quality", "Must-Have" earn nothing in ranking and look ridiculous on the invoice line and in the cart. Drop them.
• Repeated keyword variants. "Shower drain floor drain bathroom drain" reads as spam to a human and adds keyword-stuffing risk. Say the type once; let the description carry synonyms.
• Your store name. Many shops and themes already include the shop name in the rendered <title> tag (often via a meta-title separator under Shop Parameters → Traffic & SEO), so putting it in the product Name tends to duplicate it and waste the visible characters. Check your rendered <title> to confirm before deciding.
• "For Sale", "Buy Online", "Free Shipping". Nobody searches a product type that way, and it clutters the listing.
• SKU / model numbers — unless customers genuinely search them (electronics, auto parts). PrestaShop has a dedicated Reference field for the SKU; that's where it belongs, not in the Name.

Title length: what PrestaShop renders vs what Google shows

PrestaShop puts no hard limit on the Name field, so it's tempting to keep typing. Two ceilings actually matter:

• Google's SERP title truncates around 55–60 characters. Whatever you put in the Meta title (or the Name, if Meta title is blank), the keyword has to live in the first ~60 characters or searchers never see it.
• Your own category cards. Most PrestaShop themes give the product-card title a fixed height and clamp long names with an ellipsis. A name that reads fine in the editor can render as "Linear Shower Drain — Stainless Steel 304 Anti-Odour Reversi…" on the grid, hiding the very differentiator you added it for.

The practical move: keep the visible Name tight enough to survive your theme's card clamp, and push the longer keyword-rich version into the Meta title where the only constraint is Google's ~60-character window.

Consistency across the catalogue — and how to fix it at scale

A single great title helps one page; a consistent system helps the whole store. Pick one structure, one capitalisation style (Sentence case or Title Case — not both), and one separator (an en dash, a pipe, or a comma) and hold the line across a category. Inconsistent separators and attribute order make a category page look like three different shops stitched together, and that scannability cost is real: a customer comparing five drains can't compare them if each title is built differently.

The honest problem is volume. Rewriting 800 product Names by hand in the editor, one at a time, is the kind of job that never gets finished. PrestaShop's bulk tools help only so far. This is where a structured edit pays for itself — our Find and Replace module lets you normalise separators, capitalisation, and recurring phrasing across the whole catalogue from the back office, so "fix the dash to an en dash on every product in this category" is one operation instead of eight hundred. So what? The cleanup that would cost a weekend of clicking becomes a few rules — which is the only way catalogue-wide consistency actually happens rather than staying a good intention.

Multilingual titles aren't translations — they're re-searches

Because the Name lives per-language in ps_product_lang, every language tab in the editor is a separate title you control. Treat them as separate keyword decisions, not word-for-word translations: "shower drain" is "Duschrinne" in German, "caniveau de douche" in French, "canaletta doccia" in Italian — and the way each market searches differs from a literal rendering. Fill the Name (and Meta title) natively per language; a translated-but-not-researched title ranks for nothing in that market. Then make sure Google serves the right one to the right country — that's a hreflang job at the head level, not something the title field does on its own.

Measuring whether a title is doing its job

Titles aren't set-and-forget, but don't trust a hunch or three days of data either. Two sources tell you the truth:

• Google Search Console. Look at the queries each product page actually surfaces for and its click-through rate. A page with impressions but near-zero clicks has a title that ranks but doesn't tempt — that's a Meta-title problem, not necessarily a Name problem. A page surfacing for the wrong queries has a keyword problem in the Name.
• Your own category pages. Open them as a shopper. Can you tell five similar products apart in two seconds, on the card title alone, before clicking? If not, the differentiator is either missing or hidden past the theme's clamp.

The title gets the click — the page closes it

Invest in product titles first, because the Name field is unusually high-leverage in PrestaShop: it feeds your listings, your SERP snippet, your internal links, and your invoices from one place, and small edits there move both traffic and click-through. But the click is only the start. The description has to rank and persuade once the visitor lands — see writing product descriptions that rank and convert — and the layout around it decides whether they buy or bounce, covered in product page anatomy. The title's job is narrow and specific: be the most honest, scannable, keyword-true line you can write in that one field, and let the rest of the page do the rest.

Frequently asked questions

What's the difference between the product Name and the Meta title in PrestaShop?

The Name (Basic settings tab) is the visible title — it becomes the H1, the link text on every listing card, the cart line and the invoice line. The Meta title (SEO tab) overrides only the browser-tab and SERP title. Keeping them separate lets you run a clean, scannable Name on the storefront and a longer, keyword-rich title in Google. Leave the Meta title blank and PrestaShop just reuses the Name for both.

Will renaming a product break its URL and ranking?

It can. The Friendly URL is slugified from the Name, so a rename can regenerate the slug — and a changed slug breaks every inbound and internal link to that page unless a 301 redirect is in place. On PrestaShop 9 the risk is sharper because the category is no longer in the product URL, so the slug rests entirely on the Name. Before renaming a live product, either pin the old slug by hand in the Friendly URL field or make sure a redirect catches the change.

Should I put size or colour in the product Name?

Only if it's a standalone product, not a combination. If size or colour is a real combination on the Combinations tab, leave it out of the Name — PrestaShop renders the chosen option separately, and duplicating it in the Name produces awkward "T-Shirt Blue, Large — Large, Blue" strings on the page and in the cart. Bake a variant into the Name only when there are no combinations doing that job.

How long should a product title be?

Keep the visible Name short enough to survive your theme's category-card clamp — many themes ellipsis-truncate around 50–60 characters and hide your differentiator. For the Meta title, aim for roughly 40–60 characters so Google shows it whole. Put the keyword in the first ~60 characters either way; past that, searchers don't see it.

How do I fix inconsistent titles across hundreds of products?

The native back office only lets you edit Names one at a time, which never finishes for a large catalogue. A find-and-replace tool (such as our Find and Replace module) normalises separators, capitalisation and recurring phrasing across the whole catalogue in one operation — turning "swap every hyphen to an en dash in this category" from eight hundred clicks into a single rule. Always run it on a copy or with a backup first, because it edits live product data.