Skip to content

Well-Known Route Setup

Well-known routes are defined by RFC 8615. They are commonly used for domain verification and other standardized discovery endpoints.

The URL structure is:

<http|https>://<domain>/.well-known/<resource>

Common Examples

  • https://example.com/.well-known/apple-developer-merchantid-domain-association

Setup in Experience Builder

  1. Check out the latest copy of your website source code from Experience Builder.
  2. Create a directory named .well-known at the root of your project.
  3. Use this exact casing: .well-known (all lowercase).
  4. Place your provider file into this folder. The filename should match the exact instructions from the provider.
  5. Add the extension .wellknown to the end of the file name.
  6. Commit and push this change to your Experience Builder website Git repository.

Content and Response Headers

  • The well-known file content must be plain text.
  • The response should return Content-Type: text/plain.
  • The response should return Cache-Control: no-cache.

Example Project Structure

your-website-root/
  .well-known/
    apple-developer-merchantid-domain-association.wellknown

Verification Tips

  • Confirm the file path is reachable from your domain using the exact .well-known route.
  • Confirm the file name and content match the provider requirements exactly.
  • If verification fails, re-check folder casing and file naming first.