Information Density: JSON – Signal Evidence & AI Readability

JSON

(https://json.org) 📸 Data Snapshot: June 20, 2026
Information Density — The Lens

Classify each sentence as substantive or hollow. Grounding markers — numbers, currencies, dates, technical units, named entities — outweigh marketing adjectives. When fluff sits right next to hard evidence, the fluff is forgiven.

Info Density Power-words vs. Substance ratio.
29 Impact Weight: 30 / 100
97% Reputation

Information density is exceptionally high, with a fluff-to-substance ratio near zero. The H1 ‘Introducing JSON’ is followed by rigorous technical definitions including references to the ‘ECMA-262 3rd Edition’ and specific programming languages like ‘C, C++, C#, Java, JavaScript, Perl, and Python.’ The body text consists of structural grammars (e.g., ‘object { ws }’) rather than marketing adjectives, though a single point is assigned for minor conceptual repetition regarding the ‘easy for humans/machines’ value proposition.

Information Density is read straight from the body copy: how much of the text carries grounded, checkable substance versus hollow filler. Below is the clean text the engine analyzed, then the industry’s known generic-claim patterns to weigh it against.

📝 The Narrative — clean text per page (the substance-vs-filler signal)
HOMEPAGE · THIN (https://json.org) JSON
https://www.JSON.org/json-en.html
33 chars
SUB-PAGE (https://json.org/json-en.html) JSON
JSON (JavaScript Object Notation) is a lightweight data-interchange
format. It is easy for humans to read and write. It is easy for machines to
parse and generate. It is based on a subset of the
JavaScript
Programming Language Standard
ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely
language independent but uses conventions that are familiar to programmers of
the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python,
and many others. These properties make JSON an ideal data-interchange language.
JSON is built on two structures:
A collection of name/value pairs. In various languages, this is realized
as an object, record, struct, dictionary, hash table, keyed list, or
associative array.
An ordered list of values. In most languages, this is realized as an array,
vector, list, or sequence.
These are universal data structures. Virtually all modern
programming languages support them in one form or another. It makes sense
that a data format that is interchangeable with programming languages also
be based on these structures.
In JSON, they take on these forms:
An object is an unordered set of name/value pairs. An object
begins with {left brace and ends
with }right brace. Each name is followed
by :colon and the name/value pairs are
separated by ,comma.
An array is an ordered collection of values. An array begins
with [left bracket and ends
with ]right bracket. Values are separated
by ,comma.
A value can be a string in double quotes, or a number,
or true or false or null, or an object or
an array. These structures can be nested.
A string is a sequence of zero or more Unicode characters, wrapped
in double quotes, using backslash escapes. A character is represented as a
single character string. A string is very much like a C or Java string.
A number is very much like a C or Java number, except that the octal
and hexadecimal formats are not used.
Whitespace can be inserted between any pair of tokens. Excepting
a few encoding details, that completely describes the language.
json
element
value
object
array
string
number
"true"
"false"
"null"
object
'{' ws '}'
'{' members '}'
members
member
member ',' members
member
ws string ws ':' element
array
'[' ws ']'
'[' elements ']'
elements
element
element ',' elements
element
ws value ws
string
'"' characters '"'
characters
""
character characters
character
'0020' . '10FFFF' - '"' - '\'
'\' escape
escape
'"'
'\'
'/'
'b'
'f'
'n'
'r'
't'
'u' hex hex hex hex
hex
digit
'A' . 'F'
'a' . 'f'
number
integer fraction exponent
integer
digit
onenine digits
'-' digit
'-' onenine digits
digits
digit
digit digits
digit
'0'
onenine
onenine
'1' . '9'
fraction
""
'.' digits
exponent
""
'E' sign digits
'e' sign digits
sign
""
'+'
'-'
ws
""
'0020' ws
'000A' ws
'000D' ws
'0009' ws
2873 chars
🧭 Industry Context — common generic-claim patterns in Software, SaaS & Tech Products to weigh the text against
Generic Claims: the all-in-one platform, trusted by thousands of companies, increase productivity by X percent, save hours every week, the leading platform for, built for teams of all sizes…
Red Flags: AI claims without explaining what the AI does, customer logos without case study or testimonial evidence, no live product access or demo, SOC 2 claims without audit period or report availability, productivity claims without methodology, pricing hidden behind sales calls only…
Semantic Drift Patterns: homepage claims AI-powered but product is rules-based, claims enterprise-grade but pricing page shows startup tiers only, homepage shows Fortune 500 logos but case studies are small businesses, claims all-in-one but integration page shows critical missing pieces, free plan promoted but core features require expensive upgrade…
Proof Expectations: live product demo or free trial access, specific feature documentation with screenshots, verified customer logos with published case studies, third-party review scores on G2, Capterra, or TrustRadius, published uptime SLA and status page, security certifications with audit dates…