# Wistia Embed Guide: Aurora Player, SEO, Privacy, CTAs and Plans

> How to embed a Wistia video: inline, popover and iframe codes, Aurora player settings, SEO and LLM-friendly embeds, domain locks, and which plan adds CTAs.

_Source: https://professionalstoolkit.com/articles/wistia-embed — The Professional's Toolkit · updated October 2026_

---


**$79 a month** — Business billed annually, per account: the lowest Wistia plan with CTAs, forms and no Wistia branding.



- **600 px** — Minimum player width Wistia advises for Google video indexing
- **1 form + 1 CTA** — Per video on Business and up; annotation links unlimited
- **200 GB** — Free plan bandwidth a month; embeds stop a few days after it runs out


## The short answer: one embed code, and a plan for the extras

Embedding a Wistia video takes one copy and paste: open the video, click Embed, choose Inline or Popover, keep Responsive sizing and paste the code into your page. Inline with responsive sizing is what Wistia recommends for accessibility and video SEO.[1] **The plan decides what the player can do.** Free embeds carry Wistia branding and cannot hold CTAs or forms. Business, at $79 a month billed annually or $99 billed monthly per account, removes the branding and adds CTAs, forms, heatmaps and A/B tests.[2] Syncing viewer engagement into a marketing platform needs Signals on top.

| What you want from the embed | Free | Business | Signals or Enterprise |
|---|---|---|---|
| Player without Wistia branding | No | Yes | Yes |
| CTAs, Wistia Forms, annotation links | No | Yes | Yes |
| Heatmaps and A/B tests | No | Yes | Yes |
| Bandwidth a month | 200 GB | 1 TB | 2 TB on Enterprise |
| Engagement data in HubSpot, Marketo, Pardot | No | No | Signals |
| Meta Ads retargeting of viewers | No | No | Signals or Enterprise |
| Video Playback Protection | No | No | Enterprise only |

Bandwidth is the limit people forget. Thumbnails and autoplay start streaming as soon as the page loads, before anyone clicks, and a looping video thumbnail is a heavy drain. On Free there are no overages to buy: once the monthly allowance runs out, embeds keep playing for a few days and then stop until the reset. If the video sits on a high-traffic landing page, size the plan for page loads, not for plays.

## Pick the embed type before you paste anything

Wistia gives you several codes for different jobs. The **Standard inline embed** puts the player in the page and is the one that carries SEO metadata, the JavaScript Player API and every integration. The **Popover** shows a thumbnail with a play button and opens a theater-style player, and it can be launched from an image, a link or a button. The **Fallback** embed is an iframe for systems that strip JavaScript. Wistia names GoHighLevel, Skilljar, Rise, SharePoint and Drupal as site builders that may need it.

The iframe has a price. A Fallback embed still plays, but Google Analytics, the HubSpot, Marketo and Pardot integrations, the Player API and domain restrictions stop working. Use it only when the inline code truly fails. Two more codes cover special cases. The **Email embed** is a clickable thumbnail that opens a Wistia watch page, because most email clients cannot play video; it defaults to 450 pixels wide. The **LLM-friendly embed** is covered below.

WordPress has a trap. It turns a pasted Wistia URL into a sandboxed preview iframe that breaks the player. Paste the full embed code into a Custom HTML block instead. If your team copies one type all day, an Account Owner or Manager can switch on the account-wide Embed copy shortcut, which is off by default. Its choices are Inline, Popover, Email, LLM-friendly, Transcript and an embeddable media URL.

## Customize the player, and know which player you run

Current embeds use **Aurora**, a web component that appears on your page as a wistia-player element loaded by player.js. Wistia's launch post put its script at 43 KB, down from 139 KB for the older Vulcan V2 player, and old Vulcan embeds keep working. By default the code loads the latest Aurora version. A developer can pin a version by adding it to the player.js URL, but a pinned player stops getting bug fixes and security patches. Pin only while you test an upgrade.

The Customize panel holds the visual settings: a hex player color, a clickable logo in the top left corner, corner radius, and a thumbnail taken from an exact frame or a looping clip. Captions can change font size, color and contrast. Chapters can be written by hand or generated by AI from the transcript, and they show as clickable points on the play bar. Each video also gets an accessibility checklist; Wistia says the player meets WCAG AA (it cites 2.2 AA).

Two rules prevent surprises. Changes saved in Wistia update every existing embed automatically, so you never re-paste code after editing. **Options written into the embed code override** conflicting settings saved in the app. One inconsistency there explains most *why does my player look different* questions. On iPhone, fullscreen hands the video to Apple's native player, so annotation links disappear; on Android they stay.


> 💡 **Fix styling in one place:** Options written into the embed code override what you saved in Wistia's Customize panel. Keep customizations in the app unless a developer needs a page-specific override.


## Make the embed findable by Google and by AI tools

The Standard inline embed injects video JSON-LD into the page head with no sitemap or extra code. The markup carries the name, description, transcript, thumbnail URL, embed URL, duration and upload date, and it refreshes when you edit them in Wistia.[3] Automated transcripts are free on every account, so even Free videos get a transcript to feed it. Wistia adds that Google indexes only videos that are the main content of the page. Keep the player above the fold and at least 600 pixels wide.

Indexing is slow. Wistia says Google can take up to two weeks, and 10 to 15 days is not unusual. Wistia also points out that a searcher who clicks such a result lands on your own page, which it counts as the edge over YouTube SEO. To keep a video out of search, untick Inject SEO metadata in the Embed modal, add a no_index tag or block crawlers in robots.txt.

