fix(seo): Windows, flows and HubSpot on 9 locales

[wavekat-eason]

What was wrong

Two page families claimed WaveKat Voice runs on two platforms while the comparison table on the same page said three. Windows shipped in #155; /voice/alternatives/linphone/ and /voice/providers/2talk/ were never updated, in any of the nine locales.

The 2talk page was worse than stale — it told the reader Windows was hypothetical, then sent Windows visitors elsewhere:

'Mac and Linux today (Windows when there is demand).'
'Mac 和 Linux（有需求时支持 Windows）。'
"You're on Windows and want a free, lightweight client today — that's MicroSIP"

Separately, call flows and the HubSpot integration — two of the clearest differences against a plain SIP client — appeared on neither page.

Five of the nine alternatives titles also led with the brand (WaveKat Voice — a Linphone alternative, WaveKat Voice — alternativa a Linphone (Mac/Linux)), spending budget on a term that already ranks #1.

What changed

Both pages, all nine locales:

	Before	After
Platform claim	title, description, H1, intro all "Mac & Linux"	all three, everywhere, with the honest caveat that the Windows build is newer and unsigned
Titles	brand-first, or 2 platforms	demand-first, 3 platforms (Linphone alternative for Mac, Windows & Linux, 2talk 软电话（Mac/Win/Linux）)
Comparison rows	8 / 7	10 / 9 — added answering & voicemail, and CRM logging
FAQs	3 / 6	7 / 9
Breadcrumb node 1	Voice	WaveKat Voice + inLanguage

• Call flows / voicemail are stated with the mechanism, not as a bullet: greeting, opening hours, menu, voicemail or transfer; the message is recorded and transcribed; you can pick up mid-message. The FAQ names the real limits — menus, hours and transfers are Pro (free for a year in early access), and the flow runs on your own computer, so if the app isn't running the provider's voicemail takes the call.
• HubSpot: connect once, every call files itself on the number-matched contact with time, direction, outcome, duration, transcript, and a recording playable inside HubSpot. Pro, free during early access, webhooks for other CRMs.
• Fair to the competition: Linphone, Bria and MicroSIP each get "no answering of its own — voicemail is your provider's mailbox, which it can dial", and MicroSIP keeps its genuine strength ("the smallest possible Windows client") without implying we don't run there.
• Every localized title and description re-measured against its own budget (CJK ≤ 28/85, Latin ≤ 50/160) instead of translated from English. check:meta caught four CJK descriptions over budget mid-review — they're now 80–85.
• Localized "where to go next" blocks (the pages previously linked out only to the hub) and each language's conventional FAQ heading.

Verification

npm run build && npm run check:links && npm run check:meta
✓ links OK — 241 pages scanned, no broken or leaking internal links.
✓ meta OK — titles and descriptions within budget

Checked against dist/: all 18 pages carry 7/9 FAQs, 10/9 comparison rows, the corrected breadcrumb entity, and both new topics. The only surviving Mac and Linux strings on these pages are inside the new Windows FAQ answers, where they're correct.

Deliberately not in this PR

• The Bria price — NZ$5.95 + GST / month (as of July 2026) appears in the 2talk table and two FAQs in all nine locales. The dataset comment says re-check before quoting; I couldn't verify it, so I left the figure and its "as of" stamp rather than restamping it and manufacturing false freshness. Worth a two-minute check.
• Seven blog posts still open with "WaveKat Voice — the SIP softphone for Mac and Linux …" in all nine locales, two of them in the meta description. Same defect class, ~60 strings; these are dated announcements, so how to phrase it is a separate call.

🤖 Generated with Claude Code

https://claude.ai/code/session_01P1W6SyAGqXSQUbDN4fHfUi

[github-actions]

🔗 Preview: https://fix-voice-pages-windows-flow.wavekat-com.pages.dev