VJOURNAL

BusinessGlobal DeskAugust 27, 2026

Marketplace title and attributes: what goes in the line and what goes in a field

A listing title is read by a search system and by a person who looks at the grid for one second, and the two want different things. Here is what goes in the line, what goes in the fields, and what belongs nowhere.

Marketplace title and attributes: what goes in the line and what goes in a field

Answer in brief

A listing title is read by a search system and by a person who looks at the grid for one second, and the two want different things. Here is what goes in the line, what goes in the fields, and what belongs nowhere.

3 sources
A listing title serves two readers at once: the marketplace matching system and a person who looks at the grid for a second.
The meaning of the line has to be complete inside the first forty to fifty characters, because the storefront truncates the rest.
An empty attribute field removes the listing from a filtered result set entirely rather than moving it one position down.

The short answer: what a title is for: A listing title serves two readers at once: the…

A listing title has one job. Name the product in the words a buyer actually types, then add the one or two things that separate this version from the one beside it. Everything else is decoration that costs you space you do not have.

The working formula is short: product type, brand or model, the defining specification, the use case. Four slots cover almost any category. If a fifth slot feels essential, it is usually describing something that belongs in an attribute field instead.

Attributes are not an appendix to the title. They are the other half of the same job. The title answers what is this; the fields answer will it fit me, and the fields are what a buyer filters on before reading a single word of copy.

The rest of this piece covers why one line has to serve two very different readers, which facts belong in fields, what should never appear in a title, and how to check your own listing without access to anyone's private analytics.

One line, two readers

The title has two readers and they want opposite things. The marketplace search system splits the line into words and matches them against a query. The person scanning a grid never reads the line: they take the first few words, glance at the image, and jump to the price.

The same mistake therefore looks different depending on who is looking. A line stuffed with synonyms barely bothers the matching system, but it stops the human immediately. They cannot tell what the product is, so they move on to the next tile.

The opposite failure is just as common. A short, elegant title such as Our New Winter Sweater reads beautifully and is close to invisible in search, because it contains no phrase that anybody would genuinely type into the search box.

The resolution is not a compromise in the middle. It is an order of words. Put what both readers need first, the product noun and its main difference, then the words that mainly serve matching. The line stays readable and stays findable.

The first forty characters decide the rest

In a results grid the title is almost always cut off, and cut off inconsistently: earlier on a phone, later on a desktop, different again inside the app. Plan the line for the harshest truncation you can find rather than the most generous one.

That gives you a simple rule. The sentence has to finish its meaning inside the first forty to fifty characters. If removing the tail of the line stops it explaining what the product is, an important word is sitting too far to the right.

You can test this without tooling and without exports. Open your category on a phone, find your listing among the competition, and read only what is visible. That fragment, not the string in your spreadsheet, is your real title.

The tail is still worth writing. Truncation is a display decision rather than a limit on what the listing stores, so the words past the cut still describe the product in the data. They simply no longer influence the human decision.

Word order: the noun first, the difference second

The safest opening is the ordinary noun people use for the thing. Running shoes. Kettle. Throw blanket. Not item, not model, and not the name of your collection, because nobody searches for a collection they have not heard about somewhere else first.

The second slot holds whatever separates this listing from the one next to it in the same category. Sometimes that is the brand, sometimes the material, sometimes capacity or size. Choose it by what buyers compare on, not by what matters most internally.

The third slot is the use case, but only when the use case narrows the choice: for running, for induction hobs, for newborns. Those qualifiers pick up real queries and quietly reduce returns, because they turn away the wrong buyer before checkout.

Write numbers the way a customer writes them rather than the way your catalogue exports them. 1.7 L and 1700 ml are two different strings, and a matching system treats different strings as different words until somebody teaches it otherwise.

Attributes are the ranking work with the lowest price attached

Filling in fields needs no photographer, no advertising budget and no new production run. It is desk work done from documents you already own: supplier specifications, measurements, composition. That is why it costs less than most other attempts to grow.

The mechanism is blunt. A category filter is an exact match on a field value. If the field is empty, your listing does not rank lower inside that filtered view. It is not in the set at all, at any position, on any page of results.

So every blank field is a slice of demand cut off cleanly. Not a vague loss of visibility, but specific people who chose their size, colour or material and never saw your product among the results they were actually shown.

Filters are only half of it. Attribute values are text on the listing too, and a marketplace has no reason to keep that text out of matching. A material named both in the field and in the title is doing the work for you twice.

Working out which fields matter in your category

Every platform publishes a list of required attributes, but required only describes the minimum needed to upload. What actually matters is decided by how buyers in your specific category narrow their choice, and that is visible from outside the seller account.

The first source is the filter column on the category page. Anything the platform has given its own toggle is something the platform considers worth filtering on. A blank value in one of those fields costs more than a blank anywhere else in the table.

The second source is the listings that consistently sit above yours. Do not copy their wording, but do compare which fields they have filled and which they have left empty. The difference between their specification table and yours is usually short and very specific.

The third source is your own buyer questions and return reasons. If people keep asking about the same measurement, they could not find it in the table. That answer belongs in a field, not in a reply that exactly one person will ever read.

What does not belong in a title

Other people's brand names are not a clever trick. They are a takedown waiting to happen, and they usually get removed before they have earned anything at all. Compatibility with another company's device belongs in a compatibility field, if the category offers one.

Promotional words like hit, sale and best seller describe nothing and appear in no meaningful query. What they do is occupy exactly the visible part of the line the shopper sees in the grid, pushing genuinely useful words past the cut.

