Back to all checks

Text quality

Repeated spaces — Shopify catalog

Finds two or more consecutive spaces in the same area of text.

Needs your reviewAbout this check

What does repeated consecutive spaces check?

Two or more consecutive spaces can appear after word replacement, fragment concatenation, tab conversion, PDF copy/paste, or incomplete cleanup of surrounding markup.

In ordinary prose the sequence can create uneven gaps; in preformatted content, ASCII tables, code samples, or monospace alignment, the same sequence can be intentional.

Browsers often collapse whitespace in normal HTML, hiding the difference between stored data and presentation, while plain-text exports can expose the exact sequence again.

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 — two or more consecutive spaces in the same text area[correction candidate after review]

The case illustrates a possible pattern; verify preformatted text, alignment, delimiters, and rendering-hidden differences before any change.

Example B — legitimate context for repeated consecutive spacesPreserve when intent is confirmed

The same class of character can have a legitimate role. Repeated spaces can represent alignment or preformatted structure; PROVEN does not universally compress whitespace.

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 sequences of two or more consecutive spaces in the same area of text.

02

Why does it matter?

Repeated spaces can create uneven spacing and different stored values without a content difference.

Why can this matter for catalog maintenance?

Prudent normalization needs the field type, HTML context, and actual code points because U+0020, NBSP, tabs, and other spacing characters should not be flattened indiscriminately.

In an imported catalog, distribution across products can reveal a common source: double spaces after bullets, colons, or before units can point to different transformation stages.

Remediation should not rewrite newlines, tabs, or no-break spaces as if every case were repeated ASCII spacing; those characters have separate semantics and checks.

03

What can PROVEN do?

PROVEN can prepare normalization of repeated spaces; 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 two or more consecutive spaces in the same text area and preserves surrounding characters so the merchant can review position and effect.
  2. Check the semanticsThe merchant verifies preformatted text, alignment, delimiters, and rendering-hidden differences. 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?

Useful examples include names with an accidental double gap, sentences where token deletion left two separators, and templates where an empty placeholder created adjacent spaces.

Before bulk apply, sample each recurring pattern so intentional alignment in technical product families is not removed by a broad replacement.

After remediation, compare length, whitespace sequences, and rendering, then rerun detection to confirm only the targeted evidence disappeared.

Limits and abstention cases

  • This cleanup addresses data consistency; it does not assume an SEO outcome and does not justify rewriting the surrounding commercial copy.
  • It does not ignore context: preformatted text, alignment, delimiters, and rendering-hidden differences must be checked before remediation.
  • Repeated spaces can represent alignment or preformatted structure; PROVEN does not universally compress whitespace.
  • 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 repeated consecutive spaces always an error?

No. Repeated spaces can represent alignment or preformatted structure; PROVEN does not universally compress whitespace. 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.