Original diagram by Citera. Setup references: Google Business Agent Help. This is an editorial workflow, not a reproduction of the Google interface.
A useful Google Business Agent setup starts with the correct account, approved business information, and a clear owner for support. The work is easier to review when each decision has evidence and someone responsible for it.
This checklist was researched on November 9, 2026. It follows Google’s documented setup routes and adds our recommended review process. We have not activated an agent in a retailer’s account for this article, and the illustrative copy below is not a measured conversion improvement.
Use the free audit workbook to track the checks and keep unresolved items visible. For the access requirements, read features and eligibility first.
Confirm the business and account owner
Write down the retailer name, storefront domain, Merchant Center account, and person who owns the launch. Check these against the account you have actually opened. Agencies and multi-brand operators should verify the selected business before changing identity or contact details.
The brand-profile claim is its own task. Google documents that super admin access is required to claim and manage the brand profile. A missing control can be an ownership or access issue as well as an eligibility issue. Route that question to the existing business owner instead of collecting passwords or creating duplicate accounts.
Our suggested launch record has four fields: the condition being checked, the observed state, an evidence link or dated screenshot, and the next owner. Keep this operational record private when it contains account details. Publish only the business information shoppers need.
Follow the setup route available to you
Google’s current setup instructions describe Merchant Center, eligible Shopify stores using the Google & YouTube app, and management through the brand profile in Search. Menu labels and availability can change, so follow the controls shown in your account.
For Merchant Center, the documented route is Marketing → Business Agent → Customize. Review the available identity settings, preview the result, save, and use the control to turn on the customized agent when the responsible owner is ready.
For Shopify, Google’s guide describes a Business Agent recommendation card in the Google & YouTube app. Review the imported brand and support information, the preview, and the applicable terms before publishing. The guide directs advanced customization back to Merchant Center. The presence of Shopify alone does not establish that a store qualifies.
If you manage the experience from Search, confirm that the brand result and management controls belong to the intended retailer. Do not confuse these controls with those for a local Google Business Profile.
Prepare the identity fields before editing
Draft the wording in a shared review document so the interface session is used to apply approved decisions. Do not promise services, availability, or response times that the retailer cannot provide.
Setting | Review question | Example of a useful check |
|---|---|---|
Greeting | Does it explain what shoppers can ask? | Avoid implying access to private orders |
Conversation starters | Do they lead to useful shopping questions? | Ask about sizes, care, or product differences |
Tone | Does it fit the site’s current language? | Remove unsupported superlatives and guarantees |
Colors and appearance | Is the preview readable? | Check text contrast and brand consistency |
Support contact | Does it reach the correct team? | Open the destination and verify the contact details |
An illustrative greeting for a fictional bag store is: “Ask about dimensions, materials, or care. For an existing order, contact our support team.” Adapt that only if the retailer provides those information categories and an appropriate support route.
Review the preview and public experience
Treat preview approval and answer testing as separate checks. The first checks the configured identity. The second checks what a customer actually receives when asking questions.
In the preview, proofread the greeting, inspect the suggested questions, and verify the displayed support details. Ask the support owner to confirm that any link or contact route is intended for public use. Record the approval date and the version of the copy being applied.
After publication, inspect the experience as a shopper where it is available. Save the date and visible environment. Test an ordinary product question, a question that depends on a policy exception, and a request for human help. If the result differs from the preview, record that observation rather than treating configuration as proof of the public result.
Use the answer testing and support handoff guide for a repeatable review. The suggested tests are a quality-control workflow, not Google’s certification procedure.
Handle a missing control or failed check
If Business Agent is missing, return to the specific prerequisite that is unresolved. Confirm the selected account, brand-profile ownership, current customization criteria, and actual account availability. Keep the exact message or missing option in your issue record.
If the identity is correct but answers are weak, review the information behind the answer. An unclear sizing page needs a content owner. A stale price needs the appropriate product-data owner. Repeatedly changing the greeting is unlikely to resolve either problem.
Finish the setup with an owner and a review trigger. A policy update, catalog migration, support-address change, or new market is a reason to review the experience again. Keep the website and Merchant Center data checklist alongside the launch record so maintenance continues after the initial setup.
