01 / Identify the surface
Point to the exact page, field, or preview
Provide the precise URL and identify the element that creates the unsupported connection. If the problem appears only in a search preview, distinguish it from the current source page.
Avoid sending a broad complaint about an entire search result set. A reviewer needs a bounded surface and a correction the publisher can actually make.
02 / Show the mismatch
Use source facts without building a second profile
Explain that the page does not supply evidence connecting the records, or identify a source-level contradiction when one is available. Include only the minimum contextual fact needed for the reviewer to verify the mismatch.
Do not repeat sensitive values in the message when a field label, cropped reference, or case number can direct the reviewer to the same issue more safely.
Working principle
A correction request should be easier to verify than to misunderstand.
03 / Request one outcome
Choose remove, separate, correct, or refresh
Ask the publisher to remove an unsupported association, separate merged profiles, correct a defined field, or delete a duplicate. Ask a search provider to refresh a preview only when the source no longer contains the old material.
One requested outcome gives the response a clear success condition. If several independent pages are involved, create separate requests and track them separately.
04 / Preserve the record
Track the case without duplicating the disputed material
Save the request date, exact URL, neutral issue category, case number, response window, and next review date. Do not turn the tracking record into a permanent copy of the content being challenged.
After the source changes, verify the public page and major previews. If a stale snippet remains, open a new refresh step rather than treating the publisher response as a failed correction.