Google Business Profile Bulk Verification: A Practical Guide

Managing several locations creates two separate tasks: keeping the location data organised and obtaining the right verification status. A spreadsheet can help with the first, but its upload should not be mistaken for completion of the second. The difference matters when a chain is planning openings or an agency is taking over a fragmented account.

This guide explains how I would prepare a multi-location business for bulk verification. The aim is a clear location inventory, accurate data and a request that reflects the real organisation. Google reviews verification requests, so preparation should not be presented as a guaranteed approval or a fixed completion date.

Check eligibility before building the project around bulk verification

Google’s bulk verification guidance requires at least 10 profiles from the same business. Duplicate, suspended and disabled profiles do not count towards that minimum. Service-area businesses are excluded, and an agency cannot qualify by combining several different businesses in one account. The account must have no errors, and its profiles must accurately reflect the business’s size.

Begin with the real operation, not a target profile count. List the locations that actually exist and identify how they relate to the same business. Do not create speculative locations or retain duplicates to reach a threshold.

For an agency, distinguish a client’s chain from your overall portfolio. Twenty profiles across twenty unrelated clients describe an agency workload, not a single business with twenty eligible branches. Set the verification plan for each business according to its own situation.

If a chain is close to the threshold, identify exceptions early. A location that is suspended or duplicated needs its own diagnosis. Removing those exceptions from the eligible count can change which verification route is available, even when the raw account contains more than ten rows.

Create a location inventory first

I recommend one working row per real location before preparing an upload. Include an internal reference, public Maps link, current business information, ownership state and operational status. Keep notes about exceptions in their own fields so a reviewer can distinguish facts from proposed actions.

For example, separate “operating and unverified” from “already verified by another account,” “duplicate under review” and “closed branch.” Those statuses describe different work. A single label such as “not ready” hides the reason and makes it harder to assign the next step.

Ask a responsible person at each location to confirm its address, phone, hours and website destination. Head-office records can be outdated after a move or a local schedule change. Local confirmation helps identify those discrepancies before they are repeated across a bulk update.

Also record the actual chain size and any known gap between that size and the profiles in the account. A business with more operating branches than managed profiles should be able to explain the difference. Do not leave the account inventory disconnected from the real organisation.

Review existing profiles before creating new ones

Search for the existing business records and record the relevant Maps links. Some branches may already have profiles created by local staff, previous agencies or other authorised representatives. Start by establishing that history rather than assuming every unlisted row in your dashboard is a new public location.

Google’s bulk guidance says profiles claimed by someone else require an access request. Verification at account or group level does not automatically override another person’s ownership. Make these profiles a separate workstream with their own access notes and responsible person.

For suspected duplicates, compare the operating identity and location history. Decide which record is intended to remain, then use the appropriate duplicate route. Do not insert a third listing into the account merely because the first two are difficult to manage.

If the business has moved a branch, write down the chronology. An old address and a new address can look like two locations in a spreadsheet even when only one operation continues. The inventory should reflect the business history, not just the number of search results.

Prepare a clean source of location data

Keep an approved data sheet as the working source for the project. For each location, identify who confirmed the information and when. A date is useful because business data changes: the correct hours in January may be wrong by the time a verification project resumes in April.

Use fields that the team can understand consistently. Distinguish a public branch name from an internal office code, the customer phone from an escalation contact and regular hours from planned holiday hours. Ambiguous columns invite ambiguous profile edits.

Review the website destinations too. A branch profile pointing to a closed location page or the wrong branch can confuse customers even if the address field is accurate. The website team and profile team should agree which page represents each operating location.

Do not standardise genuine differences away. Two branches may have different hours, accessibility information or service availability. A consistent data process means those differences are verified and intentional; it does not mean every profile should contain identical values.

Use the current Google spreadsheet template

Google’s bulk spreadsheet instructions provide the template through Business Profile Manager → Add profile → Import profiles. Use the template for the relevant language and the current field guidance. Each location needs its own business code. Google also warns that including a column with a heading and empty cells can delete existing information for that column during an update.

That empty-cell warning is important for maintenance work. Before an upload, identify whether the file is adding locations or updating selected fields. Do not send a broad, partly empty template when the intended task is only a narrow change to existing records.

Keep a reviewed copy of the upload and its purpose. Record which fields are meant to change and which locations are included. When someone asks why a value disappeared, the exact file and an explicit change plan are much more useful than an unsaved spreadsheet edited by several people.

For different countries or regions, review the applicable address format rather than forcing every address into the same domestic pattern. Ask someone familiar with the location to confirm the final representation, especially when a building, unit or postal detail affects how customers find the premises.

Separate import checks from the verification request

Uploading the data is a preparation step. Inspect the account for errors and verify that the intended existing records and new locations are represented correctly. If an upload adds something unexpected, investigate before treating the import as approved project data.

