1. Choose author text, visitor input, or audio first
Use Mac Dictation when an author wants editable words in a WordPress post, page, excerpt, caption, alt-text field, comment, or other supported editor surface. The result is text at the focused insertion point.
Use a WordPress plugin only when the site itself needs added functionality, such as a microphone inside a form or a plugin-specific authoring tool. Use the Audio or Podcast Episode block when the artifact should remain playable media. These paths differ in permissions, code, storage, processing, accessibility, and publication behavior.
2. Identify the WordPress editor and hosting boundary
The default WordPress editor builds posts and pages from blocks. A self-hosted WordPress installation, a WordPress.com site, the experimental WordPress.com Write editor, the Classic Editor plugin, and a third-party page builder can expose different text surfaces even when they save into the same content system.
Confirm the site, user role, post type, editor, and active draft before speaking. Do not transfer a shortcut, plugin, plan, or editor behavior from WordPress.com to every self-hosted site—or from one page builder to the core block editor.
3. Dictate into the block editor on Mac
Open Posts or Pages, select the intended draft, and click inside a Paragraph block until the insertion point is visible. Trigger the shortcut currently shown under System Settings → Keyboard → Dictation, speak a short passage, stop, and confirm that the words landed in the correct block.
Dictate prose first. Then apply Heading, List, Quote, Code, Image, Button, or other block structure with WordPress controls. Speech recognition can produce words and punctuation, but it does not guarantee a correct block type, link, slug, shortcode, HTML fragment, code sample, or reusable pattern.
- Confirm the site, post, and block before a long session.
- Start with one short Paragraph block.
- Review names, links, quotations, punctuation, and line breaks.
- Stop Dictation before using slash commands or editor shortcuts.
4. Use the WordPress.com Write editor for focused prose
WordPress.com’s current Write editor is an experimental distraction-free surface for posts. It supports everyday headings, lists, quotes, links, images, videos, categories, and tags while leaving advanced layout work to the block editor.
That simpler surface can be useful for a spoken first draft. Save or publish from its top bar, or open the post in the block editor for layout work. If unsupported formatting is detected, follow the editor warning instead of assuming the dictated version preserves every block.
5. Preserve block semantics after the transcript is correct
Every block has its own toolbar and settings. A dictated paragraph can be accurate as prose while still being the wrong semantic element for a heading, list, quotation, image caption, alternative text, code block, table, button, or navigation label.
Use Document Overview and the settings sidebar to inspect structure. Add links and media deliberately, verify heading order and alternative text, and preview the rendered page at desktop and mobile widths before publishing. Voice input does not replace editorial or accessibility review.
6. Treat autosave, revisions, and publication as separate states
WordPress.com says the editor saves changes locally every 15 seconds and online about once per minute while connected. Save Draft records an unpublished draft; editing a published post continues to autosave without changing the live page until Save or Update is selected.
WordPress revisions preserve saved changes and can restore an earlier version. They are recovery tools, not proof that the correct text, post, site, author, or visibility was chosen. Review the current draft and preview before Update or Publish changes what visitors can see.
7. Install a speech-to-text plugin only for a site-level need
WordPress core treats plugins as additional software that extends the site. The official speech-to-text tag currently contains plugins aimed at different jobs, including post authoring, audio-file conversion, form voice input, and Elementor widgets. A shared tag does not make them equivalent.
WordPress documentation warns that directory plugins vary in quality and may be works in progress. Before Plugins → Add New, inspect the exact purpose, compatibility, last update, active installations, support history, permissions, external services, data handling, and uninstall behavior. Keep a backup and update installed plugins deliberately.
On WordPress.com, current plan documentation says plugin installation is available on paid Personal, Premium, Business, and Commerce plans; free sites must upgrade. That plan rule does not apply to every self-hosted WordPress installation.
8. Keep the Audio and Podcast Episode blocks outside dictation
The WordPress.com Audio block displays an uploaded file, an item from the Media Library, or audio inserted from a URL. Its player, caption, preload, loop, autoplay, and browser download behavior concern retained media. The block does not turn a live Mac voice into editable post text.
A WordPress.com podcast episode is a post with a Podcast Episode block, an uploaded audio or video file, and the configured podcast category. The post title and show notes remain separate editable fields. Upload, category, plan, feed, directory, explicit-content, and Publish settings all require deliberate review.
9. Do not confuse Posts to Podcast with speech to text
WordPress.com’s Posts to Podcast feature starts from already published writing and generates a two-host audio conversation. A successful run creates a new draft containing an Audio block and a written transcript.
That is text-to-audio generation with a generated transcript—not author dictation and not transcription of the author’s microphone. WordPress.com says a generation consumes a credit, cannot currently be retried, and does not expose voice, length, tone, or topic controls. Review the generated draft before publishing it.
10. Troubleshoot the failing layer before adding software
If Mac Dictation produces no text, test the same shortcut in TextEdit. If it fails there too, inspect Keyboard → Dictation, the selected language, shortcut, microphone input, Voice Control, and current network requirement.
If TextEdit works, return to a plain Paragraph block, refocus it, and test one sentence. Disable conflicting editor extensions or plugins for a controlled test. A page-builder canvas, code editor, embedded form, role restriction, unsaved conflict, or plugin error can fail without the speech recognizer being broken.
11. Add IraVoice only for the separate local Mac input path
IraVoice 0.7.1 is a separate option for macOS 26+ Apple-silicon Macs when speech recognition and supported formatting should run on the Mac across supported WordPress, browser, email, note, and developer fields. Models download on first use; the full trial needs no activation, and paid continuation needs one Gumroad key check.
IraVoice is not a WordPress plugin. It does not sign in to WordPress, read sites or drafts, choose blocks, install or audit plugins, upload media, generate podcasts, set categories or tags, change SEO fields, select visibility, schedule content, restore revisions, preview pages, or press Save, Update, or Publish. It targets a supported focused editable field and falls back to the clipboard when direct insertion is uncertain.