This is for hospital marketing teams and website owners who have AI Max switched on, or are considering it, and want to know where paid traffic actually lands. Final URL expansion lets Google choose a landing page other than the one in the ad. On a typical hospital website, with hundreds of doctor profiles, package pages, branch pages and news items, the choice can be right, merely adequate, or plainly wrong for a patient who needs an appointment.
The article is a teardown method. You will audit a test campaign's landing URLs, classify the errors, and decide which are fixed with exclusions, which with page changes and which by switching the feature off. It does not report results from any named hospital. The decisions come from what Google documents and from the structure of hospital websites.
If your landing pages are weak before AI Max, expansion will find the weak ones faster. Our guide to healthcare landing page elements and the specialist referral page checklist cover page quality; here we cover which page gets chosen.
What final URL expansion does, per Google
Google's help page on AI Max for Search campaigns says final URL expansion sends traffic to the most relevant URLs on your site when that is likely to perform better. It uses only URLs relevant to the query and the ad group theme. It requires text customization to be on, and pinned assets are not respected when a different URL is chosen. If an ad group has a pinned headline for a regulatory statement, a different landing page may serve without it.
The controls the page lists are the ones you will use in an audit:
- URL exclusions at campaign level, which stop specific URLs serving as landing pages.
- URL inclusions at ad group level, which add URLs that expansion did not capture.
- Reporting: a "Selected by" column in the landing pages report, and a combined view of search terms, headlines and URLs.
The same page warns that dynamic landing pages can break with certain tracking templates, which cause 404 errors, and recommends using the lpurl tag in compatible patterns and testing landing pages before enabling AI Max.
Why hospital sites are a hard case
A hospital site differs from a retail catalogue in four ways that matter here.
- Doctors move. A profile page may exist after a consultant has left, changed branches or stopped taking appointments. A query for that doctor's specialty could match the old page.
- Packages expire. Health-check and surgical packages are priced and withdrawn. Old pages often stay live and indexed.
- Branches overlap. The same service appears on five location pages. Expansion may choose the wrong city.
- Content pages look like service pages. A long educational article on knee pain can match a procedure query better than the booking page does, but it has a weaker path to an appointment.
Each of these is a real patient problem, not only an advertising inefficiency. A person who clicks an ad and arrives at a page for a doctor who is no longer there will lose trust in the hospital.
Step 1: Export the landing pages
Run the audit on a test campaign, or on a campaign that has had final URL expansion on for at least one full conversion cycle. Pull the landing pages report with the "Selected by" column. Export the URL, clicks, cost and conversions. Add the original ad group final URL for comparison.
Then add two columns from the website and CRM side:
- Page status: live and current, outdated, duplicate, or not meant for paid traffic.
- Enquiry outcome: qualified enquiries and booked appointments attributed to that URL, from your lead log.
If your enquiry log does not record the landing page, add a hidden field that captures it on forms and in click-to-call tracking. Without that, the audit measures clicks, not patients.
Step 2: Classify each expanded URL
Create a simple table and put every URL selected by expansion into one of five classes.
| Class | Example (hypothetical) | Typical fix |
|---|---|---|
| Right page, better than original | Procedure page for the exact surgery searched | Keep; consider promoting to the ad group's final URL |
| Right page, wrong location | Branch page for another city | URL inclusion or exclusion by branch; fix location targeting |
| Outdated | A withdrawn health-check package | Exclude now; then redirect or remove the page |
| Wrong intent | An educational blog post, a news item, a careers page | Exclude |
| Wrong person | Doctor profile for a specialty the query did not ask for | Exclude, or restructure the ad group |
Count how many URLs and how much spend fall in each class. The proportion is the output of your audit. Do not assume it will match another hospital's.
Step 3: Exclude, include or fix
Exclusions are the fast fix. Add every outdated, wrong-intent or non-paid-traffic URL as a campaign-level exclusion. Because URL exclusion works on specific URLs, a rule based on a directory pattern, where the interface supports it, saves effort on a site with many profile pages. Check the options in your account, because the available matching rules are set by the interface and I have not confirmed their detail from Google's documentation.
Inclusions work in the other direction. If the system never selects the best procedure page, add that URL at ad group level so it becomes eligible.
Fixing pages is the durable answer. Three fixes pay off repeatedly.
- Retire stale pages properly. Redirect withdrawn packages to the current equivalent and mark departed doctors' pages so they are not offered in paid traffic.
- Give each branch page a clear location signal. City or locality in the heading and in structured data helps people and systems tell the pages apart.
- Keep one canonical page per service per branch, and make sure the call and booking actions are present on it.




