Summary: Week 10 of the HivePulse SEO Contest is settled. Seven writers entered, all seven qualified, and five of them tied on a perfect score. 400 HIVE is going out. Week 11 is open, and it changes how a tie is broken - because word count has stopped measuring anything useful.
HivePulse SEO Contest week 10 results
Seven writers entered. Seven qualified - every single entry cleared the bar, and every single one carried the tag. After three rounds of losing good posts to a missing #hivepulse, nobody lost one this week. Five entries tied on a perfect 200/200. Seven valid entrants put the round in the under-10 tier, so the podium pool is 300 HIVE, plus the 50 HIVE X prize and a 50 HIVE referral pair. 400 HIVE is going out.
| Place | Author | Post | SEO | GEO | Words | Prize |
|---|---|---|---|---|---|---|
| 1 | How 1 Decision Changed My Life: DAE to DHMS? | 100 | 100 | 7,569 | 150 + 50 HIVE | |
| 2 | Crochet: The Best Activity Physio Can Do 2 Multiple Tasks | 100 | 100 | 5,238 | 100 HIVE | |
| 3 | 7 Funniest Things I Believed as a Kid [Quick Long Stories] | 100 | 100 | 3,308 | 50 HIVE | |
| 4 | 5 Best Things I Discovered in a Garden [Surprise Lovebird] | 100 | 100 | 1,662 | - | |
| 5 | Daily Habits: 10 Simple Ways to Improve Your Life [Guide] | 100 | 100 | 1,107 | - | |
| 6 | The Orphanage 2007: Neglect, Cruelty & the Best Lessons | 96 | 100 | 1,394 | - | |
| 7 | Reporte de Crecimiento Semanal | 82 | 100 | 470 | - |
The scores are re-derived from each post's on-chain content with the same HivePulse scoring engine the extension uses. The screenshot is evidence of entry, not the score we award.
Five perfect scores, and a tiebreak that has stopped working
@nabbas0786,
@wardah,
@ahmedabbaci,
@mayt and
@nursejoe all finished on 200/200. The published tiebreak settled the podium on word count, as it has since week 5, and the podium above is final under that rule.
But look at what the rule is now rewarding. The winning post is 7,569 words. Last round's winner was 3,217. The round before that, 1,730. We have built a length competition, and nobody set out to do that.
Three rounds ago, no entry in this contest had ever scored a perfect 100 on SEO. This round, five did. The score has done its job - it taught the checklist, and the checklist works. What it can no longer do is tell the difference between the five people who have learned it.
So from week 11 the podium is decided differently.
Referral bonus - corrected after publishing
@soyunasantacruz was referred by
@ahmedabbaci, declared it in her entry comment, and her first entry qualified at SEO 96 / GEO 100. Both receive 25 HIVE.
We missed this when the results first went out. She wrote "Referrad by" rather than "referred by", and the check that finds referrals was looking for the exact spelling, so it passed straight over her. That is our error, not hers - the rule exists so we can find the declaration, not to test anyone's spelling. The payment went out as soon as we spotted it, and the check now accepts any reasonable spelling.
The X engagement prize
Two valid quote-retweets this round. @nabbas_0786 wins 50 HIVE with 9 likes and 5 replies, against @la_santacruz (
@soyunasantacruz) on 6 and 1. That is his second X prize in two rounds, on top of first place.
@soyunasantacruz entered for the first time this week, qualified at SEO 96 / GEO 100 and promoted the contest in Spanish. Welcome - and the prize was close.
One change for week 11: paste your quote-retweet link in your entry comment. We found one of this round's two by accident. If we cannot see it, we cannot count it.
Week 11 is open - up to 500 HIVE
The prize ladder is unchanged, and still tied to the number of valid entrants:
| Valid entrants | Prize pool | Places paid |
|---|---|---|
| Under 10 | 300 HIVE | 150 · 100 · 50 |
| 10-19 | 400 HIVE | 200 · 100 · 60 · 40 |
| 20+ | 500 HIVE | 250 · 120 · 80 · 50 |
Seven valid entries this round. Three more people and the pool moves to 400.
Week 11 runs from 6 October to 13 October 2026, 12:00 UTC.
- Install HivePulse for Chrome or Firefox.
- Write and publish a new post on any supported Hive frontend with the analyzer open.
- Comment below with the post link and a screenshot of the SEO and GEO panel.
- Tag the post
#hivepulse- one word, no space. Check it before you hit publish. - You may enter more than one post. Your highest-scoring tagged post counts.
- If someone referred you, write exactly
referred by @usernamein your entry comment. When the entry qualifies, both people receive 25 HIVE. The referred person must be new to the contest.
The minimum qualifying score is SEO 70. Any language is welcome. Every entry is re-scored on-chain after the round closes.
What changes in week 11: word count is retired
If two or more entries tie on SEO + GEO, the podium goes to the post whose Reading Ease is closest to 60.
The rule is one number, and HivePulse has always shown it to you.
Open the SEO tab and look at the Readability row. The hint underneath reads something like Ease 68/100 · 33% transitions. That is the number. Reading Ease is a standard Flesch measure of how hard your sentences are to read, taken from sentence length and syllables per word. You can watch the figure move while you type.
Here is the part nobody noticed. The analyzer stops caring once you pass 60: clear it and you get the full 8/8 for readability, whether you land on 60 or on 86. Every single entry that tied on a perfect score in weeks 9 and 10 had an identical scorecard, right down to that maxed-out 8/8. So the tiebreak simply reads the same number at full resolution.
60 is the target, not the starting line.
| Round | Winning word count |
|---|---|
| Week 8 | 1,730 |
| Week 9 | 3,217 |
| Week 10 | 7,569 |
Word count had to go. Word count is unbounded, so there is always more to gain by writing more, and such a race has no finish. Reading Ease has a finish line: at 60 there is nothing further to gain, and going past it costs you.
Padding does nothing here. Reading Ease is a ratio — words per sentence, syllables per word. Copy your post seven times and the number does not move at all. The only way to improve it is to actually rewrite: shorter sentences, plainer words.
Applied to week 10, the 5,238-word entry that placed second drops to last at ease 86, and the tightest post in the field — 1,107 words, landing on exactly 60 — takes first. Week 10 stands as it was paid, under the rule published at the time. This applies from week 11 onward.
Your score does not change. Reading ease 60 or above still earns the full 8/8 for readability - 60, 70 and 86 all score exactly the same. Writing above 60 costs you nothing. The tiebreak only ever comes into play when two posts finish level on the total, and if nobody ties it never applies at all.
And you cannot drop below 60 to get closer to it. Under 60 the readability block falls from 8/8 to 7/8, your SEO lands short of 100, and you are no longer in the tie. Every perfect score this contest has recorded sits at 60 or above, and the lowest was exactly 60.
So nothing to control, and nothing new to chase: reach 60 the way you always have. Among posts that all scored 100, the one nearest 60 - the tightest writing - takes the higher place. If two tie on that as well, the earlier publication time wins, exactly as before.
The 50 HIVE X prize
Quote-retweet the Week 11 announcement tweet with your own words about your HivePulse experience. The quote-retweet with the most likes, reposts, and replies combined at the close wins 50 HIVE. It must quote the announcement itself, not a reply or your own post. No engagement farming.
Paste the link to your quote-retweet in your entry comment. Two people entered this prize in week 10 and we only found one of them by chance. If we cannot see it, we cannot count it.
👉 This is the tweet to quote: https://x.com/HdevCore/status/2107524321367425064
Subscribe to Hdev Contests for each round. Questions and discussion are welcome in Discord, and HivePulse is also on X.
- The HivePulse Team (@hdev)