Third-party embed health — high-level pointers (local fallback)

barbaracle tells you which embed on a page rendered empty. The detailed, current vendor-by-vendor remediation steps — how to refresh an Instagram token, reconnect a review widget, diagnose a stalled booking iframe, and the escalation path when a widget stays broken after a retry — live in the team wiki (set OUTLINE + OUTLINE_API_URL and the report links them directly). This file is the minimal high-level fallback for when the wiki isn’t configured: direction only, deliberately not step-by-step, so there’s no detailed content to drift out of sync with the wiki.

• Empty embed — the vendor was asked for content and returned nothing visible; confirm the account/feed is still active on the vendor’s side before touching the site.
• Instagram / social feed — expired access tokens are the most common cause; the connected account needs re-authorizing with the plugin or widget provider.
• Review widgets (Birdeye, Podium, etc.) — check the vendor dashboard for a paused sync or an API-key change before assuming the embed code is broken.
• Booking / scheduling iframes — a blank iframe is usually the third party’s own outage or a changed embed URL, not a fix on our side.
• Chat widgets — confirm the widget is still enabled for the domain in the vendor’s settings; a domain/plan change on their end silently stops rendering.
• Not-loaded (lazy) embeds — near the top of the page this is broken; below the fold, re-check after scrolling before treating it as a defect.
• Hidden embeds — a closed accordion or inactive tab is deliberate; don’t “fix” what the page intentionally hides.
• Recurring checks — schedule the same URL list on a cadence (bi-weekly/monthly) rather than waiting for a client to notice and file a ticket.

Full playbook → the team wiki’s third-party embed & widget health standards.