Build guide

Reddit CQS educational article

Create this as a long-form educational article within the site’s existing guide/blog system. Reuse the site’s current:

Part 1Build target

  • Header, navigation and footer
  • Article typography and spacing tokens
  • Breadcrumb, author and date components
  • Buttons, tables, callouts and link styles
  • Analytics and SEO systems

Do not create a separate visual theme or landing-page shell. The page should feel informative and neutral until the single commercial section near the end.

The supplied written article is the source of truth. Preserve its headings and wording; do not replace them with headings from this guide or add unsupported claims.

Part 2Page-wide structure

Use this order:

  1. Standard site header
  2. Breadcrumbs, if the article template normally includes them
  3. Article header and introduction
  4. Inline table of contents
  5. Main article sections
  6. One commercial CTA in the promotional-account section
  7. Short closing section without another CTA
  8. Standard site footer

Use one centered reading column with a maximum text width of approximately 760–820px. Tables and other wide components may extend slightly beyond the prose width where the site’s article template supports it.

Do not add:

  • A hero image
  • A hero CTA
  • A popup or inline lead-generation form
  • A floating sales banner
  • A second commercial CTA at the end
  • An FAQ section unless one is explicitly present in the supplied article
  • AutoModerator code
  • A CQS calculator or simulated checker
  • Stock photography

If a genuine screenshot of the Reddit bot reply is supplied in the site’s media library, it may be used in the checking section. Otherwise omit it rather than inventing one.

Part 3Heading and anchor structure

There must be exactly one h1: the article’s supplied main heading.

Use the article’s seven major post-introduction headings as h2 elements, in this semantic order:

  1. How CQS works and the five tiers
  2. How to check CQS
  3. Diagnosing what is blocking an account
  4. Signals that raise or lower CQS
  5. The plan for improving CQS
  6. CQS for promotional accounts
  7. The short conclusion

Use the writer’s exact heading text. Assign stable section IDs based on subject, even if the visible headings differ:

  • how-cqs-works
  • how-to-check-cqs
  • is-cqs-blocking-you
  • what-affects-cqs
  • how-to-improve-cqs
  • cqs-for-promotional-accounts
  • where-to-start

Apply scroll-margin-top to anchored headings so they are not hidden by a sticky site header.

Use h3 headings for:

  • Security
  • Past account actions
  • Network and location
  • Account behavior
  • The three improvement phases, if the writer has given each a heading
  • The stuck-on-Low diagnosis, if it is separately headed

Do not skip heading levels.

Part 4Article header and introduction

Directly below the h1, render the supplied opening as:

  1. First lead paragraph
  2. Second short paragraph
  3. The karma-versus-CQS sentence
  4. Table of contents

Style the first paragraph as the article lead using the site’s existing larger body style. Keep the second paragraph as normal body text.

Present the karma comparison as a compact neutral information strip or callout. It should be visually distinct but not warning-colored. Do not turn it into a large card.

There should be no image or CTA in this opening area.

Table of contents

Use the site’s existing table-of-contents component where available. Otherwise build a compact bordered navigation box with the default interface label “On this page.”

Include one jump link for every h2 below it, using the writer’s exact visible headings. Keep it inline in the reading column; it does not need to be sticky.

Use:

<nav aria-label="On this page">

Part 5Section component map

A. How CQS works and the five tiers

Render the opening explanation as prose, followed by a five-row semantic table.

Table columns:

  1. Tier
  2. What typically happens to posts and comments
  3. Who usually sits here

Order the rows from the bad end to the good end:

  1. Lowest
  2. Low
  3. Moderate
  4. High
  5. Highest

Use compact tier badges in the first column. Color may reinforce the order, but the written tier labels must communicate it without color. Ensure accessible contrast.

Place the supplied note about new accounts immediately below the table as a short muted note or simple paragraph. Follow it with the enforcement paragraph and the short update-frequency note.

Do not add a decorative tier image; the table is the authoritative visual explanation.

B. How to check CQS

