Adding audio to a travel blog: long stories, place names and listening on the move
A travel blog stacks two challenges for an audio version: long pieces you would like to hear on the road, and foreign place names a synthetic voice easily mangles. What can be fixed, and how.
A travel blog is not a blog like any other from an audio point of view. Its articles are often long, halfway between story and practical guide, and its reader rarely consumes them sitting at a desk: they plan a route on public transport, replay a travel log while walking, look up an address on arrival. Two constraints stack up, then: reading that has to hold over time, and a wealth of foreign proper nouns a synthetic voice can quickly mangle. Both can be handled, but you have to know where to look.
The long story is a good candidate for listening
Much web content is too short to justify listening: you read faster than you hear, and voicing three paragraphs adds nothing. The travel story escapes that rule. A thousand-word log, a detailed stage guide, a feature on a region all lend themselves naturally to listening, precisely because they are too long to read standing on a train. Audio frees the hands and the eyes, and it is the same hands-free benefit we describe for food blogs: the reader keeps doing something else while following you.
That listening on the move raises a concrete question of file weight, especially off a fast connection. A long article produces a heavier audio file, and the reader downloading over mobile data does not want to burn their allowance on it. We measured that constraint in a close context, media in French-speaking Africa, and it holds for any traveling reader: a well-encoded audio stays reasonable, but it is worth keeping in mind when you decide how long your articles run.
Place names: the real test of a voice
This is where the credibility of a voiced travel blog is decided. A piece on Guatemala, Kailash or Reykjavik puts a synthetic voice to the test in every paragraph. A voice trained mostly on common words will try to read those names by the rules of its own language, and the result rings false to anyone who knows the place. For content whose authority rests on being there, a rough pronunciation of the locations is a flaw that undermines everything else.
The good news is that this flaw can be fixed. How a voice tool behaves on proper nouns, and how to correct it by hand, is the very subject of our article on pronouncing proper nouns and place names. In practice, a pronunciation lexicon lets you fix once and for all how a recurring name should be said, and that correction then holds across all your articles. You do not solve the problem each time, you teach it to the engine.
What a synthetic voice does well, and what it will not do
Let us be clear about the limits, because hiding them would cost you at playback. A synthetic voice reads plain, correctly punctuated prose very well, with place names prepared in the lexicon. It will not carry the emotion of a narrator who actually lived the scene, and it will not guess the local pronunciation of a name it has never seen unless you tell it. Our stance, set out plainly on the French text to speech page, is to read one language well rather than many badly: for a blog full of foreign names, that means a solid base and a lexicon that absorbs the exceptions, not a promise of universal perfection.
Where to start if you run a travel blog
The simplest move is to voice your longest, most-read articles first, the ones a reader would want to take with them. Spot the recurring place names in those texts, add to the lexicon the ones the engine mangles, and replay the passage to check. In a few settings, a log that sounded mechanical becomes a reading you can genuinely follow while walking. It is a modest effort next to what it opens: your stories finally travel with the reader to the places they are about.
Try it on your own stories
The free plan of WeDispatch lets you voice your travel articles today, with your real texts and your real place names: try it now. The plans, from 69 to 419 EUR excluding VAT per month, are detailed on the pricing page.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo