toolsbracker-seo-blog

name

toolsbracker-seo-blog

description

Write SEO-optimized blog posts for toolsbracker.com — a free gaming benchmark tool site. Use this skill whenever Shakoor asks to write a blog post, article, or any content for ToolsBracker. Also trigger when he says things like "write the reaction time post", "draft a blog", "write content for the site", or "help me write about [gaming/clicking/typing topic]". This skill knows the site's full context, target audience, keyword strategy, and content rules — use it every time without exception.

ToolsBracker SEO Blog Writing Skill

Site Context (Read This First)

Site: toolsbracker.com What it is: 33 free browser-based gaming benchmark tools. No download, no signup, no ads. Owner: Shakoor (freelance developer, Pakistan) Target audience: Gamers aged 13-25, especially Minecraft PvP players, FPS gamers, and students who search for these tools at school. Main tools: CPS Test, Reaction Time Test, Typing Speed (WPM), Aim Trainer, Jitter/Butterfly/Drag Click tests, Memory tests (Chimp, Number, Sequence), Color Blind test, Hearing Age test, and more. Tech stack: Next.js, deployed on Vercel. Blog posts go in the /blog directory or as standalone pages. Competitor sites to beat: humanbenchmark.com, arealme.com, cpstest.org, clickspeedtester.com

---

Blog Post Strategy

Every blog post has one job: rank for an informational keyword and funnel readers to the matching tool on ToolsBracker.

The formula is simple:

• Person searches for an answer ("what is average reaction time by age")
• Google shows our article
• They read it, trust us
• They click through to the tool and use it
• They come back next time they want to test

---

Content Rules

Writing Voice & Style

VOICE RULE — Write like a gamer talking to another gamer. Not a professor. Not Wikipedia. Not a health website. Someone who actually plays CS2, Minecraft PvP, or Valorant and knows this stuff from real experience.

Specific rules:

• Use "you" and "your" in almost every paragraph
• Every section needs one relatable gaming moment that grounds the facts in real experience. Example: instead of "auditory reaction time is faster than visual" write "that's why you flinch at a jumpscare before you even see what scared you"
• Short punchy sentences. Mix them with longer ones.
• Never start a sentence with "It is worth noting", "It is important to understand", or "In conclusion"
• Facts need a "so what does this mean for you" follow-up. Don't just drop a number and move on.
• One unexpected detail per section that makes the reader think "I didn't know that"
• Conversational transitions between sections. Not "Furthermore" or "Additionally". Use "Here's the thing" or "And this is where it gets interesting" or just start the next point.
• No em dashes anywhere. Ever. Commas or short sentences only. Em dashes are a known AI writing signal.
• No bullet point should start with a noun followed by a definition. Rewrite as a full natural sentence. BAD: "Sleep: Being well-rested improves..." GOOD: "Getting good sleep can add 20-40ms to your score."
• The intro paragraph must hook the reader in the first sentence. No slow warmup. Start with something that makes them want to keep reading.
• Every post ends with the CTA feeling earned, not pasted on. The last paragraph before the CTA should naturally lead into wanting to test yourself.

Other style rules:

• Casual but accurate. Contractions are fine ("you're", "it's", "don't")
• Never use: "delve", "robust", "seamless", "leverage", "cutting-edge", "it's worth noting", "in conclusion"
• The audience is mostly teenagers and young adults. Keep it engaging.

SEO rules

• The primary keyword goes in: title (H1), first 100 words, one H2, and the meta description
• Secondary keywords go naturally in the body. Never force them.
• Every post ends with a CTA linking to the relevant ToolsBracker tool
• Target word count: 600-900 words. Not more. Gamers don't read essays.
• Use short paragraphs (2-3 sentences max)
• Use bullet points and tables where they help. Don't use them just to look structured.
• No keyword stuffing. If a sentence sounds weird, rewrite it.

Content honesty rules

• Never invent statistics. Use real data from the article's topic or cite it as "studies show" only for well-known facts.
• ToolsBracker is a new site. Don't write "millions of users" or fake social proof.
• If a claim could be wrong, soften it ("typically", "most players", "research suggests")

---

Blog Post Template

Use this structure for every post. Adapt section names to fit the topic.

[META — not shown on page]
Title: [Primary keyword] — keep under 60 characters
Meta description: [Primary keyword + benefit + ToolsBracker mention] — keep under 155 characters

[PAGE CONTENT]

# [H1 — same as or close to title]

[Intro paragraph — 2-3 sentences. State the topic, why it matters to gamers/readers, and what this article covers. Primary keyword appears here naturally.]

## [H2 — answers the main question directly]

[Core content. This is where you put the main data, table, or explanation.]

## [H2 — secondary angle, tips, or "how to improve"]

[Practical advice. Link to the ToolsBracker tool here if it fits naturally.]

## [H2 — optional third section for extra depth]

[Only include if there's genuinely useful content. Cut it if it's padding.]

## Frequently Asked Questions

**[Question 1]?**
[Short answer — 2-3 sentences]

**[Question 2]?**
[Short answer — 2-3 sentences]

**[Question 3]?**
[Short answer — 2-3 sentences]

---

[CTA — last paragraph before end]
Ready to test your [topic]? Use ToolsBracker's free [tool name] — no signup needed, results in seconds. [Link to tool]

---

Priority Blog Posts (Write These First)

Read references/blog-topics.md for the full list with keyword data. The top 5 to write first:

1. Average Reaction Time by Age → links to /reaction-time
2. What is a Good WPM? → links to /typing-speed
3. How to Jitter Click → links to /jitter-click-test
4. How to Butterfly Click → links to /cps-test
5. What is the Kohi Click Test? → links to /cps-test

---

How to Write a Post

When Shakoor gives you a topic or says "write the [topic] post":

1. Check references/blog-topics.md for the target keyword, secondary keywords, and which tool it links to
2. Research the topic briefly if needed (web search for accurate data like age benchmarks, averages, etc.)
3. Write the full post using the template above
4. Output in this order:
   • Meta title
   • Meta description
   • Full article in markdown
5. After the article, add a short note: "Claude Code prompt to save this" with a one-line instruction Shakoor can paste into Claude Code to save the file to the right location

---

Claude Code Usage

When this skill is used inside Claude Code (VS Code), the post should be saved as:

app/blog/[slug]/page.tsx   (if Next.js App Router)
or
content/blog/[slug].md     (if using a markdown CMS approach)

Ask Shakoor which approach the codebase uses if unsure. The slug should be the primary keyword, hyphenated and lowercase (e.g., average-reaction-time-by-age).

---

What NOT to Do

• Don't write more than 900 words unless the topic genuinely needs it
• Don't add sections just to look thorough. Every section must earn its place.
• Don't use fake data or made-up user counts
• Don't write a generic intro like "In today's digital age..." — start with the point
• Don't end with "I hope this article helped!" type closings
• Don't forget the CTA linking to the tool