Podcast website builder FAQ.

Yes. The free tier gives you a fully functional site on a PodView subdomain with all themes, automatic episode sync, SEO essentials, and multi-language support included.

No. You can launch on the free plan using a PodView subdomain. Upgrade when you need a custom domain, advanced content tools, integrations, or producer-grade AI controls.

Yes. Connect your own domain at no extra cost on the Indie plan and above. You can also register a new domain directly from us (billed separately). SSL included.

Yes. Theme choice is not paywalled. Paid plans unlock more publishing, growth, and customization tools.

No. PodView does not take a percentage of sponsorships, donations, memberships, merch, or newsletter revenue. Payment processor and third-party platform fees may still apply.

Yes. No contracts, no cancellation fees.

Yes. Annual billing is available for paid plans and usually lowers the effective monthly cost.

Your site stays online, but features outside the lower plan can become unavailable until you upgrade again. We avoid deleting your work just because you change plans.

Yes. Free sites publish on a PodView subdomain, so you can share your site without buying or connecting a custom domain.

Yes. Indie plans and above can connect an existing domain. PodView guides you through the DNS records and provides HTTPS once the domain verifies.

Yes. You can register a new domain from the dashboard when you want PodView to handle the domain setup path. Domain registration is billed separately.

Yes. You can use common setups like example.com and www.example.com, with canonical handling so visitors and search engines land on the preferred version.

Many domains verify quickly, but DNS changes can take time depending on the registrar. The dashboard shows the current status and the records still needed.

Yes. You stay in control of your domain. If you registered through PodView and later want to transfer it, the dashboard includes the transfer-out flow where available.

A growing library of professional themes, all available on every plan. No theme paywalls.

Yes. You can choose a theme and adjust brand colors, navigation, hero behavior, page sections, and other visual details from the control panel.

Yes. Blog and custom pages are available on Creator and Producer plans.

Yes. Custom pages work well for About, FAQ, Resources, Speaking, Advertise, Newsletter, or Hire Me pages.

Yes. Built-in email collection with double opt-in, plus integrations with Mailchimp, Kit (ConvertKit), and Hostinger Reach on Creator plans.

Yes. Custom CSS is available on all plans, and advanced tracking or embed snippets can be added through the appropriate customization areas.

Yes. You can feature episodes, adjust episode display behavior, and use visibility controls for episodes that should not be promoted on the public site.

Yes. Episode visibility controls let you hide individual episodes from the site without changing the source RSS feed.

Yes. PodView can surface richer episode metadata when it is available or added in the dashboard, including guests, sponsors, chapters, platform links, and transcripts.

Yes. When your feed includes Podcasting 2.0 chapter markers, PodView can render them as clickable jump points in the episode player so listeners can skip to the moments they care about.

Not if you turn on the persistent player. On any paid plan you can switch it on in General Settings, Player tab, and a sticky bar keeps the current episode playing while visitors move around your site: another episode, the archive, your about page, a tag or a blog post, no restart, no lost place. It works with the Enhanced player, so the toggle stays locked while your player type is set to the simple browser player or a custom embed. It is not a queue or autoplay: nothing plays until a listener presses play, and a full page reload still starts fresh.

Yes. Episodes with Podcasting 2.0 HLS video streams can play inline on your site, which is useful for shows that publish both audio and video from the same feed.

Yes. PodView can display episode video when the feed includes video metadata, YouTube links, or a YouTube source. For YouTube-native shows, PodView can import videos into episode-style pages instead of treating YouTube as only a social link.

Yes. Creator features include AI theme recommendations and layout suggestions that use your podcast's content and personality as context.

Every site includes automatic schema.org markup, XML sitemaps, Open Graph tags, and Apple Smart Banners. No plugins to install.

PodView publishes crawlable pages with canonical URLs, metadata, sitemaps, and structured data. Search engines still decide when and how to index each site.

Yes. Episodes have dedicated pages so listeners, search engines, newsletters, and social posts can link directly to a specific episode.

