Reporting a wrong or outdated record

Data about the physical world goes stale. When a row is wrong, telling us is genuinely useful — it is fixed for you and for everyone else who would have exported it.

First: check it is actually wrong

Open the row's Link and compare. Two frequent false alarms:

• The listing itself is wrong. We faithfully reproduce what the map publishes. If the map has the old number, so do we — and the fix has to start with the map. We can still suppress the row on request.
• The row is old, not wrong. The export describes the business as of the last time we read the listing, not as of this morning. If the map has already been updated and we have not caught up, that is a re-crawl request rather than a correction — and it is worth sending, because it moves that establishment to the front of the queue.

What to send

Email support@findandclose.com with:

• The Google ID from your export. This is the only reliable identifier — names and addresses are ambiguous, feature ids are not.
• The column that is wrong, and what it should be.
• Optionally the export id, if you would like the credit reviewed.

What happens next

1. We re-crawl that establishment out of band, ahead of its normal schedule.
2. If the source has changed, the row updates and the fix is live for everyone.
3. If the source still carries the wrong value, we tell you so — and can suppress the row so it stops being exported.

Credits

A handful of stale rows in a large export is normal and is not credited back; the index is a moving picture of the real world and nobody can hold it perfectly still. But if an export returned materially broken data — the wrong market, systematically empty columns, rows that plainly did not match your filters — we credit it back regardless of any window. See refunds.

This is not a removal request

If someone has asked to be taken out of the index — a data-subject request rather than a data-quality one — that is a different process with a different guarantee. See removal requests.

Reporting a bug in the app

Same address, but say so. Include the page, what you did, what you expected and what happened. A screenshot of the browser console helps more than a description of it.