Google provides translated versions of our Help Center, though they are not meant to change the content of our policies. The English version is the official language we use to enforce our policies. To view this article in a different language, use the language dropdown at the bottom of the page.
Location assets allow ads to include a business address, phone number, and other information (e.g. business hours and ratings) about a specific business location.
Location assets and affiliate location assets are subject to the standard Google Ads policies, the policies for text, images and video, and the requirements below.
Google Business Profile (GBP) is commonly used to create and provide data for location assets in your Google Ads account. The information about your business and images of your location are managed in your GBP account directly, not in Google Ads. GBP is only available in certain supported countries.
Location owner approvalThe following is not allowed:
Physical location unavailableAdvertising a business location without the explicit approval of the business owner at that location
The following is not allowed:
Product or service not relevant to locationLocation specified is not recognized by Google.
- Example: Address: 555 Martian Road, Massachusetts, Maldives
Location specified is for a closed location.
The following is not allowed:
The location specified does not match the business running the ad.
Note: This restriction does not apply to affiliate location assets.
- Example:
- Advertiser is a bank in Florida and location specified is a bank in California.
The product or service in the ad isn’t sold or found at the location specified.
- Examples:
- Landing page is about refrigerators, location specified includes a supermarket chain that does not sell refrigerators.
- Landing page is about refrigerators, location specified is a massage parlor.
Learn how to fix a disapproved ad or extension. If you can’t edit the online location to meet this requirement, upload a different location that complies with the policy. If you disagree with our decision or have fixed your asset, you can appeal the policy decision directly from your Google Ads account (if available). Alternatively, you can dispute policy decisions using the Disapproved ads and policy questions form.
Related policies and common disapprovalsThe following Google Ads policies are especially relevant to this ad format and are often associated with disapprovals. Learn about what happens if you violate our policies.
EditorialThe standard requirements for clarity, correct spelling, and use of capitalization and symbols apply to all ads. See the Editorial policy for more information.
Misleading contentAll information should be accurate and descriptive of what you’re advertising. See the Misleading content policy for more information.
Unavailable offersProducts or services should be priced accurately, easily found at the ad's destination, and match with headers and descriptions. See the Unavailable offers policy for more information.
Unclear relevanceAll information should be relevant to what you’re advertising. For example, all submitted ad fields must represent the same advertiser and be relevant to the promoted product. Refer to the policy on
Unclear relevancefor more information.
For sitelinks, this means that link text should clearly and accurately indicate what kind of product, service, or other content is found at the link’s destination.
Unsupported languageAll ads and extensions must be written in a supported language and link to a destination in a supported language. See the Unsupported language policy for more information.
TrademarksGoogle may remove ads or assets in response to trademark owner complaints. Advertisers are responsible for proper trademark use in their ad text, assets, and business information. Refer to the
Trademarks policyfor more information.
Was this helpful?How can we improve it?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3