A “Report an Error” Link Is Only Useful If the Report Can Be Acted On

Directory users often notice problems before the business or platform does. A customer may find a disconnected number, a closed location, or an incorrect map pin. A correction form can turn that observation into useful maintenance data when it asks the right questions.

Ask what is wrong before asking for a long explanation

Let the reporter choose the affected field: business name, address, phone, website, hours, closure status, duplicate profile, or another issue. That simple classification helps route the report and reduces vague messages such as “this is wrong.”

Capture the proposed correction

If someone says the phone number is outdated, ask what the current number should be and, where appropriate, how they know. A source URL or brief note can speed up moderation without requiring the user to write an essay.

Distinguish owners from visitors

A business owner may be able to verify a change directly. A public user can still provide valuable information, but the directory may need independent confirmation before changing core identity fields.

Close the loop internally

Correction reports should have statuses such as received, reviewing, changed, or unable to verify. Even if the platform does not notify every reporter, the internal record prevents the same issue from disappearing into an inbox.

A well-designed correction form makes community input specific enough to review while keeping the reporting process quick for the person who noticed the problem.

Correction forms should ask for the smallest useful evidence

A public correction route can reveal errors that the directory operator would never find alone. The form should identify the listing, the field believed to be wrong, the suggested value, and a way to explain the source. Requiring a full account for a simple typo report may discourage helpful submissions.