A listener says your station’s name and Alexa plays something else. It is a common and frustrating problem, but it usually has a practical cause.
1. Your name is hard to recognise
Voice assistants struggle with unusual spellings, numbers and names that sound like other stations. Say your name aloud as a listener would. Does “Z-101” become “Zee one oh one” or “Zed one hundred and one”? Amazon’s no-code radio setup allows alternative names, so use them for realistic variations.
2. Your stream fails the technical rules
For no-code radio, Amazon requires HTTPS streams and does not accept URLs containing an IP address or streams that need a click to start. Supported formats include AAC/MP4, MP3, PLS, M3U/M3U8 and HLS. A stream that plays in a browser may still fail these checks.
3. Your location details are wrong
Alexa uses location to help find nearby matches, and your listing needs the correct country, language, locale and coordinates. Errors can make it harder for local listeners to reach you.
4. Your listing has not gone live
Amazon says ingestion can take up to 72 hours, or up to three weeks for Great Britain and Ireland. Check the status in the console before assuming there is a fault.
5. Another station has a similar name
If several stations share a name, Alexa may choose another one. Teach listeners a precise phrase that includes your city or frequency, such as “Alexa, play [Station Name] [City].”
A quick test routine
- Test on a real Echo device, not only in a simulator.
- Try several ways of saying your name, and ask friends with different accents to try.
- Test from inside and outside your local area.
- Write down which exact phrases work.
- Use the most reliable phrase in every on-air promotion.
Repeat the test after any change to your stream address or station name.
Planning your station’s next step?
iBitway builds iOS and Android apps, Alexa skills and websites for radio stations. Request a free demo and tell us what you need.

