We respect your privacy.

We use strictly necessary cookies to keep you signed in and to protect against CSRF. With your permission we also use a small amount of first-party analytics to improve the product. We do not sell your data and we do not use third-party advertising trackers. See our cookie policy and privacy policy .

Crawlmind
← All learn topics

Rule schema.invalid-range

Fix invalid JSON-LD value type

schema.invalid-range is a check in Crawlmind's site audit that grades medium-impact issues of this kind. This page explains why the rule matters and the exact fix.

Impact: mediumEffort: low

Why it matters

A property value does not match the type the schema.org spec expects. Two common shapes: a date string in the wrong format (ISO 8601 is what every consumer wants), or a string used where a Person/Organization object is expected (e.g. `author: "Jane"` instead of `author: { @type: "Person", name: "Jane" }`).

The fix

```json
// ❌ Wrong type: author expects a Person/Organization, not a string.
"author": "Jane Smith"

// ✅ Right shape
"author": {
  "@type": "Person",
  "name": "Jane Smith"
}
```

Dates: use ISO 8601 (`"2026-05-27T10:00:00Z"`), never a localised string.

Validate with [schema.org's validator](https://validator.schema.org/) or [Google's Rich Results test](https://search.google.com/test/rich-results).

References