Google’s current verification route is Business Profile Manager → Verifications → Chain → Start, followed by the form and submission. If the Verifications tab is unavailable, the account may not have enough eligible profiles; Google directs businesses to individual verification in that situation.

Record the submission separately from the upload. Your project log should make it possible to answer: when was the data imported, which errors were resolved and when was the verification request actually sent? Those milestones should not share an unexplained “done” label.

Keep the recipient of Google’s follow-up available. If more information is requested, assign the response to a person who can coordinate with head office and locations. A verification project can stall when the account email is monitored by nobody with authority to obtain the requested facts.

Prepare for evidence and local coordination

Google may require additional verification, including video evidence with an authorised representative at the location. Treat that as a logistical requirement to prepare for, rather than assuming central submission removes every need for branch participation.

Identify a local contact who understands the premises and can explain the operating business. Give them a short briefing on the task and the information already confirmed. Do not send them a generic instruction to “verify Google” without telling them which profile and account the project concerns.

I would maintain an evidence index, not an unlabelled folder of images. Each item should have a purpose: identifying the business, connecting it to the premises or explaining the organisation. Avoid collecting unrelated staff or customer information just because a document is available.

If a follow-up request is unclear, read it carefully and respond to the specific point. A large attachment bundle is not automatically more persuasive than a concise answer with the relevant evidence. Keep the business facts consistent with the approved inventory.

Example: a chain with twelve records and several exceptions

Imagine a chain with twelve profiles in an account. One is a duplicate, one is suspended and another belongs to a closed branch. The raw count does not establish bulk eligibility. I would confirm the active locations, categorise the exceptions and calculate the eligible count from the real situation.

The duplicate needs a relationship review, the suspension needs its own compliance and appeal assessment, and the closed branch needs accurate closure handling. None of those tasks should be disguised as a normal new location in the upload.

Head office also confirms whether operating branches are missing from the account. If a missing branch is already claimed elsewhere, the next step concerns access to that existing record. If it genuinely lacks a profile, evaluate the appropriate creation and verification route.

The final project plan may include both central data cleanup and individual location work. That is a useful outcome of the eligibility review. Forcing everything into one bulk request would hide the exceptions rather than resolve them.

Example: an agency managing unrelated clients

An agency may manage thirty profiles and still have no single client that qualifies for bulk verification. I would organise its records by business, keep ownership and verification notes for each client and avoid treating the agency’s total as a chain size.

For a client with several eligible branches, assess that business independently. For a service-area client, follow the applicable individual guidance. The account organisation should help people understand the clients and tasks rather than imply a relationship that does not exist.

This distinction also belongs in proposals. An agency should describe what it will review and prepare without promising a bulk outcome merely because its portfolio is large. A specific eligibility assessment is more credible than a generic claim that every multi-location account can be verified together.

Maintain the account after verification

Successful verification is not the end of location-data work. Assign responsibility for new openings, closures, moves and changes to business information. A chain can quickly accumulate contradictory records if head office and branch staff update different sources without coordination.

Google’s guidance recommends reviewing account errors and updating profiles to maintain bulk verification. It may de-verify inactive accounts or change status when requirements are not met. Monitor the account email and make status changes part of the team’s normal operating review.

I recommend a recurring location audit based on the pace of the business. Review active status, public contact information, ownership exceptions and unresolved cases. Keep the audit practical: identify what is wrong, who will correct it and how the result will be checked.

For a bulk edit, test the source data and review the intended fields before upload. Afterwards, inspect representative locations and any known exceptions. The larger the dataset, the more important it is to distinguish approved data from an accidental spreadsheet change.

Preparation checklist

• Confirm at least ten eligible profiles from the same real business.
• Exclude duplicates, suspended and disabled profiles from the qualifying count.
• Check that the business type fits bulk eligibility.
• Inventory every managed location and explain ownership exceptions.
• Confirm business data with head office and local contacts.
• Use the current template and review empty-cell effects.
• Resolve account errors and submit verification separately from import.
• Assign follow-up, local evidence and ongoing maintenance responsibilities.

Common questions

Does uploading a spreadsheet verify the locations?

No. Keep the upload and verification request as separate milestones. Review the resulting records and errors before applying through the available verification flow.

Can an agency combine clients to reach ten profiles?

No. Evaluate the qualifying business itself. An agency portfolio and a chain of the same business are different arrangements, even if both involve many profiles.

How long will bulk verification take?

I would not promise a fixed duration. Plan for review and possible information requests, keep the relevant people available and track the actual status. Preparation improves clarity but does not control Google’s review timetable.

Need help preparing a multi-location account?

I help owners and agencies review location inventories, access exceptions and Google Business Profile verification preparation. Send a short description of the business, its operating-location count and the account issues you already know about.

Request a multi-location profile review, or explore my ongoing Google Business Profile management for the maintenance work after the initial setup.