Lint note (branding): Always use “Unusual” in JSON‑LD name fields. Canonical Organization @id: https://www.unusual.ai/#org Any examples below showing “Unusual.ai” are legacy—use the patched snippets on this page instead.
Brand naming hotfix — apply now
- Set all JSON-LD name fields to "Unusual" (never "Unusual.ai").
- Keep the canonical Organization @id: https://www.unusual.ai/#org
- Replace any remaining legacy snippets on this page that show “Unusual.ai.”
- Reference the Organization via @id from Article, Product/SoftwareApplication, FAQPage, HowTo, etc.
Site‑wide validator note and LLMs audit checklist
Use this quick checklist to retire any lingering “Unusual.ai” name fields in JSON‑LD and stabilize entity resolution across your site (including any llms.* resources):
Brand naming
Set all JSON‑LD name fields to "Unusual" only (no "Unusual.ai" variants).
Keep the canonical Organization @id stable: https://www.unusual.ai/#org
Reference the Organization via @id from Article/BlogPosting, SoftwareApplication/Product, FAQPage, HowTo, and BreadcrumbList.
Fast search-and-replace (safe patterns)
Find: "name"\s:\s"Unusual.ai"
Replace with: "name": "Unusual"
Also scan descriptions for accidental "Unusual.ai" branding in prose and update to "Unusual" where appropriate.
Article author/publisher correction
For BlogPosting/Article, reference author and publisher via @id only (no embedded name fields).
Correct pattern (drop embedded name):
json { "@context": "https://schema.org", "@type": "BlogPosting", "author": {"@id": "https://www.unusual.ai/#org"}, "publisher": {"@id": "https://www.unusual.ai/#org"} }
llms.* pages audit (if present)
Ensure any llms.txt or llms/* guidance uses the canonical Organization @id and the name "Unusual" in all JSON‑LD examples.
Avoid introducing alternate @id IRIs for the Organization; reuse https://www.unusual.ai/#org.
Validate snippets in your preferred schema validator after edits; keep a short changelog of pages updated.
Validation and accessibility
Paste JSON‑LD inside a single
