Profile optimisation
Google Business Profile Eligibility Evidence: Build a Clean Location File
When a profile is hard to verify or questioned, scattered screenshots and contradictory records slow down resolution.
By Chamko Research Team Updated 4 min read
Quick answer
When a profile is hard to verify or questioned, scattered screenshots and contradictory records slow down resolution.
When a profile is hard to verify or questioned, scattered screenshots and contradictory records slow down resolution. An internal location evidence file helps the owner demonstrate that the business exists and is represented accurately; it does not guarantee verification or reinstatement.
Describe the real operating model
Record whether customers visit the address, whether staff are present during stated hours, whether the business travels to customers, and which services are performed there. A hidden residential address has different requirements from a staffed storefront. Do not try to make an ineligible address appear eligible by borrowing another company’s address or adding a nameplate to a virtual office.
Collect genuine, corroborating evidence
Depending on the business, records may include current signage, business registration, lease or utility records, licensing, branded equipment, invoices, and photos of the operating premises. Keep documents genuine and consistent with the profile. If records conflict, fix the underlying mismatch rather than editing documents to force a match.
Keep one approved fact sheet
Record exact public name, address formatting, phone, website, hours, category, and service-area setup, plus the evidence source and last-checked date. Follow the verification method Google offers for the specific profile. Store sensitive records with restricted access; an evidence file is not a public content folder.
Recommended workflow
- Review the real operating facts for eligibility evidence: build a clean location file.
- Check the current official Google guidance and confirm feature availability.
- Make only the supported, evidence-based profile change.
- Test the public profile and the connected customer journey on mobile.
- Record the owner, date, and next review trigger.
Operational QA matrix
| Checkpoint | What to inspect | Pass condition |
|---|---|---|
| Describe the real operating model | Record whether customers visit the address, whether staff are present during stated hours, whether the business travels to customers, and which services are performed there. | The public profile and the real operation agree; record any exception and its owner. |
| Collect genuine, corroborating evidence | Depending on the business, records may include current signage, business registration, lease or utility records, licensing, branded equipment, invoices, and photos of the operating | The public profile and the real operation agree; record any exception and its owner. |
| Keep one approved fact sheet | Record exact public name, address formatting, phone, website, hours, category, and service-area setup, plus the evidence source and last-checked date. | The public profile and the real operation agree; record any exception and its owner. |
Use this matrix before changing the profile and again after the change has propagated. If a checkpoint fails, correct the source of truth first, then update Google and re-test the customer-facing result. Do not make unrelated edits just to see whether visibility changes.
Minimum internal record to retain
For each change, record the profile or location identifier, the field or feature reviewed, the approved value or decision, the evidence source, the person who checked it, the date, and the next review trigger. For this topic, also preserve the relevant supporting item—such as the current schedule, photo status, category rationale, destination URL, branch-level date source, or API event log—without retaining unnecessary customer data or secrets. Store sensitive evidence with access controls and follow the business’s retention rules.
Practical example
A service business keeps current invoices, branded equipment photos, and its approved public details in restricted storage so an authorized owner can answer verification questions consistently.
Scenario checks before you close the task
- Normal case: Confirm the profile’s visible information reflects the current, real-world business and that the intended customer action works.
- Exception case: Re-test after a location change, staff handoff, schedule exception, feature unavailability, or source-data change that could invalidate the earlier decision.
- Escalation case: If the current interface or policy does not support the desired action, do not improvise a misleading workaround; document the exact behavior and use the official support or documentation path.
Frequently asked questions
Does an evidence file guarantee verification?
No. Google determines the verification method and whether the submitted evidence is sufficient.
Does a nameplate make a virtual office eligible?
A nameplate alone does not establish eligibility; the actual operating model must meet Google’s rules.
Should every document be uploaded publicly?
No. Store sensitive evidence securely and provide it only through official channels when requested.
When should the file be refreshed?
After a move, rebrand, ownership change, major service change, or profile discrepancy.
Official references
This guide interprets the official documentation below for operational use. Google features, interface labels, and eligibility may vary by category, country, account, and product changes. Verify the current guidance before acting.
- https://support.google.com/business/answer/7107242?hl=en
- https://support.google.com/business/answer/3038177?hl=en
- https://support.google.com/business/answer/3039617?hl=en
Editorial note: This guide does not guarantee ranking positions, verification outcomes, photo removals, or business results. Review the live profile and current official documentation before applying changes.