Skip to content

seo: expand Organization JSON-LD sameAs to all 10 social profiles#42

Open
VaultSparkStudios wants to merge 1 commit into
mainfrom
seo/organization-schema-sameas
Open

seo: expand Organization JSON-LD sameAs to all 10 social profiles#42
VaultSparkStudios wants to merge 1 commit into
mainfrom
seo/organization-schema-sameas

Conversation

@VaultSparkStudios

Copy link
Copy Markdown
Owner

What changed

The Organization JSON-LD structured data block in index.html previously declared only 2 social profiles in sameAs (Discord + GitHub). The footer already carries 14 social channels with rel="me", and the canonical /.well-known/entity-graph.json declares 8. This mismatch means search engines and AI answer engines see an incomplete entity record for VaultSpark Studios on the most-crawled page.

Changes to index.html (head block only):

Field Before After
@id (absent) https://vaultsparkstudios.com/#organization
legalName (absent) "VaultSpark Studios LLC"
sameAs count 2 10

The 10 sameAs entries now match the entity-graph.json canonical source plus Discord and Threads, which carry rel="me" in the footer but were absent from both schema sources:

  • GitHub, YouTube, X/Twitter, Instagram, Reddit, Bluesky, Facebook, TikTok, Discord, Threads

The @id anchor (#organization) explicitly links this block to the entity-graph.json @graph node, enabling proper cross-document entity resolution.

Why it matters

  • Google/Bing knowledge graph uses sameAs + @id to build entity cards. Incomplete sameAs = fragmented entity signals across 10 separate crawled profiles that don't resolve to a single studio record.
  • AI answer engines (SGE, Perplexity, ChatGPT Browse) synthesize social profiles for studio cards. Only GitHub and Discord being wired meant 8 official channels were invisible at the schema layer.
  • legalName surfaces in rich result eligibility for organization panels.
  • Aligns with CANON-048 (dual-audience — built for Humans AND AI Agents).

What to verify

  • Run the page through Google Rich Results Test — Organization entity should show 10 sameAs URLs and both name/legalName
  • Validate with Schema.org validator — no errors expected
  • Confirm @id resolves: /.well-known/entity-graph.json already uses the same #organization anchor
  • No visual or functional change on the page — this is head-only metadata

Scope

Single file change: index.html head block (JSON-LD only). No HTML structure, no CSS, no JS touched.


Generated by Claude Code

- Adds @id anchor linking to entity-graph.json (#organization)
- Adds legalName field (VaultSpark Studios LLC)
- Expands sameAs from [Discord, GitHub] to all 10 primary social profiles,
  matching the entity-graph.json canonical source plus Discord and Threads
  which carry rel="me" in the footer but were absent from the schema

Helps Google/Bing knowledge graph entity disambiguation and AI search
systems correctly attribute studio content across all official channels.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants