For Sales

The one-line pitch

If it comes up in a security or IT-diligence conversation: "Dentolize's clinic dashboard is explicitly excluded from search engine indexing — staff-only pages can't be found via Google."

When this is relevant

This will almost never be a deal-driving feature on its own, but it can come up during security questionnaires or IT reviews for larger clinic groups, especially anyone comparing SaaS vendors on a checklist that includes "is your admin/staff interface excluded from search indexing." Now you can answer yes, with specifics if asked:

• Every route of the staff dashboard sends noindex, nofollow, noarchive —

the standard, universally-recognized way to opt out of search indexing.

• robots.txt explicitly governs crawler access, including blocking direct

crawling of exported documents (invoices, spreadsheets, photos).

Objection handling

"Was our data ever exposed via Google search?" — No. This has never been about protecting patient or clinic data — that's behind login and access control regardless of this change. It's about whether the existence of a dashboard page (its URL and title) could appear in search results. That's now explicitly disallowed.

"Why wasn't this done from day one?" — Reasonable question, no need to get defensive: robots.txt previously had no explicit rule either way, which most crawlers treat as "everything's fair game" rather than blocking anything by default. This PR makes the policy explicit rather than implicit.

Competitive angle

Not a differentiator to lead with — most competent SaaS vendors do this as a matter of course. Framing it as "we do the basics right" is accurate; framing it as a headline security feature is not.