Back to all checks

Text quality

Unusual spaces — Shopify catalog

Finds unusual spacing characters that can look like normal spaces.

Needs your reviewAbout this check

What does unusual unicode whitespace check?

NBSP, narrow no-break space, thin space, and other Unicode spacing characters can resemble ASCII space while carrying different code points and line-breaking behavior.

Copy/paste from word processors, web pages, PDFs, or supplier catalogs can introduce these characters without making the difference obvious in the editor.

A no-break space can be intentional between a number and unit, inside a proper name, or in a typographic construction; global replacement with U+0020 can change wrapping.

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 — spacing characters that can look like U+0020 while using different code points or behavior[correction candidate after review]

The case illustrates a possible pattern; verify NBSP, no-break behavior, typography, and copy/paste from external sources before any change.

Example B — legitimate context for unusual unicode whitespacePreserve when intent is confirmed

The same class of character can have a legitimate role. A non-ASCII space can be intentional, including for no-break behavior; the detector does not universally convert every space to U+0020.

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 unusual spacing characters that can look like ordinary spaces.

02

Why does it matter?

Different spacing characters can create values that look identical but are stored inconsistently.

Why can this matter for catalog maintenance?

Investigation should identify the actual code point rather than its visual appearance. Code point, Unicode property, and position provide stronger evidence than browser rendering alone.

For comparison and deduplication, two visually identical strings can remain distinct because of spacing representation; that is a consistency issue, not proof that the wording is semantically wrong.

For feeds, test JSON or CSV serialization, marketplace export, and reimport because some systems normalize NBSP while others preserve it exactly.

03

What can PROVEN do?

PROVEN can prepare replacement of unusual spacing with a normalized form; the change requires your 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 spacing characters that can look like U+0020 while using different code points or behavior and preserves surrounding characters so the merchant can review position and effect.
  2. Check the semanticsThe merchant verifies NBSP, no-break behavior, typography, and copy/paste from external sources. 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?

Safe remediation can convert cases confirmed as residue while explicitly preserving no-break behavior where spacing protects a unit, formula, or expression.

Not every invisible character is whitespace and not every whitespace character is interchangeable; WORD JOINER, ZWJ, and ZWNJ have different roles and should not be folded into this rule.

During review, showing the code point and neighboring text is more informative than a blind replace-all operation, particularly in multilingual catalogs.

Limits and abstention cases

  • A good result is consistent representation that preserves intended typography and necessary no-break behavior without making claims about rankings, traffic, or conversion.
  • It does not ignore context: NBSP, no-break behavior, typography, and copy/paste from external sources must be checked before remediation.
  • A non-ASCII space can be intentional, including for no-break behavior; the detector does not universally convert every space to U+0020.
  • 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 unusual unicode whitespace always an error?

No. A non-ASCII space can be intentional, including for no-break behavior; the detector does not universally convert every space to U+0020. 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.