Why can a character code appear instead of the intended symbol?
HTML uses character references to represent special characters, typically as a sequence beginning with an ampersand and ending with a semicolon. If text is escaped twice, imported into the wrong kind of field, or not decoded at the correct stage, the code can remain visible to shoppers instead of the intended character.
The detector looks for recognized encoded sequences left inside text values. PROVEN can prepare decoding when the result is clear; where the literal sequence is intentional, review prevents useful text from being changed.
Examples showing why context matters
These examples are fictional and explain the kind of situation the detector can flag. They are not measured store findings and do not justify an edit without checking real product data.
“Tom & Jerry” displayed literally“Tom & Jerry” may be the intended form after reviewDouble escaping can leave the code visible instead of the ampersand.
“5 < 10” in a field where the user should see “<”Decoding can be correct when the field is plain textField context matters so remediation does not create active markup.
A technical guide intentionally shows the literal text “&copy;”[may be intentional and should not be decoded]The detector requires review because character references can be legitimate educational content.
What does PROVEN check?
Checks encoded sequences that represent characters but remain displayed as text.
Why does it matter?
The sequence can display the code instead of the character it was meant to represent.
Why is this useful to a merchant?
Literal character codes can make titles and descriptions hard to read and can reveal an import or escaping pipeline applied twice. Finding them across a catalog can help identify the shared source and correct the process.
For shoppers and SEO, the goal is clear, semantically correct displayed text. The detector does not assume every ampersand sequence is wrong and does not transform markup without context.
What can PROVEN do?
PROVEN can prepare decoding of recognized sequences; the change requires your review.
How PROVEN handles this check
The workflow separates a reproducible finding from the editorial decision about the final value.
- Recognize the encoded sequencePROVEN identifies known character-reference forms that remain in their textual representation.
- Check field type and contextThe finding exposes the value so the merchant can decide whether it should be decoded or intentionally displayed literally.
- Prepare controlled decodingFor confirmed cases, PROVEN can prepare the resulting character while application stays under review.
Why might your review be required?
The same sequence can be an escaping error or intentional text in documentation, specifications, or a technical example.
Decoding must not turn plain-text content into active markup or change a sequence that the product content is supposed to display literally.
What this page does not tell you
- The detector looks for recognized encoded sequences, not every ampersand.
- A character reference does not prove that text was double-escaped.
- Decoding can have different meaning in HTML and in a field treated as plain text.
- Examples are fictional and are not findings from your store.
- This page does not promise measurable SEO improvement from decoding characters.
Frequently asked questions
What is an HTML character reference?
It is a textual escape sequence used in HTML to represent another character, such as &amp; for an ampersand in HTML source.
Why would the code appear on screen?
It can be double-escaped, imported into the wrong context, or left undecoded by a processing pipeline.
Does PROVEN decode every entity automatically?
No. Context must be reviewed to avoid changing intentional text or producing an inappropriate character.
Can this happen in product titles?
It can appear in any textual value analyzed by the detector when a pipeline stores the encoded sequence instead of the intended character.
Sources and independent context
The sources below explain the relevant platform or standards. They provide context for interpretation but do not by themselves show that your store has this finding.
- MDN — Character referenceMDN explains that character references are escape sequences used to represent other characters in HTML.
- Shopify — Product details pageShopify documents the main product text fields where such sequences can become shopper-visible if stored incorrectly.