Google Business Profile Before Opening: A Practical Launch Plan

A new location may be searched before its doors open. A careful pre-launch profile can help people understand when and where the business will operate, but it must represent a real eligible business—not a speculative listing created to reserve a keyword.

Confirm eligibility before creating a profile

Establish the real operating model first: customers visiting a staffed location, a service-area business travelling to customers, or another eligible setup. A mailbox, virtual office, or unstaffed desk should not be represented as a storefront simply because it receives mail. Confirm the public-facing name, actual address, ownership, and customer contact path. Keep verification evidence securely stored and ensure the business—not only an agency—retains appropriate access.

Use the future opening date honestly

Google allows eligible businesses to enter a future opening date up to one year ahead; after verification, the profile can appear 90 days before opening. Enter the expected month and year supported by the actual plan. If construction, permits, or staffing change the date, update it and revise connected posts and booking pages. Do not use the future date as a way to collect reviews before genuine customer experiences exist.

Build a launch checklist around real customer tasks

Add the accurate category, address or service-area configuration, phone, schedule, and a concise factual description. Use real photos as the premises become representative. Create a useful location page that agrees with the profile. Before launch, test directions, entrance instructions, phone routing, booking availability, and any promised service from a mobile device. The first month should be treated as a feedback loop: recurring questions about parking or appointments point to information gaps worth fixing.

Recommended workflow

1. Review the real operating facts for before opening: a practical launch plan.
2. Check the current official Google guidance and confirm feature availability.
3. Make only the supported, evidence-based profile change.
4. Test the public profile and the connected customer journey on mobile.
5. Record the owner, date, and next review trigger.

Operational QA matrix

Checkpoint	What to inspect	Pass condition
Confirm eligibility before creating a profile	Establish the real operating model first: customers visiting a staffed location, a service-area business travelling to customers, or another eligible setup.	The public profile and the real operation agree; record any exception and its owner.
Use the future opening date honestly	Google allows eligible businesses to enter a future opening date up to one year ahead; after verification, the profile can appear 90 days before opening.	The public profile and the real operation agree; record any exception and its owner.
Build a launch checklist around real customer tasks	Add the accurate category, address or service-area configuration, phone, schedule, and a concise factual description.	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 physiotherapy clinic expects to open in six weeks. It verifies the actual address, sets a realistic opening month, and publishes confirmed appointment information. When a contractor delay pushes the opening back, the owner updates the date and removes a post that promised appointments too early.

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

Can a business create a profile before opening?

Eligible businesses can set a future opening date; the profile can appear 90 days before opening after verification.

Can I ask for reviews before launch?

Do not ask for reviews from people who have not had a genuine customer experience; follow Google’s pre-opening guidance.

What if the date slips?

Update the date and every connected promise, including posts, booking pages, hours, and ads.

Are construction photos acceptable?

They can help if they truthfully show progress; replace them when finished premises are available.

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/9174409
• https://support.google.com/business/answer/3038177?hl=en
• https://support.google.com/business/answer/7107242?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.