How I'd grow Monologue

Monologue is a dictation app for Mac, iPhone, iPad and Apple Watch, built by Every. You hold a key, talk, and polished text lands in whatever app you’re using. It costs $15 a month, or it comes free with an Every subscription.

Monologue’s parent company, Every, has a Domain Rating of 77. The search traffic is low because its pages target the wrong searches, and because Every’s links all go to the homepage.

Monologue gets 0.2% of Wispr Flow’s search traffic

These are Ahrefs’ estimates of this month’s Google traffic for the main dictation apps.

Some of that gap is brand. About 80% of Wispr Flow’s traffic is people typing “wispr flow” (39,000 US searches a month, and another 23,000 who spell it “whisper flow”). You can’t SEO your way into someone else’s brand demand.

Smaller apps like Willow Voice and Spokenly pull in thousands of visits from people who have never heard of them, searching for things like “dictation software” and “speech to text mac”. Visitors like these are the ones most likely to start a trial.

Every visit Monologue gets comes from one word

Every keyword Monologue ranks for in Ahrefs is the word “monologue”, in one country or another. All of it lands on the homepage. DataForSEO agrees: 49 of the 50 searches it has Monologue ranking for go to the homepage.

That word is mostly searched by people looking for theatre monologues. So when Google tested Monologue for it, traffic rose. When Google decided those searchers wanted drama school, it fell.

That chart is from third-party estimates, not Monologue’s Search Console, so the trend is more reliable than the exact numbers. Either way, a peak of 3,000 visits from people who wanted a Shakespeare speech was never going to sell many subscriptions.

The right pages exist, and they’re good

I didn’t expect this. Monologue’s sitemap has 80 pages, and many of them are the pages I’d tell a dictation app to build:

• six comparison pages (Wispr Flow, Superwhisper, Aqua Voice, Willow Voice, Granola and Otter)
• five use-case pages (developers, writers, product managers, founders and support)
• a dictation page, a notes page, pricing, docs and a changelog

Nothing technical holds these pages back. An SEO Skill crawl shows they’re indexable, have self canonicals, sit in the sitemap and are linked from the main navigation. The Wispr Flow comparison is about 2,500 words with Article, FAQ and breadcrumb structured data. The others are about 1,100 words each.

The comparison pages are also new. The Wayback Machine first saw them on 19 October, so some of the gap is just time. The titles explain the rest.

The pages answer a question buyers don’t ask

The comparison pages are titled “Monologue vs Wispr Flow”, “Monologue vs Superwhisper” and so on. It’s a natural way to write them, but almost nobody searches for those titles, because you can only search “Monologue vs Wispr Flow” if you already know Monologue exists.

These are the searches people make when they want to switch dictation apps (DataForSEO, US monthly searches).

About 1,300 people a month search for a Wispr Flow alternative, at a difficulty of zero. Another 1,000 compare Superwhisper and Wispr Flow directly. Those people are about to pay for a dictation app, or already are and want a better one. Right now Medium posts and YouTube videos get them.

The existing pages can stay mostly as they are. I’d keep the vs pages. Then I’d add alternatives pages that answer “what should I use instead of Wispr Flow”, and a page comparing the two leaders that’s honest about both (and makes the case for a third option).

Every links to Monologue 278 times, and always to the homepage

This is the biggest finding, and I only found it because I crawled Every’s site as well as Monologue’s.

Every.to has a Domain Rating of 77 and about 7,800 sites linking to it. Monologue has 50 and 780. A crawl of 600 every.to pages found every link to a Monologue URL.

218 of the 600 pages link to Monologue. Nearly all of those links point at the homepage, which already ranks for the brand. The comparison and use-case pages get no links. The same pattern repeats for Every’s other apps: about 450 links to the Cora homepage, 440 to Sparkle and 180 to Spiral, all with the product name as the anchor.

Four posts also link to monologue.co, a parked domain, five times in all. Readers who click those links to try the app get a parking page. It looks like a typo for monologue.to: in one post the link text even says “monologue.to”.

