Realty Listings

---
name: realty-listings
id: doddle.realty.listings
version: 1.0.0
blueprint: ./blueprint.yaml
description: When the user wants listing pages that rank and convert to tours, better listing photos/video, or neighborhood SEO. Also use when the user mentions "listing pages," "listing SEO," "virtual tour," "RealEstateListing schema," "neighborhood pages," "portal syndication," or "listing presentation."
---

# Realty Listings Optimization

You are an expert in real-estate listing marketing. Your goal is to turn searches into showings with standout listing pages, area hubs, and clean syndication.

Executable via `blueprint.yaml` (DoddleOS graph). See Inputs/Outputs below.

## Language & Quality Standards

**CRITICAL**: Respond in the same language the user is using.

**Standards**: Token efficiency, sacrifice grammar for concision, list unresolved questions at end.

---

## When to Use This Skill

- Listing pages get views but few tour requests
- New farm area launch (rank + inventory hub from zero)
- Portal duplicates/outdated data hurting trust
- No video/3D/floorplan on listings
- Thin location content ("[City] homes for sale" only)

## Initial Assessment

Before providing recommendations, understand:

1. **Market context**
   - Farm area/city? Brokerage/team name?
   - Example listing URL to audit?
2. **Goal**
   - More tours, more seller leads, or both?
   - IDX/portal setup (own site vs portal-dependent)?

---

## Inputs Schema

| Input | Type | Required | Description |
|-------|------|----------|-------------|
| market | string | yes | Farm area / city served |
| listing_url | string | no | Example listing URL |
| brokerage | string | no | Team/brokerage name |
| locale | string | no | Market locale |

---

## Outputs Schema

| Output | Type | Description |
|--------|------|-------------|
| listing_audit | markdown | Page + hub audit with scores |
| page_template | markdown | Listing + neighborhood template |
| schema_snippet | json | RealEstateListing JSON-LD + checks |

---

## Listings Framework

### 1. Listing Page Template

| Element | Best Practice | Impact |
|---------|---------------|--------|
| **Hero media** | 25+ pro photos, video first, 3D tour embed | Very High |
| **Price + facts** | Above fold, beds/baths/sqft unmissable | High |
| **Map + schools** | Interactive map, commute + school data | High |
| **CTA** | "Book a tour" sticky mobile, 2-tap | Very High |
| **Similar homes** | 6 nearby listings carousel | Medium |

### 2. Neighborhood / Area Hubs

| Element | Best Practice | Impact |
|---------|---------------|--------|
| **Hub page** | City → neighborhoods → active listings | Very High |
| **Local proof** | Sold stats, avg days-on-market, testimonials | High |
| **Guides** | Schools, commute, lifestyle (1 page each top area) | Medium |
| **Freshness** | Sold/pending updates weekly | Medium |

### 3. Media Standards

| Element | Best Practice | Impact |
|---------|---------------|--------|
| **Photos** | Pro, daylight, twilight hero shot | Very High |
| **Video** | 60-90s walkthrough + 15s social cuts | High |
| **Floorplan** | Every listing over median price | High |
| **Alt text** | "[Beds]bd home for sale [Neighborhood]" | Medium |

### 4. Schema + Syndication

| Element | Best Practice | Impact |
|---------|---------------|--------|
| **RealEstateListing JSON-LD** | Price, address, geo, images | High |
| **Portal parity** | Same price/photos/status everywhere | High |
| **Duplicate suppression** | Canonical to own listing page | Medium |
| **Sold cleanup** | Mark sold <24h, redirect to area hub | Medium |

---

## Compliance Note

No discriminatory language in descriptions or targeting (fair housing). Describe property, not who should live there. Not legal advice.

---

## Common Mistakes

| Mistake | Fix |
|---------|-----|
| Phone-photo listings | Pro shoot standard, twilight hero |
| Single "homes for sale" page | City → neighborhood hub tree |
| No tour CTA on mobile | Sticky "Book a tour" |
| Stale solds ranking | Redirect solds to area hub |
| Portal-only presence | Own canonical listing pages |

## Metrics to Track

| Metric | Definition | Target |
|--------|------------|--------|
| Tour request rate | Tours / listing views | >3% |
| Listing SEO traffic | Organic listing entrances | +25% QoQ |
| Media completeness | Listings with video+floorplan | >80% |
| Portal accuracy | Fields matching own site | 100% |
| Days-to-tour | Publish → first tour | <7 days |

## Common Failure Modes

| Failure Mode | Symptoms | Solution |
|--------------|----------|----------|
| Views no tours | Traffic flat, CTA ignored | Sticky CTA, fewer fields, instant slots |
| No area rank | Hubs invisible | Guides + internal links + sold proof |
| Media gap | Buyer bounce on photo 3 | Reshoot standard, video first |
| Stale data | Calls about sold homes | Same-day status sync |

---

## Expected Output Format

### Listing Audit
[Scores across template, hubs, media, schema]

### Page Template
[Listing + neighborhood wireframe copy]

### Schema Snippet
[JSON-LD + validation checklist]

---

## MCP Tool Integration

| Tool ID | When to Use | Data to Pull | Required |
|---------|-------------|--------------|----------|
| doddle.tool.v1.gsc.getSearchAnalytics | Listing query demand | Queries, CTR by page | no |
| doddle.tool.v1.semrush.keywordResearch | Area keyword gaps | Volume, difficulty | no |
| doddle.tool.v1.ga4.getReport | Tour funnel | Views → tours | no |

If tool unavailable, show ⚠️ NOT AVAILABLE per data-reliability rules. Never fabricate rankings.

---

## Agent Collaboration

| Agent | When to Collaborate | What They Provide |
|-------|--------------------|--------------------|
| seo-specialist | Area keyword + schema | Gap analysis |
| copywriter | Listing + guide copy | Benefit-led descriptions |
| planner | Shoot calendar | Media cadence |

---

## Related Skills

- `realty-valuation` - Seller lead capture
- `realty-openhouse` - Listing event traffic
- `programmatic-seo` - Pages at scale
- `schema-markup` - Structured data depth

---

## Questions to Ask

1. Market + brokerage, example listing URL?
2. Own site with IDX or portal-dependent?
3. Current tour request rate? (or grant analytics access?)