Skip to main content
Version 2026-10. This page covers listing_score on your own listings and its score_breakdown, computed with Alura’s listing score rubric, version 1.5.0 (the @pixell-co/alura-listing-score package, pinned to exactly 1.5.0). The breakdown names its rubric version in version.
The listing score rates how complete and searchable a listing is, from 0 to 100. It looks only at what the listing shows a shopper: photos, video, title, description and tags. It doesn’t look at sales, views or price.

Where the score comes from

  • listing_score is the score Alura stores with the listing. Search, sort and filter use this stored value (sort=listing_score, listing_score_min, listing_score_max).
  • score_breakdown is computed when you ask for it, with expand=score_breakdown on GET /v1/workspace/listings/{id}, or include: ["score_breakdown"] on get_my_listing. It uses the listing’s stored photos, videos, title, description and tags.
Both use the same rubric, so the breakdown’s total equals listing_score when the stored score was computed with the same version. When it wasn’t, or Alura doesn’t know which version computed it, the breakdown adds a score_version_mismatch notice: its total may differ from listing_score until Alura scores the listing again.

The sections and checks

The score has 5 sections and 14 checks. Each check earns points up to its maximum, and the score is the points earned as a share of the points possible, rounded to a whole number. length and keyword-upfront appear in both the title and the description section. Identify a check by its section and its id together. When Alura doesn’t know the size of any photo, or of the video, the quality check has 0 possible points, so it can neither raise nor lower the score. Tags in the API. The rubric can also count a tag as wasted when it repeats the listing’s category or an attribute. The API’s breakdown and the stored score don’t give the rubric the category or attributes, so here wasted only flags a tag you used twice (Etsy reads singular and plural as the same tag).

How score_breakdown reports it

Part of a breakdown, with one section and one check shown:
  • total is the score out of 100.
  • Each section has its score and max_score, and its checks.
  • Each check has:
    • value: what the rubric found, as short text such as 13/13, 8 words or Missing;
    • score and max_score: the points earned and possible;
    • status: pass at 90% of the possible points or more (slots needs all 13 tags), partial above 0, fail at 0, and na when the check has no possible points;
    • advice: the rubric’s advice for that result, in English.

When it is null

  • listing_score is null when Alura has no stored score for the listing yet, or the stored value isn’t a score from 1 to 100. A stored 0 reads as null: it’s never 0 for a listing Alura hasn’t scored.
  • score_breakdown is null when Alura hasn’t stored all of the listing’s photos, or the listing has a video Alura hasn’t stored. The response then has score_breakdown_error: "media_incomplete". Scoring a listing with missing photos would give it a lower score than it has.

Version history

An earlier plan for this page counted 15 checks. Rubric 1.5.0 has 14.