Your portfolio page showcases past events, shows, and performances. This blueprint structures each entry as a machine-readable record so AI systems can cite specific events and outcomes when recommending your entertainment venue.
The portfolio page is your proof of experience. When someone asks AI "show me venues that have hosted large concerts" or "who has experience with corporate entertainment events," this is the page that provides the evidence. Without structured event data, AI cannot connect your past work to incoming queries.
CollectionPage as the page type to signal that this is a curated set of items, not a single article or event listing.CreativeWork node with a name, description, image, and dateCreated. This gives AI a structured record of what you hosted, when, and what it looked like.EntertainmentBusiness node using creator so AI knows which venue hosted it.contentLocation to each entry tells AI where the event took place, reinforcing your venue's identity and geographic relevance.Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.
Researched and tested by Minnesota AI
nameurlCopy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.
You are implementing AIFDS-compliant JSON-LD structured data for a Entertainment Business Portfolio page. AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which structured data fields AI systems actually read, parse, and use when deciding whether to cite a page. Documentation at aifds.org. Before generating any code, ask me for the following information in a single numbered list. Do not generate schema until I have answered every required field. REQUIRED — do not proceed without these: 1. Domain 2. Event date 3. Event description 4. Event image 5. Event name 6. Faq answer 7. Faq question 8. Logo 9. Portfolio page description 10. Portfolio page title 11. Venue name OPTIONAL — ask for these but proceed if I skip them: 1. Any additional details not covered above Once I provide the information, output a complete JSON-LD script block ready to paste into the <head> of my HTML page. Output requirements: - Valid JSON-LD wrapped in <script type="application/ld+json"> tags - schema.org vocabulary only - Every AIFDS-required field for this industry and page type included - Include this data attribute on the script tag: data-aifds="aifds.org Entertainment Business Portfolio" - No placeholder text — omit missing optional fields rather than fill with examples - After the code block, list any optional fields skipped that would strengthen AI citation
Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai
Copy the template below and replace every YOUR_* value with your own data. Add or remove CreativeWork entries to match the number of past events in your portfolio.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "CollectionPage",
"@id": "https://YOUR_DOMAIN.com/portfolio/",
"name": "YOUR_PORTFOLIO_PAGE_TITLE",
"description": "YOUR_PORTFOLIO_PAGE_DESCRIPTION",
"url": "https://YOUR_DOMAIN.com/portfolio/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/portfolio/#breadcrumb"
},
"mainEntity": {
"@type": "ItemList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@id": "https://YOUR_DOMAIN.com/portfolio/#event-1"
}
},
{
"@type": "ListItem",
"position": 2,
"item": {
"@id": "https://YOUR_DOMAIN.com/portfolio/#event-2"
}
},
{
"@type": "ListItem",
"position": 3,
"item": {
"@id": "https://YOUR_DOMAIN.com/portfolio/#event-3"
}
}
]
}
},
{
"@type": "CreativeWork",
"@id": "https://YOUR_DOMAIN.com/portfolio/#event-1",
"name": "YOUR_EVENT_NAME_1",
"description": "YOUR_EVENT_DESCRIPTION_1",
"image": "https://YOUR_DOMAIN.com/YOUR_EVENT_IMAGE_1.jpg",
"dateCreated": "YOUR_EVENT_DATE_1",
"creator": {
"@id": "https://YOUR_DOMAIN.com/#business"
},
"contentLocation": {
"@type": "Place",
"name": "YOUR_VENUE_NAME"
}
},
{
"@type": "CreativeWork",
"@id": "https://YOUR_DOMAIN.com/portfolio/#event-2",
"name": "YOUR_EVENT_NAME_2",
"description": "YOUR_EVENT_DESCRIPTION_2",
"image": "https://YOUR_DOMAIN.com/YOUR_EVENT_IMAGE_2.jpg",
"dateCreated": "YOUR_EVENT_DATE_2",
"creator": {
"@id": "https://YOUR_DOMAIN.com/#business"
},
"contentLocation": {
"@type": "Place",
"name": "YOUR_VENUE_NAME"
}
},
{
"@type": "CreativeWork",
"@id": "https://YOUR_DOMAIN.com/portfolio/#event-3",
"name": "YOUR_EVENT_NAME_3",
"description": "YOUR_EVENT_DESCRIPTION_3",
"image": "https://YOUR_DOMAIN.com/YOUR_EVENT_IMAGE_3.jpg",
"dateCreated": "YOUR_EVENT_DATE_3",
"creator": {
"@id": "https://YOUR_DOMAIN.com/#business"
},
"contentLocation": {
"@type": "Place",
"name": "YOUR_VENUE_NAME"
}
},
{
"@type": "EntertainmentBusiness",
"@id": "https://YOUR_DOMAIN.com/#business",
"name": "YOUR_VENUE_NAME",
"url": "https://YOUR_DOMAIN.com",
"logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png"
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/portfolio/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Portfolio",
"item": "https://YOUR_DOMAIN.com/portfolio/"
}
]
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_2"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_3",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_3"
}
}
]
}
]
}
The Event type is for upcoming or current events with dates and ticket availability. Portfolio entries are records of past events — they showcase what you have done, not what is happening next. CreativeWork is the best general-purpose type for portfolio entries because it supports name, description, image, dateCreated, and creator — everything AI needs to understand a completed event.
Include every past event you want AI to know about. There is no practical limit, but each entry should have a clear name, description, and image. Quality matters more than quantity — three well-described events with photos are more useful to AI than twenty entries with just a title.
If you are comfortable sharing them, include attendance figures in the description field. There is no standard Schema.org property for event attendance on CreativeWork, but AI reads description text and can use numbers like "500+ attendees" to gauge your venue's capacity and popularity when answering queries about large event venues.