What the numbers beside a filter mean
Each count is how many results you would be left with if you picked that option, with your other filters still applied.
Every count is computed with all your other filters applied but not that one, so it never promises rows a click cannot deliver, and never reads zero next to an option that would work.
When a filter empties the page
If one filter explains it, the page names it, for example "The pay stated filter is hiding 41 of 42 results", with a single click to undo it. When no single filter is to blame you get one button to clear them all.
Two filters go back to the server
Date posted and Remote fetch again rather than filtering what you already have. The rows on screen are the strongest matches for your words, so narrowing them locally would show you the recent ones among your best matches, not the best matches among the recent ones.
Where it stops
Counts appear once a search has settled. While boards are still answering, the numbers would move under the cursor, so they wait.
Related articles
- Narrowing a result setThere are 11 ways to narrow a result set, and the count beside each option is what you would be left with if you clicked it.
- When a search returns nothingEither your filters removed everything, in which case the page names the one responsible, or the index holds nothing yet for that query.
- Why so many listings show no payBecause the employer did not state any. We show pay as it was quoted and drop anything we cannot vouch for, rather than guessing.
Did this answer your question?
Still stuck? Ask us directly, and mention this article so we know where to start.