XML Sitemaps and Robots.txt for Dental Websites: A Guide

TL;DR: An XML sitemap tells search engines which pages on your dental website matter, and a robots.txt file tells crawlers where not to go. Google's own documentation says robots.txt is not a way to keep a page out of search results, so private pages need a noindex tag or a password instead. This guide walks a practice owner through checking both files in under an hour.

Is Google actually finding every page on your practice website? For a small, well-built site the answer is often yes. But new pages, service pages buried three clicks deep and old URLs left over from a redesign can all slip through. As of October 2026, two small text files influence how search engines move through your site: the XML sitemap and robots.txt. This guide explains both in plain language, using Google Search Central's own documentation as the reference.

What is an XML sitemap?

Google describes a sitemap as a file where you provide information about the pages, videos and other files on your site, which search engines read to crawl the site more efficiently. Think of it as a table of contents you hand to Google, listing the pages you want found.

A sitemap is a hint, not a command. Google states plainly that a sitemap helps search engines discover URLs, but it does not guarantee that every item in it will be crawled and indexed.

Does a dental practice website need a sitemap?

Many practice websites are small. Google says you may not need a sitemap if your site is "small," which it defines as about 500 pages or fewer, if the site is comprehensively linked internally, and if you don't have many media files or news pages you want in search results. Even so, Google adds that in most cases a site will benefit from having one.

Google also lists situations where a sitemap is more useful, including a site that is new and has few external links to it. That describes many newly opened or rebranded practices in the GTA. If you recently launched a site for a new location in Vaughan or Brampton, a sitemap helps Google find pages that nobody else links to yet.

Pro Tip: Before building anything, type your domain followed by /sitemap.xml into a browser. Google notes that if you use a content management system, it has likely already made a sitemap available. You may already have one.

How do you build a sitemap that Google can use?

If your website platform doesn't generate one, Google's build-a-sitemap guidance sets out the rules that matter most:

• Size limits: a single sitemap is limited to 50 MB uncompressed or 50,000 URLs. Few practice websites come close, but larger multi-location groups can use a sitemap index file that points to several sitemaps.
• Full URLs only: use fully qualified, absolute URLs, such as https://www.yourpractice.ca/services/implants, not relative paths.
• Canonical URLs only: if the same page loads at two addresses, list the one you prefer, so each page appears once under its canonical address.
• Location: Google recommends posting the sitemap at the site root, because a sitemap there can affect all files on the site.
• Encoding: the file must be UTF-8 encoded.

Which sitemap fields does Google ignore?

Many sitemap generators add <priority> and <changefreq> tags. Google says it ignores both. It does use <lastmod>, the last-modified date, but only when that date is consistently and verifiably accurate. If your plugin stamps today's date on every page each night, that signal is not accurate, so it is not helping.

How do you submit a sitemap to Google?

Two of the simplest ways Google lists are:

1. Search Console: submit the sitemap URL in the Sitemaps report. If you haven't set up Search Console yet, our guide to using Google Search Console for your dental practice covers verification.
2. robots.txt: add a line anywhere in your robots.txt file that points to the sitemap, for example Sitemap: https://www.yourpractice.ca/sitemap.xml.

What is robots.txt, and what is it not?

Google says robots.txt is used primarily to manage crawler traffic to your site. It is a plain text file of rules telling crawlers which paths they may or may not crawl.

Google is just as clear about what it is not: robots.txt "is not a mechanism for keeping a web page out of Google." A page that is disallowed in robots.txt can still be indexed if other sites link to it, and its URL can still appear in search results. Google also notes that robots.txt cannot enforce crawler behaviour; it is up to each crawler to obey the rules, and not all search engines support every rule.

What are the robots.txt rules every practice should know?

Google's guide to creating a robots.txt file sets out the basics:

