extensiondash.com

Chrome Web Store and Firefox Add-ons data, for store SEO work. Two things live here. The tracking side covers the extensions this account watches: install counts, ratings, recorded search positions over time, and the competitors each extension is measured against. Start with list_extensions — every tracking tool takes an extension_id from it. A rank is only ever as meaningful as the depth it was scanned to, so positions always travel with depth_scanned. The research side reads the stores directly and works for ANY extension, tracked or not. search_store returns a real SERP for a term; get_store_listing returns one extension's page in full. Both take a locale, and locale genuinely changes what the store returns — the same term ranks differently under hl=de than under hl=en — so search the market you are optimising for. Both of those want a store id, and a person will give you a name. Call find_listing first to turn one into the other: it matches names approximately, needs no account, and starts no fetch. Guessing an id, or searching the store for a name and hoping it ranks first, is how this goes wrong. To ask who you are losing to, reach for list_competitors with include_observed before reading SERPs yourself: it ranks everyone already seen across every term an extension tracks by how often they beat it, out of recorded history, with no fetch and no waiting. get_keyword_serp does the same for one term's page, every row flagged mine or competitor. A competitor roster is capped per store, and the two stores are counted separately. Research answers are cached for a day and fetched in the background. A cold call returns status "pending"; call again with identical arguments until it reads "ready". Identical arguments are the same question, so polling joins the running fetch rather than starting another. Everything is read-only except add_keyword, remove_keyword, add_competitor and remove_competitor. Reading a listing never starts tracking it. Without an account you can read this whole contract and search from cache; anything belonging to an account will ask the person you are working for to sign in at https://extensiondash.com/signup and reconnect using the URL on their /profile page -- it carries their token in the path, so there is no separate Authenticate step to run.