Turn the supplied checking procedure into a numbered list. Preserve the writer’s exact steps and order.

Immediately after the steps, include a small neutral link box containing the existing reference to r/WhatIsMyCQS. Link it to:

https://www.reddit.com/r/WhatIsMyCQS/

The box should resemble a useful external resource, not a CTA for the client’s product.

Continue with the supplied paragraphs explaining:

  • Where the response appears
  • The difference between r/WhatIsMyCQS and the older r/cqs
  • What to do if the reply does not arrive
  • Why the check is safe
  • Why third-party checkers are only estimates

Render the multiple-account routine as a standard bulleted checklist. Do not build an input field or offer to check other usernames.

If external links open in a new tab under the site’s normal convention, include the appropriate rel="noopener noreferrer" attributes.

C. Diagnosing what is blocking an account

Build the four possible block types as a semantic comparison table.

Columns:

  1. What you see
  2. What it usually means
  3. How to confirm

The four rows should distinguish:

  • CQS or Reddit reputation filtering
  • Karma or account-age requirements
  • A shadowban
  • A subreddit rule removal

Keep all qualifications from the written article. Do not shorten the rows to unsupported labels.

Place the follow/chat/DM distinction immediately after the table as a short note.

Render the final “do” and “don’t” guidance as two compact panels on desktop:

  • Do
  • Don’t

Stack the panels on mobile. Use normal list markup inside each panel. Avoid aggressive red/green styling; subtle icons and accessible text labels are sufficient.

D. Signals that affect CQS

Use four concise h3 subsections in this order:

  1. Security
  2. Past account actions
  3. Network and location
  4. Behavior

These should remain straightforward article subsections, not a feature-card grid.

After the four signal blocks, render the quiet-trigger material as a two-column semantic table:

  1. Quiet trigger
  2. What to do instead or when to wait

Each trigger should receive its own row, including profile links or emoji, early NSFW settings, rapid deletions, repeated cross-posting and repeated links to one outside domain.

Follow the table with the supplied DM and alternate-account notes as two short paragraphs or compact notes. Do not merge them into the table unless the written article already does so.

E. Plan for raising CQS

Present the main plan as three visibly numbered phases:

  1. Setup
  2. First week
  3. Second week onward

Use the writer’s exact phase headings where provided. Each phase should contain a short list. A vertical ordered sequence is preferred over three horizontal columns because the phases must be followed in order.

After the phases, place the supplied guidance about:

  • Which subreddits and sizes to use
  • Comments on other people’s threads
  • Replies on the account’s own posts

Keep these as prose or short notes in the same order as the article.

Improvement timeline

Build the timing information as a four-column table:

  1. From
  2. To
  3. Typical time
  4. What it takes

Keep the progression in ascending order, from initial verification through Highest. Include the article’s warning that bursts do not shorten the process and removals can set it back.

Stuck-on-Low diagnosis

Render the cause-and-fix material as a two-column table:

  1. Likely cause
  2. What to do

Each cause should have a separate row, including recent bans, heavily downvoted comments, inactivity, network or VPN issues, profile changes and recent deletions.

Place the recovery statement after the table as a normal concluding paragraph or positive neutral note. Do not style it as a guarantee.

F. Promotional-account section

This is the first and only article-local sales section.

Render the educational paragraph first with no button beside it. It must remain visually consistent with the rest of the guide.

Render the buying explanation next. After the complete explanation, add one CTA block containing:

  • One primary button linking to the site’s existing aged/verified Reddit account listing
  • One short supporting line taken from the written copy describing verification, age and activity history

Use the existing product-listing route already present on the site. Do not create a placeholder URL or a new product page.

The button label must come from the supplied article or the site’s established product CTA language. Do not imply:

  • A guaranteed CQS tier
  • Guaranteed posting access
  • Guaranteed account safety
  • Guaranteed performance

Do not add ratings, urgency, countdowns, scarcity messaging or an extra product grid here.

Track the button using the site’s existing analytics convention. Use a clear event name such as reddit_cqs_article_account_cta if custom event naming is required.

