What Eye Care Google Ads Accounts Need to Know About AI Max Before September 2026
Your agency has not mentioned AI Max in a QBR. Your account still runs Dynamic Search Ads, automatically created assets, and campaign-level broad match. In September 2026, Google migrates all three into AI Max automatically, whether you prepared or not.
This article covers what AI Max is, what the forced migration does, and the specific pre-September steps that keep eye care accounts in control of the feature set. HIPAA implications get particular attention, because final URL expansion is the place most healthcare accounts accidentally violate compliance.
Why Every Eye Care Account Is on a Countdown Clock
Starting September 2026, Google forcibly migrates Dynamic Search Ads, automatically created assets, and campaign-level broad match into AI Max (Google blog, April 2026). Every eye care account running any of these campaign types is on a countdown clock, whether the agency has mentioned it or not.
The migration is not a destructive change. Your campaigns keep running. Spend continues. Conversions continue. What changes is the control surface: features inside AI Max replace the legacy DSA/ACA/broad-match mechanics, and Google configures the default settings to mirror what the account was doing. The defaults are reasonable. The problem is that the defaults are just defaults, and reasonable defaults for a typical advertiser are not always reasonable defaults for a HIPAA-regulated healthcare account.
Accounts that migrate voluntarily before September retain the window to baseline current performance, configure brand restrictions, set text customization guidelines, and opt out of specific AI Max features the account does not need. Accounts that get auto-migrated in September lose that window. The campaigns keep running; the control is what disappears.
This article describes what to do before September. Not abstractly. Specifically.
How AI Max Actually Works as a Feature Suite Inside Search
AI Max is not a new campaign type. It is a three-feature suite inside existing Search campaigns. Understanding the three features separately is the first and most important step, because the right decision for eye care is often “turn some on, leave others off.”
Feature one: search term matching. This is the broad-match-plus-keywordless expansion that replaces legacy broad match. AI Max uses query intent signals beyond keyword text to match ads to searches. For tight-intent healthcare queries, this can expand reach; for loose-intent or condition-specific queries, it can surface searches you do not want to be in.
Feature two: text customization. Previously ACA (automatically created assets), now integrated into AI Max. The system generates headline and description variations from your landing pages, sitelinks, and ad copy. For generic healthcare content, this is low-risk. For condition-specific or symptom-specific landing pages, AI-generated headlines can surface language that creates HIPAA exposure.
Feature three: final URL expansion. The highest-risk feature. FUE substitutes advertiser-provided URLs with dynamic landing pages selected from Google’s analysis of the site. If your sitemap includes condition-specific pages (diabetic retinopathy, glaucoma, dry eye treatment), AI Max can route ads to them without your explicit approval.
AI Max sits between traditional Search and Performance Max in the control-vs-automation spectrum. Unlike Performance Max, which mostly opaques the control surface, AI Max preserves keyword-level visibility. But the three features collectively erode the bright-line predictability healthcare accounts rely on.
Google’s Reported Lift Numbers and What They Mean for Eye Care
The numbers Google publishes and what they actually say about healthcare performance.
Google reports approximately 14% more conversions at similar CPA/ROAS for typical AI Max activation, and approximately 27% for exact and phrase-heavy accounts (Google blog, April 2026). These are blended across verticals, including ecommerce where the conversion event is the revenue event. For lead-gen healthcare, the lift often comes from lower-quality form fills that do not convert to patients.
The full-suite vs. search-term-matching-alone lift is approximately 7% incremental (Google). This is the number most relevant to healthcare configuration. It says that turning on text customization and final URL expansion adds 7% on top of search term matching alone. Whether that 7% is worth the additional HIPAA surface depends entirely on landing page governance.
Independent data: Brainlabs found a 40% higher success rate when all three AI Max features are enabled together (PPC Live, April 2026). This is cross-industry practitioner data, not eye care specifically. For healthcare, discount the success rate 20–40% to account for lead-quality dynamics and compliance constraints. See the eye care PPC benchmarks reference for the underlying CPC and CVR context.
Five Red Flags in Your Pre-Migration Eye Care Account
Five conditions that should be addressed before September 2026, in priority order.
DSA campaigns still running with no migration plan. DSAs auto-migrate to AI Max in September. If your agency does not have a documented plan for what the migrated campaign should look like, the default settings take over. This is the default failure mode.
Final URL expansion enabled on accounts with condition-specific pages in the sitemap. If your site has pages for diabetic retinopathy, macular degeneration, dry eye treatment, and similar condition content, FUE can route ads to those pages. Without URL controls whitelisting HIPAA-safe destinations, FUE is a compliance risk. Most eye care accounts should default to FUE off.
No brand restrictions configured. AI Max, like PMax, can bid on queries including your brand name, inflating CPCs on searches where defensive brand bidding should cost almost nothing. Brand restrictions should be set before migration, not after.
No pre-migration performance baseline captured. Once AI Max migrates the campaign, the historical attribution of which tactic drove which conversion gets blended. If you have not captured a 30-day baseline of DSA, broad-match, and exact-match performance pre-migration, you cannot measure what AI Max actually changed. See the 15-minute Google Ads audit for the baseline checklist.
Tracking templates not validated against dynamic landing pages. If your conversion tracking depends on URL parameters or page patterns, FUE can break tracking by routing ads to pages with different parameter structures. Validate every tracking template against every URL AI Max might route to.
Voluntary Migration in 15 Minutes, 30 Days, and 90 Days
The pre-September migration sequence across three windows.
Immediate, within 15 minutes: open Google Ads Recommendations, filter to AI Max, and review what Google is suggesting for your account. Do not accept any recommendations automatically. Open your campaigns and identify which run DSA, ACA, or campaign-level broad match. That list is your migration scope.
Within 30 days: capture a 30-day performance baseline of the campaigns in scope. Export the data, including CPA, CVR, conversion volume, impression share, and search-term reports. This is the pre-migration reference you will compare against post-migration performance. Without it, you cannot answer “did AI Max help or hurt?” after the fact.
Within 60 days: voluntarily migrate at least one campaign to AI Max with search term matching enabled but text customization and final URL expansion off. This is the safest feature mix for eye care. Run the migrated campaign for two conversion cycles and compare CPA and lead quality against the baseline. If performance holds, gradually enable additional features for the other migrating campaigns.
Within 90 days (pre-September): configure brand restrictions, location controls, text customization guidelines, and URL controls for every campaign. Tighten negative-keyword lists because AI Max’s search term matching surfaces queries your old keyword lists did not contemplate. Document every configuration decision so the post-September account has a written record of the choices that got made.
Why the AI Max Feature Mix Is the Eye Care Decision
Our view is specific. The September migration is not optional, but the specific AI Max feature mix is. Eye care practices should turn on search term matching carefully, test text customization with supervision, and default off on final URL expansion until HIPAA-safe landing page governance is proven.
This is a governance decision, not just a configuration one. The feature mix your account runs should be documented, reviewed, and tied to specific landing-page controls that prevent condition-specific pages from becoming ad destinations without explicit approval. Agencies that cannot produce that documentation in 2026 are not ready for the migration, regardless of whether they have started “talking about it.”
For the full platform playbook covering Performance Max configuration, AI Max governance, HIPAA-safe feature selection, and the complete set of platform decisions eye care accounts face in 2026, see Performance Max and AI Max for Healthcare: What Actually Works.
What happens if we do nothing before September 2026?
Google auto-migrates your DSA, ACA, and broad-match campaigns to AI Max with settings configured to mirror legacy behavior (Google blog, April 2026). Auto-migrated accounts lose the window to baseline performance and to opt out of specific features. The campaigns keep running; the control is what disappears.
Can we opt out of AI Max entirely?
Not if you run DSA, ACA, or campaign-level broad match. Those are the auto-migrated campaign types. You can decline individual AI Max features (text customization, final URL expansion) within a migrated campaign. Fully keyword-based Search campaigns with exact/phrase match and pinned assets continue to run without AI Max upgrades.
