Back to all checks

Text quality

Unbalanced brackets — Shopify catalog

Finds opening or closing brackets without the matching pair.

Needs your reviewAbout this check

What does unbalanced brackets in catalog text check?

Round `()`, square `[]`, and curly `{}` brackets can delimit sizes, codes, options, formulas, or clarifications; an incomplete pair can indicate truncation but does not reveal which character is missing.

A closing bracket without an opening partner can come from a copied fragment, while an opening bracket without a close can signal import truncation, unfinished editing, or an accidentally deleted delimiter.

Nesting complicates review: `(text [detail])` is structurally balanced, while simple character counts can miss incorrect order or crossing bracket types.

Examples that require context

These are fictional educational examples. They illustrate situations where review is useful and do not represent real merchant data.

Example A — round, square, or curly brackets without the corresponding pair[correction candidate after review]

The case illustrates a possible pattern; verify truncated text, nesting, formulas, codes, and stray marks before any change.

Example B — legitimate context for unbalanced brackets in catalog textPreserve when intent is confirmed

The same class of character can have a legitimate role. Mechanical balancing does not prove the correct form: a mark may be missing, extra, or the text may be truncated.

Example C — value without this findingPreserve the value

Absence of this issue does not prove overall text quality; other detectors remain independent.

01

What does PROVEN check?

Checks round, square, or curly brackets that do not have a matching pair.

02

Why does it matter?

An incomplete pair can indicate truncated text, a missing character, or accidentally entered punctuation.

Why can this matter for catalog maintenance?

Technical codes, mathematical expressions, regexes, JSON-like text, and commercial names may use brackets intentionally, so remediation cannot treat every bracket as ordinary prose punctuation.

PROVEN can show position and type but does not invent the missing partner: `Size (XL` might require `)`, removal of `(`, or wording confirmed from a trusted source.

The source of truth is the product, technical sheet, supplier, or sentence context. Adding a “probable” bracket without confirmation can change meaning or a code.

03

What can PROVEN do?

PROVEN can flag the position and bracket type; the correct form must be established through review.

How PROVEN handles the finding

The workflow preserves evidence and separates detection from the remediation decision to avoid speculative normalization.

  1. Locate the evidencePROVEN locates round, square, or curly brackets without the corresponding pair and preserves surrounding characters so the merchant can review position and effect.
  2. Check the semanticsThe merchant verifies truncated text, nesting, formulas, codes, and stray marks. Context determines whether the finding is residue, a valid convention, or a case that should remain unchanged.
  3. Prepare the changeOnly after confirmation can PROVEN prepare a targeted edit. The proposal preserves unrelated text and remains reviewable before application.

What should be reviewed before application?

In HTML, markup syntax must be separated from visible text; brackets used by code or attributes are not equivalent to punctuation displayed to the shopper.

For bulk review, identical patterns at one column or suffix can indicate systematic truncation, while isolated free-form examples need an individual editorial decision.

Post-fix validation checks pairing, nesting order, and textual fidelity rather than only comparing the number of opening and closing characters.

Limits and abstention cases

  • This detector is a lightweight syntactic integrity signal; it does not claim that every balanced pair is semantically correct and does not promise SEO results.
  • It does not ignore context: truncated text, nesting, formulas, codes, and stray marks must be checked before remediation.
  • Mechanical balancing does not prove the correct form: a mark may be missing, extra, or the text may be truncated.
  • The result should be interpreted in the context of the field and product; a finding is not an automatic verdict.
  • It does not invent copy, missing characters, data provenance, or merchant intent.
  • It does not guarantee SEO, ranking, traffic, or conversion benefits after remediation.

Frequently asked questions

Is unbalanced brackets in catalog text always an error?

No. Mechanical balancing does not prove the correct form: a mark may be missing, extra, or the text may be truncated. The finding identifies a review case, and the decision depends on field, language, format, and evidence.

Does PROVEN apply the change automatically?

Not from the finding alone. This check requires review, and the proposal must be checked before application.

Is this an official Shopify limit?

No. Shopify sources provide content-editing context; the exact criterion remains PROVEN detector-specific.

Why are Unicode sources used?

They provide context about text representation and processing and help interpret the finding.

Sources and independent context

The sources explain the relevant standard or content editor. They provide context for interpretation but do not by themselves show that a store has this finding.