Email verification
Confirm access to the podcast owner email found in the RSS metadata.
Castee separates public feed import from publishing authority so creators can explore a draft without letting someone else claim their show.
Ownership verification is a publishing requirement on every plan.
What it does
Public RSS data can be imported for a draft, but the right to publish a branded website must be verified.
The primary flow sends a verification message to the owner email exposed by the podcast feed. A manual path covers feeds without a usable owner email.
Confirm access to the podcast owner email found in the RSS metadata.
Keep publishing unavailable until ownership requirements are satisfied.
Provide a fallback when the public feed does not expose a workable owner address.
How it works
Use the same controlled workflow whether you are starting your first website or maintaining an established show.
Castee reads the public podcast metadata.
Use the available owner email or begin the documented manual path.
Publish after the verification state is approved.
SEO impact
Castee handles repeatable technical work while you control the accuracy, usefulness, and editorial quality of the public content.
Castee verification is a product safety control, not a Google ranking factor.
It helps keep site administration tied to an authorized podcast operator.
Authorized owners can maintain canonical domains, branding, and show information over time.
A public RSS feed can be read by anyone. Verification prevents someone from publishing an official-looking Castee site without authority.
Use the manual review path described in the product workflow.
No. It is an authorization control, not an SEO ranking feature.
Use your own podcast
Paste a public RSS feed and see how your episodes and artwork fit a Castee site.
Start for free