On-page audio · text to podcast

Turn an article into a short two-voice conversation.

Two voices talk through your article for a few minutes. The player sits on your page with the transcript under it, and search engines can read both.

Paste one snippet into WordPress, Webflow or any CMS
Transcript and schema markup rendered on the page
30 voices and 24 languages
your-blog.com / post Listen player · embedded
Listen to this article Two-voice · 6:24
0:00 6:24
View transcript
Host: The article is about writing an expense policy for a small company. The first point is that the policy should fit on one page.
Guest: One page sounds short. What goes on it?
Host: Who can spend, up to how much, and how they get paid back. The author says anything past that gets ignored.
Guest: And the receipts question. The piece says to pick one place for them and stop there.
2 voices
A host and a guest, talking through the article
30
Voices to pick the host and guest from
24
Languages, auto-detected or set by hand
4-18 min
Three lengths: short, standard and deep
Why it helps SEO

What search engines can read.

The audio file itself is invisible to a crawler. The transcript and the structured data next to it are not.

On the page
Crawlable transcript
The full transcript is rendered as HTML on the page, so crawlers read it without running JavaScript.
Structured data
AudioObject and PodcastEpisode JSON-LD, with transcript, duration, and content URL.
What it is not
Not a copy of your article
The transcript is a conversation written from your article, so the page does not carry the same text twice.
Not a read-aloud
A host and a guest explain the article in their own words, which is a different page than the one a screen reader would read.
What you can see
Listening numbers
Plays, pauses, resumes, progress and completions, per episode.
Time on page
How long listeners stay compared with readers who did not press play.
Engagement you can measure

See how people listen.

The player sends five events, and the chart is built from them. No cookies, and nothing that identifies a person.

PlayPauseResumeProgressCompletion No PII collected
Listener journey Last 30 days · Example data
Played4,820 · 100%
Reached 25%3,610 · 75%
Reached 50%2,740 · 57%
Completed1,980 · 41%
3:58
avg. listen time
41%
finish the audio
+38%
time on page
What you get

What comes with the snippet.

Hosted audio, the player, the transcript, the schema markup and the listening numbers. Nothing to record.

Three lengths
Short is 4 to 5 minutes, Standard 8 to 10, Deep 15 to 18.
Two voices
A host and a guest. Pick each one from 30 voices.
Copy-paste embed
One snippet with the button, the audio, and a collapsible transcript.
Hosted by us
The audio loads when someone presses play, not when the page loads.
Listening numbers
Play, pause, resume, progress and completion. Nothing that identifies a person.
Schema + transcript
AudioObject and PodcastEpisode JSON-LD plus a crawlable transcript on the page.
The embed

Paste one snippet.

Drop it into a Webflow code embed, a WordPress block or any CMS. It carries the button, the audio, the transcript, the listening events and the schema markup. The audio loads when someone presses play.

WordPress plugin Webflow embed Any CMS
embed.html
<!-- Hi, Moose · Listen to this article -->
<div class="himoose-podcast-player"
     data-job-id="yourJobId"
     data-title="Listen to this article"
     data-analytics-url="https://pod.himoose.com/track"
     data-primary-color="#f69e0b">
  <div class="himoose-player-container">
    <audio preload="metadata" style="display:none">
      <source src="https://audio.himoose.com/listen/your-blog.com/yourJobId.mp3" type="audio/mpeg">
    </audio>
    <div class="himoose-player-controls">…</div>
  </div>
  <details class="himoose-transcript">
    <summary>View Transcript</summary>…</details>
</div>
<script src="https://player.himoose.com/himoose-podcast-player.js" defer></script>
Questions & answers

Listen to this article, explained.

What exactly does the generator do?
It turns an article or URL into a short two-voice conversation. You get a hosted audio file, an embeddable player, a transcript rendered on the page, and listening numbers.
How is this different from a standard read-aloud player?
A read-aloud player reads your page out loud, word for word. This writes a short conversation about your article, records it with two voices, and puts the transcript and schema markup on the page.
Does it work with WordPress and Webflow?
Yes. There is a WordPress plugin, and for Webflow or most other CMSs you paste the snippet into a code embed or HTML element.
Is the transcript just my article again?
No. It is the conversation the two voices have about your article, written out. It does not repeat your text.
Which languages and voices are supported?
24 languages, detected from the article or set by hand, and 30 voices. Each voice has a style, such as bright, firm or knowledgeable.
How long are the podcasts?
You pick one of three lengths. Short runs 4 to 5 minutes, Standard 8 to 10, Deep 15 to 18.
Who owns the audio and transcript?
You do, as long as you own the article. We host the files while you are a customer. If you leave, download the MP3 and host it yourself.
What does it cost?
Every account gets 3 free episodes, for life. After that, audio is on every paid plan. On plans with AI included, each episode uses your monthly AI credits. The first 10,000 listens a month are included, and more cost $5 per 10,000.
Publish content people can read or listen to

Add a listen button to your next article.

Paste the article, pick two voices and a length, and put the player on the page. The first 3 episodes are free.

Make your first episode See pricing