How Amazon's Search Query Performance report works per ASIN, which ASINs to track when the list is capped, three traps in the data, and what to ask Claude.
Amazon's Search Query Performance report is the closest a brand owner gets to seeing the whole search funnel: how often shoppers searched a query, how many saw your product, how many clicked, added it to cart and bought, set against the same numbers for every product on that query. It is also one of the easiest reports to misread, because it works per ASIN and per query, and its totals repeat on every row.
This guide covers what the report contains at the ASIN level, how to choose which ASINs to track when the list is capped, the traps in the data, and the questions worth asking your AI once SQP sits next to your sales and ads. For the wider Brand Analytics picture, start with our guide to Amazon Brand Analytics.
Each row is one child ASIN, one search query and one week or month. Two kinds of numbers sit side by side:
Divide the first by the second and you get your share at each step of the funnel. That share, not the raw count, is what tells you where you win or lose a query.
The report also carries Amazon's Search Query Score. It ranks a query against the other queries for the same ASIN by overall performance, and a score of 1 marks the best-performing query for that ASIN. It is not your position in search results. If a tool or a prompt treats it as a rank, the answer will be wrong.
Amazon gives SQP to Seller Central accounts registered in Brand Registry with the Brand Analytics role in the Selling Partner API. Through the API it is a Seller Central report: Vendor Central accounts and Ads-only connections cannot pull it. The report covers every North American and Far East store, and in Europe and the Middle East it covers Spain, the UK, France, the Netherlands, Germany, Italy, Sweden, Turkey, Saudi Arabia, the UAE and India.
Weeks run Sunday to Saturday. Amazon publishes a week after Monday 12pm UTC and a month on the fifth of the following month, so the newest data is always a few days old by design.
SQP is pulled for the ASINs you choose, not for the whole catalog. As of 21 October 2026, the limits look like this:
You set the list in the app under Sellers & Vendors, or let your AI do it: the DataDoe MCP server exposes tools to list, add and remove SQP ASINs, and the REST API has matching endpoints. Limits change as Amazon and DataDoe change them, so the SQP documentation is the place to check the current numbers.
A cap plus a three-day lock means the list deserves a decision, not a paste of your top sellers. A practical order:
Leave out long-tail ASINs that sell a few units a month. Their queries are too thin to read, and the slot is worth more elsewhere.
With DataDoe connected to Claude, or to any other AI client, the SQP tables sit in the same schema as orders, fees, ads and stock. Your AI does the joins when you ask. Questions that work well:
Each answer is only as good as the ASIN list behind it, which is why the list comes first.
No. Search Terms ranks the most-searched terms in a category and shows which ASINs take the clicks and conversions, yours or not. SQP starts from your ASIN and shows its funnel on every query it appeared on. Most brand owners need both.
Not through the Selling Partner API, which is where DataDoe reads it from. Vendor accounts in DataDoe have their own sales, traffic and inventory data, but not SQP.
Usually because Amazon has not published it yet: weeks appear after Monday 12pm UTC. Amazon can also delay a week or send it incomplete, and DataDoe requests a missed week again later in the week.
No. Removed ASINs keep their history under your retention settings. Only new downloads stop.