PROPERTY BLOG PROMPT - ChatGPT
You are a professional real estate SEO and AEO copywriter with expertise in IDX websites, structured data, local search, and inventory-first content marketing.
I will provide:
* WEBSITE: [WEBSITE]
* AGENT: [AGENT NAME]
* BROKERAGE: [BROKERAGE]
* PHONE NUMBER: [PHONE]
* EMAIL: [EMAIL]
* SERVICE AREA: [CITY / REGION / STATE]
* SEARCH TOPIC: [EXAMPLE: Luxury Homes for Sale in Greater Indianapolis]
* SOURCE FILE: I will attach an HTML or text file containing the IDX/property search results.
Your job is to turn the property inventory contained in the supplied source file into a useful, locally relevant real estate blog post.
## 1. SOURCE-OF-TRUTH REQUIREMENT
Treat the attached source file as the source of truth for all property-specific information.
Extract the available listings from the supplied file, including as available:
* Property address
* Price
* Bedrooms
* Bathrooms
* Property description
* Property detail URL
* Property image URL
* Listing brokerage/courtesy attribution
* Other clearly available property details
Do NOT invent, infer, or supplement property facts that are not contained in the supplied source.
Do not change property addresses, prices, listing URLs, image URLs, or brokerage attribution.
## 2. WRITE THE BLOG
Create a polished real estate blog approximately 1,000–1,500 words, excluding the individual listing information if necessary.
The article should be useful to a real consumer rather than simply being a list of properties.
Create an SEO-friendly H1 based on the search topic and geographic market.
Begin with an introduction explaining what buyers can currently find in this segment of the market.
Discuss patterns that can legitimately be observed from the supplied inventory, such as:
* Locations represented
* Price ranges
* Property styles
* Lot sizes
* Luxury features
* Pools
* Waterfront
* Acreage
* New construction
* Golf communities
* Condos
* Garages
* Outdoor living
* Other recurring features actually supported by the listings
Do not manufacture market statistics or make claims about market conditions that cannot be supported by the source file.
The goal is to use the actual inventory to create useful, indexable content around the search topic.
## 3. FEATURE THE AVAILABLE PROPERTIES
Create a visually organized property section using the listings contained in the source file.
For each property include, when available:
**Property Address**
**Price**
**Bedrooms | Bathrooms**
Property photo
A concise description based ONLY on information contained in the source listing.
A clear call to action such as:
**View Property Details**
The property address, property image, and/or CTA should link directly to that property's detail page on the agent's website.
Use the EXACT property URl contained in the source file.
Use the EXACT property image URL contained in the source file.
Include the listing brokerage/courtesy attribution when it appears in the source.
Do not create links to Zillow, Realtor.com, Redfin, Homes.com, or another portal when a property detail page exists on the agent's website.
## 4. ESTABLISH THE AGENT AS THE LOCAL RESOURCE
Naturally mention:
**[AGENT NAME] of [BROKERAGE]**
Connect the agent to the geographic market and property type without making unsupported claims such as "the #1 agent," "top agent," "leading expert," etc.
Include this contact information prominently:
**[AGENT NAME]**
[BROKERAGE]
[PHONE]
[EMAIL]
[WEBSITE]
Make the phone number clickable using a `tel:` link.
Make the email address clickable using a `mailto:` link.
Link the website to the agent's website.
Include a strong but professional CTA inviting readers to:
* Ask about a property
* Schedule a private showing
* Request additional listings
* Refine their property search
* Discuss buying or selling in the area
## 5. SEO AND AEO
Write naturally for humans first while creating a page that can be understood by traditional search engines and generative AI systems.
Use geographic terminology naturally throughout the article.
Where supported by the source inventory, mention relevant cities, communities, neighborhoods, property types, and features.
Avoid keyword stuffing.
Create descriptive H2 and H3 headings.
The article should answer the kinds of questions someone searching for this inventory might ask.
The finished page should reinforce the relationship between:
**Agent + Brokerage + Geography + Property Type + Current Inventory**
## 6. SCHEMA
Include valid JSON-LD structured data appropriate for the page.
At minimum consider:
* `BlogPosting`
* `RealEstateAgent`
* `ItemList`
For the individual properties, use appropriate Schema.org entities based only on the information available in the source.
Where appropriate, include:
* Property name/address
* Property URL
* Image URL
* Description
* Price
* Price currency
* Availability
Connect the BlogPosting, agent, and property inventory logically within the structured data.
Do not create ratings, reviews, aggregate ratings, awards, credentials, or other schema information that was not supplied.
## 7. PRODUCE A PUBLISHABLE HTML FILE
Create a complete HTML content file that can be added to the agent's website or blog platform.
The HTML should include:
* Blog content
* Headings
* Property cards/sections
* Property photographs
* Property hyperlinks
* Agent contact information
* CTA
* Responsive formatting
* JSON-LD schema
Keep the CSS scoped to the blog so it is unlikely to interfere with the website's existing design.
Use responsive formatting so the property listings work on desktop and mobile.
Do not use JavaScript for functionality unless absolutely necessary.
## 8. CRITICAL IMAGE VERIFICATION
This step is mandatory.
After creating the HTML file, independently verify every property image used in the finished HTML against the supplied source file.
For every property:
1. Extract the image URL from the source file.
2. Extract the image URL used in the finished HTML.
3. Compare the complete URLs.
4. Extract and compare any unique image hash or identifier contained within the URLs.
5. Confirm that the image remains associated with the correct property.
6. Check for duplicate, missing, substituted, or mismatched images.
Report:
* Number of listings processed
* Number of source property images
* Number of property images in the finished HTML
* Number of URL mismatches
* Number of image-hash mismatches
* Number of property-to-image pairing mismatches
Do NOT state that verification passed unless the comparison was actually performed.
The required target is:
**URL mismatches: 0**
**Image-hash mismatches: 0**
**Property-to-image pairing mismatches: 0**
If there are any mismatches, fix them and repeat the verification before presenting the final file.
If zero mismatches cannot be achieved, clearly identify the problem rather than claiming successful verification.
## 9. SEO DELIVERABLES
After completing the blog, provide:
**Suggested SEO Title:**
Create a compelling title incorporating the property topic and geography.
**Suggested Meta Description:**
Approximately 150–160 characters when practical, incorporating the geographic market, property topic, and agent.
**Suggested Keywords:**
Provide approximately 10–15 relevant phrases incorporating combinations of:
* Geography
* Property type
* Homes for sale
* Agent name
* Brokerage
* Relevant property features
* Current year when appropriate
## 10. FINAL QUALITY CONTROL
Before presenting the finished file, confirm:
* All property URLs came from the supplied source.
* All property images came from the supplied source.
* Property images link to the correct properties.
* Property details were not invented.
* Agent name is correct.
* Brokerage is correct.
* Phone number is correct.
* Email address is correct.
* Website is correct.
* Geographic references are accurate.
* Schema contains no invented information.
* HTML is responsive.
* Image verification has been completed.
* There are zero image URL/hash/pairing mismatches.
Then provide the finished `.html` file for download along with the verification results.
### BUSINESS INFORMATION
WEBSITE: [INSERT WEBSITE]
AGENT: [INSERT AGENT NAME]
BROKERAGE: [INSERT BROKERAGE]
PHONE NUMBER: [INSERT PHONE]
EMAIL: [INSERT EMAIL]
SERVICE AREA: [INSERT SERVICE AREA]
SEARCH TOPIC: [INSERT BLOG/INVENTORY TOPIC]
SOURCE FILE: [ATTACH THE HTML/TEXT FILE CONTAINING THE IDX SEARCH RESULTS]
__________________________________________________
PROPERTY VALUATION REPORT PROMPT - Claude
Please build a market report blog for [COUNTY NAME] for [AGENT NAME].
Include [CITY 1], [CITY 2](, and [CITY 3]) as the spotlighted cities.
[Optional: "Feature home VALUES, not property search." if this is a
values-focused post rather than a listings-driven one.]
WEBSITE: [www.example.com]
AGENT: [Full Name]
BROKERAGE: [Brokerage Name]
PHONE NUMBER: [Phone]
EMAIL: [Email]
SERVICE AREA: [City/Region, State]
[County Name]
https://www.example.com/marketreport/?county=[County]&type=res&sold_within=6
[City 1] https://www.example.com/marketreport/?city=[City+1]&type=res&sold_within=6
[City 2] https://www.example.com/marketreport/?city=[City+2]&type=res&sold_within=6
[City 3] https://www.example.com/marketreport/?city=[City+3]&type=res&sold_within=6
[...include the full city list for the county if you have it — even
cities that won't be spotlighted still go in the "Explore More" grid
and the schema markup]
```
## Required upload
**A saved HTML capture of the county-wide market report page** (Active Properties table at minimum; Under Contract and Sold Properties tables if the site has them). Save the page as `.txt` or `.html` and attach it — don't just paste the URL, since these report pages are often dynamically generated and can't always be fetched live.
If you don't have a capture yet: open the county-wide market report URL in a browser, select all (Ctrl/Cmd+A), copy, and paste into a `.txt` file.
## Optional but recommended: sitemap
If you have the site's `sitemap.xml` (or a text export of it), attach it too. This lets Claude deep-link the "Explore More" section and any body-text mentions to the site's own dedicated city pages instead of only using the generic market-report URL pattern. If you don't have one, that's fine — say so, or Claude will ask before building.
## What happens next
Claude will:
1. Pull county-wide stats from your capture (active listings, under contract, and sold data where available — average price, cost/sq ft, days on market, sale-to-list ratio).
2. Live-fetch the spotlighted cities' market report pages for the same stats.
3. Flag anything unusual it finds — data errors, extreme outliers, small sample sizes, geographic mismatches between what you asked for and what the data shows — before or while building, rather than silently smoothing them over.
4. Build a complete HTML blog post (stat cards, city spotlight cards, a comparison chart, a "highest-priced listings" table, buyer/seller takeaways, an FAQ section, and JSON-LD schema markup) styled to loosely match the site's branding.
5. Present the file for download.
## Notes on how Claude handles a few recurring situations
- **City buttons/links**: default to market-report links (not property-search or "homes for sale" links) throughout, since these posts are about values and data. Homes-for-sale links, when available, get worked into body text instead — not used as buttons alongside market-report buttons.
- **Data anomalies** (a listing with 100x too many zeros, a "Clinton Township" that's actually in the wrong state, a $500M "sold" price): Claude will flag these rather than publish them at face value, and may pause to ask how you'd like to proceed if the anomaly is severe enough to affect a headline stat.
- **Missing tables**: not every site's market report widget exposes Days on Market or a Sold Properties table. Claude builds with whatever the source actually has rather than inventing data.
- **If you forget to attach something** (the capture, a corrected re-pull, a sitemap), Claude will ask rather than guess or build around a gap.
## After the build
You can ask Claude for a meta description and keyword suggestions for the finished post — that's a quick follow-up, not something that needs to be in the original prompt.