To show your CTA on top of a page, that page has to render inside a frame. Plenty of sites refuse — they send an X-Frame-Options header or a Content-Security-Policy: frame-ancestors directive, and the browser obeys. No frame, no overlay. This is how the web works and every tool in this category has the same ceiling.
What Visib does about it
- It warns you before you publish. While you type the destination, Visib requests it and reads the framing headers. If it is blocked, you see it at creation time instead of finding out from a reader.
- It falls back at runtime. If a frame never renders, the visitor is sent on to the destination rather than left on a blank page. You lose the overlay, not the click.
- It offers the actual fix: a snapshot.
How a snapshot works
Install the Visib Snapshot Chrome extension, open the page you want to share, and capture it. The extension saves the whole page as a single self-contained file and uploads it. Your link then serves that copy with your CTA on top — no framing involved, so nothing to block. Scripts are stripped and cookie banners are hidden, which usually makes the snapshot cleaner than the original.
Snapshots are a Pro feature. On the free plan you still get the pre-publish warning and the redirect fallback.
When to use which
- Framing allowed — link live. The reader gets the current page.
- Framing blocked — snapshot it, or share it without a CTA and keep the analytics.
- Login required — do not bother framing it. Sign-in inside a third-party frame is blocked by browsers regardless.
