Following a scan live
While a scan runs, FilterWise shows the step it is on rather than a progress bar that teaches you nothing. The steps are real: each is a moment in the actual work.
The steps of a site scan
- Queued — the scan is claimed; it starts on the next minute.
- Fetching the page — FilterWise opens the page in its own browser. This is the long step on sites that build their content in JavaScript: the page has to finish rendering before it can be read.
- Bypassing anti-bot (only when needed) — the site served a challenge wall. FilterWise tries again differently, from another exit address.
- Extracting listings with AI — the page is cleaned, then read.
- Filtering the listings found — each one is compared against your instructions.
- Done — with the number of matches out of the listings found.
What is normal
- A step taking 20–30 seconds: some portals do not finish rendering faster. FilterWise waits rather than read a half-built page.
- A scan with no new listing: the site published nothing since the last pass. Listings already known are not re-analysed and cost nothing.
What is not
- Site blocked (anti-bot): the portal refuses automated visits — see Handling blocked sites.
- Permanently failed: the page could not be read after every retry. It will not try again on its own; Re-analyze gives it another go.
Testing a filter
The test panel shows the same steps on a single listing, including the wait for the AI's answer. It is the fastest way to see where something is stuck without waiting for the daily scan.
Related articles: Adding source URLs · Handling blocked sites · Listing statuses