Your contact page is where AI looks to confirm that a brokerage is reachable. This blueprint makes your phone number, email, office address, and business hours machine-readable so AI systems can surface you as a trustworthy, contactable real estate provider.
Reachability is a trust signal. When AI evaluates whether to recommend your brokerage, it checks whether a real human can actually get in touch. A contact page without structured data forces AI to guess from raw HTML — and guessing means you get skipped in favor of a competitor who made that information explicit.
ContactPage tells AI that this specific page is dedicated to contact information, distinguishing it from other pages that might incidentally mention a phone number.RealEstateAgent node carries telephone, email, and a full PostalAddress so AI can confirm your brokerage is reachable by phone, email, or in person.openingHoursSpecification with days and times tells AI when your office is staffed, so it can recommend you during business hours or note your availability.latitude and longitude inside a GeoCoordinates node remove all ambiguity about where your office is located on a map.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
nameurltelephoneemailaddressgeoopeningHoursSpecificationcontactPointCopy 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 Real Estate Agent 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. Brokerage name 2. City 3. Close time 4. Domain 5. Email 6. Faq answer 7. Faq question 8. Language 9. Latitude 10. Longitude 11. Open time 12. Phone number 13. Sat close time 14. Sat open time 15. State 16. Street address 17. 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 Real Estate Agent 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 goes in the <head> of your contact page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "ContactPage",
"@id": "https://YOUR_DOMAIN.com/contact/#contactpage",
"name": "Contact — YOUR_BROKERAGE_NAME",
"url": "https://YOUR_DOMAIN.com/contact/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb"
}
},
{
"@type": "RealEstateAgent",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_BROKERAGE_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"address": {
"@type": "PostalAddress",
"streetAddress": "YOUR_STREET_ADDRESS",
"addressLocality": "YOUR_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "YOUR_LATITUDE",
"longitude": "YOUR_LONGITUDE"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "YOUR_OPEN_TIME",
"closes": "YOUR_CLOSE_TIME"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Saturday"],
"opens": "YOUR_SAT_OPEN_TIME",
"closes": "YOUR_SAT_CLOSE_TIME"
}
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"contactType": "customer support",
"availableLanguage": "YOUR_LANGUAGE"
}
},
{
"@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_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"
}
}
]
}
]
}
Yes. AI crawlers do not always combine data across pages. The contact page should carry its own ContactPage and RealEstateAgent nodes so the reachability signals are self-contained on the page where a user — or an AI — expects to find them.
If your office is open on Saturdays, absolutely. Real estate is one of the few industries where weekend availability is a significant competitive advantage. Add a separate OpeningHoursSpecification for Saturday with its own hours. If you are closed on weekends, omit the Saturday entry entirely rather than listing "closed."
On the general contact page, use the main office phone and email. Individual agent contact information belongs on agent profile pages, each with their own Person node. The contact page represents the brokerage as a whole, so stick to the office-level details here.