The contact page surfaces how customers reach your store — email, phone, chat, hours. When AI systems evaluate whether to recommend a store, reachability is a trust signal. This blueprint structures your contact information so AI can confirm your store is accessible and responsive.
A contact page must declare every way a customer can reach your store and when support is available. AI systems use this data to answer questions like "can I call this store?" or "what are their support hours?" before sending a shopper your way.
Organization node includes a contactPoint array with ContactPoint entries for each department — customer support, returns, sales — each with email, telephone, contactType, and availableLanguage.PostalAddress tells AI where your business is located, even if you are primarily online. This anchors your store to a real-world entity.openingHoursSpecification on each contact point tells AI when your team is available, so it can set accurate expectations for shoppers.ContactPage tells AI this is the canonical place to find your store's contact information, not just a page that happens to mention an email address.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
nameurlcontactPoint@idCopy 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 Ecommerce Contact 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. City 2. Contact faq answer 3. Contact faq question 4. Domain 5. Logo 6. Returns email 7. State 8. Store name 9. Street address 10. Support close 11. Support email 12. Support open 13. Support phone 14. Zip 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 Ecommerce Contact" - 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 your contact page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_STORE_NAME",
"url": "https://YOUR_DOMAIN.com",
"logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png",
"address": {
"@type": "PostalAddress",
"streetAddress": "YOUR_STREET_ADDRESS",
"addressLocality": "YOUR_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
},
"contactPoint": [
{
"@type": "ContactPoint",
"contactType": "customer support",
"email": "YOUR_SUPPORT_EMAIL",
"telephone": "YOUR_SUPPORT_PHONE",
"availableLanguage": ["English"],
"hoursAvailable": {
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "YOUR_SUPPORT_OPEN",
"closes": "YOUR_SUPPORT_CLOSE"
}
},
{
"@type": "ContactPoint",
"contactType": "returns",
"email": "YOUR_RETURNS_EMAIL",
"availableLanguage": ["English"]
}
]
},
{
"@type": "ContactPage",
"@id": "https://YOUR_DOMAIN.com/contact/#webpage",
"url": "https://YOUR_DOMAIN.com/contact/",
"name": "Contact Us",
"isPartOf": {
"@type": "WebSite",
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#organization"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Contact",
"item": "https://YOUR_DOMAIN.com/contact/"
}
]
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_CONTACT_FAQ_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_CONTACT_FAQ_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_CONTACT_FAQ_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_CONTACT_FAQ_ANSWER_2"
}
}
]
}
]
}
Different contact points serve different purposes. A customer asking about a return needs a different email than someone asking about product availability. By declaring separate ContactPoint entries with distinct contactType values, AI systems can route shoppers to the right channel and give more specific answers about how to reach you.
Yes. Even if your store is always open for orders, your support team has working hours. The hoursAvailable property on each contact point tells AI when a human will respond. This prevents AI from telling a shopper to call you at midnight when no one is there to answer.
The contact page is about reachability — how to get in touch and when. The about page is about identity — who you are, your story, and your mission. AI systems treat these as different signals. A contact page builds trust through accessibility, while an about page builds trust through transparency.