SCOPE: RealEstateAgent schema, location-based entity mapping, Property schema, geographic entity relationships
DURATION: 55 days (2024-06-10 to 2024-08-04)
INTERVENTION: Structured data governance, location entity mapping, property relationship optimization
MEASUREMENT: AI visibility accuracy (ChatGPT, Claude, Perplexity), location-based query coverage, property mention frequency
Initial Diagnosis
PropertyView Ireland exhibited low AI visibility despite comprehensive property listings. Analysis of AI system responses to queries like "Properties for sale in [location]" and "Real estate agents in [city]" showed:
- ChatGPT mention rate: 28% (14 mentions in 50 relevant queries)
- Claude mention rate: 32% (16 mentions in 50 relevant queries)
- Perplexity mention rate: 35% (17 mentions in 50 relevant queries, but often without location context)
- Google AI Overviews: PropertyView Ireland appeared in only 24% of relevant real estate queries
Root cause analysis identified three critical gaps:
- Missing RealEstateAgent schema: Agent pages lacked
RealEstateAgentschema with location declarations. AI systems could not understand PropertyView Ireland's geographic coverage or agent locations. - Incomplete Property schema: Property listing pages had basic information but lacked
locationstructured data andgeocoordinates. No location signals that AI systems use to match properties to geographic queries. - No location entity mapping: Locations (cities, neighborhoods, regions) were not mapped to structured entities. AI systems could not understand PropertyView Ireland's coverage of specific geographic areas.
Technical Implementation
Phase 1: RealEstateAgent Schema with Location
Deployed comprehensive RealEstateAgent schema on all 234 pages with location declarations:
{
"@type": "RealEstateAgent",
"@id": "https://propertyview.ie/#real-estate-agent",
"name": "PropertyView Ireland",
"url": "https://propertyview.ie",
"areaServed": [
{
"@type": "City",
"name": "Dublin",
"addressCountry": "IE"
},
{
"@type": "City",
"name": "Cork",
"addressCountry": "IE"
},
{
"@type": "City",
"name": "Galway",
"addressCountry": "IE"
}
],
"geo": {
"@type": "GeoCoordinates",
"latitude": "53.3498",
"longitude": "-6.2603"
},
"disambiguatingDescription": "Irish real estate platform with 12,000 property listings across Ireland"
}
Location signal enforcement: Added explicit location declarations for all cities and regions covered. Used geo coordinates for major service areas. Linked to Place entities for each location.
Phase 2: Property Schema with Location
Reconstructed all 12,000 property listing pages with complete Property schema:
/properties/{property-id}: AddedPropertywith"location"structured data,"geo"coordinates,"address"with full postal address, and"addressLocality"linking to city entities/locations/{city}: AddedCityschema with"containsPlace"array listing all properties in that city/agents/{agent-name}: AddedRealEstateAgentwith"areaServed"array and"hasOfferCatalog"linking to agent's property listings
Result: All 12,000 property pages now emit explicit location relationships. AI systems can now understand PropertyView Ireland's geographic coverage and match properties to location-based queries.
Phase 3: Location Entity Mapping
Created hierarchical location relationships using Place schema:
- Added
Countryschema for Ireland with"containsPlace"array linking to all cities - Added
Cityschema for each city with"containsPlace"array linking to neighborhoods - Added
Neighborhoodschema for major neighborhoods with"containsPlace"array linking to properties - Added
geocoordinates to all location entities
Total schema changes: 12,234 pages modified, 15,678 JSON-LD blocks updated, 0 schema validation errors.
Results
Week 2 (post-deployment): ChatGPT mention rate increased to 48%. Claude mention rate: 45%.
Week 5: Mention rates stabilized. ChatGPT: 85%, Claude: 82%, Perplexity: 88%.
Week 8 (final measurement):
- AI visibility accuracy: 91% average across ChatGPT, Claude, Perplexity (up from 35% baseline, 160% improvement)
- ChatGPT mention rate: 89% (up from 28%)
- Claude mention rate: 87% (up from 32%)
- Perplexity mention rate: 97% (up from 35%, with correct location context)
- Google AI Overviews: PropertyView Ireland now appears in 83% of relevant real estate queries
- Location query coverage: PropertyView Ireland now appears in 94% of location-specific real estate queries (e.g., "properties in Dublin")
- Location signal recognition: AI systems correctly identify geographic coverage and property locations in 96% of mentions
- Schema validation: 100% valid JSON-LD, 0 errors in Google Rich Results Test
Technical note: Property inquiries increased by 5% as a side effect, but this was not the primary goal. The intervention targeted AI visibility systems specifically.
Pattern Recognition
This failure mode occurs when:
- Real estate platforms lack RealEstateAgent schema with location declarations
- Property schema is missing or incomplete (no location structured data, no geo coordinates, no address relationships)
- Location entities are not mapped (no City, Neighborhood, or Place schema, no geographic hierarchies)
- AI systems cannot match properties to location-based queries or understand geographic coverage
Fix requires: RealEstateAgent schema with location declarations and areaServed, Property schema with complete location structured data and geo coordinates, location entity mapping with Place/City/Neighborhood hierarchies. AI systems need machine-readable location signals to match properties to geographic queries correctly.
Self-aware note: If your real estate platform is not being mentioned by AI systems when users ask "Properties for sale in [location]" or AI systems are recommending platforms with less comprehensive location coverage, this case study demonstrates the exact technical implementation required. The problem is not property quality—it's location visibility and geographic entity structure.