What to do before a screening
If you are preparing for a screening, background check errors should be handled as an evidence-and-correction task: identify the exact inaccurate information, preserve proof, request correction from the source, and track what changes afterward.
- Do not assume that a generic screening label tells you which records or online sources will be considered.
- Build a list of inaccurate URLs, profiles, images, names, company associations, and other factual claims before taking action.
- Ask the publisher or platform to correct the original information when the source is wrong.
- Track removal requests separately from search-result suppression, because changing a search result does not necessarily change the source page.
- Keep a dated record of every request, document, response, and status so you can show what was corrected and what remains unresolved.
This guide focuses on information connected with an individual or company across websites, profiles, directories, social platforms, publishing platforms, search engines, and AI-driven discovery systems. It does not identify the exact contents of a screening report, because that depends on the particular screening process and the information actually associated with the person.
What can a background check company actually see?
A screening provider’s exact view cannot be determined from the phrase “background check” alone; you should identify the specific information being considered rather than assume that every online result is included.
A person’s digital identity may be represented in many places: an official website, professional profile, directory entry, social account, published article, image result, business listing, or AI-generated answer. These assets can contain names, name variations, professional identities, company relationships, locations, services, and other claims. They may also contain outdated or inaccurate information.
That does not mean every such item belongs in a screening report or is treated in the same way. The practical first step is to separate three questions:
- What information is actually being considered? Record the exact source, URL, platform, and claim.
- Is the information accurate? Compare it with documents or other material that supports the correct version.
- Where is the correction needed? The source page, a profile owner, a directory, a search engine, or an AI discovery system may each require a different action.
Avoid building your response around assumptions such as “everything online will be checked” or “one search result represents the full record.” Those assumptions can send you toward the wrong remedy and make it harder to explain the issue clearly.
How should you inventory inaccurate information?
Create a structured inventory containing the exact query, each affected URL, the claim that is wrong, the correct information, and the documentation that supports your correction.
Start with the exact name or search query likely to be used. Add legitimate name variations that appear in search results. Then record each relevant result in a working table with fields such as:
- Exact search query
- Name variation displayed
- URL
- Domain
- Platform
- Content type
- Date published, where shown
- The inaccurate statement or image
- The accurate replacement information
- Documentation available
- Current status
- Date last checked
- Next action
Include official websites, professional profiles, company pages, directories, social profiles, publishing accounts, articles, and images when they create confusion about identity or professional background. Note incorrect company associations, outdated locations, inaccurate job information, false relationships, and other factual claims only when you have a specific source showing them.
Do not describe a result generally as “bad” or “misleading” without recording what it says and why it is wrong. A precise description gives the recipient something actionable. For example, distinguish between an incorrect name variation, a wrong company connection, an outdated profile, an inaccurate article, an image attached to the wrong identity, and a page that merely ranks prominently but is factually accurate.
The inventory is also useful when the same claim appears in several places. Each URL should be recorded separately, even when the wording is similar, because one publisher’s correction does not automatically update every other page.
What evidence should you collect before requesting a correction?
Collect documentation that establishes the accurate identity, professional information, company relationship, location, or other disputed fact before contacting a publisher or platform.
The central record should contain verified facts about the person or company. It can include the exact public name, legitimate name variations, company or brand, professional title, occupation, industry, country, city or region, website, public contact details, existing profile URLs, current and previous positions, services, expertise, education, certifications, licenses, awards, associations, publications, speaking engagements, community involvement, and approved personal-brand information—but only when supplied by the client or independently verified.
Not every field belongs in a public correction. The record is a source of truth for deciding what can be stated publicly. Information that has not been supplied or verified should remain outside published profiles, articles, directory entries, and correction requests.
For each disputed item, assemble the supporting material that is appropriate to share with the recipient. Keep a private copy of what was sent, the date it was submitted, the recipient, and any response. If a platform has a verification process, record its status separately from the content correction itself.
Do not manufacture supporting material, add credentials that were not verified, or describe an employer, award, education, client, license, review, or achievement that is not documented. A correction request is stronger when it narrows the dispute to an accurate, supportable statement instead of introducing additional claims.
Which correction route fits the problem?
Use the source-correction route when the original page is inaccurate, the platform route when a profile or account is wrong, and a search or AI-discovery route only when the underlying source has already been addressed or the issue is specifically about how information is presented.
The source is wrong
Contact the publisher, website owner, directory operator, or profile owner responsible for the page. Identify the URL, quote or describe the inaccurate statement, provide the accurate replacement, and attach or reference the documentation that supports it. Keep the submission date and response status in your record.
The profile or account is wrong
Use the platform’s available reporting, editing, verification, or correction process for that profile. State whether the issue is an incorrect identity, inaccurate employment, wrong company association, outdated location, copied image, or another factual error. Do not present yourself as an independent third party or create a deceptive account to influence the result.
The search result is outdated or misleading
First determine whether the source page is still wrong. If it is, request correction from the source. If the source has changed but search results still display an old version, record the result separately and use the relevant search-engine update or deindexing process where appropriate. Do not state that a page has disappeared until it has been checked at the source or appropriately deindexed.
The AI-generated answer is inaccurate
Record the exact answer, the system that displayed it, the query used, and the official or authoritative sources that establish the correct information. Correct the underlying web information and maintain consistent official details across legitimate profiles and websites. AI systems may draw relationships from available online information, so conflicting names, companies, locations, or professions should be resolved at their sources rather than replaced with unsupported claims.
For issues involving a search knowledge panel, a separate guide on correcting a Google knowledge panel may be relevant. The appropriate route depends on whether the factual problem is in the source material, the panel, or both.
Which routes do not work, and why?
Creating false profiles, publishing unsupported claims, repeating the same biography across many sites, or treating suppression as source correction will not create a reliable correction record.
Several commonly confused approaches should be kept separate:
- Do not create deceptive accounts. A profile that pretends to be an independent person or third party can create another identity problem instead of correcting the original one.
- Do not invent positive information. Adding unverified awards, clients, employment, education, reviews, press coverage, or accomplishments does not correct an inaccurate claim.
- Do not rely on repetition alone. Publishing many weak pages or copying the same biography does not establish a clear, credible identity. Information should be useful, factually supported, and appropriate for the platform.
- Do not confuse correction with suppression. A page can remain available at its source even if a different result becomes more visible in search. Track direct removal and suppression as separate workflows.
- Do not claim a result has been removed prematurely. Record “requested,” “pending,” “removed,” or “deindexed” according to what has actually been verified.
- Do not contact the wrong party. A directory correction, a profile correction, a publisher request, and a search-engine request are different actions. Sending the same message everywhere can leave the original source unchanged.
- Do not use circular linking as a substitute for accuracy. Links between official properties can help people navigate legitimate information, but they should be natural and controlled by the client rather than part of an obvious link scheme.
The right response is usually the narrowest one that addresses the documented error. If the source is accurate and the concern is only that it appears prominently, the task is different from correcting a false statement.
How do you request a correction from a source?
Send a concise, factual request that identifies the page, explains the exact error, states the correct information, and preserves a record of the submission.
A useful request should contain:
- The recipient or platform team.
- The exact URL or profile identifier.
- The inaccurate statement, image, association, or name variation.
- A plain explanation of why it is inaccurate.
- The corrected wording or requested action.
- Documentation that supports the correction, when appropriate.
- A contact method for follow-up.
- The date submitted and any reference number.
Keep the tone professional. Avoid broad accusations, unsupported legal conclusions, or unrelated reputation complaints. The recipient needs to understand the specific change being requested.
If the page contains several issues, list them separately. This makes it possible to record which items were addressed and which remain open. If the recipient declines, keep the response and record the stated reason rather than treating the request as completed.
When an image is involved, identify the image URL or page location and explain the identity problem precisely. Do not substitute an AI-generated face for the real person or present an unapproved image as an authentic client photograph.
How should you track removal and search-result suppression?
Maintain separate records for direct removal requests and search-result suppression so that an unresolved source page is not mistaken for a completed correction.
For a potentially removable URL, record:
- URL
- Domain
- Content type
- Publication date
- Platform
- Basis for requesting removal
- Documentation available
- Submission date
- Status
- Follow-up date
- Whether the item was removed
- Whether it was deindexed or remains indexed
For a result that cannot be removed or has not been removed, record:
- Search query
- Negative URL
- Starting position
- Current position
- Positive assets appearing above it
- New legitimate assets created
- Movement over time
This distinction matters because improving the visibility of accurate information does not alter the underlying page. Likewise, a source correction does not automatically mean every search index, profile, or AI system has updated its presentation.
Use statuses that describe reality: planned, generated, review required, approved, published, indexed, ranking, needs update, failed, or removed. A status should be supported by the latest check, with the next action recorded rather than assumed.
How should you prepare a consistent public identity?
Prepare one canonical entity record and use it as the single source of truth for every legitimate profile, directory entry, article, and correction request.
The record should identify the primary entity, entity type, primary location, primary profession, primary company, primary and secondary topics, verified facts, approved biographical facts, prohibited or unverified claims, official URLs, and target search queries.
Consistency does not mean publishing identical text everywhere. A professional network, business directory, publishing platform, and social profile require different descriptions. The facts should remain compatible while the wording, length, structure, and emphasis fit the destination.
Clear relationships are especially useful for reducing confusion. Where verified, state relationships in plain language, such as a person being associated with a company, a person specializing in a topic, a company being based in a location, or a company providing a service. Do not add a relationship merely because it would make the profile more prominent.
Before publication, check every statement for factual support, correct identity, duplication, natural language, platform fit, search clarity, AI entity clarity, and overall reputation accuracy. A smaller set of legitimate, useful assets is preferable to a large collection of thin or repetitive pages.
When should you seek specialist help?
Seek specialist help when the issue spans multiple platforms, involves conflicting identities, requires coordinated source and search tracking, or cannot be documented clearly through a single correction request.
A specialist workflow can organize the master entity record, distinguish direct correction from suppression, maintain documentation, prepare platform-appropriate profiles, monitor official URLs, and update inaccurate information where the relevant process allows it. Before choosing a provider, review its methods, evidence standards, reporting process, and separation of source correction from search visibility work. The online reputation management service should be evaluated by what actions it actually includes, not by broad statements about outcomes.
Ask for a clear record of the URLs being addressed, the basis for each request, the documentation required, the status of each action, and the difference between a source being changed and a result becoming less visible. You should also expect factual review before publication and a process for preventing unsupported claims from entering profiles or articles.
What should you do today?
Start today by creating the inventory, confirming the exact errors, collecting supporting documentation, and sending only the correction requests that match the responsible source or platform.
A practical order is:
- Write down the exact name and search query being used.
- Record every relevant URL, platform, image, profile, and inaccurate statement.
- Separate accurate but unwanted information from information that is factually wrong.
- Build the canonical record from supplied or independently verified facts.
- Contact the original source or responsible platform with a specific correction request.
- Record the date, recipient, documentation, reference number, and response.
- Track source correction, indexing, deindexing, and search visibility as separate statuses.
- Review official profiles and controlled pages for compatible names, companies, locations, and professional descriptions.
- Recheck each item and update the next action.
This sequence helps prevent the most common mistake: publishing new material before the underlying facts and existing sources have been organized. ReputationGeo applies this type of accuracy-first approach to legitimate online presence and reputation work.
FAQ
Can I know exactly what a screening company will see from an online search?
Not from the general label alone. Record the exact sources and claims connected with your identity, then determine which information is relevant to the particular screening process rather than assuming every online result is included.
Should I correct the search result or the original page first?
Correct the original page first when the source contains the factual error. Track search-result updates separately when an old result remains visible after the source changes.
Is moving an inaccurate result lower in search the same as correcting it?
No. Suppression concerns visibility among search results, while direct correction concerns the source itself. Keep separate records for both.
What if I cannot prove that a statement is wrong?
Do not publish a replacement claim or describe the statement as false without supporting documentation. Mark the item as unresolved and identify what evidence is needed before requesting a correction.
Can I create new profiles to present the correct information?
Create profiles only where the person or business legitimately qualifies for an account. Do not create deceptive accounts or use unverified information; each profile should reflect the canonical record and the platform’s purpose.
ReputationGeo can help organize legitimate correction, consistency, and online presence work around verified information.
Top comments (1)
The structured inventory approach you outlined for managing background check errors is a practical and systematic way to tackle a complex issue. By breaking down the information into precise categories, it not only aids in clarity but also ensures that corrections are effectively communicated to the relevant parties. One perspective to consider is integrating automated tools or scripts to streamline the data collection process, especially if managing large datasets. If you're looking for help in developing such automation or enhancing this process, I'd be glad to explore a paid collaboration. What tools or methods do you find most effective in tracking changes after submitting correction requests?