Definition
Search relevance is how closely a marketplace listing's title, description, tags, and keywords match the queries merchants type into the marketplace search bar. Every marketplace runs its own search index — Shopify's App Store, Atlassian Marketplace, WordPress.org, Zendesk Marketplace — and each weights title-match, description-match, category-match, and install-velocity-of-recent-clickers differently. The common pattern across platforms: an exact-phrase match in the title outranks a partial match in the description, and synonyms compete unless the listing explicitly enumerates them. For developers, search relevance is the highest-ROI listing lever because it determines the universe of queries the listing can rank for at all. A listing with a generic title and no tag coverage is invisible for tail queries no matter how strong its install velocity. AppRanks does not run a proprietary relevance score; we surface the title, description, tags, and category data as scraped so developers can compare their listing's keyword coverage against category competitors.
Where you see it on AppRanks: Audit page "Title & description" check, compare page side-by-side listing fields.
Why this metric matters
Search relevance determines the universe of queries a listing can rank for at all — a generic title and thin tag coverage caps the listing's organic reach regardless of how strong its install velocity becomes downstream. For developers, the highest-leverage relevance work is keyword coverage: enumerating the synonyms merchants actually type (e.g., "pre-order" + "preorder" + "back in stock" + "waitlist") so the listing surfaces for the long tail of related queries. Once a listing is keyword-discoverable across the relevant query space, install velocity and review signals take over to rank the listing within the candidate set. Skipping the relevance step caps every downstream metric.
How AppRanks computes it
AppRanks does not run a proprietary search-relevance score because the marketplaces' own search indexes (and their query distributions) are not public. Instead, the audit page surfaces the raw listing inputs — title, description word count, tag list, category assignments — and the developer can compare those against category competitors via the head-to-head compare pages (/compare/{platform}/{slug-a}-vs-{slug-b}). The relevance signal you see on AppRanks is therefore structural (what's in the listing) rather than algorithmic (what the marketplace's ranker scored it). For keyword research, we suggest pairing AppRanks listing data with each marketplace's own search-suggest API or third-party ASO tools.
Use cases
- Keyword coverage audit: list the synonyms merchants actually search and check the listing's title + description + tags against the list — every missing synonym is an invisible query.
- Competitive teardown: pull a category leader's title/description/tags via the compare page and identify the keyword combinations they cover that your listing doesn't.
See also: App store optimization — the parent discipline · Listing health — the structural floor under relevance · Audit hub — per-listing relevance checks