Template
Google Business Profile verification attempt log
When Google asks you to verify a Business Profile again, record the exact reverification signal, the changed field and its before value, who observed or submitted the event, and the Google Account context. Keep the original attempt fields, then make a separate owner-view, Google Search, and Google Maps follow-up with its own timestamp, result, evidence, and next check. This is a local recordkeeping template, not a Google form. Google determines the available verification methods, and some profiles may need more than one method.1
Use the Google Business Profile verification answer for setup and method steps. Use the video-verification preparation guide for Business video. Use the verification-pending breakdown to separate ordinary review from rejection, a missing method, postcard delivery, or re-verification.
Read moreShow less
By Sergey Sulimko, Founder · · 6 Google help pages, read Oct 21 - Nov 2, 2026
| What you need | Jump to the record or rule |
|---|---|
| Copyable attempt record | Copy the Google Business Profile verification attempt record |
| Reverification handover | Record the reverification trigger and before state |
| Public-state follow-up | Copy the separate public-state follow-up record |
| Field-by-field guidance | What should I record in each field? |
| Method and evidence rules | How should I record the method and evidence? |
| Status and next action | How should I choose the next action and check date? |
| Filled example | What does a completed record look like? |
| Use and follow-up | How should I use this log after each attempt? |
| Boundaries | What should I not do with this log? |
Show all 9 rows
The Google Business Profile verification attempt record
Copy this block once for each attempt. Keep the method offered, the evidence shown or submitted, and the exact status or error as separate fields.
Google Business Profile verification attempt record
Attempt number: [1]
Business Profile name / location: [business name, city or service location]
Profile URL or local identifier: [URL or identifier, if available]
Reverification handover context
Changed field: [exact field changed, or not captured]
Value before change: [exact value before the change, or not captured]
Value submitted or current: [exact value saved or shown after the change]
Changed by: [local actor or team role, if known]
Change submitted at: [YYYY-MM-DD HH:MM, time zone]
Reverification signal observed at: [YYYY-MM-DD HH:MM, time zone]
Exact reverification signal: [copy the button, notice, or status exactly, such as
Get verified,Give additional info to re-verify, orReview issues]Trigger surface: [owner profile view, Search, Maps, or another exact surface]
Google Account that observed the signal: [account label or email, no password]
Google Account that submitted the attempt: [account label or email, no password]
Account context: [linked account confirmed / not confirmed / not checked]
Google Account used: [account label or email, no password]
Business Profile ID: [ID, if visible]
Attempt date and time: [YYYY-MM-DD HH:MM, time zone]
Event recorded: [started / submitted / code entered / video uploaded / other]
Method Google offered: [exact label shown, or no method offered]
Method destination or access check: [masked phone, email label, or mailing-address note; access confirmed / not confirmed]
Evidence shown or submitted: [what was shown or submitted, or Not applicable]
Exact status or error text: [copy the current screen text exactly]
Support reference: [Business Profile ID and any case or interaction reference Google supplied]
Next allowed action: [action allowed by the current screen or Google guidance]
Next check date: [YYYY-MM-DD]
Why this date: [method-specific window or your reason for checking]
Notes and source link: [what changed, what was shown, or the official Help URL]
Public-state follow-up record
Profile identifier: [business name, location, profile URL, or local identifier]
Changed field checked: [one exact field]
Surface: [Owner view / Google Search / Google Maps; copy one record per surface]
Query or path: [exact Search query, Maps query or app path, or owner path]
Device and account context: [device, browser or app, signed-in state, and location context when relevant]
Checked at: [YYYY-MM-DD HH:MM, time zone]
Public or returned value: [exact value observed, or not visible]
Owner-side result: [exact edit status or Google update signal, if checked]
Evidence: [profile URL, status view, notification, screenshot, or saved record]
Next check: [YYYY-MM-DD HH:MM, time zone]
Next action and owner: [recheck, record, correct, appeal, or close-out action; responsible role]
The bracketed values are for your record. This page does not claim that Google requires this exact field set. Do not put a password or verification code in the log. Google says it will not ask for the verification code and that the code should not be shared, including with people who manage the profile.1
Reverification handover context
Record the changed field and the value before the change before you retry verification. Copy the exact signal that appeared and keep the change-submission time separate from the time the signal was observed. Google describes repeated Get verified and requests for additional information as verification signals, while its edit guidance makes some changed-field triggers conditional.1,2,3
| Handover field | What to record | Boundary to keep |
|---|---|---|
| Changed field | One exact field, such as business name, address, category, or another profile field. | Google documents conditional triggers for some fields. Do not write that every edit causes reverification.2,3 |
| Value before change | The exact value visible before the edit, or not captured. |
Do not reconstruct the value from memory or from the later public profile. |
| Value submitted or current | The exact value saved or shown after the edit. | Keep the owner-submitted value separate from any later Search or Maps value. |
| Actor and account roles | Who changed the field locally, which Google Account observed the signal, and which account submitted the attempt. | Use a local role or account label. Do not claim that Google exposes the person's identity. |
| Account context | Whether the Google Account linked to the Business Profile was confirmed, not confirmed, or not checked. | Never record a password or verification code. Google requires the linked account for editing profile information.2 |
| Trigger timing and surface | Local timestamps for the change and signal, plus the exact surface where the signal appeared. | These are local observation times, not Google's processing or completion times. |
The actor and account fields may name the same person or account, but keep their roles separate when one person observes the signal and another submits the attempt. The verification method remains an observed value. Google determines which methods are available, and the owner cannot switch to a method the profile does not offer.1
Public-state follow-up record
Create a separate follow-up for the owner view, Google Search, and Google Maps after the owner-side event. Copy one record per surface so the query or path, context, timestamp, returned value, evidence, and next check cannot be mistaken for another surface's observation.
| Follow-up field | What to record | Boundary to keep |
|---|---|---|
| Profile identifier and changed field | The profile and one exact field being checked. | Keep the field tied to the reverification handover; do not merge several changed fields into one result. |
| Surface | Owner view, Google Search, or Google Maps. |
Search and Maps are separate surfaces. Do not copy one surface's result into the other.2 |
| Query or path | The exact Search query, Maps query or app path, or owner path. | A public read-back records what appeared for that check. |
| Device and account context | Device, browser or app, signed-in state, and location context when relevant. | Preserve the context needed to repeat the observation. |
| Checked at | The local date, time, and time zone. | This is an observation time, not Google's change time or a public propagation deadline. |
| Public or returned value | The exact value shown, or not visible. |
Do not turn the observation into a ranking, causal, or AI-inclusion claim. |
| Owner-side result | The exact owner edit status or Google update signal, if checked. | Keep Accepted, Pending, or Not approved separate from reverification signals and public values.4 |
| Evidence, next check, and owner | The saved evidence, the next local check time, and the responsible role or action. | A local next check is a follow-up plan, not a Google deadline. |
The Google Business Profile public read-back checklist provides the separate Search and Maps record structure. Use it for the public observation, while this page preserves the verification attempt and its exact method-specific result.
What should I record in each field?
Use one row for one attempt or submitted method. Google says you must sign in to the Google Account associated with the profile and can find the profile by searching the business name and city or my business.1
| Field | What to write | Why it matters |
|---|---|---|
| Attempt number | A local sequence such as 1, 2, or 3. |
This is a local recordkeeping field, not a Google status. |
| Changed field and before state | The exact field changed, its value before the change, and the value submitted or shown after it. | Do not infer the before value from a later public result. |
| Reverification signal and timing | The exact signal, the surface where it appeared, and separate local timestamps for the change and observation. | Get verified, additional-information instructions, and Review issues are distinct observable states.1 |
| Actor and Google Account roles | The local actor, the account that observed the signal, the account that submitted the attempt, and linked-account context. | Use labels without passwords or verification codes. |
| Business Profile name / location | The business name, city or service location, and profile URL or local label when available. | The context helps you distinguish profiles with similar names. It is a local record, not a Google status. |
| Google Account used | The signed-in account label or email used for the attempt. Never record its password. | Google says the account must be associated with the Business Profile.1 |
| Business Profile ID | The ID if it is visible in the profile's advanced settings. | Google describes it as the listing's unique identifier and says it can be shared with Google support.5 |
| Attempt date and time | When the relevant event happened, with the time zone if known. | Label the event accurately, such as submitted or video uploaded. Do not turn a local timestamp into a claim about when Google completed its review. |
| Event recorded | The event that happened: started, submitted, code entered, video uploaded, or another precise event. | This keeps the review window tied to the completed step instead of the first time you opened the screen. |
| Method Google offered | The method label exactly as shown, such as Phone, SMS, Email, Live video call, Business video, Postcard, or Mail. |
Google automatically determines available methods. The owner cannot switch to a method that Google has not offered.1 |
| Method destination or access check | A masked phone number, email label, or mailing-address note, plus whether you could access it. | Phone or SMS needs access to the business phone or texts. Email uses the address displayed on the verification screen.1 |
| Evidence shown or submitted | What you showed or submitted, or Not applicable for a code or email step. |
The field records what happened. It does not prove why Google accepted or rejected the attempt. |
| Exact status or error text | Copy the current button, notification, or error text exactly. | Get verified, Review issues, and a request for additional information describe different observable states.1 |
| Support reference | The Business Profile ID and any support case or interaction reference Google actually supplied. | Keep the source-backed profile identifier with the interaction. A case number is optional unless Google gives you one.5 |
| Next allowed action | The action allowed by the current screen or Google's guidance, such as Follow on-screen instructions, Re-verify, or Contact support. |
Do not tell yourself to choose a method that the profile does not display. |
| Next check date | A date you choose for checking the current status again. | This is a planning date, not a Google deadline. Record why the date fits the method. |
| Notes and source link | A short note about what changed or what you showed, plus the official Help URL that explains the method or status. | Keep the evidence row-specific so later attempts can be compared without reconstructing the history. |
Show all 17 rowsShow fewer rows
For a separate owner, Search, or Maps follow-up, use the public-state follow-up record and keep its checked-at timestamp, returned value, evidence, and next check separate from the attempt's Attempt date and time. A submitted edit and a public value are different observations.
How should I record the method and evidence?
Record the method Google shows at that moment. Availability can depend on the business type, public information, region, or business hours, and Google may require more than one method.1
| Method shown by Google | Record in the row | Boundary to keep with the record |
|---|---|---|
| Phone or SMS | The exact method label, the masked destination, whether the call or text was accessible, and the submission or code-entry event. | An Interactive Voice Response system will not receive the code. Do not record a code itself.1 |
| The exact label, the email address label displayed on the verification screen, and whether the instructions were completed. | The address must be the one shown in the verification screen.1 | |
| Live video call | The call date and time, the location and business or equipment shown, and the management proof shown. | Live video may not be available for every business and is available only during the location's business hours.1 |
| Business video | The live recording and upload events, the evidence groups shown, and any result or issue text. | Use the Business video preparation guide for the recording requirements. Do not use this row as a substitute for the video evidence checklist. |
| Postcard or Mail | The exact method label, the mailing address confirmed, the request or submission date, and whether the code arrived or was entered. | Most codes arrive within 14 days and expire after 30 days. Keep the business name, address, and category unchanged while the code is in the mail, and do not request a new code while waiting.1 |
| Search Console or bulk verification | The method or condition shown, the event that completed it, and the result. | Google names these as cases where instant verification may happen. Do not treat instant verification as a general option.1 |
For live video, the evidence field can name the three groups Google describes: the current location, the business or its equipment, and proof of management. Examples include an outside sign or street sign, products or branded equipment, and an employee-only area, cash register, kitchen, storage room, non-sensitive business document, or key. These are examples for the live-video path, not requirements for every method.1
How should I choose the next action and check date?
Choose the next action from the status on screen. Choose the check date yourself, then write the method and the reason beside it. Google gives method-specific windows, not one deadline for every verification attempt.
| Exact status or situation | What to do next | Timing to record |
|---|---|---|
| A method was completed and no failure or rejection is shown | Check the current verification status and follow the current on-screen instruction. | Google says verification reviews take up to 5 business days after the verification steps are complete, and rare reviews may take longer. This is not a completion guarantee.1 |
Get verified appears again |
Try to verify again. Use another method only if the profile displays one. | Record the prompt separately from a pending review. Google says the business was not completely verified.1 |
Review issues appears after a video |
Select Review issues, read the displayed instructions, and record what the next video must address. |
Treat this as a video result, not ordinary pending review.1 The verification-pending breakdown shows the separate branch. |
| Google asks for additional information to re-verify | Select Get verified, review the requested information, and follow the current steps. |
Do not invent a deadline. Google says this request is likely related to recently updated business details.1 |
| No verification method is offered | Confirm the profile and account, then use the support route Google displays when available. | Record that no method was submitted. The owner cannot add a method manually.1 |
| A postcard is in the mail | Leave the business name, address, and category unchanged. Do not request another code while the current one is in transit. | Most codes arrive within 14 days, but that is not a promise for every code. Codes expire after 30 days.1 |
The ordinary five-business-day review statement belongs after a completed verification step. It does not replace the delivery wait for a postcard, the access check for phone, SMS, or email, or the business-hours condition for a live video call.1
What does a completed record look like?
This fictional example shows the level of detail to preserve. It is an example of this template and does not represent a real business.
| Field | Completed example |
|---|---|
| Attempt number | 2 |
| Business Profile name / location | Northside Plumbing / Austin, TX |
| Changed field | Business category |
| Value before change | Plumber |
| Value submitted or current | Drainage service |
| Changed by | Taylor Reed, owner |
| Change submitted at | 2026-10-20 16:05, Central Time |
| Reverification signal observed at | 2026-10-20 16:12, Central Time |
| Exact reverification signal | Give additional info to re-verify |
| Trigger surface | Owner profile view |
| Google Account that observed the signal | Taylor's Google Account |
| Google Account that submitted the attempt | Taylor's Google Account |
| Account context | Linked account confirmed |
| Profile URL or local identifier | Profile URL saved in the business's private records |
| Google Account used | Taylor's Google Account |
| Business Profile ID | BP-ID-EXAMPLE-2741 |
| Attempt date and time | 2026-10-21 14:20, Central Time |
| Event recorded | Video uploaded |
| Method Google offered | Business video |
| Method destination or access check | Mobile device access confirmed |
| Evidence shown or submitted | Location: storefront sign. Business: branded equipment. Management: cash register. |
| Exact status or error text | Review issues |
| Support reference | Business Profile ID recorded; no support case reference supplied |
| Next allowed action | Select Review issues and follow the displayed instructions |
| Next check date | 2026-10-22 |
| Why this date | Check the displayed video issue before recording a replacement |
| Notes and source link | Fictional example. Add the official Google Help URL used for the row. |
| Public-state follow-up — surface | Google Search; copy a separate record for Google Maps |
| Public-state follow-up — query or path | Northside Plumbing Austin |
| Public-state follow-up — checked at | 2026-10-22 09:10, Central Time |
| Public-state follow-up — returned value | Category not visible in the Search profile view |
| Public-state follow-up — owner-side result | Review issues |
| Public-state follow-up — evidence | Search screenshot and owner status screenshot |
| Public-state follow-up — next check | 2026-10-23 09:10, Central Time |
| Public-state follow-up — next action and owner | Recheck Search and Maps separately; owner: Taylor Reed |
Show all 35 rowsShow fewer rows
The example keeps the uploaded event, evidence, and status separate. That separation lets a later reader tell a rejected video from a review that is still pending.
How should I use this log after each attempt?
- Before retrying, record the exact reverification signal, changed field, before value, local actor, account roles, and separate change and observation times.
- Copy a new record before the attempt when possible. Otherwise, create it immediately after the event.
- Record the exact method Google offered, the destination or access check, and the event that actually happened.
- Copy the status, notification, or error text exactly. Do not replace every result with
failed,pending, orcomplete. - Write the next action only after reading the current screen and the relevant verification guidance. If the screen shows Business video, use the video-verification preparation guide for that method.
- Add a separate owner-view, Search, and Maps follow-up with its own context, timestamp, returned value, evidence, next check, and owner. Do not merge the public observation into the attempt status.
- Add a next check date and state its reason. If the status changes, add the new check to the row's notes without erasing the original status or event.
- If the issue is a missing method or an unchanged status, use the verification-pending breakdown to choose the matching branch instead of restarting a method at random.
What should I not do with this log?
| Do not | Do instead |
|---|---|
| Treat this layout as a Google-required form or history. | Use it as a local record and mark a field Not applicable when the method does not use it. |
| Choose a phone, email, video, or postcard method because you prefer it. | Record and use the method Google displays for that profile.1 |
| Turn an absent status into a diagnosis. | Record No status shown as your observation and follow the current screen. |
| Apply the five-business-day review window to a postcard's delivery or to an unsubmitted method. | Name the method and event before choosing a check date.1 |
| Request a new postcard as a generic recovery step. | Keep the business name, address, and category unchanged while the current code is in the mail.1 |
| Put a password or verification code in the record. | Use an account label, a masked destination, and the Business Profile ID. Google says the verification code should not be shared.1 |
| Create a second profile because the current profile has no method. | Confirm the profile and account, then use Google's current add, claim, or support path. Google's add-or-claim guidance separates a new profile, an unverified claim, and an ownership request.6 |
Maps Agent service
Where your profile stands now
Visibility Score 0-100 · 20 scored factors · free · no signup
- Profile Completeness
- 11 checks · 40% of score
- Performance
- 4 checks · 35% of score
- Competitive Position
- 5 metrics · 25% of score