<a href="https://monologue.co/">monologue.to</a>

<a href="https://www.monologue.to/">monologue.to</a>

None of this needs new content. A find-and-replace across Every’s CMS fixes it and puts Every’s links behind the pages that sell.

New content: the searches competitors win with no Monologue page

The alternatives pages above go after searches Monologue already half-targets. The bigger gap is the searches it doesn’t target at all: non-brand searches that Wispr Flow, Superwhisper, Willow Voice, Spokenly, Aqua Voice and Typeless rank for in the US (Ahrefs), with no matching page in Monologue’s sitemap.

Most of the competitors’ non-brand traffic lands on a handful of pages, and none of them sells anything directly.

Superwhisper’s list of the best speech to text apps is 856 words long, and after the homepage it’s the page that gets the most visits on the whole site. Willow Voice’s list is the same idea, about six times as long. Both are a dictation app ranking dictation apps, and both rank on page one.

Grouped, the gaps make four clusters, plus a free tool Monologue has already built. The volumes below are Ahrefs’ US estimates, so they won’t match the DataForSEO table above (Ahrefs puts “wispr flow alternative” at 150, DataForSEO at 720).

1. A best dictation apps page

The biggest cluster is people choosing a dictation app: about 8,850 US searches a month across nine searches, at difficulties from 5 to 43.

Wirecutter, Zapier and PCMag rank for them, next to the lists from Willow Voice and Superwhisper. Zapier’s list already includes Monologue. PCMag’s, Willow Voice’s and Superwhisper’s don’t.

Monologue has something none of these lists publish: measured accuracy. Its post introducing mono-1 tested its own model on WildSpeech-Bench (a 7.22% word error rate, second-lowest of the systems tested, behind GPT-4o Transcribe at 6.68%). Run every app on the list through the same test, and publish the error rates and response times in one table. Be as honest about where other apps win as the comparison pages already are.

Proposed page: The best dictation apps for Mac and iPhone in 2026, at /best-dictation-apps.

2. A Mac dictation guide

Monologue works best on the Mac, and about 1,630 US searches a month come from people trying to dictate on one. Most have difficulties of 0 or 1.

Apple’s own help page ranks first, then YouTube videos. Spokenly’s “Speech to Text on Mac: 9 Best Apps Tested” and Willow Voice’s Mac list rank sixth and seventh for “speech to text mac”. Nobody on page one covers both the built-in Dictation and when an app does better.

Proposed page: How to dictate on a Mac, at /guides/mac-dictation.

3. A guide to talking to coding agents

This is the newest cluster and the one closest to Every’s readers. “claude code voice mode” gets about 500 US searches a month and “claude code voice” about 450. They’re new enough that Ahrefs has no difficulty or results page for either.

ChatGPT and Google AI Mode answer “how do I dictate prompts to claude code” with GitHub and Claude’s own docs, and name no dictation app. Monologue’s developers page already has “Prompt Coding Agents by Voice” in its title, but it’s an 877-word product page, and these searchers want steps.

Proposed page: How to talk to Claude Code, Codex and Cursor, at /guides/voice-coding, linked from the developers page and from every Every essay about coding agents.

4. Meetings and voice memos without a bot

Bot-free meeting notes are in Monologue’s homepage title. Wispr Flow is the one getting the searches. Its notetaker section gets about 1,270 US visits a month (Ahrefs), and an AI Overview cited its “record meetings without a bot” page when I asked how to do exactly that. Monologue has no page that answers the question.

The Granola and Otter comparison pages stay. The alternatives pages work like the Wispr Flow one: they answer “what should I use instead” for people who don’t know Monologue yet.

I’d leave two big clusters alone for now. “ai note taker” gets 16,000 searches but has a difficulty of 80. Medical dictation (1,000 searches, difficulty 3) is where Wispr Flow and Willow Voice get some of their traffic, but those buyers need compliance answers before features.

Talk Fast: the free tool Monologue already built