The **LLM-friendly embed**, announced in November 2025, puts the transcript in plain HTML where the player loads. Crawlers that cannot run JavaScript, which Wistia says includes AI crawlers, can then read what the video says. Schema markup stays in, and the SEO metadata cannot currently be switched off in this code. Wistia admits a small page-speed cost, since more content loads before playback, and argues the HTML transcript is a fallback rather than cloaking. Use it on pages you want quoted.

## Lock it down: domain restrictions, passwords and Privacy Mode

**Domain restrictions** let a video play only on domains you allowlist in Account Settings. Only the Account Owner can change that list. A parent domain such as example.com also covers its subdomains, while a single subdomain covers only itself. Enter bare domains, without the protocol prefix. Elsewhere, including share links and fast.wistia.com preview URLs, viewers see an error that the video is not authorized there. The page needs the wistia-player element and player.js, and some referrer policies break the check.

A **password** set in Customize is one shared password for every viewer, with no Wistia login needed. Audio files cannot be password protected. Private sharing is stricter: invited users must log in to Wistia, and how many you can invite depends on the plan. Neither option tells you who watched. Private sharing and team permissions collect no individual viewer identity, so capturing emails still needs a Wistia Form.

**Privacy Mode** anonymizes viewer IP addresses and turns off session and cookie tracking, and the Account Owner can apply it account-wide. It costs you data. The GA4 and Meta Ads integrations stop sending events, and each view counts as a new visitor. It is a GDPR aid, not a health-data answer: Wistia says it does not meet HIPAA requirements and signs no BAAs. The help pages we read describe domain restrictions and Privacy Mode without tying them to a plan.


> ⚠ **The iframe drops your safeguards:** A Fallback (iframe) embed still plays, but domain restrictions, Google Analytics, marketing-automation integrations and the Player API stop working on it.




> ⚠ **Privacy Mode cuts tracking data:** With Privacy Mode on, the GA4 and Meta Ads integrations stop sending events and every view counts as a new visitor.

## Add CTAs and forms that capture leads

Lead tools need Business or higher. Each video can hold one Wistia Form and one call to action, plus unlimited annotation links, and none of them may overlap.[4] Annotation links come in Compact, Large and Minimal layouts with start and end times. A custom HTML CTA gives layout freedom, but Wistia strips JavaScript from it and records no Action analytics. None of these tools work on audio files.

Wistia Forms replaced the old Turnstile email gate; existing Turnstile embeds still play. Custom fields can be text, dropdown or a single checkbox, required or optional. A developer can show the form before, at the end or at a set second, as an overlay that keeps playing or a pause gate, with Skip off by default. Logged-in Wistia viewers and people arriving from a tagged email link never see the form, since Wistia already knows them.


> 💡 **Test forms in a private window:** Wistia hides its Forms from logged-in Wistia viewers and from people arriving through a tagged email link. Log out before you check that the gate appears.


Which email tools receive submissions depends on the plan. A HubSpot form on the video sends data only to HubSpot and nothing to Wistia. On the Business plan, monthly billing costs $891 over nine months and $990 over ten, against $948 for a year billed annually, so annual wins from the tenth month on, by our arithmetic. Engagement data on contact records in HubSpot, Marketo or Pardot needs Signals: Business + Signals is $329 a month billed annually or $412 billed monthly. Wistia gives no refunds for cancellations or unused time; our [Wistia pricing guide](/articles/wistia-pricing) covers billing rules. For branded video hubs see [Wistia Channels](/articles/wistia-channels); for scripted control of the player, the [Wistia API guide](/articles/wistia-api).


## FAQ

**Can I embed a Wistia video on an AMP page?**

Yes. Wistia's developer docs say videos can be embedded in AMP HTML pages with the amp-wistia-player tag.

**Do CTAs and forms stay in a downloaded Wistia video?**

No. Forms, CTAs and annotation links are part of the player, so they do not appear in a downloaded video file.

**Will a Wistia video play inline in a LinkedIn post?**

No. LinkedIn does not support inline Wistia embeds in posts or Pulse articles, so the video shows as a thumbnail with a link. With domain restrictions on, LinkedIn also needs cdn.embedly.com allowlisted, which opens playback to any site that supports Embed.ly.

**Does Wistia playback work in mainland China?**

Wistia says it cannot guarantee playback in mainland China because of government restrictions, and performance there is inconsistent.


## The bottom line

Start with the Standard inline embed and responsive sizing, because it is the only code that keeps SEO metadata, integrations and domain restrictions working. Add the LLM-friendly code on pages you want AI tools to read. Move to Business when you need CTAs, forms or a player without Wistia branding, and add Signals only if engagement must reach your marketing platform. Fall back to the iframe only when a site builder forces it.



## Sources

[1] Wistia Help: embed your media — https://support.wistia.com/en/articles/8233354-embed-your-media (2026-10)
[2] Wistia Pricing - Free, Business, and Enterprise Plans — https://wistia.com/pricing (2026-10)
[3] Wistia Help: media seo with wistia — https://support.wistia.com/en/articles/8229319-media-seo-with-wistia (2026-10)
[4] Wistia Help: lead generation tools — https://support.wistia.com/en/articles/8229249-lead-generation-tools (2026-10)
[5] Wistia Help Center — https://support.wistia.com/en/articles/8264552-account-usage-and-bandwidth
[6] Wistia Terms of Service — https://wistia.com/terms
[7] G2, Wistia reviews — https://www.g2.com/products/wistia/reviews