Back to all checks

Text quality

Invisible character between words — Shopify catalog

Flags an invisible character used to keep text together and requiring review.

Needs your reviewAbout this check

What does word joiner u+2060 in catalog text check?

U+2060 WORD JOINER is an invisible no-break character that can suppress a line-break opportunity between fragments without inserting a visible space.

It can be legitimate in formulas, units, numbers, symbols, or sequences whose author wants two fragments to remain together, especially in carefully controlled typographic content.

It is not equivalent to ZWJ or ZWNJ, which influence joining behavior in certain writing systems, and it is not the same as U+FEFF historically used as a BOM.

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 — invisible U+2060 WORD JOINER that can suppress a line-break opportunity[correction candidate after review]

The case illustrates a possible pattern; verify intentional no-break behavior, units, formulas, and distinction from ZWJ/ZWNJ or U+FEFF before any change.

Example B — legitimate context for word joiner u+2060 in catalog textPreserve when intent is confirmed

The same class of character can have a legitimate role. U+2060 WORD JOINER can legitimately provide no-break behavior; it is not ZWJ/ZWNJ and must not be removed merely because it is invisible.

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 for an invisible character used to prevent text separation.

02

Why does it matter?

The character can be intentional in some contexts, so its presence alone is not enough for automatic cleanup.

Why can this matter for catalog maintenance?

Copy/paste from documentation, PDF, or an editor can introduce U+2060 unintentionally; the detector flags context rather than ordering removal of every word joiner.

Review should inspect characters on both sides and the actual line-breaking effect. A unit such as “10 kg”, a formula, or a technical name can have different needs from ordinary prose.

If removal changes wrapping in an undesirable place, the no-break semantics are relevant and the character may need to remain or be replaced by an explicit editorial solution.

03

What can PROVEN do?

PROVEN can show the position and context; keeping or removing it must be decided 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 invisible U+2060 WORD JOINER that can suppress a line-break opportunity and preserves surrounding characters so the merchant can review position and effect.
  2. Check the semanticsThe merchant verifies intentional no-break behavior, units, formulas, and distinction from ZWJ/ZWNJ or U+FEFF. 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 single-line fields the visual effect can be invisible today, while the same text may later be reused in feeds, responsive cards, or exports where line breaking becomes observable.

Remediation must not automatically convert U+2060 into a space because WORD JOINER is not a lexical separator and such a change could introduce new content.

Multilingual catalogs require extra caution around scripts and writing conventions; mandatory review prevents an ASCII-oriented rule from being applied universally.

Limits and abstention cases

  • Final verification checks the code point, wrapping behavior, and neighboring text without claiming that U+2060 presence or removal changes rankings, traffic, or conversion.
  • It does not ignore context: intentional no-break behavior, units, formulas, and distinction from ZWJ/ZWNJ or U+FEFF must be checked before remediation.
  • U+2060 WORD JOINER can legitimately provide no-break behavior; it is not ZWJ/ZWNJ and must not be removed merely because it is invisible.
  • 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 word joiner u+2060 in catalog text always an error?

No. U+2060 WORD JOINER can legitimately provide no-break behavior; it is not ZWJ/ZWNJ and must not be removed merely because it is invisible. 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.