Can an expired license or insurance document pause my Local Services Ads without me knowing?
Yes. Verification documents have expiry dates, and when one lapses the profile can stop serving or lose its badge while the account still looks active at a glance. Notices go to the account email, which is often unmonitored. Track every document's expiry outside the platform, and monitor daily lead volume so an unexplained drop surfaces within a day rather than at month end.
The failure is quiet by design
Nothing in the interface flashes red across your whole account. The campaign still exists, the budget still shows, and the change is in eligibility rather than in the settings you look at. Shops routinely lose a week or more before someone connects a slow phone to a document nobody uploaded.
Treat this as a monitoring problem rather than a discipline problem. Discipline fails predictably in a busy service business; monitoring does not care how busy you are.
Build a document register you control
Keep the register outside the ad platform, in whatever system your office actually opens every day.
- General liability certificate. Expiry, carrier, renewal contact, and who uploads the new one.
- Trade and contractor licenses. Per state and per jurisdiction where you operate. Requirements vary and are worth confirming locally rather than assuming.
- Background screening dates. Owners and, in some categories, field staff. New hires create new obligations.
- Account access. Who can log in, and whether the notification address is a monitored group rather than an individual.
Alert on volume, not on status alone
Status flags are the direct signal, but they are not always immediate or obvious. Lead volume is the downstream signal and it is unambiguous. If yesterday's charged lead count falls well outside the normal band for that day of week and season, something changed and it needs a human look.
That check is trivial to automate once lead data flows out of the platform on a schedule, which is one of the practical arguments for connecting Local Services data to your own systems rather than living inside the dashboard.
Assign the recovery path in advance
When a lapse happens, the time cost is not the upload. It is finding out who has the certificate, who at the insurer sends it, and who has permission to log in. Write that chain down once and the next lapse costs an hour instead of a week.
For multi-location operators the same register needs a row per location, because each profile carries its own documents and each can fail on its own schedule. Rolling that status into one view alongside lead volume per market is ordinary business intelligence work and it prevents the most avoidable revenue gap in the channel.
Topics: LSA · verification · compliance · monitoring
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.