Store Domains And Branding

Your store can launch on an included Go!BrightCart-hosted subdomain and graduate to a branded custom domain later.

URL options

• Hosted subdomain is included with every store and is the cleanest starting link. This looks like your-store.mygobrightcart.com.
• Default hosted path stays available as a fallback link for testing, migration, and redirects. This looks like mygobrightcart.com/your-store.
• Custom domain is the paid domain upgrade when the storefront is part of your main brand presence. This looks like shop.yourbrand.com or store.yourbrand.com.

Branding checklist

• Match the store name to the name customers already know.
• Keep announcement text, support copy, shipping notes, and trust messaging aligned with the storefront’s purpose.
• Review the shared storefront URL after any branding change so you can catch outdated text.

Custom domain setup

Use a custom domain only after the store is already working on its included hosted subdomain. That keeps setup simple and gives you a fallback link while DNS changes propagate.

Before you start

• Make sure your plan includes custom domains. The hosted Go!BrightCart subdomain is included on every plan.
• Decide which hostname you want buyers to use, such as shop.yourbrand.com.
• Enter only the domain or subdomain you own. Do not include http://, https://, or a path.
• Do not use Go!BrightCart reserved domains like mygobrightcart.com, mygobrightcart.test, gobrightcart.com, gobrightcart.test, or any of their subdomains.

Recommended setup order

1. Launch and test the store on the hosted subdomain first.
2. Add the custom domain in store setup or store settings.
3. Update DNS with your domain provider so that hostname points to your Go!BrightCart storefront destination.
4. Wait for DNS changes to propagate.
5. Open the custom domain in a browser and confirm the storefront, product pages, and checkout all load correctly.

DNS tips

• Most sellers should use a subdomain like shop.yourbrand.com instead of the root domain because it is usually easier to manage.
• For a subdomain like shop.yourbrand.com, create one DNS record with your domain provider:
  • Type: CNAME
  • Name, Host, or Alias: shop
  • Target, Value, or Points to: mygobrightcart.com
  • TTL: leave the default value unless your DNS provider tells you otherwise.
• Do not enter https://, a trailing path, or the full storefront URL in the DNS target. The CNAME target should be only mygobrightcart.com.
• Remove any existing A, AAAA, or other CNAME record for the same subdomain before adding the new CNAME. A hostname like shop.yourbrand.com should not have multiple conflicting records.
• Root domains like yourbrand.com usually cannot use a normal CNAME. Many DNS providers instead use ALIAS, ANAME, or CNAME flattening for the apex domain.
• If your DNS provider offers only one root-domain option for pointing at another service, use the record type they recommend for the apex domain.
• DNS changes can take time to update, so it is normal if the custom domain does not work immediately.

How Go!BrightCart knows which store to load

• DNS only sends the request to Go!BrightCart.
• Go!BrightCart matches the incoming hostname, such as shop.yourbrand.com, to the custom domain saved on your store.
• That means buyers can stay on your custom domain in the browser while still reaching the correct storefront, product pages, checkout, and account pages.

Do you need CORS changes?

• Usually no. A normal storefront on a custom domain is served directly from that same domain, so standard browsing does not need extra CORS setup.
• CORS matters more for embedded widgets, browser API calls from another site, or other cross-origin integrations.

Good examples

• shop.acme.com
• store.example.org
• buy.brand.co

Invalid examples

• http://shop.acme.com
• https://shop.acme.com/store
• my-store.mygobrightcart.com
• bubble-store.gobrightcart.test

Redirect alternate storefront URLs

Go!BrightCart can optionally redirect alternate storefront URLs to the store’s preferred public URL.

• If the store has a custom domain, the preferred URL is the custom domain.
• If the store does not have a custom domain, the preferred URL is the store subdomain.
• If redirect is turned off, the slug URL, subdomain, and custom domain can all stay live, while canonicals still point to the preferred storefront URL.

Why turn redirect on

• You want one clear public URL for SEO and link sharing.
• You want customers to always land on the branded domain you intend to promote.
• You want to reduce duplicate-entry points when sharing products, checkout links, or account links.
• You want carts, account sessions, and analytics to stay on one consistent host.

Why leave redirect off

• You are still testing the new domain or subdomain before making it the only public entry point.
• You want fallback URLs available during migration or DNS propagation.
• You want the hosted subdomain or fallback path to keep working temporarily in case the branded domain has a setup problem.

Recommended rollout

1. Create the store and confirm the hosted subdomain works.
2. Add products and listings.
3. Test checkout and customer-facing messaging.
4. Connect a custom domain once the storefront is ready for promotion.