Entity Schema Builder Prompt (Person & Organization Graph)

You are a semantic SEO specialist.

by growthack88·MIT license·GitHub ↗

Use now

23 lines · 1,642 characters · paste it into ChatGPT, Claude or Gemini

Inside this prompt

prompt text · the author's own words
You are a semantic SEO specialist. Build me a complete JSON-LD entity graph for my personal/brand site. Output ONE <script type="applicatio…

MY ENTITY:
- Person: name, role/title, one-line credential: [X]
- Primary domain (the entity hub): [X]
- Organization(s) I own/represent: [name + URL each]
- Creative works: books/guides/courses: [title + URL + type each]
- Products/apps: [name + URL + one-liner each]
- Social & authority profiles for sameAs: [LinkedIn, YouTube, X, GitHub, Wikipedia if any...]
- Languages I publish in: [X]

BUILD RULES:
1. @graph with stable @id URIs for every node (https://domain.com/#person, /#organization, /#book-slug...) — never anonymous nodes.
2. Person node: jobTitle, description, knowsAbout (5-8 topical entities), knowsLanguage, sameAs (ALL profiles), image placeholder.
3. Each Organization/Product/CreativeWork: correct schema type (SoftwareApplication for SaaS, Book/Guide for publications), url, and founde…
4. WebSite node with publisher → Person @id.

Word-for-word excerpt, not a result. Read the full prompt ↓

The prompt

23 lines · 1,642 characters
1You are a semantic SEO specialist. Build me a complete JSON-LD entity graph for my personal/brand site. Output ONE <script type="application/ld+json"> block using @graph.
2 
3MY ENTITY:
4- Person: name, role/title, one-line credential: [X]
5- Primary domain (the entity hub): [X]
6- Organization(s) I own/represent: [name + URL each]
7- Creative works: books/guides/courses: [title + URL + type each]
8- Products/apps: [name + URL + one-liner each]
9- Social & authority profiles for sameAs: [LinkedIn, YouTube, X, GitHub, Wikipedia if any...]
10- Languages I publish in: [X]
11 
12BUILD RULES:
131. @graph with stable @id URIs for every node (https://domain.com/#person, /#organization, /#book-slug...) — never anonymous nodes.
142. Person node: jobTitle, description, knowsAbout (5-8 topical entities), knowsLanguage, sameAs (ALL profiles), image placeholder.
153. Each Organization/Product/CreativeWork: correct schema type (SoftwareApplication for SaaS, Book/Guide for publications), url, and founder/author/publisher pointing BACK to the Person @id — the graph must be bidirectional.
164. WebSite node with publisher → Person @id.
175. NO claims that aren't verifiable on the listed URLs. If I gave you a credential you can't tie to a URL, put it in a comment for me to decide.
186. Output must validate: no trailing commas, correct @context, one block.
19 
20THEN OUTPUT:
21- A placement note: which page(s) this belongs on (entity hub page vs sitewide)
22- A maintenance checklist: what to update when I launch a new product
23- 3 test queries to run in an LLM a few weeks later to check entity resolution ("who is [name]?", "what is [product]?", "what has [name] created?")

Discussion