Use Multi-Page Widget

Already set — leave them for maximum convenience

On a normal WordPress / blog theme you usually do nothing after Cloud activation — Multi-Page is already created and published. Both placement and reading targets are prefilled:

• Render Element — already a comma-separated list of common content wrappers (where the player appears). Default: .entry-content,.post-content,.post_content,.post,.blog,.blog-body,.content,.section,article.
• Content Selector — already self_class (what is spoken).

Change Render Element only if your theme uses a custom content wrapper that is not in that list (for example .wp-content or #main). Until then, leave it.

self_class = right where the player is

self_class means: narrate the same element the player was injected into. Player UI and spoken text stay in one place — that is the convenient default.

• Do not change Content Selector for normal use — keep self_class.
• If you later change Render Element for a custom wrapper, keep self_class — it still means “read that same place.”
• Change Content Selector only when spoken text must come from a different node than where the player sits.
• Render Position — Before or After (After is typical). Change only if you want a different insert side.

Exclude List and the nospeech class

Optional — only when something inside the content block should stay silent (comments, share buttons, related posts, promo boxes):

• Exclude List — comma-separated CSS selectors that must not be read, even inside the spoken block. Example: #comments,.sidebar,.ads,.share-buttons,.related-posts.
• nospeech class — built into GSpeech. Any element with class nospeech is skipped automatically (no need to put it in Exclude List).

Example: <div class="promo-box nospeech">…</div>

Prefer nospeech when you control the HTML. Use Exclude List when you cannot edit the markup.

Allowed Urls and Blocked Urls (optional)

By default the player can appear on every page where Render Element matches. Touch URL lists only when you want to limit that:

• Allowed Urls — only these URLs get the player. One URL per line. * = wildcard.
• Blocked Urls — hide the player on these URLs.

• Only About — Allowed: https://example.com/about.
• Everywhere except About — Blocked: https://example.com/about.
• All blog posts — Allowed: https://example.com/blog/*.
• Hide homepage — Blocked: homepage URL.

How to use Multi-Page (usually already on)

1. Activate Cloud for your website — the Multi-Page widget is created and published by default (with RHT; Welcome stays disabled; shortcode widgets are ready when you place a shortcode).
2. Open Widgets → Multi-Page Full Page Player only if you want to review settings.
3. Leave Render Element and Content Selector (self_class) as they are — maximum convenience.
4. Change something only if you need it: custom Render Element, Exclude List / nospeech, or Allowed / Blocked Urls.
5. Hard-reload a page and confirm the player appears where you expect.