Put your page on your own domain

Outcome: your CoreLoop page served at your own web address, with your llms.txt, your agent card and your agent endpoints answering there too.

You need: a Pro plan or above, a domain you control, and access to its DNS settings — or the person who has it.

Step 1 — Decide which address

The decision worth five minutes, because it is the one people get wrong. Connecting an address means that address shows your CoreLoop page. Nothing on your existing website is changed, moved or deleted — CoreLoop controls only what that one address serves. But if the address you connect is the one currently serving your own site, your site is what stops appearing there.

So: to keep your website, connect a spare subdomain, pages.yourbusiness.com being the conventional shape. If your CoreLoop page is your web presence, connect the bare domain.

Step 2 — Connect it

Settings → Channels, in the CoreLoop page section. Type the address and confirm. Connect a bare domain and the www. form is claimed alongside it and permanently redirected to it, so visitors who still type www. arrive.

Step 3 — Add the records at your provider

The panel then shows exactly which DNS records to add — an A record or a CNAME, depending on the shape of your address. Copy the values from the panel rather than from any guide, this one included: they are fetched live and can change. Sometimes a verification record appears and the status reads One more step, meaning the address was claimed elsewhere before and ownership has to be proven. Add the TXT record shown; the check continues on its own.

Step 4 — Wait for Active

• Setting up — records not in place, or DNS still propagating. Minutes is typical; up to a day is normal, and not a fault.
• One more step — the verification record above.
• Active — serving.
• Needs attention — it worked and stopped. Check the records, press Check now.
• Paused — your plan no longer includes custom domains.

Checking is frequent at first, every few minutes for the first week, then daily. After a month in the same unfinished state it stops, with one email about it — not a dead end, since Check now restarts the whole clock. An already-active address keeps its own daily check indefinitely.

Step 5 — Know what the address serves

Your page at the root, in every language you have enabled, plus /llms.txt, /robots.txt, /sitemap.xml and /.well-known/agent-card.json at their conventional root locations. Your own MCP and A2A endpoints answer there too, which is what lets the in-page tools work without cross-origin requests. Everything else — other businesses, the dashboard, CoreLoop’s platform-level discovery card — redirects to coreloop.so: your domain is an alias for your page, not a second copy of CoreLoop. While it is setting up or broken, every path on it redirects rather than erroring.

Step 6 — Know what a downgrade does

Below Pro the domain is paused, not deleted: the address and its configuration are kept, and the host redirects to your page on coreloop.so, so there is no dead address and no SEO cliff. Upgrade again and it re-enters verification by itself, back to Active without you touching DNS. Disconnecting is the separate, deliberate act that actually releases the address.

Done when

Your address loads your page over HTTPS, yourdomain/llms.txt returns your profile’s llms.txt, and the panel reads Active.

Deeper detail: the custom domains doc, and the story version in Your page on your own domain.