Your services page is where you list every type of real estate service you provide — buyer representation, seller representation, property management, relocation assistance, and more. This blueprint structures those offerings into a machine-readable catalog so AI systems can match your agency to the right client queries instead of guessing from paragraph copy.
The services page is where AI maps your actual real estate capabilities. When someone asks "find an agent who handles relocation services" or "who offers buyer representation in Austin," this is the page that answers. Without structured service data, AI has to guess what you do from marketing copy — and it often guesses wrong.
hasOfferCatalog is the critical field. It wraps each real estate service in a structured Offer with a Service item so AI can index your offerings individually — buyer representation, seller representation, property management, and relocation services.name and description — short, specific, and free of marketing fluff. "Buyer representation" is better than "Your dream home journey starts here."areaServed on the business node tells AI where these services are available, which is essential for location-based recommendations in real estate.RealEstateAgent node ties all services back to your agency with name, url, and telephone, so AI knows exactly who provides these offerings.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
nameurltelephoneareaServedhasOfferCatalogCopy 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 Services 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. Agency name 2. Buyer representation description 3. Domain 4. Faq answer 5. Faq question 6. Phone number 7. Primary city 8. Primary state 9. Property management description 10. Relocation services description 11. Seller representation description 12. Services page description 13. Services page title 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 Services" - 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 this template and replace every YOUR_* placeholder with your own data. Add or remove services from the hasOfferCatalog array to match your actual offerings.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/services/#webpage",
"name": "YOUR_SERVICES_PAGE_TITLE",
"description": "YOUR_SERVICES_PAGE_DESCRIPTION",
"url": "https://YOUR_DOMAIN.com/services/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/services/#breadcrumb"
}
},
{
"@type": "RealEstateAgent",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_AGENCY_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"areaServed": [
{
"@type": "City",
"name": "YOUR_PRIMARY_CITY"
},
{
"@type": "State",
"name": "YOUR_PRIMARY_STATE"
}
],
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Real Estate Services",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Buyer Representation",
"description": "YOUR_BUYER_REPRESENTATION_DESCRIPTION"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Seller Representation",
"description": "YOUR_SELLER_REPRESENTATION_DESCRIPTION"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Property Management",
"description": "YOUR_PROPERTY_MANAGEMENT_DESCRIPTION"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Relocation Services",
"description": "YOUR_RELOCATION_SERVICES_DESCRIPTION"
}
}
]
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/services/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Services",
"item": "https://YOUR_DOMAIN.com/services/"
}
]
},
{
"@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"
}
}
]
}
]
}
Include every distinct real estate service you offer. There is no upper limit, but each entry should be a genuinely separate offering — not variations of the same thing. If you provide buyer representation, seller representation, property management, and relocation assistance, list all four. AI uses this catalog to match you to specific queries, so completeness matters.
Use @id references to connect nodes without duplicating data. The RealEstateAgent node here should share the same @id as on your homepage so AI treats them as the same entity. You only need to include the fields relevant to this page — primarily hasOfferCatalog, areaServed, and telephone.
Yes, and it is a good strategy. You can have individual pages for buyer representation, seller representation, and so on, each with their own detailed JSON-LD. The services overview page should still list all offerings in one hasOfferCatalog so AI has a single index of everything you do. Individual pages can then go deeper on each service.