Google Local Services Platform Policies Renamed to Local Services Ads Requirements (2026)

The short version

Google renamed its Local Services Platform Policies to Local Services Ads Requirements in June 2026, with the change taking effect on July 6, 2026. The underlying advertising rules for background checks, license verification, insurance, and review standards did not change — only the terminology and where the documentation lives. This is part of Google’s broader consolidation of Local Services Ads (LSAs) into the main Google Ads platform, which includes retiring the standalone LSA dashboard and making LSAs available through Performance Max campaigns.

Key facts

• The rename from “Local Services Platform Policies” to “Local Services Ads Requirements” took effect July 6, 2026
• No substantive policy rules changed — only the name and URL location of the documentation
• The policy docs moved from localservices.google.com to support.google.com/google-ads
• This is one piece of a larger LSA-to-Google-Ads platform migration happening throughout 2026
• Affected advertisers: home services, legal, healthcare, real estate, and all other LSA-eligible verticals

What happened

In early June 2026, Google quietly began updating its Local Services Ads documentation, rebranding the “Local Services Platform Policies” as “Local Services Ads Requirements,” according to Search Engine Roundtable’s coverage on June 8, 2026 Search Engine Roundtable. The change went live across all Google support properties by July 6, with ALM Corp providing a detailed breakdown of what advertisers needed to know ahead of the deadline ALM Corp.

The rebranding is cosmetic — no policy rules around background checks, license verification, insurance minimums, review solicitation, or service-area accuracy changed. Google simply moved the policy pages from the standalone localservices.google.com domain to the main Google Ads Help center at support.google.com/google-ads, reflecting the platform’s broader strategy of folding LSAs into the core Google Ads ecosystem.

Why did Google rename the policies?

The answer is consolidation. Throughout 2026, Google has been systematically migrating Local Services Ads into the Google Ads platform. Search Engine Land reported that LSAs are now available through Google Ads via Performance Max campaigns Search Engine Land, and JumpFly confirmed that “Local Service Ads (LSAs) Are Shifting To Google Ads” as part of a multi-phase platform transition JumpFly.

The renaming is the logical next step — when the policies live under support.google.com/google-ads instead of a standalone domain, calling them “Local Services Platform Policies” no longer makes sense. “Local Services Ads Requirements” accurately describes what they are: the requirements for running Local Services Ads from within the Google Ads ecosystem.

Who is affected, and what actually changed?

Every business running Local Services Ads is affected by the rename in the sense that the documentation URL you bookmarked has moved. But operationally, nothing changes for your active campaigns.

The change is entirely navigational and terminological:

• Old name: “Local Services Platform Policies”
• New name: “Local Services Ads Requirements”
• Old URL: localservices.google.com domain
• New URL: support.google.com/google-ads domain
• Policy substance: Unchanged

MediaPost reported on July 20, 2026 that “Google Local Ads For Services Transitions Into Wider Campaign Platform,” confirming that the policy rename is one element of a platform-level migration MediaPost. The standalone LSA dashboard is being retired starting August 2026, with EIN Presswire noting that third-party tools like CallRadius have already added migration safeguards to help advertisers transition EIN Presswire.

What this means (our take)

This rename signals that LSAs are no longer a separate platform — they’re a campaign type inside Google Ads, governed by the same help center and navigational structure as Search, Performance Max, and Demand Gen.

Practically, this means:

1. Update your bookmarks. The old localservices.google.com policy pages redirect. Train your team to find the Requirements under the Google Ads Help center.
2. Prepare for the dashboard retirement. The hard change is the LSA dashboard going dark in August 2026. Learn about the broader migration here.
3. The rules haven’t loosened. The “requirements” label reinforces that background checks, license verification, and review policies remain mandatory, not optional.

What to do now

1. Navigate to the new policy location. Open Google Ads → Tools & Settings → Local Services Ads → Requirements. Verify your business still meets every listed requirement.
2. Audit your LSA profile for policy compliance. Even though the rules didn’t change, a manual audit is good practice during any platform migration. Check your license expiration dates, insurance coverage amounts, and service-area accuracy in Google Business Profile.
3. Set up LSA management in Google Ads. If you’re still using the standalone LSA dashboard, explore how LSAs integrate with Performance Max and begin transitioning your workflows. The dashboard retirement in August 2026 means the clock is ticking.
4. Monitor the Google Ads blog for further changes. The LSA migration is ongoing. Google is shipping changes throughout 2026 — budget controls, bidding options, and reporting features are all evolving as the platforms merge.

FAQ

Sources

• Search Engine Roundtable — Google Local Services Platform Policies Now Local Services Ads Requirements (June 8, 2026)
• ALM Corp — Google Will Update Its Local Services Ads Policies on July 6 (June 2026)
• Search Engine Land — Local Services Ads come to Google Ads via Performance Max
• JumpFly — Local Service Ads (LSAs) Are Shifting To Google Ads
• MediaPost — Google Local Ads For Services Transitions Into Wider Campaign Platform (July 20, 2026)
• EIN Presswire — Google to Retire LSA Dashboard beginning August 2026