Set up verification.
Ship trust signals.
You're adding domain verification and trust signals for a business. This page covers exactly what to do, step by step. No marketing, just implementation.
Mediary uses DNS-based domain verification — similar to Google Search Console — to confirm domain ownership, then evaluates 8 trust signals including SSL certificates, business registration, and contact information. The entire setup takes 15-30 minutes. Once verified, your client's trust profile is published as a JSON endpoint that AI agents can query without authentication. See how agents consume trust profiles, or learn what businesses gain from AI visibility.
Total setup: 15–30 minutes
DNS propagation usually takes 15 minutes but can take up to 48 hours. If you've verified a site with Google Search Console, this is the same process.
What you're setting up
You're adding a DNS TXT record (or HTTP file) to prove domain ownership, then optionally submitting evidence for trust signals that can't be checked automatically. The output is a machine-readable trust profile hosted at /entities/{id}/trust.json that AI agents can query.
Domain verification
Two methods available. DNS is recommended; HTTP is the fallback.
Recommended DNS TXT Record
Add a TXT record to your domain's DNS settings. This is the same mechanism used for SPF, DKIM, and Google Search Console verification.
# Add this TXT record to _mediary-verify.yourdomain.com
Host: _mediary-verify
Type: TXT
Value: mediary-verify=abc123def456
Propagation takes 5 minutes to 48 hours depending on your DNS provider. Most resolve within 15 minutes.
HTTP Well-Known File
If you can't modify DNS, upload a verification file to your web server instead.
# Create this file on your server
URL: https://yourdomain.com/.well-known/mediary-verify.txt
Contents: mediary-verify=abc123def456
File must be accessible over HTTPS. Checked immediately on submission.
The 8 trust signals
6 signals are checked automatically. 2 may require you to submit evidence.
| # | Signal | What we check | Pass criteria | Method |
|---|---|---|---|---|
| 01 | Website Reachable | HTTP response | 200 within 5s | Auto |
| 02 | HTTPS Valid | SSL/TLS certificate | Valid, non-expired, correct chain | Auto |
| 03 | Contact Methods | Email, phone, address on site | At least one found | Auto |
| 04 | Physical Address | Structured address on site | Structured address on contact/about page | Auto |
| 05 | Legal Business ID | Company number on site or evidence | Detected or submitted | Evidence |
| 06 | Content Recency | Last-modified / content change | Updated within 90 days | Auto |
| 07 | Domain Claimed | DNS TXT or HTTP file | Verification completed | Verify |
| 08 | No Red Flags | Blocklist / malware scan | Clean on Safe Browsing, PhishTank | Auto |
Your trust profile endpoint
Once verified, your entity gets a publicly queryable trust profile:
GET
https://api.mediary.co/api/v1/entities/{entity_id}/trust.json
You can also enable discovery via:
- • HTML link relation:
<link rel="trust-profile" href="..." /> - • Well-known:
/.well-known/mediary.json
Common issues
DNS record not detected
Propagation can take up to 48 hours. Check with dig TXT _mediary-verify.yourdomain.com. If it shows the record but Mediary doesn't detect it, try re-triggering verification from your dashboard.
HTTPS certificate fails
Ensure the certificate covers the exact domain (not just www). Check for expired certs, incorrect chains, or mixed content. Tools like SSL Labs can help diagnose.
Contact method not detected
Ensure at least one email address, phone number, or structured address is in the HTML text (not just an image or iframe). Schema.org markup helps detection.
Testing your setup
After verification, check that your trust profile is complete:
- All 6 auto-detected signals show as verified in your dashboard
- Domain claim status shows "verified"
- Trust profile endpoint returns valid JSON
- TRI score is above 60 (all auto signals passing)
Submit evidence for Legal Business ID (signal 05) to reach the highest possible score.
What your client gets
After you complete the integration, your client's business becomes AI-visible. Here's what that means in practice:
- A published trust profile that AI agents can query — like an SSL certificate for trust
- A TRI score from 0 to 100, updated automatically as signals are re-verified
- Eligibility for AI-powered recommendations in ChatGPT, Perplexity, and other tools
- Zero ongoing maintenance — the profile updates automatically
Will this break my site?
No. Mediary uses a DNS TXT record for verification — it does not modify your website, inject scripts, or require any code changes. The TXT record sits alongside your existing DNS configuration and has no effect on email, hosting, or site functionality.
Frequently Asked Questions
- How is this different from adding schema.org markup?
- Schema.org markup describes your content to search engines. Mediary independently verifies trust signals — domain ownership, business registration, SSL — and publishes a trust score. Schema.org is self-reported; Mediary is independently verified.
- What if DNS propagation takes a long time?
- Mediary retries verification automatically. Once the DNS TXT record propagates, verification completes without any additional action. Most domains propagate within 15 minutes; worst case is 48 hours.
- Can I integrate this for multiple client domains?
- Yes. Each domain is claimed and verified independently. The process is the same for each — add a DNS TXT record, wait for propagation, and the trust profile is published automatically.
Ready to verify?
Start the verification flow to claim the domain and publish the trust profile.