Your own domain
Connecting a domain like yourbrand.com to your SeedWebs site — the DNS records to add, what each SSL status means, and why a domain might not come up.
Last updated 2026-11-05
Every site has a {slug}.seedwebs.app subdomain from creation, and keeps it when you connect your own domain. Point a domain you own, like yourbrand.com, at your site: visitors see your domain, and the SSL certificate (https) is issued and renewed for you — nothing to buy.
The page for this is not in the admin panel
Domains are connected from the Dashboard at seedwebs.com, not from a site’s own admin panel at /admin. There is no domain menu in the admin panel.
- Go to
https://seedwebs.com/dashboardand sign in as the account that owns the site. - Click the site’s row to open its page (
/dashboard/site?slug={slug}). - Under Web address, press Connect your own domain (or Manage domain once one is connected). The page that opens (
/dashboard/site/domain?slug={slug}) has a Your own domain card.
Who can connect one
Two conditions, both of which must hold. Nothing has to be switched on for your site first.
| Condition | Detail |
|---|---|
| Plan | A paid plan — Seed, Pro or Business. A site on the trial, or past it (expired_trial), cannot connect one |
| Who you are | The site owner, meaning the account that signed the site up. A super_admin, admin, editor or writer signed into /admin has no route to this page at all |
The site’s page shows the connect button on Seed, Pro and Business; a trial or expired site is told it needs a paid plan. A domain already connected always shows, on any plan, so you can see or remove it.
“Upgrade to use your own domain” means the plan is the blocker — see Plans and billing. “Your own domain is not available yet. Check back soon” means connecting is switched off platform-wide for now; a connected domain keeps working and still shows here.
One domain per site, and any given domain can be attached to only one site across the whole platform.
Connecting
- In the Your own domain card, type the domain —
yourbrand.com— and press Connect. - Add the TXT record the card shows (see Proving the domain is yours) at your DNS provider, then press Verify and connect.
- Once it is found, SeedWebs registers the domain with Cloudflare and shows a table of the DNS records to add.
- Go to your registrar or DNS provider and add every record in the table.
- Come back to this page and wait for the status to become Active.
Proving the domain is yours
Before anything is registered, add one TXT record SeedWebs issues to your site:
| Type | Name | Value |
|---|---|---|
| TXT | _seedwebs-verify | seedwebs-verify= and 32 letters and digits, as shown |
- The full name is
_seedwebs-verify.yourbrand.com; most DNS providers add the domain themselves, so enter_seedwebs-verify(the card says which). Forblog.yourbrand.comit is_seedwebs-verify.blog. The bare domain and itswwwshare one record. - It does not change where the domain points, so add it first. It works for one connect, for your site only: delete it once connected; connecting again later, from any site, asks for a new value.
- DNS can take minutes, sometimes an hour. If the record is not found yet, check it, wait and press Verify and connect again: those checks (up to 60 an hour) do not use up connect attempts. Come back later and the card shows the same record.
Why: a domain whose DNS still points at SeedWebs from an earlier site must not be connectable by just anyone; the record shows it is yours now. If you cannot add DNS records, ask the SeedWebs team (Contact the team).
The field accepts either form. Paste https://yourbrand.com/ and the https:// and the trailing / are stripped, and the rest lowercased.
Thai domains
A Thai domain such as ธัชภูมิ.com works — type it in Thai. DNS speaks only ASCII, so SeedWebs converts it to the standard xn-- form (xn--b3c1azae1fva7a.com) wherever it must (the certificate, the DNS records, the address your browser sends); the page keeps showing the Thai spelling.
Both forms mean the same domain, so it does not matter which one you paste, and nobody else can claim the other spelling of a domain you have already connected. .ไทย addresses work too, including ธุรกิจ.ไทย, ศึกษา.ไทย, รัฐบาล.ไทย, องค์กร.ไทย, เน็ต.ไทย and ทหาร.ไทย.
Two things to expect. Your registrar may show the domain in the xn-- form, or in Thai, or let you switch — all three are the same name. And a Thai name grows about three times longer once converted, so a name that looks short can still be too long for DNS; that is what domain_too_long below means.
A failed connect shows a red box under the field. The message is a short code; this table explains them.
| Code | Cause |
|---|---|
invalid_domain | The name is malformed. It needs at least one dot, a real ending like .com (not a number or an IP address), and no spaces, @, : or / |
domain_reserved | It is seedwebs.app / .com / .site or a subdomain of one |
domain_too_long | Too long for DNS once converted: the whole name has a 253-character limit and each part between dots has a 63-character limit, both measured after conversion. A Thai name roughly triples, so about 20 Thai characters is the practical ceiling for one part |
domain_taken | Another site on the platform already has this domain |
ownership_unverified | The ownership TXT record (shown on the card) is not in DNS yet. Add it, wait a few minutes, press Verify and connect |
ownership_check_unavailable | No DNS resolver answered just then. Try again in a minute |
rate_limited | Over 10 connect attempts, or 60 ownership checks, in an hour (per site). Wait out the hour |
upgrade_required | The current plan does not include it. Seed, Pro or Business is required |
feature_not_available | Connecting domains is switched off for the whole platform for now. Try again later, or ask the SeedWebs team (Contact the team) |
cf_rejected | Cloudflare refused to register this domain |
cf_unavailable | SeedWebs could not reach Cloudflare just then. Try again |
The DNS records to add
The table on the page tells you everything. Click a Name or Value cell to copy it — a green tick confirms.
Most rows carry a note underneath. Those notes are in English only.
The table appears while the status is Verifying… or Failed. Once the domain reads Active it disappears, because there is nothing left to do.
The value you point at is your site’s subdomain, not plain seedwebs.app. If your site is mystore.seedwebs.app, the value is mystore.seedwebs.app.
A root domain, like yourbrand.com
Two records:
| Type | Name | Value |
|---|---|---|
| CNAME | @ | {slug}.seedwebs.app |
| CNAME | www | {slug}.seedwebs.app |
@ means the bare domain (some DNS providers call it root or apex, or want the field left empty). The second row is what makes https://www.yourbrand.com/ work. It is not optional.
Some registrars do not allow a CNAME at the bare domain. On Route53 or DNSimple, use ALIAS or ANAME for the @ row instead. If your registrar offers neither, move your DNS to a provider that does.
A subdomain, like blog.yourbrand.com
One record, whose name is the part in front of the root domain:
| Type | Name | Value |
|---|---|---|
| CNAME | blog | {slug}.seedwebs.app |
A subdomain gets no automatic www twin.
SeedWebs knows about two-part Thai suffixes — .co.th, .ac.th, .go.th, .or.th, .in.th, .net.th, .mi.th, and their .ไทย equivalents ธุรกิจ.ไทย, ศึกษา.ไทย, รัฐบาล.ไทย, องค์กร.ไทย, เน็ต.ไทย, ทหาร.ไทย — so materdei.ac.th counts as a root domain and gets @ and www rows, not a row named materdei.
The TXT row for ownership
Cloudflare’s own, separate from _seedwebs-verify: Cloudflare sometimes asks for an extra TXT record to prove you own the domain. When it does, the table shows it, with a note that it can be removed once the status is Active. No TXT row in the table means none is needed.
Copy the TXT name exactly as shown. Some DNS providers append your domain name themselves; if pasting the full value ends up with the domain twice, remove the domain part from the name field.
If your DNS is already on Cloudflare
The page checks your domain’s nameservers. If they are Cloudflare’s, the intro changes to “Your domain is on Cloudflare. Add these records, set each one to DNS only (grey cloud), and we will verify automatically”, and each CNAME row is tagged Proxy status: DNS only.
This is not optional. Every CNAME row must be DNS only, not Proxied (orange cloud).
www and the bare domain travel together
Connecting a root domain registers the other side for you:
- enter
yourbrand.com→www.yourbrand.comis added - enter
www.yourbrand.com→yourbrand.comis added
Whichever you typed is the canonical one, and once SSL is active the other side 301-redirects to it. However a visitor types it, they end up on the same address.
Registering it with Cloudflare is not the same as creating the DNS record, though. Add only one row and the other side will not resolve — so add both rows from the table.
Statuses, and how long to wait
There are four status badges.
| Badge | Meaning |
|---|---|
| Verifying… | Cloudflare is still working. This covers three stages: pending verification, issuing the certificate, and deploying it to the edge |
| Active | The certificate is live and the domain works. You get a “Verified at …” line and an Open site → button |
| Failed | Verification did not pass, or the certificate is unusable. If Cloudflare gave reasons, they are itemised in a red box under the domain |
| Suspended | Rare: left by an older card subscription that ended. Opening this page reads Cloudflare again and shows its status instead. What happens when a paid plan ends is below |
There is no guaranteed timeline; it depends on Cloudflare and on how fast your DNS propagates. What SeedWebs does do:
- While Verifying…, the page re-checks every 10 seconds for up to 5 minutes.
- After those 5 minutes, press Check now or refresh the page to check again.
- You can close the page. A background job re-checks every unfinished domain every hour until it resolves, so there is no need to sit and watch. Domains that have gone to Failed are not re-checked automatically — press Retry yourself.
- Verifying… and Failed also put the site under Needs attention at
seedwebs.com/dashboard.
A badge reading “Could not reach Cloudflare — showing the last known status” means the connection to Cloudflare is temporarily down and what you are seeing is the last saved value, not the current one. Check again later. The DNS records table stays hidden until Cloudflare is reachable again.
Once the domain is active
- Visitors arriving at
{slug}.seedwebs.appare 301-redirected to your domain, keeping the path. - Every
.seedwebs.appsubdomain is noindex, so your site appears in Google under your own domain only — no duplicate content at two addresses. - The admin panel stays on the subdomain, but your domain points to it. Opening
https://yourbrand.com/admin/forwards you tohttps://{slug}.seedwebs.app/admin/, keeping the rest of the path, soyourbrand.com/adminis the only address you need to remember. You sign in on the subdomain because sign-in is tied to it. - Email your site sends does not switch to your domain as part of this. Verifying a sending domain is a separate matter.
When the domain will not come up
- Are both records there? A root domain needs the
@row and thewwwrow. Missing one breaks that side. - Is the value right? It must be your site’s
{slug}.seedwebs.app— not plainseedwebs.app, and not an IP address. - On Cloudflare, is it DNS only? The cloud must be grey.
- Any leftover records? If the domain used to point somewhere else via an A, AAAA or older CNAME record, delete those first. Two records on the same name give unpredictable results.
- Status says Failed — read the red box, fix what it says, then press Retry.
- Status says Active but the site returns error 522 or times out — that one is not your DNS. Ask the SeedWebs team (Contact the team). There is an automatic repair job that runs hourly, and it usually clears within the hour.
- Records only just added — DNS takes time to propagate. Give it a while, then press Check now again.
- A Thai domain, and the records look wrong — compare the
xn--form, not the Thai. Your registrar and this page may show different spellings of the same name; thexn--form under the domain on this page is the one to match.
Changing the domain
With a domain already connected, the card has no field for a new one. Press Remove on the current domain first, and the field comes back.
The new domain’s DNS records are a different set. What you added at your DNS provider for the old domain does not apply — add the new records, including a new _seedwebs-verify record for the new domain.
Removing the domain
Press Remove in the card. You are asked to confirm: “Remove this custom domain? The site will go back to its .seedwebs.app subdomain.”
Removing deregisters both the bare domain and the www side from Cloudflare, and the site serves from {slug}.seedwebs.app again. No content is deleted. The DNS records you created are still at your DNS provider — remove those yourself, the _seedwebs-verify record included.
If this site moved here from WordPress
If this site moved from WordPress (the “Move to SeedWebs” plugin), the domain page shows a checklist and starts the field with the old site’s domain.
- The old site’s domain attaches once the files are complete. While content is still being pulled or files copied, the old domain (with or without
www) is refused, with a link to the move page. If files cannot be fetched, press Skip the remaining files, then attach. Other domains attach as usual. - No pulling while DNS changes. From attaching the old domain until it is active, pulling is locked. To pull again, remove the domain.
- When the domain turns active, the move ends. The plugin connection closes, and an email “ย้าย {domain} เสร็จแล้ว” lists what to do next. The move report stays readable for 90 days.
- Removing the domain within 90 days undoes it. The move goes back to stopped, and the plugin must connect again before anything is pulled (the remove dialog says so). After 90 days it does not touch the move.
When the paid plan ends
Your domain keeps working through the 14-day grace period after the paid period ends. If the site is still unpaid on day 15 (or a payment is refunded in full), the whole site closes: your domain and {slug}.seedwebs.app both show the same “temporarily closed” page, and the admin cannot be signed into (Plans and billing). What does not change:
- The domain stays connected. SeedWebs does not deregister it from Cloudflare, so your DNS setup is intact.
- No content is deleted.
Buy a plan from the portal and the site reopens at once, on your domain too. There is no new verification.
Limits
| Thing | Limit |
|---|---|
| Domains per site | 1 (that domain’s www side is included in it) |
| The same domain on several sites | Not possible. One domain, one site |
| Connect attempts | 10 per hour per site (ownership-record checks: 60 an hour, not counted) |
| SSL certificates | Issued and renewed automatically. There is no field to upload your own |
| The admin panel on your domain | Does not run there. yourbrand.com/admin/ forwards to {slug}.seedwebs.app/admin/ |
The admin panel is mapped out in Admin panel overview, and plans in Plans and billing.