Back to all checks

Text quality

Missing space after punctuation — Shopify catalog

Finds punctuation followed by text without the expected space.

Needs your reviewAbout this check

What does missing space after punctuation check?

In ordinary prose, `product.Excellent` can indicate a missing separator, while `example.com`, `3.14`, `v2.1`, `A/B`, times, addresses, and abbreviations show why punctuation needs context.

The detector targets positions where the profile expects separation between a mark and following text; it does not define universal grammar for every language or field.

A missing space can be introduced by sentence concatenation, removal of an empty placeholder, column imports, or replacement logic that accidentally consumed the separator between fragments.

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 — punctuation followed immediately by text where the profile expects separation[correction candidate after review]

The case illustrates a possible pattern; verify decimals, URLs, abbreviations, identifiers, and language conventions before any change.

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

The same class of character can have a legitimate role. Punctuation in URLs, decimals, and identifiers can be structural; PROVEN does not insert spaces universally.

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 punctuation followed immediately by text where a space is expected.

02

Why does it matter?

A missing space can join words or sentences and create inconsistent text.

Why can this matter for catalog maintenance?

Periods, commas, colons, semicolons, question marks, and exclamation marks follow different conventions; URLs, decimals, and identifiers need contextual exclusion rather than blind repair.

In English and Romanian prose, many constructions use spacing after terminal punctuation, while quotations, parentheses, units, and technical forms can change the character neighborhood.

Remediation should insert U+0020 only when meaning and structure confirm two units that need separation. Adding spaces inside a domain or decimal would corrupt the value.

03

What can PROVEN do?

PROVEN can flag the position and context; correction remains a reviewed edit.

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 punctuation followed immediately by text where the profile expects separation and preserves surrounding characters so the merchant can review position and effect.
  2. Check the semanticsThe merchant verifies decimals, URLs, abbreviations, identifiers, and language conventions. 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?

Review should expose several characters on each side so the merchant can tell whether this is a sentence boundary, technical token, or intentionally compact format.

For repeated findings, an identical combination may come from one template; grouping by mark and context is safer than a global “space after every punctuation” command.

After correction, verify tokenization, numbers, links, and the complete sentence, then rerun detection to confirm only the intended case was resolved.

Limits and abstention cases

  • The rule supports readability and consistency where context justifies it; it does not guarantee ranking, traffic, or conversion.
  • It does not ignore context: decimals, URLs, abbreviations, identifiers, and language conventions must be checked before remediation.
  • Punctuation in URLs, decimals, and identifiers can be structural; PROVEN does not insert spaces universally.
  • 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 missing space after punctuation always an error?

No. Punctuation in URLs, decimals, and identifiers can be structural; PROVEN does not insert spaces universally. 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.