Monologue has a free speaking speed test called Talk Fast. You read a line out loud, it times you, scores how much survived transcription and ranks you on a leaderboard. It’s in the sitemap, but the homepage and the dictation page don’t link to it, and its title doesn’t use any words people search for.

TypingMaster and Teleprompter.com rank first and second for “speaking speed test”, and Superwhisper’s words per minute test is seventh. The first fix is the search result.

Then the page needs words that a searcher and a crawler can read. Today its HTML has 63 words, and the leaderboard loads in the browser, so a crawler sees “Loading the board…”. I’d add a short section on average speaking rates, a comparison with typing speed (the dictation page says you can “speak up to 3x faster than you type”, and Talk Fast can show it), and the leaderboard’s own numbers in the HTML: the top 20 and the median speed of everyone who has taken the test. That’s data only Monologue has.

Typing tests are the long shot. “words per minute test” gets 26,000 searches a month at a difficulty of 68. A “typing vs talking” mode on Talk Fast would give Monologue a reason to compete for it.

One page per app

People search for dictation inside the app they’re using. “voice to text google docs” gets about 1,600 US searches a month at a difficulty of 9, and “voice typing google docs” 1,000 at 4. Google’s own help page and a public Google Doc rank first, then YouTube.

Monologue works in every app, and on the Mac a mode can switch on by itself for a chosen app or website. That’s the pattern: one page per app at /dictation/[app], each with what the app’s own voice typing does, how Monologue works there, and a mode to copy for it. Each page needs its own steps and screenshots. The same page with the app name swapped would be thin.

What AI crawlers get from Monologue

Access doesn’t decide who AI answers cite. Monologue’s homepage and Wispr Flow comparison return the same full page, with a 200, to a browser and to the GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot user agents. The homepage, the dictation page, the developers page and the Wispr Flow comparison point to their Markdown copies with an alternate link. Wispr Flow also serves full pages to every user agent and its robots.txt allows everything. Superwhisper has an llms.txt and Willow Voice doesn’t.

Who AI answers cite instead of Monologue

Monologue was cited in none of the 26 answers ChatGPT search, Google AI Mode and Google AI Overviews gave to ten questions buyers ask about dictation apps. Wispr Flow was cited in 7 of 29 answers to the same questions. (Three answers used the word “monologue”, but it’s also an ordinary word, so I don’t count them.)

The sources from a second run of the same questions through ChatGPT search and AI Mode (DataForSEO) show who gets cited instead.

• Superwhisper was a source in 9 of the 20 answers, more than any other site. For “superwhisper vs wispr flow”, both engines cited its page comparing the two. That’s the page I suggested above, and Superwhisper got there first.
• Wispr Flow gets cited for pages that answer the question as it’s asked: its pricing page, a Superwhisper alternative page, its dictionary help article and “record meetings without a bot”.
• Two questions had no dictation app in the answer. Apple Watch voice notes went to Wave and Just Press Record, and dictating prompts to Claude Code went to GitHub and Claude’s docs. Monologue runs on Apple Watch and is built for prompting coding agents, and no dictation app holds those citations yet.
• Offline Mac dictation went to MacWhisper and VoiceInk, and meetings without a bot to Otter and Krisp.
• Monologue did get cited once, in the second run: AI Mode put it second in its answer for “best dictation app for mac”, citing Monologue’s homepage next to Zapier’s list, which includes Monologue. Lists feed answers, so the roundup outreach matters here as much as in Google.

The cited pages have something in common: the title is the question, and the answer is near the top. Monologue’s comparison pages do open with a short answer, but every one of them puts Monologue in the question. AI answers to questions that don’t name Monologue need pages that don’t either.

The fixes are the pages above, in this order for AI answers: Superwhisper vs Wispr Flow, how to record a meeting without a bot, voice notes on Apple Watch, the coding agents guide, and the best dictation apps page with its benchmark table. Then rerun the same ten questions once a month and compare.

Ship it all today, then let it settle

None of this needs a four-week sprint. Each fix is a separate job, so coding agents can work on all of them at once:

