Most treatment center websites we audit carry at least one overlay that the marketing team did not ask for: an insurance verification modal, a chat launcher, a sticky call bar, a timed pop-up. Each one was added for a sensible reason, usually more admissions calls. The problem is that Google has published specific guidance on overlays, and a second, measurable standard (Core Web Vitals) that many of these widgets quietly fail. This post covers what Google actually says, where overlays cost you, and a check you can run on your own site this afternoon.
What Google Actually Counts as an Intrusive Interstitial
Google’s documentation separates two things. An interstitial is an overlay on the whole page. A dialog is an overlay on part of the page that may still obscure the content beneath it. Google’s guidance on intrusive interstitials and dialogs says they make it hard for search engines to understand your content, “which may lead to poor search performance,” and it gives two direct instructions: don’t obscure the entire page, and don’t redirect the user to a separate page for their consent or input.
The recommended alternative is a banner that takes up only a small fraction of the screen. Note what is missing: Google does not publish a percentage or pixel threshold. If a vendor or plugin tells you Google allows overlays up to a certain share of the screen, that figure is not from Google’s documentation. The practical test is simpler: can a visitor read the content they came for without closing anything first?
There is one exemption. Interstitials that are legally mandatory, such as an age gate, are excluded from the guidance. A marketing modal asking for insurance details is not a legal requirement, so the exemption does not cover it.
Where Overlays Actually Cost You: Layout Shift
Google’s Search Console Core Web Vitals report rates Cumulative Layout Shift (CLS) as Good at 0.1 or below, Needs improvement up to 0.25, and Poor above 0.25, measured across 75% of real Chrome visits to a group of similar pages. On treatment center websites, a common source of that shift is a chat launcher, verification banner or sticky call bar that a script injects after the page has already rendered, with no space reserved for it, so everything below it jumps. Because one tag usually loads on every template, a single widget can move an entire site’s mobile CLS status at once.
This matters more than the interstitial guidance alone, because Google is explicit that Core Web Vitals are used by its ranking systems. Its page experience documentation states this directly, while noting that other page experience aspects do not directly help a site rank higher. The Core Web Vitals report help page adds two details worth knowing: a URL group’s status is set by its worst metric, so good loading speed does not rescue poor CLS, and the data comes from real Chrome users rather than a lab test. The other two thresholds are Largest Contentful Paint at 2.5 seconds or less and Interaction to Next Paint at 200 milliseconds or less. Heavy third-party chat scripts compete for the same browser main thread that responds to taps, which is why they can drag down INP as well.
Five Overlays We Keep Finding on Treatment Center Sites
Load-triggered insurance verification modal: a form that opens the moment the page loads and fills the whole screen on a phone, which is exactly the “obscure the entire page” pattern Google tells you to avoid.
Late-loading chat launcher: a chat bubble injected through a tag manager after first paint that expands into a greeting or pushes a sticky footer upward, adding layout shift on every page it loads.
Script-inserted call bar: a “Call now” bar added by JavaScript instead of being built into the page template, so the header, hero and first paragraph all slide down once it appears.
Timed or scroll-triggered pop-up: exit-intent tools cannot detect a cursor leaving the window on a touchscreen, so many fall back to timers or scroll depth, which means the modal lands in the middle of someone reading about detox or levels of care.
Consent or disclaimer redirect: a setup that sends every first-time visitor to a single consent or disclaimer page. Google warns that redirecting all URLs to one page can remove all but that page from search results, because Googlebot can only fetch that page.
The Inconvenient Part: Your Web Team Often Didn’t Install Them
When we trace these overlays back to their source, they are frequently not in the WordPress theme at all. They arrive as snippets from an admissions CRM, a call tracking provider, a verification-of-benefits vendor or a chat service, pasted into Google Tag Manager or a header-scripts plugin by whoever set up that tool. That has three consequences.
First, they survive redesigns. A new theme can be fast and stable in testing, then inherit every old tag the day it goes live. Second, nobody owns their performance: the vendor optimizes for its own conversion metric, and the web team cannot see the widget in the theme files. Third, they are often collecting health information. A chat window or verification form that asks about insurance, substances or symptoms may be handling protected health information if your organization is a HIPAA covered entity, and a vendor that receives it on your behalf generally needs a business associate agreement. That is a question for your compliance lead or counsel, not a web setting, but an overlay audit is often the first time anyone lists every vendor collecting data on the site.
A 15-Minute Overlay Audit You Can Run Today
Pick your homepage and your highest-traffic admissions or program page, then work through these steps:
- Phone test: open each page on a phone in a private browsing window. For the first five seconds, note anything that covers the content, anything that appears late, and whether the close control is easy to tap.
- See the shift: on a desktop, open Chrome DevTools, go to More tools, then Rendering, and tick Layout Shift Regions. Reload the page with the device toolbar set to a phone size. Every area that jumps is highlighted as it moves.
- Check field data: run the same URL through PageSpeed Insights. Compare the real-user CLS figure at the top with the lab diagnostics below, and look for layout shift culprits whose element or script names match your chat, call tracking or verification vendor.
- Inventory the tags: in Google Tag Manager, sort tags by trigger and list every tag firing on All Pages. Mark each one that draws something on screen, and who owns it.
- Validate after fixing: in Search Console, open Core Web Vitals, then Mobile. If a CLS issue is listed, fix the cause and click Start tracking. Google monitors the issue over a 28-day window of real-user data, so do not expect the status to change the next morning.
What to Use Instead
None of this means removing the tools that bring in admissions calls. It means building them into the page rather than on top of it:
- Put the phone number and a “Verify insurance” button in the page template HTML, so they render with the page instead of arriving afterward.
- Reserve space for anything sticky. A fixed-height slot for the call bar or chat launcher, set in CSS before the script loads, removes the jump.
- Open the verification form when someone taps the button, or place it inline on the insurance page, instead of launching it on load.
- Load chat scripts after the first interaction or after the main content has rendered, and turn off auto-expanding greetings on mobile.
- Where you need an announcement, such as a crisis line or new program, use a small banner, which is the format Google recommends.
These are template decisions, which is why we handle them as part of web design rather than as a plugin setting. For paid advertising landing pages the same logic applies: a visitor who clicked an ad should see the offer they clicked, not a modal.
What Fixing Overlays Will Not Do
Clearing overlays and passing Core Web Vitals will not by itself move a page to the top of results. Google says so plainly: good scores in Search Console or third-party tools do not guarantee top rankings, and chasing a perfect score purely for SEO reasons may not be the best use of your time. Relevance still comes first. Where page experience helps is in competitive queries, where many providers have helpful content and Google has to choose between them.
The better reason to fix overlays is the person on the other side of the screen. Someone searching for treatment at night on a phone, for themselves or a family member, should reach your program information and phone number without dismissing a form first. If you want a second set of eyes on what is loading across your site, our SEO services start with exactly this kind of technical audit.