Yes. PodView generates sitemaps for public podcast pages and keeps them aligned with your published episodes and site content.

Yes. Public pages include Open Graph and social metadata so links render cleanly when shared in messaging apps, social networks, and community platforms.

Yes. PodView handles many technical SEO basics automatically, then gives you places to improve titles, descriptions, content, internal links, and episode context.

Yes. PodView can include Apple Smart Banners so iOS visitors have a cleaner path from your website to Apple Podcasts.

Yes. On Producer plans, PodView suggests internal links between your episodes, blog posts, and pages, and you accept or reject each one.

Yes. Producer SEO tools include advanced analysis and keyphrase checks so you can find pages that need stronger titles, descriptions, internal links, or content depth.

Yes. PodView includes redirect management so old links can point visitors and search engines to the right replacement page after a migration or URL change.

Yes. PodView publishes robots.txt alongside sitemaps and canonical metadata so crawlers have a clearer map of your public site.

AI visibility means making your show easier for AI assistants and answer engines to understand, cite, and summarize accurately.

Yes. PodView includes LLM-friendly markdown surfaces such as llms.txt and page mirrors so assistants can read concise, structured versions of your public content.

Producer features let you guide topics, FAQs, instructions, episode takeaways, and other signals that AI systems can reuse when summarizing your podcast.

Yes. Producer sites can maintain structured Q/A entries that render into AI-readable surfaces and matching structured data.

No platform can guarantee inclusion in AI answers. PodView focuses on clean, accessible, structured content so assistants have better source material.

Yes. Transcripts give crawlers and assistants more context about each episode. When transcript data is available, PodView can expose it in useful public and AI-readable forms.

Markdown mirrors are clean text versions of public pages, episodes, and product pages. They give assistants a source that is easier to parse than visual HTML while staying aligned with the same public content.

Yes. Producer curation lets you guide episode takeaways, preferred topics, FAQ entries, and instructions so AI assistants have clearer wording to reuse.

Yes. Built-in audience analytics include AI-crawler visits, which helps you understand when assistants and AI search systems are reading your public content.

Yes. PodView includes newsletter signup forms and double opt-in flows so your website can capture listeners who want updates.

PodView supports built-in collection plus integrations such as Mailchimp, Kit (ConvertKit), and Hostinger Reach on Creator plans.

Yes. Subscriber lists can be exported as CSV.

Yes. Depending on your theme and settings, you can use embedded newsletter areas, footer forms, and popup-style signup prompts.

Yes. Each subscriber records the page they signed up on, such as the homepage, an episode page, or a popup, and that field is a column in the CSV export. For campaign-level attribution, connect GA4 or route the signup event to your own tools with a webhook.

Yes. Creator plans can deliver a file after a subscriber confirms their email, which is useful for checklists, bonus guides, worksheets, or private resource downloads.

Yes. Confirmed subscribers can sync in real time to Mailchimp audiences, Kit forms or sequences, and Hostinger Reach contact groups.

Yes. The integrations workflow supports connecting to different lists, forms, or groups so you can route podcast subscribers into the right email destination.

Yes. Announcement bars and promotional popups can support launches, lead magnets, sponsor campaigns, ticket sales, or other time-sensitive calls to action.

Yes. Producer plans include automatic new-episode email alerts to your subscriber list, and automation recipes can send more customized campaigns through email tools.

Yes. You can add sponsor information, episode links, custom pages, and calls to action that support sponsorship campaigns.

Yes. PodView supports links and sections for platforms like Patreon, Buy Me a Coffee, Ko-fi, Supercast, and other listener-support tools.

Yes. You can use supported ad and custom-code options, including Google AdSense where your plan and account setup allow it.

Yes. Custom pages and media kit tools make it possible to explain your audience, sponsorship options, and contact path for advertisers.

PodView can link and integrate with monetization platforms, but your payment provider or membership platform usually remains the system of record for payments.

Yes. Producer plans support members-only episode audio with subscribe calls to action for membership paths such as Patreon, Apple Podcasts subscriptions, and similar platforms.

