A sitemap lists a website’s URLs for search engines, not visitors. On a real estate portal where hundreds of listings appear and disappear every week, that distinction changes everything. The challenge isn’t just submitting an XML file to Google: it’s knowing which pages are worth crawling, which are outdated, and how to turn this technical inventory into a reliable browsing experience.
XML and HTML sitemaps on a real estate website: two distinct purposes
| Criterion | XML sitemap | HTML sitemap |
|---|---|---|
| Primary audience | Search engine bots | Website visitors |
| Format | .xml file at the root of the website | Standard web page with clickable links |
| Typical content (real estate) | All URLs: listings, city pages, agencies, guides | Selection of useful pages: categories, areas, help pages |
| Handling sold listings | Remove or redirect the URL in the file | Remove the visible link for visitors |
| Updates | Automatic via CMS or script | Manual or semi-automatic |
| Direct SEO benefit | Facilitates crawling and indexing | Improves internal linking |
On a real estate website, the XML sitemap serves as a comprehensive directory. It lists every property listing, every city page, and every agency profile. The HTML sitemap, by contrast, should display only pages that are genuinely useful to someone looking for a property.
Confusing the two means exposing visitors to technical URLs (pagination pages, duplicate filters, expired listings) that offer them no value. This is a common pitfall on high-volume real estate portals.
For a real-world example, Immodeule’s sitemap organizes its URLs by category, making it easy to identify the site’s structure and the types of pages it publishes.

Organizing a real estate sitemap by content type
A real estate portal can split its sitemaps by page type, then bring them together in an index. This approach makes it easier to analyze errors and changes by section, especially when a category of listings generates invalid URLs.
In practice, a sitemap index might look like this:
- A dedicated sitemap for properties for sale, grouping active listings with their actual last-modified dates
- A sitemap for rental listings, separate from the previous one to isolate issues specific to each market
- A sitemap for city or neighborhood pages, which change less often but structure geographic internal linking
- A sitemap for editorial content (guides, advice, local market news)
Splitting sitemaps by content type makes it possible to quickly isolate a problematic section. If the coverage report in Google Search Console shows a spike in 404 errors, segmentation immediately reveals whether the issue comes from listings, geographic pages, or another section.
Outdated listings in the sitemap: the real problem for real estate websites
A property that has been sold or taken off the market doesn’t automatically disappear from search results. If its URL remains in the sitemap without being handled, Google may continue showing it to visitors, who then land on an empty page or an error message.
A URL in the sitemap isn’t guaranteed to be indexed, but it is an invitation to crawl. Leaving hundreds of outdated listings in the file is like asking bots to crawl pages with no value, at the expense of active listings.
Three options for handling a withdrawn listing
- Remove the URL from the sitemap and return a 410 status code (content permanently removed) to speed up deindexing
- Redirect the URL (301) to a relevant results page, such as a list of similar properties in the same area
- Keep the page with a clear status (“property sold”) and links to comparable listings, preserving the traffic the URL has already earned
The right choice depends on the number of listings and the site’s SEO strategy. Very high-volume portals often favor simply removing listings to keep the sitemap clean. Smaller sites may benefit from redirects to category pages.

How reliable is the lastmod tag? What Google actually checks
The lastmod tag indicates the date an URL was last modified in the XML sitemap. Google recommends using it only when it is accurate and verifiable. Changing this value every time the file is regenerated, without any actual change to the page content, undermines its reliability in the search engine’s eyes.
For a property listing, only a substantial change justifies updating lastmod: a price change, new availability, added photos, or updated structured data. Simply recalculating the page on the server doesn’t count.
Sites that update lastmod every time the sitemap is generated, sometimes several times a day, send a misleading signal. Google may eventually ignore this tag for the domain, which can hurt pages that have genuinely been updated.
Sitemaps and coverage diagnostics: finding pages that haven’t been crawled
A sitemap does more than list URLs. By comparing it with Google Search Console’s coverage reports and the URL Inspection tool, a real estate website operator can check whether its strategic pages are actually being crawled.
Comparing the sitemap with coverage reports reveals pages Google is ignoring. If listings included in the sitemap never show up as indexed, this may point to a content quality issue, insufficient internal linking, or conflicting robots directives.
The IndexNow protocol lets you notify compatible search engines (Bing, Yandex) about added, updated, or deleted URLs. It complements the sitemap for portals that frequently publish new listings. Google is not among the search engines participating in this protocol. IndexNow does not replace a sitemap and does not guarantee indexing.
A well-structured sitemap, split by content type and cleared of outdated listings, remains the technical foundation of a crawlable real estate website. The difference between a portal whose listings appear quickly on Google and one whose pages languish often comes down to how carefully this inventory is maintained.



