Updated 25 October 2026 with Vin's word ranges. Not the live site.

V8: AI content framework

For: Vin (review), Hoa (hand check), Austin (claims), Bobby (SEO check) From: Som Draft: Sunday 4 Oct 2026 · updated Tuesday 13 Oct 2026 from Vin's review · updated Sunday 25 Oct 2026 with word ranges, the measuring prompt and the keywords block · first page from it: CS2 game page

The page structures come from what ranks today (V12 and the audit's briefs in section 16) and Bobby's keyword answers of 7 Oct. Bobby does the SEO check on every draft; section 6 is Som's self-check before it goes to him.

What this covers: every page in C1 to C7 (titles and copy, the trust page, the gaming guide, 13 game pages, the low-FPS page, comparison pages and problem pages). What it does not cover: the content calendar (N1) and outreach.

1. How a page gets made

About 3 hours of Som's time per page, which matches the plan's estimate for game and problem pages and keeps two pages a week.

2. Facts every page uses (the fact sheet block)

Paste this block into every drafting session. The AI may only state facts about Hypertune that appear here or in the page's own sources. The master copy of every fact is the V13 fact sheet; this block is a short copy of it. When a fact changes, change V13 first, then this block, and changes are made only when Austin signs them off.

FACTS (as of 13 Oct 2026; [A] = Austin to confirm before publishing)
- Company: Hypertune is made by COMPREADY Inc., a US company. Austin Copeland founded it in 2022.
  Do not name Thomas Schappy.
- Platforms: "available for Windows and Mac". [A: Mac wording, tracker C2-6]
  Designed to optimize Intel and AMD processors and NVIDIA and AMD graphics cards.
- What it does: reads CPU, GPU, memory and storage once; applies only the features the user turns on.
  Feature names, in this order, as the product uses them: CPU Overclocking, GPU Overclocking,
  Windows Debloating, Network Optimizations, Memory Optimizations, Game Hub.
- Revert in the app: Restore tab > most recent restore point > Restore.
- Expert Tuning: an optional paid add-on, one-on-one with a technician. Never part of the subscription.
- Safety facts: stress-tests an overclock on the user's hardware and skips it if cooling cannot hold it;
  makes no unsafe changes (Game Hub profiles can change files inside a game); creates a Windows restore point automatically;
  changes can be reverted in the app.
- Intel: Intel partner, trusted by Intel and AMD; CPU tuning built on Intel's XTU technology,
  developed in collaboration with Intel. The Intel logo may be used.
- AMD: AMD partner; "partnered with AMD"; AMD may be named and the AMD logo used.
- NVIDIA: "supports NVIDIA" or "works on NVIDIA hardware" only.
- Price: $9.99 a month. Yearly: $69.99 a year from 16 Oct 2026, shown against $119.88 struck through.
  Until 16 Oct the yearly plan runs as a limited-time offer at the current price.
  Subscribers already on a yearly price keep it.
- Refund: 7-day money-back guarantee on the first payment.
- Free trial: a 7-day free trial exists but is not featured. Do not lead with it or put it in titles or
  descriptions; mention it only where Austin has approved it for that page. [A per page]
- FPS claim: "up to 60% higher FPS; results vary by hardware and game". A higher number is allowed only
  when it comes from Hypertune's own data, with the source and date on the page.
- Anti-cheat line: "Game Hub profiles can change files inside a game. Hypertune makes no unsafe changes."
  Never write that Hypertune does not touch, edit or modify game files or game code (Mo, 19 Oct).
  Do not say it is safe with a named anti-cheat unless Austin confirms that system.
- Live site lines: the existing "Verified by" and "100% safe" lines stay where they are. Do not delete them;
  do not add new ones in new copy.

NEVER WRITE
- "endorsed by", "certified", "ban-proof", "undetectable"
- "trusted by", "verified by" or "100% safe" anywhere except "Trusted by Intel and AMD" and the existing live lines
- NVIDIA as a partner ("NVIDIA partner", "partnered with NVIDIA"), or the NVIDIA logo
- an FPS number above 60% without Hypertune's own data and a source (not 40%, 41%, 42%, 18-140, 130 to 210 from elsewhere)
- names of pros, streamers or creators, or testimonials, unless they are on Austin's approved list for that game (tracker C4-6)
- Thomas Schappy
- a free version, or a price other than those above
- em dashes; use a comma, colon or full stop instead
- that Hypertune does not touch, edit or modify game files or game code

The nine answer rules for every page (approved by Vin, 19 Oct)

Paste these with the facts block into every drafting session. Every page follows all nine.

1. The title and H1 use the question's own words.
2. The first 40 to 60 words under each heading answer it outright and name Hypertune or the game.
3. Paragraphs name their subject instead of saying "it", so a lifted passage still makes sense.
4. Numbers carry their date and source, for example "From 16 Oct 2026, Hypertune costs $9.99 a month or $69.99 a year."
5. Settings and comparisons go in tables, with a fair word on free alternatives.
6. Every page shows a visible "Last updated" date.
7. Price and partner lines link to the facts page (until it goes live on 4 Nov, price lines link to https://hypertune.gg/pricing); performance figures link to the test method once it is published.
8. Each page answers its follow-up questions in its own FAQ, marked up for that page only. The Hypertune reviewer checks the FAQ answers for accuracy.
9. Guides and game pages carry the named author (Austin, agreed 13 Oct) with one line on why he knows.

3. Page types

Six page types cover every planned page. Each one has a fixed order of sections; the AI drafts into that order and does not add sections.

General rules for every type: - Answer first. The first one or two sentences answer the search, in words an AI answer can quote. - Headings are the searches. H2s use the phrasings people search (from the brief), written as plain statements or questions. - Free steps before the product. Every guide gives the manual steps in full; Hypertune appears in one section, as "or let Hypertune do steps X to Y", and links /technology. It never replaces the steps. - Every number has a source and a date (audit article rules). Settings values come from the brief's sources or Som's own test, never from the model. - Length (Vin, 23 Oct): at brief time, measure the target with the measuring prompt in section 4. Write within the range for the page type in the table below. If the measured range and the default range differ, the measured one wins. Going higher is fine when the extra length is content Travis adds: technician settings, screenshots with their explanations, or corrections. Going lower than the range is not. Count the words a reader sees on the page, tables included. Leave out draft notes, yellow technician boxes, and the nav and footer. - Byline and date: author name, "Last updated" date and, for game pages, the game patch version. [Austin to confirm who the named author is; the audit recommends named people, such as a CompReady engineer] - Schema: articles and guides use Article with headline, author, datePublished, dateModified. Game pages use WebPage plus BreadcrumbList (Home > Games > [Game]), as on the CS2 page. The homepage and /technology each carry FAQPage markup for their own questions only (C29); other pages do not add FAQPage unless C29 is extended to them. No HowTo.

Word ranges by page type (Vin, 23 Oct). If the measured range and the default range differ, the measured one wins.

3.1 Game page (C4)

Format (decided 7 Oct): game pages are dedicated designed pages built from one reusable template, not blog articles. The sections below are the content; the layout is the build spec in C4. A designer designs the template first, then Kamil builds it. No byline needed (WebPage and BreadcrumbList schema, not Article); keep the patch version and "last checked" date.

URL: /games/[game] [Austin to confirm the pattern; handover decision 2. /game/valorant exists today] Primary keyword: "[game] pro settings" (Bobby, 7 Oct: "cs2 pro settings", "valorant pro settings"). Where a game has no measurable pro-settings searches, use "best [game] settings" from the content calendar (N1). Secondaries, always all of: "best [game] settings", "[game] fps boost", "[game] low fps / fps drops", "[game] stuttering", and "[game] launch options" where the game has them. These are the page's sections (Bobby, 7 Oct). Title: Best [Game] Pro Settings: FPS Boost, Less Stutter | Hypertune (shorten to 60 characters). Pro settings means the settings competitive players use; no player is named unless they are on Austin's approved list.

Internal links out: games hub, trust page (/is-hypertune-safe), /technology, the gaming guide (C3), the game's problem page if it exists. Links in (for Kamil's ticket): games hub, homepage games section, the problem page, the gaming guide.

3.2 Problem page (C7, C5)

URL: /fix/[problem], for example /fix/cs2-stuttering [Austin to confirm] Primary keyword: the exact problem phrase, for example "cs2 stuttering fix" or "low fps on high end pc".

Links out: the game page, the gaming guide, trust page. Links in: the game page's stutter section, the low-FPS page (C5).

3.3 Comparison page (C6)

URL: /compare/hypertune-vs-[competitor], plus /compare/best-fps-booster [Austin to confirm] Primary keyword: "hypertune vs [competitor]" or "[competitor] alternative"; "best fps booster for pc" for the roundup.

Rules: competitor prices and features are checked on their site the day the draft goes to Hoa, with a saved screenshot. No claims about a competitor's safety or ethics.

3.4 Guide (C3 and later how-to guides)

Examples: "how to optimize pc for gaming" (C3), "best bios settings for gaming", "cs2 launch options".

3.5 Answer page (pricing, benchmark method, trust page)

Use the audit's briefs (section 16, "Briefs for the priority pages") and the C2 draft as the model: H1 is the question, the answer in the first sentence, then sections that each answer one sub-question, then the questions block. These pages are mostly Austin's facts, so the AI only structures and words them.

3.6 Titles, descriptions and on-page copy (C1)

Already drafted in C1. Rules for any new title or description: primary keyword near the start, brand at the end of titles, titles 50 to 60 characters, descriptions 140 to 155 characters, one H1 per page, and no keyword used as the primary of two pages (check the keyword split in C1 and section 3 of this document).

4. Brief template

Fill one per page before drafting. Everything in it comes from Ahrefs, Search Console or the live results, not from the AI.

BRIEF: [page name]                          Type: [game | problem | comparison | guide | answer]
Planned URL:                                Publish week:
Primary keyword:            volume (US / global):        difficulty:
Secondary keywords (with volumes):
Search Console queries already showing for this topic (impressions, position):
Search intent (one line):

WHAT RANKS (top 5, non-forum, measured on [date]):
| # | URL | type (guide, list, vendor, forum) | words | what it has that we must match |
Median length of top 5: ___ words · range for this type: ___ to ___ → target ___ (the median, kept within the range)
AI Overview: yes/no; cited sources:
Reddit threads in top 10 (titles): → questions to answer

QUESTIONS TO ANSWER (from People Also Ask, Search Console, Reddit):
1.
2.
3.

SOURCES FOR FACTS AND SETTINGS (every value in the draft must trace to one of these):
- Official: [game patch notes, developer support pages, Microsoft, NVIDIA, AMD, Intel]
- Hypertune: the fact sheet block (section 2); [any Hypertune test data, with date]
- Som's own test: [PC spec, patch version, date]

UI PATHS (exact labels from the app, site or walkthrough video, for every step the page gives):
SCREENSHOTS NEEDED (one per feature or step listed; source for each):

INTERNAL LINKS OUT (from section 3 for this type):
INTERNAL LINKS IN (for Kamil's ticket):
OPEN QUESTIONS FOR AUSTIN:

Measuring prompt (Vin, 23 Oct). At brief time the writer pastes this into an AI tool that can search the web, then copies the reply into WHAT RANKS. Replace the keyword, the page type and the range.

Primary keyword: [KEYWORD]. Market: United States.
1. Find the top 10 Google results for this keyword (use Ahrefs SERP overview).
2. Skip forums and communities (Reddit, Steam, Discord, any forum), videos (YouTube) and social posts. Take the first 5 that remain.
3. Open each page and count the words in the main content only: leave out the nav, footer, sidebars, comments and cookie banners. Keep tables.
4. Give me: the 5 URLs with their word counts, the median, the range within 20% of the median, and today's date.
5. Compare it with our default range for this page type ([PAGE TYPE]: [RANGE]) and tell me which to use. The measured range wins if they differ.

Keywords block for the handover notes

Every draft goes to its checkers with handover notes that open with this block. Som and Hoa use the same block, so Bobby checks the headings against the list instead of cross-referencing the keyword map (agreed 24 Oct). Fill it from the keyword map: V12 and the primary keyword and US volume columns in N1.

KEYWORDS (from the keyword map: V12 and N1)
Primary keyword: [keyword] (US volume: ___ a month)
Secondary keywords:
- [keyword] (US volume: ___)
- [keyword] (US volume: ___)

| Heading | Level (H2/H3) | Keyword it targets |
|---|---|---|
|  |  |  |

Filled example: CS2 game page (C4, live mockup at hypertune-cs2-page.pages.dev)

5. Drafting prompts

Run in one chat per page, in this order. Paste the fact sheet block and the filled brief at the start. Any capable chat model works; the rules below matter more than the model.

Prompt 1: setup

You are drafting a page for hypertune.gg, a Windows PC optimization app for gamers.
Write in plain, direct English for PC gamers: second person, short paragraphs, exact clicks and values.
Rules:
1. State facts about Hypertune only if they are in the FACTS block. Follow NEVER WRITE exactly.
2. Do not invent settings values, version numbers, statistics, prices or quotes. If the sources I give
   do not contain a value, write [source needed: what is missing] instead.
3. Copy any line marked [A] in FACTS with the tag [Austin to confirm] after it.
4. Use the section order for this page type exactly. Do not add sections, intros or conclusions.
5. Answer the search in the first two sentences.
6. No filler: no "in today's world", "ultimate", "game-changer", "unlock", "elevate", "seamless",
   no rhetorical questions, no summary at the end.
7. No em dashes anywhere, including headings, tables, alt text and the meta description.
8. Give one value per setting. If the right value depends on something (for example Reflex on or off),
   say so in the same place, and use the same rule everywhere the setting appears.
Lessons from reviews (trust page, 14 Oct; CS2 and the 12 Oct call):
9.  Reassure, don't defend. Say what Hypertune does, not what it isn't. Only name a fear (mining,
    cracks, bans) if the page answers that exact question, and then in one calm line.
10. Each fact appears once, in the section a reader would look for it. FAQ answers don't restate
    facts from the page unless the question asks for them.
11. A section about a partner mentions only that partner (no AMD in an Intel section). Mark any
    press or review list [Austin to confirm], since he knows which articles partners dislike.
12. Facts come from FACTS; wording doesn't. Lead with what the reader gets, in second person, and
    give the page one line of why the company exists. No spec-sheet sentences.
13. Legal and policy detail goes behind a link: one line, then link the Terms or Privacy Policy.
14. Separate what Hypertune stores from what a third party processes (Stripe and PayPal take
    payments, so Hypertune never sees card details). If a source is unclear, tag [Austin to confirm].
15. Steps use the exact labels from the app, the site or the walkthrough video. If the real path is
    not in the sources, write [UI path needed]; never write a generic step.
16. Use the product's own feature names, in the product's order (FACTS).
17. When the copy lists features or steps, list the visual each one needs, or none. Write
    [Screenshot needed: what it shows] where one is missing.
18. Say the things a reader would otherwise get wrong: paid add-ons are optional and who they are
    for; platforms (Windows and Mac) and hardware are stated once, clearly.
Reply "ready" and wait for the brief.

[FACTS block]
[Page type section from section 3]

Prompt 2: outline

Here is the brief: [brief]
Write the outline only: H1, every H2 and H3, and one line under each saying what it covers and
which source it uses. Use the secondary keywords as H2 phrasings where they fit naturally.
List any question from the brief you could not place.

Som checks the outline against the brief before going on: every secondary keyword placed, every question answered, nothing outside the page type.

Prompt 3: draft

Write the full page from the approved outline. Target [N] words.
Settings tables: only values found in these sources: [paste the source text or notes].
Mark every value with its source in brackets, for example (Valve patch notes, 1 Oct 2026); I will
remove the brackets after checking.

Prompt 4: self-check

Check your draft against the FACTS and NEVER WRITE lists and the rules. List every sentence that:
- states a Hypertune fact not in FACTS,
- uses a NEVER WRITE phrase,
- contains a number without a source,
- uses one of the filler words,
- contains an em dash,
- breaks rules 9 to 18 (a defensive line, a repeated fact, another partner in a partner section,
  spec-sheet wording, legal detail without a link, a generic step, an invented feature name,
  a feature with no visual, an add-on not marked optional).
Then list every setting that appears more than once (summary list, stutter fixes, settings table,
PC-tier columns, FAQ, captions) with each value given, and flag any two lines that give different
advice for the same setting, quoting both.
Do not rewrite the page; just list them with the fix.

Som applies the fixes by hand, then removes the source brackets only after checking each value.

6. Self-check before Bobby's SEO check

Som runs this on every draft and pastes it at the end, ticked, before the draft goes to Bobby. Bobby does the SEO check; this list catches the basics so his check is about the keywords and structure.

7. Hand check (Hoa and Vin)

From the plan: facts, prices, claims, links, and that it reads like a person wrote it. In practice: - Every Hypertune fact matches the fact sheet block, and every [Austin to confirm] is still tagged. - No NEVER WRITE phrase, including in image alt text and the meta description. - Every number has a source and a date; open three sources at random and check them. - Settings: the patch version on the page is the current one. - Every link works and goes to the right page. - Read the first screen aloud: if it sounds like an ad or like an AI summary, send it back.

8. Keyword decisions (approved by Vin, 13 Oct)

9. What's next

10. Open questions

For Austin (also in Austin-decisions-ranked.md): 1. URL patterns for game, problem and comparison pages (handover decision 2 covers games only). 2. The named author for guides (game pages need none). 3. Whether game pages may name each game's anti-cheat system, and which ones he confirms. 4. Is "Team Hypertune" in Marvel Rivals an esports team, and is it Hypertune's? It decides when Marvel Rivals gets a page. 5. Which pages may mention the 7-day free trial, and the Mac wording (C2-6). 6. Per-game test data Hypertune can publish (the benchmark method page). Until it arrives, settings come from published sources and the pages make no "tested by us" claims.