Yes. Creator plans can link out to products, courses, merch, and other offers from the site so your podcast website can support more than listening.

Yes. The media kit can include sponsorship packages, rates, audience metrics, contact calls to action, and proof points for brands evaluating your show.

Yes. PodView includes site analytics so you can understand page views, popular pages, and visitor activity without installing a separate analytics stack.

Your podcast host remains the source for download analytics. PodView focuses on the website layer, such as pages, visitors, clicks, and on-site behavior.

Yes. GA4 can be added through the analytics and tracking settings.

Yes. You can add Google Tag Manager through custom tracking code where your setup requires it.

Yes. Tools such as Plausible or Fathom can be added through custom tracking snippets if you prefer that analytics model.

Yes. The dashboard highlights traffic patterns so you can see which pages and episodes are attracting attention.

Yes. Built-in pageview analytics are first-party and cookieless, focused on aggregate site behavior such as referrers, popular pages, audience patterns, and AI-crawler visits.

Yes. Indie plans and above include consumption analytics for per-episode plays, completion rate, and drop-off so you can see how people engage on the site.

Yes. Creator plans include shortlinks with redirect hit counts, useful for campaigns, guest links, sponsor reads, QR codes, and offline promotion.

Yes. Producer automation features can send webhook events to tools like Zapier, Make, IFTTT, n8n, Pipedream, or your own endpoint.

Producer webhooks can fire for new episodes, confirmed subscribers, Apple Podcasts reviews, contact messages, voicemails, blog posts, and guest intake submissions.

Yes. Review automation can distinguish newly imported reviews and negative reviews, so a team can route praise to social proof and low ratings to a private follow-up workflow.

Yes. Webhooks and integrations can route new audience, sponsor, guest, or contact activity into a CRM or spreadsheet.

Yes. Webhook recipes can notify your team or community when important site activity happens.

No for common no-code tools. You only need code if you want to receive webhook events in your own custom application.

Yes. PodView signs automation payloads with HMAC-SHA256 in the X-PodView-Signature header so custom receivers and advanced no-code workflows can verify the event is genuine.

Yes. Episode automation payloads can include fields such as episode_url, guest details, profile URLs, and tags, which lets workflows build share kits or branch by topic.

Yes, when enabled for the endpoint. Contact PII such as email, phone, company, or guest answers is intentionally controlled so teams can decide which workflows receive it.

Custom code recipes are copy-paste snippets for Creator sites. They help you add things PodView does not ship as a built-in setting, such as ad pixels, heatmaps, booking widgets, live chat, storefront embeds, or special structured data.

Code recipes change what runs on your public website through head or body code. Automation recipes react to events through webhooks, such as a new subscriber, contact message, voicemail, or episode publish. Some workflows use both.

Yes. For example, a custom embedded form or booking widget can collect interest on the site, while a webhook automation routes the resulting subscriber, contact, or lead event into Slack, Notion, HubSpot, Airtable, or an email platform.

Yes. Creator custom code can add snippets such as Meta Pixel, TikTok Pixel, LinkedIn Insight Tag, Google Ads remarketing, or other trusted tracking scripts. If cookie consent is enabled, tracking scripts should be configured with that behavior in mind.

Yes. Custom head code can load tools like Microsoft Clarity, Hotjar, PostHog, or similar products so marketers can study clicks, scroll depth, session replays, and funnel behavior beyond PodView's built-in analytics.

Yes. Most third-party widgets provide a script or iframe snippet. Paste trusted widgets into the appropriate custom code slot and test them on your public site.

Head code is best for verification tags, structured data, fonts, and scripts that must load early. Body code is better for chat widgets, embeds, non-critical scripts, and floating buttons that can load near the end of the page.

Yes. Use the custom head-code slot for verification meta tags from Google Search Console, Bing Webmaster Tools, Pinterest, Facebook Business, and similar platforms.

Yes. The custom code recipe pages include AI prompts you can paste into an assistant to adapt a snippet for your show, your widget, and the correct head or body slot.

