Google Ads guide

How to Set Up Google Ads Ad Assets for Local Businesses

To set up Google Ads ad assets for a local business, document the services, service area, branches, hours, capacity, and response path first. Then create text and visual assets that match the local offer, add location, call, booking, direction, navigation, or offer paths where eligible, and test the handoff through a qualified call, appointment, visit, or completed job.

Google’s ad-assets guidance explains the additional information and formats available to eligible campaigns. The platform decides when eligible assets can show; the business must keep local data, promises, and response routes accurate.

Document the local operating rules

Start with a single source for services, products, areas, branches, hours, holiday closures, capacity, staff, minimum job or order value, and response method. Mark whether the business serves a radius, selected postal areas, storefront visitors, delivery zones, or appointment-only customers.

For every branch or service theme, record:

  • the service or product available;
  • the area and location boundary;
  • address, phone, hours, parking, or directions;
  • booking, call, form, or visit path;
  • current offer and eligibility; and
  • owner and last review date.

These rules prevent a location asset or headline from promising work a branch cannot fulfill. They also make it easier to review local pages and phone routes when staff or hours change.

Map each campaign to a local promise

Create a message map for the campaign or asset group. Include service or problem, location or branch, customer type, benefit or process, proof, response expectation, and next action. Use city or neighborhood language only when the service area and destination support it.

Choose a promise the business can keep. A same-day statement requires capacity. A “free estimate” may require an on-site visit and may exclude certain jobs. A “24/7” message requires actual coverage. A location name should not imply a staffed branch if the business only travels there.

Keep separate groups for incompatible branches, services, or response paths. A broad local asset group can make a person believe the wrong team will answer their call.

Prepare text and visual assets

Write text variants for service, local fit, customer problem, process, proof, hours or appointment context, and action. Avoid repeating generic “contact us” language. Tell the right person what they can ask for and what happens next.

Use images or video showing the real storefront, team, work, product, facility, or service setting. Check that the visual is current, permitted, and representative of the branch or service. Do not show a specialist, location, certification, or result the business cannot support.

Review each asset for:

  1. service and local accuracy;
  2. branch or area relevance;
  3. readable mobile composition;
  4. current logo and brand identity;
  5. claims, permissions, and rights; and
  6. a destination that matches the promise.

For a multi-location business, use local visuals or details where they help a customer choose. For a service-area business, show the work and route rather than implying a storefront.

Configure call, booking, location, and direction paths

Where the campaign supports them, add call, location, booking, message, and navigation assets. Match the path to the business model. An urgent service may need a call. An appointment service may need a calendar. A store may need directions and opening hours. A quote process may need a form with service and location fields.

Test the path before publishing:

  1. phone reaches the correct branch or monitored line;
  2. hours and holiday messages are current;
  3. booking slots match capacity and service area;
  4. address, directions, parking, and branch details are correct;
  5. form fields support qualification without needless friction; and
  6. call, booking, direction, visit, and form events are measured once.

Do not advertise an unstaffed line, a closed branch, or a calendar that has no practical availability. If the business responds only during hours, say so.

Add navigation, service, and offer paths

Use sitelinks or related navigation for services, branches, service area, hours, pricing context, booking, directions, FAQs, proof, and contact where eligible. Match the route to intent. A service query should land on the relevant service. A local query should land on local information. An estimate request should explain the estimate process.

If using offer or price information, check service, customer eligibility, date, location, minimum value, and landing-page presentation. A local promotion may apply only to new customers or one branch. Avoid permanent urgency or a low headline price that omits required work.

Keep every destination live. Test on a phone and check that the page shows the right address, hours, service area, phone, booking, and response expectation.

Keep local asset groups coherent

Create a QA record for campaign, branch or service, area, audience, asset type, promise, destination, phone or booking path, owner, and review date. Use separate groups when service, branch, language, or response rules differ.

For automated formats, provide varied but consistent text and visuals. Read a representative combination together. A service, city, image, and link should not create a promise that no branch can fulfill. The platform may select eligible combinations; the business remains responsible for their meaning.

Refresh the record after a move, branch closure, opening hours change, phone change, staffing change, service launch, promotion, season, or capacity adjustment.

Measure qualified local outcomes

Track interactions, but evaluate qualified calls, booked appointments, attended visits, completed jobs, purchases, revenue, margin, capacity, and repeat customers. Google’s measurement guidance provides platform context; local phone, booking, point-of-sale, and job records explain quality.

If calls increase but qualification falls, inspect service, area, hours, and text. If bookings increase but attendance falls, inspect calendar, reminders, and expectation. If a good query reaches a missed call or closed page, fix the handoff before changing the asset.

Record asset, branch, service, hypothesis, launch date, owner, and review window. Note weather, local events, closures, promotions, and staffing so comparisons are fair.

Use the local-business Performance Max guide for wider context. adz.so can help inspect supported account data and organize the setup, but it does not answer calls, set a service boundary, schedule work, or verify local completion.

Local asset setup checklist

Before publishing, confirm that:

  1. service, area, branch, hours, capacity, and response rules are documented;
  2. text assets state a truthful local offer and next step;
  3. images, video, and logos reflect the real business and service;
  4. call, location, booking, message, form, and direction paths are tested;
  5. sitelinks lead to live services, branches, hours, and contact pages;
  6. offers, prices, qualifications, and trust claims are current;
  7. asset groups do not mix incompatible branches or promises;
  8. operations, web, media, call, booking, and analytics owners have reviewed; and
  9. success will be checked against qualified local outcomes.

Local assets are set up well when a person can tell what the business does, where it serves, when it can respond, and what to do next. Keep those facts current and let completed work guide future creative changes.