Tiptap headless editor
Modern React-friendly editor; word count as a custom extension.
Writer Utility / SaaS · Case Study
Text Word Count — Tiptap Editor for Writers & SEO Teams
A web app for writers and SEO teams — word count, character count, reading time, and keyword density analysis on a Tiptap editor — targeting Lighthouse 100/100.
Results
Measurable Outcomes
100/100
Lighthouse SEO
200ms debounce
Real-time calculation
TR + EN
Language support
TODO — GA4
Monthly active users
The Brief
What was the goal?
Writers count words in one tab, measure keyword density in another tool, estimate read time in a third editor. There wasn't a single editor delivering all those metrics live (especially with Turkish + English language support).
The Approach
Which methodology pillars I applied
I applied the Technical pillar (Lighthouse 100/100 target, INP < 100ms) and AEO pillar (snippet-ready Q&A formatting for "how long does X words take to read").
See the full process → 47-Point AI-Ready SEO Audit methodology.
Tech Stack
What it's built with
- Next.js 15
- TypeScript
- Tiptap
- Tailwind CSS
- Schema.org SoftwareApplication
The Build
Key decisions and tradeoffs
Tiptap editor pick over TinyMCE/Quill: modern, headless, React-friendly, clean plugin system. Word/character count is a custom extension.
All calculations run real-time with 200ms debounce; the UI stays smooth. Separate word-boundary regex for Turkish + English (Turkish handles connectives differently).
Output block: "X words, Y characters, Z minutes reading" tagged with SpeakableSpecification — AI Overview can cite us on "how long does X words take to read".
Steps Applied
Methodology in practice
TR/EN word boundary regex
Separate regex for Turkish + English; consistent handling of connectives + compounds.
Speakable output block
"X words, Y characters, Z minutes" with SpeakableSpecification, AI-citation-ready.
Honest Reflection
What I'd Do Differently
On launch we added a keyword density module but didn't guide users on "which words matter" — just showed numbers. Writers kept asking "is this density good or bad?". v2 added a per-word "target range: 0.5-1.5%" benchmark with red/yellow/green indicators. In writer tools, raw data isn't enough — interpreted data is the product.
Screenshots
Want this for your project?
Same 47-point methodology, $499 fixed price, 5-7 business days. Book the audit.