Why search shows fewer results than it counts
For anyone who searched, was told “About 40 results” and could only open six — what the count is counting, and why an empty page is not the end of the list.
The count is not a count of things you can open. It is an estimate of everything that matched, worked out before EVVA checked which of those you are allowed to see. That is why the line reads “About N results” and not “N results”.
Two separate things shrink the list between the count and your screen.
1. The count reaches past the results
The number counts matches beyond the part of the list that can actually be paged through. Then a second stage removes anything you may not see — and it filters after counting, and it never refills the page to make up the difference.
So a page can be short, or completely empty, while there is still more list to load.
An empty page with more to come says “No results in this part of the list. Keep loading for more.” — not “nothing matched”. If you see that, press Show more results. Stopping there means stopping early.
2. Results are looked up again before they are shown
The search index stores only a pointer to each match, never a copy of the post, profile or listing. Every result is then read back from the live product, which applies its own visibility rules.
If something was unpublished, made private or deleted since it was indexed, that read returns nothing and the result cannot be shown. The screen counts those and tells you: “1 more result is not available to show.” or “N more results are not available to show.”
This is the honest version of a stale search result. Rather than showing you a row that leads nowhere, EVVA says it could not show it.
When the order is not the usual one
If the engine had to fall back to a simpler kind of matching, the screen adds: “Results are ordered by word match this time, so the best result may not be first.”
Take that literally — the list is still relevant, but the ordering is weaker than usual. Scan further down than you normally would.
Sorting and matching
Results come back by best match by default. Newest and oldest are the other two orders. There is no sort by popularity, by price or by earnings on any search surface.
When search itself cannot answer
These are distinct situations, and the wording tells you which one you are in:
Only the last row means “there is nothing there”. The other three mean “search could not answer”, and the creators, posts and listings are all still on EVVA. Browse instead of concluding the platform is empty.
If a search is refused outright
A search can be refused for asking something the contract does not allow — an unknown filter, an unknown sort, too many filters or facets, an over-long parameter, a damaged “load more” position, or a page of more than 100 results. A page size above 100 is refused rather than trimmed, because the page size is part of how paging positions are calculated.
Refusals name the rule that was broken and never echo the value you sent back at you.