Chains of synonyms, throw blanket bedspread coverlet quilt, are an old tactic that now works against the listing. A person reads that as a warehouse label rather than a product, and clicks the neighbouring tile where the wording is plain.

Capital letters, emoji and star separators all solve one problem, getting attention, while creating another: the line becomes harder to read in a second. That second is the entire attention budget you are working with in a results grid.

One rule set for the whole product family

When a product has variants, whether sizes, colours or capacities, the titles should be built from a single template. Inconsistency inside a family reads as unrelated products from unrelated sellers and makes the comparison the buyer came to make harder.

Colour naming deserves its own discipline. Graphite, anthracite and dark grey may describe the same shade, but in a filter they are three separate values. Your catalogue needs one vocabulary, and preferably the one the platform already uses.

The same applies to units and to the way sizes are written. One format across the whole catalogue saves time on every future upload and removes an entire class of errors that otherwise get found by hand in an export a week before a season.

A practical habit: keep the title template and the value vocabulary in a file rather than in somebody's head. Then a new product is created from a pattern instead of from the memory of whoever created the last one and is now on holiday.

Where the title ends and the description starts

The split is simpler than it looks. The title carries what people search and skim on. The fields carry anything that can be measured and compared. The description carries what has to be explained in sentences, because a number cannot say it.

A description is not the place to repeat the specification table. If size, composition and weight already sit in fields, restating them adds neither data nor credibility, while pushing down the only thing anyone opens a description to find.

And they open it to settle a doubt: will it fit, how is it cared for, what is in the box, how does it differ from the cheaper option sitting next to it. One paragraph per doubt, and the text stops being a formality.

When a fact could live in either place, put it in the field. A field participates in filtering and in comparison; a paragraph participates only in reading. With equal content, the machine-readable location wins every time.

Titles and attributes on your own website

On your own site the same data lives in Schema.org Product markup: name, brand, sku, offers and additional properties. It is not a copy of the marketplace listing but the same product record, written in a form that programs can read.

The point is having a single source. When the product name, the colour and the size all come from one table, your site and your marketplace listings stop drifting apart, and drift is exactly what a buyer notices and reads uncharitably.

One note on PDFs: a specification sheet in PDF is indexed as text rather than treated as a picture. That means the document can bring people to your site, and for the same reason it is no place to put anything you would rather not publish.

Markup does not replace a title and will not lift a listing by itself. It makes the product record legible to the systems that collect it, and that is precisely the kind of work that is cheaper to do carefully once than to redo later.

Text you can see but cannot read

A common way sellers lose data is by putting specifications only inside an image. To a person that is text. To a search system and to a screen reader it is a rectangle of pixels with nothing written inside it at all.

The WCAG 2.2 guidance is direct about this: keep text as text wherever you can, and give images a text alternative. On your own site that is your responsibility, and it happens to point in the same direction as search does, down to the last item.

Colour is the same problem in miniature. If a variant is distinguished only by a swatch, some buyers cannot name what they are choosing. Naming the colour in words settles the accessibility question and the filtering question with one edit.

The rule worth remembering is that an infographic repeats data but never stores it. Anything shown on an image has to exist as well in the title, in an attribute field, or in the description, as real text rather than as a picture.

What to buy if you are not doing this yourself

When the starting words are the unknown, the entry point is the Demand Audit at $50. It runs 1-2 working days and includes one round on the findings document. Access to your seller account is not part of that work, and it is not needed for it.

When the keyword list already exists but the listings have not been rewritten against it, Listing Refresh at $70 fits: 2-3 working days and one round of revisions. Photography, ad spend and account management are not included in that package.

The Marketplace + SEO System at $110 pulls titles, fields and copy into one consistent set over 3-5 working days, with two rounds on listings and copy; photography and paid placement sit outside it. When the date matters more than the scope, Marketplace + SEO Express is $190 for 3 working days and one round.

After that it stops being an edit and becomes a routine: Managed Demand Growth at $200 per month, a monthly cycle with 30 days notice to stop, and advertising spend on the marketplace excluded. The terms for every package sit on /services/marketplaces.

Practical checklist

  • Check on a phone whether the first forty characters still explain the product.
  • Put the category noun at the start of the line and the main difference right after it.
  • Open the filters on your category page and fill in every field listed there.
  • Remove competitor brands, promotional words, emoji and synonym chains from the title.
  • Reduce colour names, units and size formats to one vocabulary across the catalogue.
  • Move into fields and copy everything that currently exists only on an image.

Questions and answers

Which comes first, rewriting titles or filling in attributes?

Attributes first. Filling fields needs no photography and no budget, and an empty field switches the listing out of a filtered view completely. Rewriting a title changes your position; filling a field changes whether you are in the set at all.

What does it cost to start and what is included?

The Demand Audit is $50, 1-2 working days, with one round on the findings document; access to your seller account is not part of it. Listing Refresh is $70, 2-3 working days, one round of revisions, with photography, ad spend and account management excluded.

How long should a title be?

Aim at the truncation point in the grid rather than at the character limit. Finish the meaning inside the first forty to fifty characters; the rest is written for matching and no longer affects what the shopper decides.

Can I mention competing brands in the title?

No. It is a claim on somebody else's name inside the catalogue and a reason for the listing to be removed. If the product is genuinely compatible with another company's device, state that in a compatibility field where the category provides one.

Do we need Schema.org markup if we only sell on a marketplace?

The marketplace itself does not need it, because it reads your fields and not your website. But if you do run a site, Product markup keeps the name, colour and size in one source with your listings and removes the mismatches buyers notice.