This article is published in English.
ChatGPT vs Claude vs Gemini on One Blog Brief: Which Draft Was Publishable
The same blog brief went to ChatGPT, Claude and Gemini, with timed edits and four scores per draft, to show which assistant fits voice, speed and fact-heavy blogging work.
A third draft opened in Google Docs, and by line three the problem was obvious: it said "recent data shows" with no source, no link and no date. Rebuilding every fact would have eaten the afternoon. That moment sets the standard used here. A publishable draft is the one that needs the fewest hands-on fixes. Entry paid tiers sit around $20 a month, so fit mattered more than price. The sections below describe the brief, the four scores and which assistant suits which blogging job.
One brief, three drafts
A single brief went through each tool three times, and every raw file stayed untouched. The rough split that came out of it:
- Claude for voice-sensitive long form, since it holds tone across the whole piece
- ChatGPT for quick variations, headlines and iteration on mixed tasks
- Gemini for current facts through live search, plus drafting in Docs and Gmail
- Paid plans for daily blogging, because usage caps hurt most during revision loops
At $20 per month, entry paid access covers ChatGPT Plus and Claude Pro.
The brief itself
Each tool received identical text, untouched, using the stock consumer settings of its app and the same order of pasting. The brief gave the audience, goal, voice sample, length, structure and limits on facts. Hands-on fixes were timed, and each draft was scored on accuracy, structure, voice match and fix time.
Audience: [beginner bloggers]
Goal: [publish without heavy rewrite]
Voice sample: [paste 150 words]
Length: [1,200 words]
Structure: [intro, three sections, FAQ]
Fact limits: [no uncited stats, flag uncertain claims]
A fair run needs a few ground rules:
- One brief file for all three runs
- The default flagship model, with no custom instructions
- Raw outputs saved before any cleanup
- A timer running during every edit pass
- Four scores logged for each draft
Stamp each file with the run date. Models and plan details change quickly, so check current defaults on the official pages before relying on any of this.
ChatGPT: fast, but it needs a firm edit
ChatGPT Plus on default settings returned a clean draft quickly. Headlines arrived fast and variations arrived faster. The outline was usable straight away, with an intro, subheads, an FAQ and a close. Image tools, voice input, browsing and deep research share one interface, so there's less tab switching. GPT-5 handles up to 400,000 tokens of context, which kept long threads intact and helped when background notes went in.
Tone was the price. It came across cheerful and glossy, the kind of voice any marketing blog could have used. Edits required:
- Replacing generic openers with plain, specific lines
- Cutting points repeated across sections
- Flagging two uncited claims for a live search check
- Rewriting transitions to match the sample's rhythm
- Trimming filler answers from the FAQ
A concrete case: the brief asked for a short section in a dry, direct voice taken from the sample. The first attempt missed the mark and sounded like a product page. A button label shows the gap, with "Submit" as the weak version and "Send my teardown" as the strong one. The structure stayed and the voice was rewritten line by line. Fixing it took longer than generating it, which is why ChatGPT scores high for speed and lower for voice match.
Claude: the most natural draft, the fewest fixes
Claude got closer to the voice on the first pass. Sentence lengths varied and the rhythm lasted beyond the intro. Its 1M-token window for long documents meant the whole background could go in uncut. That steadiness showed in the middle sections, where other drafts tend to drift. Revision felt lighter too: a request for a tighter second section kept the same tone while cutting repetition. You can also build a Style in your own voice from a sample.
Weaknesses appeared away from the writing itself. Quick back-and-forth replies came slower, and the built-in tools for images and voice felt thinner. Edits required:
- Trimming two long paragraphs that restated one point
- Adding source flags for recent claims
- Removing a soft closing line that wandered off the brief
For the concrete case, a meeting transcript went in with a request for a draft that kept the speaker's phrasing. Claude retained two of the original turns almost intact. Keeping those lines and editing around them saved a full rewrite pass, and that's why Claude took the least hands-on time.
Gemini: research first, prose like search results
Gemini was the quickest for research. Live search grounding pulled in current references without a separate hunt in another tab, and drafting inside Docs and Gmail cut paste steps. One benchmark has Gemini 3 Flash about 50% faster than the default ChatGPT model on raw output speed, which matched the experience: quick drafts landed first here.
The prose was clear but flat. The facts were present and the texture was thin, so editing time went into adding voice, not fixing structure. Edits required:
- Rewriting flat topic sentences with concrete detail
- Adding the sample's rhythm to three sections
- Checking every search-grounded claim against a second source
- Cutting generic summary lines at the end of sections
For the concrete case, a section of current facts with checkable sources came back with clean links and plain wording. The facts stayed and the sentences were rewritten in the target cadence. The research head start remained useful even after a full voice edit. Flat but factual text still needs a voice pass before it ships.
Comparing accuracy and edit time
Claude needed the least fix time, and that's the entire test in one line. Each draft pulled in a different direction, with accuracy, structure and voice split between them, so your job should decide the pick. Independent context helps here: on the Vectara hallucination leaderboard, ChatGPT-4 Turbo shows a hallucination rate near 1.7%, and every draft still needed live checks. Look at the scores before trusting any uncited line.
- ChatGPT: accuracy needs checking, structure solid, voice generic, fix time middle
- Claude: accuracy needs checking, structure steady, voice close, fix time least
- Gemini: accuracy current, structure solid, voice flat, fix time middle
Read the list by criterion, not by assistant. When current facts are your bottleneck, start with the accuracy leader and check each claim. If rewrites eat your week, begin with the voice leader. If outlines stall, begin with the structure leaders. Fix time breaks ties because it folds the other three into hours you get back.
Matching tool to job
The scores point to jobs and not to one overall winner. Choose whichever helper clears your bottleneck fastest with the fewest fixes.
Entry prices are close together: ChatGPT Plus and Claude Pro are $20 per month, and Google's AI Pro tier for Gemini lists at $19.99. Heavy use costs a lot more: Claude Max starts at $100 per month (Claude Max pricing) and ChatGPT Pro lists at $200 for high-capacity access. Caps affect daily work more than list prices do. The Claude free tier allows roughly 30 to 100 messages a day, which runs out fast during revision loops. Confirm current pricing on the official plan pages for your test date, because tiers shift quickly.
- Mostly long pieces where voice matters: Claude, for fewer voice fixes
- Mostly many variations and mixed tasks: ChatGPT, for iteration speed
- Mostly current facts and Workspace drafting: Gemini, with every claim verified
- Writing for hours every day: pay for a plan and look at the caps well before a deadline week
Why mix models
Because of those results, different steps can go to different models: Claude for voice-sensitive long form, ChatGPT for fast variations and Gemini for grounding in current facts. Replay the same brief and scores on one of your own posts and see which assistant leaves you the shortest edit list.