Usually no. PodView already emits core podcast schema, sitemaps, social cards, analytics, signup forms, and other built-ins. Custom code is best for extending the site with tools or markup that are specific to your workflow.

PodView renders custom code exactly as written, so only paste snippets from services you trust. Add one snippet at a time, keep a copy of what changed, and test the public site after saving.

Yes. Guest intake tools let potential guests submit information through your site so you can review and manage requests.

Yes. You can collect the details that matter for your booking workflow, such as topic ideas, bio, links, audience fit, and availability.

Yes. Media kit features help package show information, audience signals, contact paths, and sponsor-friendly details.

Yes. Public contact forms can route messages to you without exposing your email address directly on the page.

Yes. A media kit can be published as a shareable page while staying noindex, so brands can view it without making the page a public search target.

Yes. Media kit social proof can use curated reviews, featured reviews, or top-rated fallback reviews depending on how you configure the kit.

Yes. Guest management includes guest alert emails, and automation recipes can send more detailed share kits when an episode with guests goes live.

Yes. Voicemail collection lets listeners send short audio messages from your site, and automation webhooks can route those clips to Slack, Drive, or transcription workflows.

Yes. Guest submissions export as CSV from the guests dashboard.

Yes. You can export subscriber and guest lists as CSV at any time.

Yes. All sites get automatic SSL certificates, including custom domains.

Any host that provides an RSS feed: Buzzsprout, Libsyn, Anchor, Transistor, Captivate, Simplecast, Podbean, Megaphone, RSS.com, Spreaker, and more.

Every 12 hours on the free plan, every 4 hours on Indie, hourly on Creator, and every 30 minutes on Producer. You can also trigger a sync yourself from the dashboard when you want a change live sooner.

PodView keeps the existing site available and records sync status so you can see whether the feed needs attention.

PodView supports podcast feeds with video-related metadata where available and includes display options for shows that publish video.

PodView is designed for public podcast websites. Private or authenticated feeds may not work unless they expose public metadata that the site can read.

Yes. PodView themes are responsive and built to work across phones, tablets, and desktop screens.

Yes. PodView includes multi-language support for public site labels and can work with podcast content published in many languages.

On the Producer plan, yes. PodView attribution comes off the public site entirely. Free, Indie, and Creator sites keep the footer credit.

Yes. Podcast sites include privacy-policy support, and you can point visitors to your own privacy policy or terms pages from the Legal tab. Custom pages can also cover policies, sponsorship terms, disclosures, or other legal content.

Yes. The Indie tracking settings can show a consent banner and block GA4 or custom tracking scripts until the visitor accepts. PodView's built-in first-party analytics are cookieless.

Yes, on a custom domain (Indie plan and up). Search Console verifies ownership with a DNS TXT record, not a code snippet: add the google-site-verification record to your domain's DNS, at your own registrar if you brought your domain, or in PodView's DNS editor for domains you registered with us, then confirm the domain in Search Console. No custom code needed.

PodView serves context-aware error pages for podcast and product surfaces. If you need a special landing experience for old URLs, use 301 redirects to send visitors to the right page.

Yes. Keep your podcast host, connect your feed to PodView, recreate key pages, and move your domain when you are ready to switch.

Yes. Beamly was formerly Podcastpage, and the same migration pattern applies: connect the podcast feed, rebuild or import key pages where needed, point the domain to PodView, and use redirects for important old URLs.

No. Your podcast subscribers follow the RSS feed from your podcast host. Moving the website does not move the feed unless you separately change podcast hosts.

You can keep your domain and create matching pages where practical. Exact URL parity depends on the old platform and the paths you need to preserve.

Yes. Your podcast feed stays with your podcast host, your domain stays under your control, and PodView lets you export key audience data such as subscribers and guests.

Yes. The help center, dashboard guidance, and support channels are available when you need help connecting a feed, domain, theme, or integration.

Use the contact page or support channel with the podcast URL, what you expected, and what happened. Specific examples help us reproduce and prioritize the issue.