• The file must be named robots.txt, and a site can have only one.
• It must sit at the root of the site host it applies to, for example https://www.yourpractice.ca/robots.txt.
• It applies only to the protocol, host and port where it is posted. A booking subdomain is a separate host, so the rules in your main file do not apply to it.
• It must be a UTF-8 encoded text file.
• Rules are built from user-agent, disallow, allow and sitemap lines, and the paths in those rules are case-sensitive.
• By default, a crawler may crawl any page or directory not blocked by a disallow rule.

A minimal file for most practice websites looks like this:

User-agent: *
Disallow:

Sitemap: https://www.yourpractice.ca/sitemap.xml

An empty Disallow: line blocks nothing. That is often exactly right for a small practice site where every public page should be crawlable.

Pro Tip: If your site is on a hosted platform such as Wix, Google notes you might not need to, or be able to, edit robots.txt directly. Check your platform's SEO settings before asking your developer for a custom file.

How do you keep private pages out of Google?

This is where practices most often go wrong. A thank-you page, a staff portal, an old promotion or a downloadable PDF sometimes shows up in search results, and the instinct is to add it to robots.txt. Based on Google's documentation, that is the wrong tool.

Google's guidance is to block indexing with noindex or to password-protect the page. A noindex rule can go in a <meta> tag on the page or in an HTTP response header called X-Robots-Tag; the header version works for non-HTML files such as PDFs and images. When Google sees noindex, it drops the page from search results regardless of whether other sites link to it.

There is one trap. For noindex to work, the page must not be blocked by robots.txt, because Google has to be able to crawl the page to see the tag. Blocking a page in robots.txt and adding noindex at the same time means Google may never see the noindex. Also expect a delay: Google notes it may take months for Googlebot to revisit some pages.

Anything containing patient information should never be publicly reachable in the first place. Neither robots.txt nor noindex is a privacy control. Intake forms, uploaded documents and patient portals belong behind proper authentication, and questions about privacy obligations should go to your privacy adviser.

A one-hour audit checklist for your practice website

1. Open /robots.txt on your domain. Confirm it exists, is short and does not disallow pages you want patients to find, such as service or location pages.
2. Open your sitemap. Confirm it lists full https:// URLs for your real pages, not test pages or old redirected addresses.
3. Confirm the robots.txt file has a Sitemap: line pointing to the sitemap.
4. In Search Console, submit the sitemap in the Sitemaps report and check the robots.txt report.
5. Search Google for pages that should not be public. If any appear, use noindex or a password, and make sure robots.txt is not blocking those pages.
6. Read every page you are asking Google to surface. Under the Royal College of Dental Surgeons of Ontario (RCDSO) Advertising Guidelines, you must personally control all printed and electronic material about your practice and avoid statements that are unclear, untrue or misleading. A forgotten page from years ago is still your advertising.

Practices in Toronto, Markham and across Ontario often have years of content layered on one site. A sitemap that lists only accurate, current pages helps search engines and supports your compliance housekeeping at the same time. For related technical guides, see our posts on schema markup and image SEO and alt text.

Sources

• Google Search Central, Learn about sitemaps
• Google Search Central, Build and submit a sitemap
• Google Search Central, Introduction to robots.txt
• Google Search Central, How to write and submit a robots.txt file
• Google Search Central, Block Search indexing with noindex
• RCDSO, Advertising Guidelines

Frequently Asked Questions

Q: Does a small dental website need an XML sitemap?

Not always, but it usually helps. Google says sites of about 500 pages or fewer that are well linked internally may not need one, yet adds that in most cases a site will benefit from having a sitemap, especially if it is new and has few external links.

Q: Will blocking a page in robots.txt remove it from Google?

No. Google states that robots.txt is not a mechanism for keeping a page out of Google, and a blocked URL can still appear in search results if other sites link to it. Use a noindex tag or password protection instead, and don't block that page in robots.txt.

Q: Does Google use the priority and changefreq tags in a sitemap?

No. Google says it ignores priority and changefreq values. It uses lastmod only when the date is consistently and verifiably accurate.

Have you checked your practice's robots.txt file lately? Share what you found, or the website question you want us to cover next, with the EBIKO Dental team at ebiko.ca.