A medical site with thirty pages and no sitemap is like a practice where half of the rooms are not shown on any map. Crawlers come, index what they find, and ignore the rest. The problem is not visible in the practitioner’s browser, but in the Search Console, where specialty or appointment pages remain absent from the results for weeks.
Tags ignored by Google: what the XML sitemap no longer does in 2026
We often start by setting up a sitemap with all the available options in the plugin, thinking that every tag matters. In reality, Google completely ignores the priority and changefreq tags. Filling them out does not trigger an error, but it has no effect on crawling or ranking.
The old unauthenticated ping endpoint, which some guides still recommended recently, now returns a 404 error. Google no longer processes it. The only two recognized mechanisms for signaling a sitemap are declaration in the robots.txt file and submission via the Search Console.
Specifically, on a medical site that publishes little new content each month, the tag that retains real utility is lastmod. It indicates the last modification date of a page. When a practitioner updates their fees or consultation hours, a correctly updated lastmod tag helps Google revisit that page more quickly. Without it, the engine decides on its own the frequency of recrawling, often with several weeks of delay.
To see how an XML sitemap concretely structures the URLs of a site specialized in health equipment, one can consult the sitemap of the MS Medical site, which groups different product categories and information pages into a readable index.
Structuring the sitemap of a multi-practitioner medical site
A practice that includes several specialists poses a hierarchy problem. Each practitioner has their profile, their procedures, sometimes their own appointment page. Without organization of the sitemap, these pages all end up at the same level, without hierarchy.
The best practice is to segment the URLs by content type using sub-sitemaps (sitemap index). For example, we separate:
- A sitemap for practitioner profiles, with their specialty and location in the meta tags
- A sitemap for medical procedure or treated pathology pages, which form the informative content of the site
- A sitemap for institutional pages (legal notices, privacy policy, contact), which have a low update frequency
- A sitemap dedicated to health blog articles, if the practice publishes editorial content
This segmentation does not directly improve ranking, but it facilitates diagnosis. When a group of pages is not indexed, we can immediately identify which sub-sitemap the problem lies in. On a site with five pages, this is superfluous. Once we exceed twenty active URLs, the sitemap index becomes a tool for managing crawling.
Sitemap and GDPR compliance on a health site
One point that most SEO guides do not address: the pages that should not be included in the sitemap. On a medical site, some URLs contain patient data forms, connected spaces, or exam result portals. These pages have no place in a publicly accessible file.
Any URL listed in a sitemap is by definition discoverable by search engines. If an appointment page displays a pre-filled name, or if a patient space uses URLs with identifiers as parameters, their presence in the sitemap exposes sensitive access paths.
The verification is simple: open the sitemap, go through each URL, and check that none points to protected content or a page that should not appear in search results. Pages to exclude must be blocked in the robots.txt and carry a noindex meta tag, in addition to being absent from the sitemap.
Update frequency and lastmod for reliable medical content
Google evaluates the reliability of health content with particular rigor, related to YMYL (Your Money or Your Life) criteria. An article on the side effects of a medication published three years ago without an update sends a negative signal to both users and algorithms.
The sitemap plays a role in this mechanism through the lastmod tag. When updating medical content to incorporate new recommendations or correct a dosage, the lastmod tag must reflect the actual modification date. Some CMS automatically update this date with every page save, even for a comma correction. This behavior dilutes the signal.
The cleanest configuration is to update lastmod only during substantial content changes. On WordPress, several SEO plugins allow you to choose between automatic or manual updates of this date. Feedback varies on this point depending on configurations, but the rule remains the same: lastmod must not misrepresent the actual freshness of the content.
Common errors in medical site sitemaps
After auditing the structure of several practice and clinic sites, certain patterns consistently emerge:
- Duplicate URLs with and without a trailing slash (/dermatologie and /dermatologie/), which generates duplicate content in the index
- Draft or staging pages forgotten in the sitemap, sometimes indexed by Google even before their official publication
- Sitemaps that exceed the limit of 50,000 URLs without going through a sitemap index, causing reading errors
- The absence of a sitemap in the robots.txt, which forces manual submission in the Search Console without a safety net
Each of these errors can be corrected in a few minutes, but none can be detected without opening the sitemap file and comparing it to the list of actually active pages on the site.
A well-maintained sitemap does not replace internal linking or content quality. It remains a technical file, a map that engines consult to know where to search. On a medical site, where trust and information freshness matter more than elsewhere, it is the first file to check before touching the rest of the SEO.