Editorial Policy

Last updated: 2026-09-15

Our purpose

To be the most accurate and genuinely useful resource about brick breaker games: how to play them, how they work underneath, where they came from, and how to build one. Everything published here is judged against whether it helps a reader do one of those things.

Who writes and reviews

All content is written and reviewed by Daniel Carter, the site's editor. There is no team, no guest contributors and no outsourced writing. Where an article makes a claim about game behaviour, that claim is verified against the game code, which the same person wrote.

We state clearly that our editor's expertise is editorial and practical - eight-plus years writing about arcade and browser gaming, plus building the games published here - and not a formal professional credential. We make no claim to academic qualifications, industry awards or employment history in game development.

How topics are chosen

A topic is published when it meets all four tests:

1. A real question. Someone is actually trying to find this out.
2. A distinct intent. It is not already answered by an existing page here. We do not publish near-duplicates targeting keyword variations.
3. Something to add. We can say something more specific, more accurate or better organised than what already exists.
4. Verifiable. We can check the claims, either against our own code or against a documented source.

Topics that fail these tests are not published, regardless of their search volume. We do not create pages solely to increase the number of URLs on the site.

The production process

1. Research. Gather sources. For gameplay claims, that means reading the engine code and playing the game. For historical claims, that means documented references.
2. Outline. Structure the article around the reader's actual question, and confirm it does not overlap an existing page.
3. Draft. Write it, including specific numbers and worked examples rather than generalities.
4. Fact check. Verify every factual claim against a source or against the game. See the fact checking policy.
5. Editorial review. Check accuracy, clarity, internal links and whether the article actually answers the question it promises.
6. SEO review. Title, meta description, heading structure, alt text, internal links and structured data - applied after the content is right, never before.
7. Publish.
8. Maintain. Review when a game changes or new information emerges.

Standards every article must meet

• Original. Written from scratch. Nothing is scraped, spun or paraphrased from another site.
• Specific. Real numbers, real examples, named games. "Use power-ups wisely" is not advice.
• Honest about uncertainty. Contested historical claims are attributed. Where we do not know, we say so.
• No invented data. No fabricated statistics, ratings, testimonials, awards or user numbers - anywhere on the site, including structured data.
• Readable. Plain language, short paragraphs, headings that describe what is below them.
• Properly linked. Internal links where they genuinely help, external sources where a claim needs support.

What we do not do

• Keyword stuffing, or writing for a search engine rather than a reader.
• Thin pages created to target a keyword variation.
• Doorway pages, auto-generated content or AI-written filler published without review.
• Paid reviews, sponsored articles or affiliate links.
• Clickbait headlines that the article does not deliver on.
• Copying game code, level designs, artwork or descriptions from other developers.

Advertising and editorial independence

Advertising, if enabled, is served by third-party networks that have no influence over what we publish. No advertiser receives editorial coverage, review or placement in return for payment. No affiliate links are used anywhere on this site.

Ad containers sit in fixed positions in the layout - after an article's introduction, in the sidebar and at the foot of the page. They are never placed inside a game area, never styled to resemble a game control, and never positioned where an accidental click is likely.

Publication and update dates

Every article shows when it was published and when it was last updated. The updated date changes only when content actually changes in a meaningful way - a corrected fact, a revised recommendation, a new section. It is never refreshed cosmetically to appear current.

Corrections

We correct errors as quickly as we can confirm them. Significant corrections that change an article's meaning are noted on the page itself. The process is in the fact checking policy.

Report an error to editorial@brickbreakergames.xyz.

Use of AI tools

We use software tools in production, including for drafting assistance and proofreading. No article is published without a human reading it in full, verifying its factual claims and taking editorial responsibility for it. We do not publish unreviewed machine-generated text, and the editor named on an article is accountable for everything in it.

Content review schedule

Game guides are reviewed whenever the game they describe is retuned. Historical articles are reviewed when new sources become available. Everything else is reviewed at least annually, and the updated date changes only if the review produced a change.