Blog posts let your restaurant share stories, seasonal updates, recipes, and event announcements. Structured data on each post ensures AI systems can attribute your content to the right author and restaurant, making it citable in food-related queries and editorial recommendations.
A blog post without structured data is invisible to AI as authored content. It may be indexed as generic text, but AI will not know who wrote it, when it was published, or which restaurant it represents. Structured data turns every post into a citable source.
BlogPosting node declares this page as a published article with a headline, date, and body, which AI systems index differently from static pages.Person node with author gives AI a named individual to credit, strengthening authority signals for your content.Organization node as publisher connects the post to your restaurant, ensuring AI knows which business produced this content.datePublished, dateModified, and image properties help AI assess freshness and provide rich results when surfacing your post.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
headlinedescriptiondatePublisheddateModifiedauthorpublisherurlimagenameCopy 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 Restaurant Blog 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. Author name 2. Author title 3. Domain 4. Faq answer 5. Faq question 6. Logo 7. Modified date 8. Post description 9. Post image 10. Post slug 11. Post title 12. Publish date 13. Restaurant 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 Restaurant Blog" - 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. This block belongs in a <script type="application/ld+json"> tag in the <head> of each blog post.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "BlogPosting",
"@id": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/#article",
"headline": "YOUR_POST_TITLE",
"description": "YOUR_POST_DESCRIPTION",
"url": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/",
"datePublished": "YOUR_PUBLISH_DATE",
"dateModified": "YOUR_MODIFIED_DATE",
"image": "https://YOUR_DOMAIN.com/YOUR_POST_IMAGE.jpg",
"author": {
"@type": "Person",
"@id": "https://YOUR_DOMAIN.com/#author",
"name": "YOUR_AUTHOR_NAME",
"jobTitle": "YOUR_AUTHOR_TITLE",
"url": "https://YOUR_DOMAIN.com/about/"
},
"publisher": {
"@type": "Organization",
"@id": "https://YOUR_DOMAIN.com/#restaurant",
"name": "YOUR_RESTAURANT_NAME",
"logo": {
"@type": "ImageObject",
"url": "https://YOUR_DOMAIN.com/YOUR_LOGO.png"
}
},
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
}
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/#webpage",
"url": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/",
"name": "YOUR_POST_TITLE",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Blog",
"item": "https://YOUR_DOMAIN.com/blog/"
},
{
"@type": "ListItem",
"position": 3,
"name": "YOUR_POST_TITLE",
"item": "https://YOUR_DOMAIN.com/blog/YOUR_POST_SLUG/"
}
]
},
{
"@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"
}
}
]
}
]
}
BlogPosting is a subtype of Article and is the correct choice for blog content. It signals to AI that this is an informal, regularly published piece of content rather than a formal news article or scholarly work. Use Article only if the content is more formal or journalistic in nature.
Technically yes, but a Person author is stronger. AI systems give more authority to content attributed to a named individual. If the post is written by the chef, owner, or a staff member, use their name. Use the restaurant as author only if the content truly has no individual attribution.
Very important. AI systems use dateModified to assess content freshness. A post published two years ago but updated last month signals that the information is current. If you update a post, always update the dateModified field to reflect the change.