The site said 141 listings. I delivered 109. It was 100%

Description and use

The site claimed 141 listings, but after cross‑checking three independent entry points, it was confirmed that only 109 are actually published, representing 100 % of the real data.

Problem

How to verify that a scraped dataset is complete when the site’s own counter may be inaccurate.

Outcome

The final dataset contained 109 listings, verified as complete by cross‑checking three independent entry points and normalizing data, demonstrating that the site’s counter overstates the actual published listings.

Workflow

• 1. Bypass Cloudflare challenge by respecting crawling rules, human pace, and no forbidden paths.
• 2. Access listings page and load all results via infinite scroll until no more data.
• 3. Collect listings from three independent entry points (e.g., homepage, city page, search results).
• 4. Normalize data fields (e.g., convert decimal commas to periods).
• 5. Deduplicate listings across entry points and remove non‑listing cards (ads).
• 6. Compare counts from all entry points; confirm convergence on 109 listings.
• 7. Generate a quality report detailing coverage, missing fields, and verification method.

Evidence

The site’s own counter said 141 listings.

Source

I delivered 109.

Source

All three converged on the same 109 listings. Not one listing appeared in one path and not the others.

Source

Number formats. The listings write 72,30 m², with a decimal comma. Read the wrong way, that becomes 7,230 m².

Source