How-tos
Use default shortcodes — drop a player into WordPress content
Default shortcodes are the fastest way to put a GSpeech player inside a WordPress post, page, or product. When you activate Cloud, three shortcode widgets are created automatically (Full / Button / Circle) and are ready — you only need to paste the shortcode where the player should appear. With Content Selector parent_class, the widget narrates the parent content around that shortcode.
- Why useful — no custom CSS selectors for typical posts; insert once and the parent block is read automatically.
- Created on activation — Full / Button / Circle shortcode widgets already exist; you place the shortcode in the editor.
- Works in the editor — [gspeech], [gspeech-button], or [gspeech-circle].
- parent_class default — reads the wrapping content, not the empty shortcode node.
Open Cloud Console
WordPress docs
All How-tos
Why
When default shortcodes are the right tool
- Article listening — put a Full Player shortcode at the top of the post body.
- Compact listen CTA — Button or Circle shortcode next to a heading or CTA.
- Per-page placement — you choose the exact spot in content without multi-page URL rules.
Setup
How to use a default shortcode
- Activate Cloud — the three shortcode widgets (Full / Button / Circle) are created automatically and ready.
- Leave Content Selector as parent_class unless you need a custom selector.
- In the WordPress editor, paste the shortcode where the player should appear — Full: [gspeech], Button: [gspeech-button], Circle: [gspeech-circle].
- Save the page, open the front end, and press play to confirm the parent content is narrated.
parent_class
Why parent_class is the default
The shortcode itself is an empty mount. parent_class tells GSpeech to read the parent wrapper where you inserted the shortcode — typically the post content block — so visitors hear the article, not an empty node.
- Change Content Selector only when you need a precise CSS target (for example .entry-content or article).
- Use Exclude List to skip comments, related posts, or ads inside that parent.
- For players outside the post body (sidebar / footer), prefer a custom widget placement with explicit Render Element + Content Selector.
FAQ
Default shortcodes FAQ
-
For the default Shortcode widgets, keep the documented mount class (for example .gsp_full_player). Allowed / Blocked URLs are usually not needed when you place the shortcode manually on each page.
-
Shortcode = you pick the exact insert point per page. Multi-page = automatic placement by URL / selector rules across many pages. Start with shortcodes when you want simple, per-page control.
