Update from support feedback: custom domain topology and subpath verification

[mintlify]

Summary

Two support threads needed human help because the docs don't state that a custom domain connects to exactly one deployment, or that the verification TXT records shown in the dashboard stay unverified (harmlessly) when a customer's own reverse proxy serves the docs subpath. This adds two help center articles covering those questions, short cross-linking notes on the custom domain and subpath pages, and mirrored translations.

Changes

• New help center article: "Can I host multiple docs sites on the same domain?" covering one-deployment-per-domain, path-based navigation vs. separate subdomains, and consolidation/redirect guidance.
• New help center article: "_cf-custom-hostname TXT record stuck unverified" explaining why the records never verify in proxied-subpath setups and that this is safe to ignore.
• Notes on customize/custom-domain and deploy/docs-subpath linking to both articles; corrected the claim that the dashboard hides DNS records for subpath setups.
• Mirrored all changes into French, Spanish, and Chinese (translated articles, page edits, and es.json/fr.json/zh.json navigation entries).
• Shortened both new articles' descriptions to meet the 160-character SEO limit.

Support context

• Host different Mintlify sites on the same domain (multi-product setup)
• Custom domain _cf-custom-hostname TXT record stuck unverified on proxied subpath setup

---

Note

Low Risk
Documentation-only changes with no application code, auth, or deployment logic affected.

Overview
Adds documentation driven by support gaps around one custom domain per deployment and harmless unverified dashboard TXT records when docs are served at a subpath via a customer reverse proxy.

Two new Help Center articles (English plus es, fr, zh): one explains that a domain maps to a single deployment and outlines path-based consolidation vs. per-product subdomains (including multi-repo and consolidation steps); the other explains why _cf-custom-hostname / _acme-challenge TXT records never verify when traffic does not route through Mintlify’s CNAME, and that skipping dashboard DNS in favor of the proxy is correct.

customize/custom-domain and deploy/docs-subpath gain cross-links and clearer subpath guidance: use provider reverse-proxy guides instead of the Mintlify CNAME, and expect verification TXT to remain unverified. The prior implication that the dashboard swaps DNS for proxy guides is corrected. Help Center nav entries are added in docs.json and locale JSON files.

^{Reviewed by Cursor Bugbot for commit 2bbe14c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
mintlify	🟢 Ready	View Preview	Sep 4, 2026, 4:28 PM

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
tomee	🟡 Building	–	Sep 4, 2026, 4:26 PM

💡 Tip: Enable Automations to automatically generate PRs for you.