Amazon, Flipkart, Google Shopping and your own theme each cut a title off at a different point and reward a different order of words. Where each surface truncates, what a buyer scans for, and how to keep one attribute source that generates every version.
By Rehan Idrisi · · 6 min read
Part of: Marketing
The same title gets pasted into the Amazon listing, the Flipkart listing, the Shopify product and the Merchant Center feed. On a marketplace it works as a search string. On your store it is a headline under a photo. In a Google result it is a line measured in pixels. One string serving four jobs does at most one of them well, and in our experience it is usually the marketplace job, because that is where the title was written first.
We maintain catalogs where each channel's title is generated from attribute columns instead of typed, and the difference shows up as the volume of manual fixing that stops.
A buyer skimming a results page checks, in order: is this the thing I searched for, is it the variant I want, how much of it is there, and do I trust the name on it. That gives an order of product type, key attribute, size or pack, brand. Amazon's policy puts brand first, so on Amazon the order becomes brand, product type, key attribute, size or pack. Either way the product type sits inside the first few words, because that is what gets read on a small screen before the ellipsis.
Indian buyers read pack sizes closely. Pack of 2, 500 g, 1 L and combo carry more decision weight than any adjective, and they belong in the title in metric units, written the same way across the whole catalog. Premium, best quality, latest and 100% are skipped by the eye and, on Amazon, count against the repeated-word limit when they appear alongside the same words in the bullets.
Marketplace pattern: {brand} {product_type} {key_attribute}, {variant}, {pack}
Store pattern: {product_type} {key_attribute}, {variant}
Search title tag: {product_type} {key_attribute} {variant} | {brand}Before (one title everywhere, 150 characters):
BEST QUALITY Premium Cotton Bedsheet Double Bed King Size Bedsheets for Double Bed with 2 Pillow Covers Set Bedsheet 100% Cotton Soft Bed Sheet (Blue)
Amazon (75 cap):
Brandname Cotton Double Bedsheet, King, 2 Pillow Covers, 144 TC, Blue
Google Shopping (first 70 matter):
Brandname Cotton Double Bedsheet King Size with 2 Pillow Covers, Blue
Own store, product page:
Cotton double bedsheet with 2 pillow covers, blue
Own store, title tag:
Cotton double bedsheet, king, 2 pillow covers | BrandnameThe before title says bedsheet four times and cotton twice. The rewrites say each thing once, keep the product type in the first three words, and drop everything a buyer cannot act on. The thread count moved into the Amazon title because it is the attribute a bedsheet buyer compares on; it can move out again for a product where it does not matter.
On a marketplace you sit on a results page beside a hundred lookalikes, and the title is the main field the search engine indexes. It has to carry the words a buyer types. On your own store the buyer has already chosen you. The brand in every title is noise, the collection card clamps the text, and the product page has a description, bullets and specifications sitting right under the name to carry the detail. A store title is a name, not a keyword string.
The title tag is a third thing again. It is written for the search query, not for the page, so it can lead with the words people search and end with the brand, and it is judged by pixel width in the result. Case differs too: marketplaces expect Title Case, most store themes read better in sentence case, and the Case Converter flips a column between the two without retyping.
Store the parts, not the finished string. Brand, product type, key attribute, variant, pack, and any channel-specific extras each get a column in the catalog sheet or a field in the product record. A template per channel assembles the title from those columns. When a pack size changes, one cell changes and every channel's title follows. When a marketplace changes its cap, as Amazon did this year, one template changes and the catalog regenerates.
The generated column still needs checking. Paste it into the Word Counter to see the character count per row against each channel's cap. Run Find & Replace with a regular expression over the source columns to strip the adjectives that crept in from supplier data, such as premium, best quality and 100%, before they reach any template. Check the title tag column in the SERP Snippet Preview, because a title that fits 60 characters can still overflow the pixel limit when it is full of wide letters.
A listing that ranks today ranks on the words in its current title, so a rewrite that drops a term buyers search for costs traffic even when the new title is cleaner. Before regenerating, pull the search terms each listing already earns from the marketplace's own report and make sure the template keeps them. Change the marketplaces first, one category at a time, and watch impressions for that category before doing the next. Your own store's title tags are safer to change in bulk because the page URL does not move, but keep the product type words that the page already ranks for.
As long as the surface shows and no longer. Amazon now caps titles at 75 characters outside media. Google Shopping allows 150 but shoppers see about 70. A search result title is limited by pixel width, and a store's collection card by its CSS clamp. Put the product type and key attribute in the first few words everywhere.
Count words, characters, sentences and paragraphs live, with reading time and keyword density.
Preview how a title tag and meta description render in a Google result, measured by pixel width instead of character count.
Transform written copy into camelCase, snake_case, Sentence case, or UPPERCASE with detailed readability metrics.
Replace text across a whole document at once, with whole-word matching and regular expression support.