A sitemap is a file that lists the URLs of a website to facilitate exploration by search engines. On a real estate portal, where listings appear and disappear at the pace of transactions, this file plays a particular role: it allows for the quick signaling of new pages and the removal of those that no longer exist.
XML Sitemap and Real Estate Site: A Constant Renewal Constraint
A traditional showcase site publishes a few pages per month. A real estate portal, on the other hand, manages a continuous flow of listings being created and removed. This rapid turnover poses a concrete problem: removed listings must exit the sitemap as soon as they are no longer accessible. Keeping expired listing URLs in the file means sending search engines an inventory that no longer reflects the actual content of the site.
Google recommends including only canonical, accessible, and relevant URLs in the sitemap. For a real estate site, this means that a property sold or taken off the market must lead to the removal of its URL from the XML file, ideally in an automated manner.
This type of maintenance is precisely what distinguishes a static sitemap, manually updated, from a dynamically generated sitemap by the CMS or the back-office managing the listings. Most professional real estate platforms incorporate this automatic generation, but it remains useful to regularly check that the file does not contain obsolete URLs.
To see a concrete example of a sitemap structured by categories, you can access the Immobserver sitemap and see how the different content categories are organized.
Lastmod Tag on Listings: When the Modification Date Really Matters
The XML sitemap file allows for associating a lastmod tag with each URL, indicating the date of the last modification of the page. On a real estate site, this information takes on very concrete meaning.
A price change, the addition of new photos, or the modification of a property’s description constitutes substantial updates. In these cases, updating the lastmod date signals to search engines that a visit to this page is warranted.
However, Google specifies that this date is only taken into account if it consistently and verifiably corresponds to a real modification of the content. Automatically regenerating the date with each file reconstruction, without any actual change on the page, renders the information useless. Search engines eventually ignore the lastmod dates of a site that manipulates them without basis.
What Changes Justify an Update of Lastmod
- A modification of the price displayed on the listing, whether up or down
- The addition or replacement of photos of the property, which alters the visual content of the page
- A change in status visible to the user (for example, from “available” to “under offer”)
- The rewriting of the property’s description, with additional information about the area, environment, or renovations
Purely technical modifications (template change, plugin update) do not justify altering this date.
Real Estate Search Pages and Listing Sheets: Two Distinct Logics in the Sitemap
A real estate site is not limited to its listing sheets. It also offers search pages by location or criteria (apartments in Lyon, houses with gardens in Brittany). These editorial or semi-editorial pages have their own SEO value, as they respond to queries that users actually formulate.
Including these pages in the sitemap makes sense, provided they present sufficiently stable and useful content. An empty or nearly empty results page, generated for every possible combination of filters, adds no value for search engines or visitors.
Separating Flows in the Sitemap
The best practice is to use a sitemap index that groups several distinct files. One file for active listings, another for geographic search pages, a third for editorial content (guides, market news). This segmentation facilitates diagnostics: if there is a problem with the indexing of listings, the relevant file is immediately identifiable in the Search Console.
Google allows a site to declare multiple sitemaps, provided each complies with the sitemaps.org standard. A file can contain up to 50,000 URLs, which covers the needs of the vast majority of real estate portals.
HTML Sitemap for Visitors: An Underestimated Navigation Tool on Real Estate Portals
The XML sitemap is aimed at search engines. The HTML sitemap, on the other hand, is aimed at human visitors. On a real estate site, this sitemap page provides an overview of the available sections: types of properties, geographic areas covered, practical guides.
For a buyer who does not know exactly how to formulate their search, or who is discovering the site for the first time, this page acts as a summary. It reduces the number of clicks needed to reach a specific category, especially on portals that cover multiple regions or types of transactions (sale, rental, new, old).
The HTML sitemap also strengthens the internal linking of the site. Each link present on this page distributes weight to deeper sections, complementing the work of the XML file without replacing it.
Checking and Declaring Your Sitemap: Control Points
A sitemap is only useful if it is declared to search engines and free of errors. There are two declaration channels:
- Direct submission via Google Search Console, which also allows monitoring of reading errors and the indexing rate of submitted URLs
- Including the sitemap URL in the robots.txt file, placed at the root of the site, in the form Sitemap: https://example.com/sitemap.xml
- Regularly checking that the file does not return HTTP errors (404 or 500) and that its XML syntax remains valid after each automatic update
On an active real estate site, a monthly check in the Search Console is usually sufficient to spot anomalies before they affect indexing. The sitemap file does not guarantee that a page will be crawled or indexed, but its absence deprives the site of a clear signal sent to search engines about the structure and freshness of its content.
