A real estate site that publishes several dozen listings per week, removes just as many, and updates prices daily generates a volume of URLs that search engines cannot guess on their own. Without a properly maintained sitemap file, some of these listings remain invisible for days, sometimes weeks. It is this gap between the reality of the catalog and what Google sees that poses a real operational problem.
Turnover of real estate listings and Google’s crawl
On a classic showcase site, pages change little. On a real estate portal, the turnover of listings changes the game: properties appear, disappear, or have their prices modified several times a day. Google does not revisit every URL constantly. It allocates a limited crawl budget to each site.
The XML sitemap is precisely used to guide this budget. By listing active URLs with an up-to-date lastmod field, we signal to the bots which pages deserve a new visit. A listing published in the morning can thus rise in search results the same day, instead of waiting for Googlebot to discover it by chance through internal linking.
Conversely, removing sold or expired listings from the sitemap prevents wasting bot visits on dead pages. This principle is concretely applied on the sitemap page of Up Immo, where only relevant URLs are exposed to search engines.
Real estate filter pages: what the sitemap should not contain
Real estate portals often offer advanced filters (price, area, number of rooms, neighborhood). Each combination of filters generates a distinct URL. The reflex would be to include all of them in the sitemap to increase coverage. This is a common technical mistake.
Empty or ultra-specific result pages dilute the perceived quality of the site. Google identifies them as thin content, meaning pages with no real added value. If the sitemap is full of them, the engine loses trust in the entire file and slows down the crawling of important pages.
The right approach is to filter what goes into the sitemap:
- Structuring category pages (listings by city, by neighborhood, by property type) deserve to be included, as they target real user queries.
- Pages resulting from overly specific filter combinations (3-room apartment between 47 and 52 m² under 800 m from the metro) should remain in noindex and out of the sitemap.
- Result pages that return zero listings have no reason to exist in Google’s eyes and waste crawl budget for nothing.
We clean the sitemap as we clean a showcase: only show what has value for the visitor.
Real estate site structure and the three-click rule
A sitemap does not replace a good site architecture, but it compensates for its weaknesses. On a portal with thousands of listings, some pages end up buried five or six levels deep. Google crawls pages located beyond three clicks from the homepage less effectively.
The sitemap acts as a shortcut. Even if a recent listing in a little-visited neighborhood is only linked by a deep breadcrumb trail, its presence in the sitemap ensures that Googlebot will find it without relying on internal linking.
Navigation depth and SEO visibility
For a real estate site, navigation depth directly impacts the visibility of listings in search results. Pages close to the root are crawled more frequently. The sitemap allows for artificially elevating priority listings in the robot’s queue, without altering the site’s structure.
In practice, we can segment the sitemap into several files (one per city or property type) via a sitemap index. This organization helps search engines process the catalog in logical blocks rather than as a flat list of several thousand URLs.
Check that Google is actually reading your real estate sitemap
Submitting a sitemap in Google Search Console is not enough. You need to regularly check that the file is being read and that the submitted URLs are indeed being crawled.
Search Console displays the number of URLs discovered via the sitemap and those actually indexed. A significant gap between submitted URLs and indexed URLs indicates a problem: 404 error pages, redirect loops, duplicate content, or pages blocked by robots.txt.
Feedback varies on this point depending on the size of the site, but a few regular checks can help detect anomalies:
- Compare the number of URLs in the sitemap with the number of URLs indexed in the coverage report.
- Check that the lastmod field accurately reflects the actual last modification date of each listing, not a fixed date or one generated automatically without content change.
- Ensure that listings removed from the catalog are also removed from the sitemap within a reasonable timeframe.
The trap of a fixed lastmod
Google recently reminded that the lastmod field is only considered if it corresponds to a real content change. Some real estate CMSs regenerate the sitemap with the current date on all URLs, even without changes. The engine eventually ignores this signal, negating the sitemap’s usefulness for speeding up the crawl of updated listings.
A well-maintained sitemap on a real estate site is not a file that is generated once and forgotten. It is a living tool, aligned with the actual rhythm of the catalog. When listings move quickly, the sitemap must keep pace, or risk leaving Google to work with an outdated map.