How-tos
Exclude unwanted text — Exclude List and nospeech
Sometimes the player is in the right place but it still speaks comments, share buttons, related posts, or promo boxes. Use Exclude List and/or the built-in nospeech class so those nodes stay silent while the article still plays.
- Why useful — clean narration without shrinking Content Selector / Render Element too aggressively.
- Exclude List — comma-separated CSS selectors in the widget (or website settings) that must not be read.
- nospeech — add the class in HTML; GSpeech always skips it (no console entry needed).
Open Cloud Console
Multi-Page how-to
All How-tos
How
Exclude List vs nospeech
- Exclude List — example: #comments,.sidebar,.ads,.share-buttons,.related-posts. Best when you cannot edit theme HTML.
- nospeech — example: <div class="promo-box nospeech">…</div>. Best when you control the markup.
- Both apply inside the spoken Content Selector / self_class / parent_class block.
- You can combine them: mark your own blocks with nospeech, exclude third-party widgets via Exclude List.
Setup
How to skip unwanted text
- Play the page and note what should stay silent (comments, CTA strip, related posts).
- In DevTools, copy the CSS selector for that node (#id or .class).
- Open the widget (or website settings) → Exclude List → paste selectors, comma-separated → Save.
- Or, if you edit the theme, add class nospeech on those wrappers instead.
- Hard-reload and listen again — excluded nodes should no longer appear in the audio.
FAQ
Exclude FAQ
-
No. nospeech is built-in and always skipped.
-
Website-level rules apply broadly; widget-level Exclude is for one player. Use website rules for global junk (share bars), widget rules for one layout quirk.