1. 1

   Portfolio links

   Point Every links at the dictation, comparison and developers pages with descriptive anchors. Fix the five monologue.co links, and link to www.monologue.to directly.

2. 2

   Alternatives pages

   Wispr Flow, Superwhisper, Granola and Otter alternative pages, plus Superwhisper vs Wispr Flow.

3. 3

   Best dictation apps page

   Run every app through the mono-1 benchmark and publish the error rates and response times in one table.

4. 4

   Mac dictation guide

   Built-in Dictation, its shortcuts and fixes, offline dictation on Apple silicon, and when an app does better.

5. 5

   Coding agents guide

   Talking to Claude Code, Codex and Cursor, linked from the developers page and Every essays.

6. 6

   Meeting and voice memo pages

   Recording a meeting without a bot, and transcribing voice memos on iPhone and Apple Watch.

7. 7

   Talk Fast

   New title and description, a short section on speaking rates, the leaderboard in the HTML, a Markdown copy, and links from the homepage and the dictation page.

8. 8

   App pages

   Start with Google Docs and Word, each with its own steps, screenshots and a mode to copy.

9. 9

   Markdown copy for the blog

   A Markdown copy and alternate link for the mono-1 post.

10. 10

    Roundup list

    Find the best dictation software posts that rank and leave Monologue out, such as PCMag's, and draft a short, accurate pitch for each.

Someone on the team still needs to review the new pages and do the roundup outreach. The link, title and Markdown changes need only a quick check.

Then I’d spend 30 days checking the results:

1. Day 0

   Day 0: Ask Google to recrawl

   Submit every new and changed URL to Index My Site, so Google recrawls them now instead of on its own schedule.

2. Day 3

   Day 3: Check indexing

   Confirm the new guides, the alternatives pages and the retitled comparison pages are indexed.

3. Day 7

   Day 7: First impressions

   Look for impressions on "wispr flow alternative" and "superwhisper vs wispr flow" in Search Console.

4. Day 14

   Day 14: Clicks from Every

   Check clicks from every.to links to the comparison and dictation pages.

5. Day 30

   Day 30: Trials

   Compare trial sign-ups from search with the month before.

6. Day 30

   Day 30: AI answers

   Ask the same ten questions with ai_answers, for Monologue and Wispr Flow, and compare the citations.

Get the changes seen quickly

Every step above either changes existing pages or adds new ones, and Google doesn’t recrawl a two-week-old comparison page on your schedule. I’d submit each new and changed URL to Index My Site the day it ships, so Google is asked to recrawl it straight away instead of finding it on its own schedule. That matters most for the retitled comparison pages, where the old title is what Google currently has.

How I ran this

Everything in this teardown came from SEO Skill, run by an agent. You can run the same audit on your own site.

1. Connect the hosted MCP server. It’s free. You sign in with Google, and there’s no password and nothing to install. In Claude Code:

claude mcp add --transport http seoskill https://seoskill.dev/mcp

Codex, Cursor and Claude on the web work too. The MCP guide has the steps for each one.

2. Add a research key. On your account page, save an Ahrefs or DataForSEO key. The key gives your agent search volumes, rankings and results pages, like the tables above.

3. Install the CLI for crawling. The crawl runs on your machine, so it can read any site:

npm i -g seo
seo login

4. Ask your agent. This is close to the prompt I used:

Audit example.com and every site we own.
Crawl each one with seo crawl. Find where our sites
link to each other and which pages those links hit.
Use seo_research to find the searches our buyers
make, who ranks for them and whether we can compete.
Find the searches our competitors win that we have
no page for. Ask ai_answers ten questions our buyers
ask, for us and our top competitor.
Rank every fix by how close it sits to revenue.

On your own site, the hosted server adds the part I couldn’t see from the outside: your real Search Console clicks and queries. With those, you get measured numbers where this post has estimates.

Then crawl your parent or sister sites and look at where they link to you. Most audits skip that step.

If you’re on the Monologue team, I’m happy to go through any of this. And if you’d like the same teardown for your site, SEO Skill will run it for you.