HivePulse SEO Contest: New Week 12 Round (500 HIVE)

Summary: Week 11 of the HivePulse SEO Contest is settled. Four writers entered and three of them tied on a perfect score and on the new reading-ease tiebreak, so the podium came down to who published first. 350 HIVE is going out. Week 12 is open, and the GEO score gets harder.

HivePulse SEO Contest week 11 results

Four writers entered. The new tiebreak had its first outing and ran straight into the one case it cannot resolve: three entries tied on a perfect 200/200 and landed on reading ease 60 exactly. The published cascade settled it on earliest publication. Four valid entrants put the round in the under-10 tier, so the podium pool is 300 HIVE, plus the 50 HIVE X prize. 350 HIVE is going out.

Place	Author	Post	SEO	GEO	Ease	Published	Prize
1	@nabbas0786	How Did 2 Intense Overs Change This Evening?	100	100	60	6 Oct	150 + 50 HIVE
2	@wardah	3 (Best) Friends @ Oru: Creating Countless Memories Together	100	100	60	7 Oct	100 HIVE
3	@ahmedabbaci	The Overthinking Trap: Action vs Analysis [3 Best Tips]	100	100	60	12 Oct	50 HIVE
4	@soyunasantacruz	[Music] Shakira's Latest Concert: My Experience + 4 [Best] Facts	97	100	60	4 Oct	-

The scores are re-derived from each post's on-chain content with the same HivePulse scoring engine the extension uses.

@ahmedabbaci entered twice. His second post could not be ranked: it carries suseonapulse, suseona, hivepakistan, hive and contest, but not #hivepulse. The word appears in the body, which is not the same thing as a tag.

@soyunasantacruz got a 100 in the panel, and deserves the credit for it

@soyunasantacruz entered with a screenshot showing a perfect 100, and the screenshot is real. Here is what happened between screenshot and published post.

The title runs to 56 characters on its own, which earns the full 12 out of 12 - exactly what the panel showed. Published into Scrobble.life, the title carries that community's [Music] prefix, and those eight characters nudge the length past the 60-character band. We re-score from what was published, so the result reads 97.

Three points to a title convention, and not one to the writing. @soyunasantacruz hit a perfect score on merit, in a second round, in a second language, after telling us she nearly gave up installing the extension at all. That is the part worth remembering.

@soyunasantacruz, you already know how to do this. Drop the prefix, or shorten the rest of the title to make room, and the 100 is yours on the board as well as in the panel. See you in week 12.

The tiebreak met its limit in week one

Three entries scored a perfect 200/200 and all three landed on reading ease 60 exactly. The tiebreak could not separate them, so the published cascade did what it says and fell through to earliest publication - 6 October, 7 October, 12 October.

The cascade worked exactly as published. The tiebreak also reached its edge in its very first round, which is the honest reason for what comes next.

The X engagement prize

Three valid quote-retweets this round, up from two, and all three pasted their link in their entry comment as asked. Pasting those links is the whole reason we could count them.

@nabbas_0786 wins 50 HIVE on 9 likes, 8 reposts and 7 replies - 24 against @la_santacruz's 22 (14 likes, 6 reposts, 2 replies) and @DrWardahx's 2. Reposts decided the prize; on likes alone the result would have gone the other way.

Week 12 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

Four valid entries this round, down from seven. Six more people and the pool moves to 400.

Week 12 runs from 13 October to 20 October 2026, 12:00 UTC.

1. Install HivePulse for Chrome or Firefox.
2. Write and publish a new post on any supported Hive frontend with the analyzer open.
3. Publish it inside the round window - between the two dates above. A post written before the round opened cannot be entered.
4. Comment below with the post link and a screenshot of the SEO and GEO panel.
5. Tag the post #hivepulse - one word, no space, in the tags and not only in the body. Check the tag list before you hit publish.
6. You may enter more than one post. Your highest-scoring tagged post counts.
7. If someone referred you, say so in your entry comment and name them. 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.

If two or more entries tie, the podium goes to the post whose Reading Ease is closest to 60, then to the earlier publication time. Unchanged from week 11.

The GEO score is getting harder from week 12

Your GEO score is going to drop next week. The bar moved up — your writing did not get worse.

Here is the problem, in one number. Across every entry this contest has ever scored, 57% of them held a perfect GEO 100. More than half the field, maxed out. A score most people max is not telling anyone anything, and it is the real reason five of you kept tying on 200/200 and needing a tiebreak to separate you.

So from week 12 the GEO checks get harder. Same checks, same names, nothing new to learn — the top band on each one now asks for more:

• Your opening has to be tighter. 12 to 45 words, or an explicit TL;DR.
• Question headings — two of them for full marks, where one used to do.
• Definitions — three, where two used to do.
• Numbers and sources — five figures with a source, where three used to do.

And there is one new check, for personal posts only: Concrete detail.

A story an AI can quote names things. "My friend helped me" is not quotable. "Ahmed walked me through it on Discord for four hours" is a fact an engine can lift and attribute to you. Name the people, the places, the dates, the numbers. That is the whole check.

What this means in practice. On the same posts, perfect scores fall from 57% of entries to about 9%. The median lands near 86. 100 is still reachable — a handful of posts in this contest's history still earn it under the new rubric — but it has to be earned.

And it makes ties rare again. In weeks 9 and 10, five entries tied at the top of each round. Under the new scoring that drops to one. The Reading Ease tiebreak stays exactly as published, but it goes back to being a rare fallback instead of the thing deciding your podium.

Weeks 1 through 11 are not reopened. Every round already judged stays judged on the rubric that was published at the time, including this one. This applies to week 12 onward, and you are reading it before week 12 opens.

The 50 HIVE X prize

Quote-retweet the Week 12 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. Your quote-retweet must target the announcement itself, not a reply or your own post. No engagement farming.

Paste the link to your quote-retweet in your entry comment. All three entrants did this last round and it worked perfectly.

👉 This is the tweet to quote: https://x.com/HdevCore/status/2110002368209420772

Subscribe to Hdev Contests for each round. Questions and discussion are welcome in Discord, and HivePulse is also on X.

- The HivePulse Team (@hdev)