Six Specialist Copy Checkers, Plus the Full Listing Scan (No Signup)

This launch guide covers the specialist checkers and the separate full listing scan. The current specialist suite also includes the Shopify Description Checker. For field counters and the full current suite, see all tools.

The launch checker guide, no signup#

When we launched the compliance scanner, every check ran behind an account. That protected the pipeline but hid the actual product: the rules. So we moved the rules to the front door. Six specialist checkers and a separate full listing scan now run on the site, no signup required. The focused browser checkers use documented rule subsets, while the full listing scanner uses the same compliance engine the generator runs after generation.

• Amazon Title Checker — the 75-character limit that took effect on 27 July 2026, repeated words, promotional phrases, prohibited symbols, and ALL-CAPS emphasis (recognised acronyms like USB and BPA are left alone).
• Amazon Backend Keywords Checker — a field-budget and overlap check. Amazon says generic keywords should stay under 250 bytes; over-budget content can be ignored by Search. Bytes are not characters: an accented "é" costs two. The checker shows raw UTF-8 bytes and a separate Amazon-budget count that excludes whitespace and punctuation. It also shows which words overlap your supplied title; it cannot observe what Amazon actually indexed.
• Product Claim Checker — health, certification, ranking, review-count and green claims, each with the evidence that would support it.
• FTC Claim Checker — the same engine framed around the FTC substantiation standard: a reasonable basis for every objective claim, before publication.
• Meta Ad Copy Checker — configured personal-attribute, outcome and sensational-claim patterns. Meta makes the final platform review decision.
• Shopify Description Checker — Shopify description formatting and configured claim patterns, checked locally in your browser.
• Amazon Listing Compliance Checker — the full paste-and-scan against the rules whose declared scope applies to Amazon. Ad-only or other channel-only rules are not silently treated as Amazon coverage.

Where the checks run#

The focused title, keyword and claim checkers run in your browser, so pasted text for those checks stays on the device. The full Amazon Listing Compliance Checker sends only the text you submit to CopyForge’s same-origin API, scans it in memory with the same compliance engine used after generation, and does not save the pasted text. Each page states its own data path so the privacy claim matches the implementation.

What a clean scan does and does not mean#

A clean result means the configured checks found nothing. It is not marketplace, legal or factual approval — the scan cannot verify your product details, review your certificates, or know your category's tighter caps. What it does do is surface common mechanical and wording risks before publication: length, repetition, prohibited phrasing, and claims that need substantiation.

For the claims that do need evidence, that is where the workflow starts: register the wording, attach the document, get it approved, and only then reuse it everywhere. The checkers find the risk; the registry governs it.

Choose a checker from the question you need answered#

For a fictional mug brief containing only ceramic, white, 300 ml and one mug per box, a short title can fit the budget while a dishwasher-safe promise remains unsupported. Run the title check for field mechanics, then compare every claim against the brief. Use the facts-first exercise to see a clean pattern scan that still misses an unsupported claim.

For keyword sizing, paste café déjà into the backend checker: it has 9 characters, 12 raw UTF-8 bytes and 11 Amazon-budget bytes. The byte walkthrough explains the difference. Neither count tells you whether the terms match customer demand.

This route saves you from using one result to answer a different question. A character pass, a wording scan and a factual review are separate records.

Source boundaries#

See Amazon’s title announcement and the FTC substantiation statement for the underlying policy contexts. Our field counters, completeness checks and pattern scoring are implementation heuristics, not approvals from these organizations.