Back to all checks

Text quality

Space before punctuation — Shopify catalog

Finds spaces placed incorrectly before punctuation.

Needs your reviewAbout this check

What does space before punctuation check?

A space before a comma or period is accidental in much prose, but conventions for colons, semicolons, question marks, exclamation marks, quotation marks, and other signs differ by language and style guide.

French typography, for example, can use spacing before some punctuation where English does not; a multilingual catalog cannot apply one assumption to every locale.

The space can come from copy/paste, templates with an empty placeholder, NBSP conversion, translation, or edits where punctuation moved without removing the previous separator.

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 — space before punctuation in contexts where the profile does not expect it[correction candidate after review]

The case illustrates a possible pattern; verify locale, typography, multilingual conventions, numbers, and technical formats before any change.

Example B — legitimate context for space before punctuationPreserve when intent is confirmed

The same class of character can have a legitimate role. Spacing conventions differ across languages; PROVEN does not apply English rules to every locale.

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 spaces placed before punctuation where they are not expected.

02

Why does it matter?

Unusual spacing creates inconsistent text and can alter the displayed value.

Why can this matter for catalog maintenance?

Numbers, units, emoticons, formulas, and technical strings can have their own conventions, so the finding must be interpreted with locale and field type.

U+0020 before punctuation should not be confused with NBSP or narrow no-break space; visual similarity does not mean wrapping semantics or safe normalization are identical.

Remediation removes the space only when contextual rules establish residue. Global normalization could damage localized copy or deliberate typography.

03

What can PROVEN do?

PROVEN can prepare removal of identified safe spaces before punctuation; 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 space before punctuation in contexts where the profile does not expect it and preserves surrounding characters so the merchant can review position and effect.
  2. Check the semanticsThe merchant verifies locale, typography, multilingual conventions, numbers, and technical formats. 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 review presents the whole construction rather than only the “space + mark” pair so abbreviations, citations, and mathematical expressions are not detached from meaning.

For bulk apply, segment by language and source first; the same sequence can be an error in one supplier feed and a correct convention in a localized translation.

After editing, both visual rendering and raw text should remain coherent, with intentional no-break behavior preserved where it exists.

Limits and abstention cases

  • This page documents a contextual hygiene check rather than a universal punctuation law and does not promise SEO results.
  • It does not ignore context: locale, typography, multilingual conventions, numbers, and technical formats must be checked before remediation.
  • Spacing conventions differ across languages; PROVEN does not apply English rules to every locale.
  • 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 space before punctuation always an error?

No. Spacing conventions differ across languages; PROVEN does not apply English rules to every locale. 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.