G. Closing section

Render the closing heading and its short summary paragraph only.

Do not add:

  • Another button
  • A newsletter form
  • A product carousel
  • New claims
  • A second summary table

The standard global footer may follow immediately.

Part 6Table behavior

Use real HTML table markup with:

  • <table>
  • <thead>
  • <tbody>
  • <th scope="col">
  • <th scope="row"> where appropriate

Give each table a descriptive accessible label or caption based on its subject. A caption may be visually hidden if a nearby heading already provides the visible context.

On narrow screens:

  • Place tables inside a horizontally scrollable wrapper
  • Keep the first column readable and prevent tier labels from wrapping excessively
  • Add keyboard access to the scroll region if required by the site’s accessibility pattern
  • Do not reduce body text below the site’s standard mobile size
  • Do not turn rows into unlabeled blocks that lose their column relationships

Use restrained borders, zebra striping or row separation consistent with the existing theme.

Part 7Visual hierarchy

Maintain an educational, provider-expert tone rather than a product-landing-page appearance.

Recommended hierarchy:

  • Generous spacing before each h2
  • Moderate spacing before h3 headings
  • Compact table cells with readable line height
  • Neutral callouts for notes
  • Warning styling only where the text genuinely warns against an action
  • Primary brand styling reserved mainly for links and the single commercial button

Do not overuse cards. Tables, ordered steps and ordinary prose should carry most of the page.

Preserve all meaningful links supplied with the article.

At minimum, ensure:

  • r/WhatIsMyCQS links to its subreddit
  • Any mention of the older r/cqs links there if the supplied copy includes a link
  • The commercial button links to the existing account-listing page
  • Existing internal links use canonical site URLs

Do not add links to bypass tools, vote sellers or third-party CQS estimators.

Use descriptive anchor text rather than “click here.”

Part 9SEO and page metadata

Use the SEO title and meta description supplied with the written article. If no separate SEO fields are supplied:

  • Use the article title as the title tag
  • Use the CMS’s normal excerpt behavior based on the opening definition
  • Do not invent promotional metadata

Also implement:

  • Self-referencing canonical URL
  • Standard index/follow directives
  • Open Graph and social metadata using the article title and excerpt
  • The site’s default social image if no dedicated image exists
  • Article structured data with real headline, author, publication date, modification date and canonical URL
  • BreadcrumbList schema if visible breadcrumbs are present

Do not add FAQ schema because the page is not structured as an FAQ. Do not invent reviews, ratings or product schema for the article.

Use the site’s real author identity and credentials only. Do not create a fictional CQS expert or unsupported biography.

Part 10Accessibility and performance

  • Keep one h1 and a logical heading hierarchy.
  • Ensure all links and controls have visible focus states.
  • Do not communicate tier quality by color alone.
  • Maintain WCAG-compliant color contrast.
  • If a screenshot is supplied, give it concise alt text describing the visible CQS reply. Decorative imagery should use empty alt text.
  • Respect reduced-motion preferences.
  • Avoid layout shifts from tables, fonts or optional media.
  • Do not add page-specific JavaScript except what is required for the existing TOC, analytics or standard site behavior.

Part 11Final QA checklist

Before publishing, confirm:

  • The opening defines CQS before the table of contents.
  • The karma distinction is visible near the top.
  • All seven major sections appear in the required order.
  • The TOC links reach the correct headings.
  • The five tiers run from Lowest to Highest.
  • The checking procedure is a numbered list.
  • The real subreddit check is not presented as a site-owned tool.
  • The four blocking scenarios appear in a comparison table.
  • The signals section has four clear subsections.
  • All five required tables are present.
  • The improvement plan has three ordered phases.
  • There is only one article-local commercial CTA.
  • The CTA appears only after the educational guidance.
  • No CQS tier is promised for purchased accounts.
  • The conclusion contains no second CTA.
  • Tables work on mobile and remain accessible.
  • No unsupported copy, screenshots, statistics or guarantees have been added.