Why Your Manus Website Isn’t Showing Up on Your Custom Domain (And How to Fix It)
You built your website on Manus. You connected your custom domain. You waited. And nothing happened. The site still shows a generic URL or a blank page, and your branded domain is going nowhere. This is one of the most common frustrations among Manus users, and the good news is that it is almost always fixable once you understand exactly what is going wrong and why.
This guide breaks down every root cause behind a Manus website not resolving on a custom domain, walks you through the step-by-step fixes, and explains when you need professional help to get it done right the first time. Whether you are a business owner trying to launch your site or a freelancer managing client projects, getting this right matters because every day your domain is broken is a day your brand is invisible online.
What It Means When Your Manus Site Is Not Showing on Your Custom Domain
When you publish a website through Manus, it lives on Manus infrastructure by default. That means it gets a Manus-generated URL, something that includes their domain name rather than yours. To make your website appear at your own domain, you have to configure a connection between your domain registrar and the Manus platform. This connection is built on something called DNS, which stands for Domain Name System.
DNS is essentially the internet’s phone book. When someone types your domain name into a browser, DNS translates that name into the address of the server where your website lives. If DNS is misconfigured, the browser cannot find your site. If the connection between your registrar and Manus is broken, missing, or pointing at the wrong destination, your domain will either time out, show an error, or load a completely different page.
The problem is not always with Manus itself. It is often a combination of where the mistake happens, from your domain registrar settings to SSL configuration to propagation delays. Understanding the layers helps you fix the right thing instead of wasting hours in the wrong place.
The Most Common Reasons Your Manus Custom Domain Is Not Working
DNS Records Are Not Configured Correctly
This is the number one culprit. When you connect a custom domain to Manus, you are required to add specific DNS records at your domain registrar or hosting provider. These records tell the internet to send traffic from your domain to Manus servers.
Manus typically requires you to add a CNAME record that points your domain or subdomain to their platform. Some configurations also require an A record, which is a direct IP address pointer. If either of these records is missing, entered with a typo, or pointing to an old destination, your domain will not resolve correctly.
The mistake people make most often is entering the CNAME value with a trailing period or without one when the registrar requires it, using the wrong host field such as typing the full domain instead of just “www,” or leaving an old conflicting record in place that overrides the new one. A records and CNAME records cannot coexist on the same host entry in many registrar systems, and having both pointing in different directions causes resolution failures.
DNS Propagation Has Not Completed
Even when you configure everything correctly, DNS changes do not take effect instantly. The internet runs on a distributed system of servers that cache DNS information, and those caches update on their own schedule. Full global propagation can take anywhere from a few minutes to 72 hours, depending on your registrar, your previous TTL settings, and the specific DNS servers in use around the world.
If you set up your records and immediately check whether your site is loading, you are likely checking too early. The mistake here is assuming something is broken when it is actually just propagating. That said, if more than 48 hours have passed and your domain still does not resolve, propagation is no longer the issue and you need to look deeper.
The Domain Was Not Properly Verified in Manus
Manus requires you to verify that you own the domain before fully activating the connection. This verification process typically involves adding a TXT record to your DNS settings. This record contains a unique code that Manus checks to confirm ownership.
If you skipped this step, forgot to add the TXT record, or removed it after verification thinking it was no longer needed, Manus may not have completed the domain handshake on their end. Without verified domain ownership, even correct DNS settings may not produce a live site because Manus has not authorized that domain for delivery.
SSL Certificate Has Not Been Issued
Modern browsers expect every website to have a valid SSL certificate, which is what puts the “https” in your URL and the padlock in the browser bar. When you connect a custom domain to Manus, an SSL certificate needs to be issued for that domain specifically. This is different from the SSL that protects the default Manus URL.
If the SSL certificate has not been issued or failed to issue, browsers will show a security warning instead of your website. Some browsers block the page entirely. Users who see a security warning almost always leave immediately, so a missing SSL certificate is as damaging as a site that does not load at all.
Certificate issuance depends on your DNS being configured correctly first. If DNS pointed to Manus before the certificate was issued, Manus can usually provision it automatically. If DNS was misconfigured during setup, the certificate may have failed to issue and you may need to trigger the process again after fixing your DNS.
Conflicting Records at Your Domain Registrar
Many domain registrars add default records when you first register a domain. These might include placeholder A records pointing to a parking page, or default nameservers that were set up for a different hosting provider you used before. If you previously had your domain pointed at another website builder, an old hosting company, or a previous agency setup, those records may still be active and overriding your Manus configuration.
Two records competing for the same host value will cause inconsistent behavior. Sometimes the site loads and sometimes it does not. Sometimes it loads the old site. Sometimes it shows a generic error. Cleaning up conflicting records is essential before your Manus connection can work reliably.
The Subdomain vs Root Domain Confusion
There is an important technical distinction between pointing your root domain, which is yourdomain.com, and pointing a subdomain, which is www.yourdomain.com or any other prefix. Many users set up only one of these and wonder why the other does not work.
Manus may require you to configure both separately, and they may use different record types. A root domain often requires an A record or a special ALIAS or ANAME record if your registrar supports it, because a root domain cannot technically be a CNAME in standard DNS. A www subdomain can use a CNAME. If you only configured one, visitors using the other version of your URL will hit a dead end.
Additionally, if you want yourdomain.com to automatically redirect to www.yourdomain.com or vice versa, that redirect behavior needs to be configured as well. Without it, one version of your domain resolves and the other does not, which splits your traffic and creates a confusing experience for visitors.
The Domain Is Not Fully Transferred or Active
If you recently registered your domain or transferred it from another registrar, it may not be fully active yet. Newly registered domains can take up to 24 hours to become globally reachable. Transferred domains go through an authorization process that can take several days, and during that time DNS changes may not propagate reliably.
If you are working with a freshly registered or recently transferred domain, wait until the domain shows a fully active status in your registrar’s control panel before setting up and testing your Manus DNS configuration.
How to Fix Each of These Problems
Step One: Log Into Your Domain Registrar and Audit Your DNS Records
Start by logging into wherever you purchased or manage your domain. This is typically a company like GoDaddy, Namecheap, Cloudflare, Google Domains, or a similar registrar. Navigate to the DNS management or DNS settings section for your domain.
Look at every record that is currently active. Write them down or take a screenshot. You are looking for A records, CNAME records, and TXT records in particular. Identify any records that were set up by a previous hosting provider or that you do not recognize. These are the candidates for deletion or replacement.
Step Two: Match Your DNS Records Exactly to What Manus Requires
Go to your Manus account and find the domain connection settings. Manus provides explicit DNS record values you need to add. Copy these values exactly. Do not retype them manually because a single character error, an extra space, or a missing period in a CNAME value will cause the record to fail.
Add the required records, delete any conflicting records pointing to old destinations, and save your changes. If Manus requires a TXT record for verification, make sure that is added as well and that you do not delete it after adding it.
Step Three: Configure Both Root Domain and WWW
If your registrar supports ALIAS or ANAME records, use one for your root domain pointing to the Manus destination. Add a CNAME for www.yourdomain.com pointing to the same Manus destination. If your registrar does not support ALIAS or ANAME records for the root domain, you may need to use the IP address approach with an A record, using the IP address that Manus specifies.
If you want all traffic on the root domain to redirect to www or the other way around, set up that redirect within Manus or through your registrar’s redirect tools. This ensures visitors always land on a consistent URL regardless of which version they type.
Step Four: Wait for Propagation and Then Test
After making DNS changes, wait at least two to four hours before assuming something is wrong. For a more accurate test, use a DNS propagation checker tool by searching for one in your browser. These tools show you how your domain is resolving from multiple locations around the world so you can see whether propagation is in progress or complete.
Do not rely only on testing from your own computer. Your local DNS cache may be showing you an outdated result. Clear your browser cache and DNS cache, or use a different device or network to test.
Step Five: Confirm SSL Is Issued
Once your domain is resolving correctly, check that your site loads over https. If the site loads but shows a security warning, the SSL certificate has not yet been issued. Go into your Manus settings and look for an SSL or security section. In many cases, Manus will automatically provision an SSL certificate once DNS is correctly pointing to their platform. If there is an option to manually trigger certificate issuance or re-verify your domain, use it.
If the certificate still does not issue after several hours of correct DNS configuration, contact Manus support with your domain name and DNS record details so they can investigate on their end.
When to Bring in a Professional
DNS and domain configuration errors look simple from the outside but can become genuinely complex, especially when multiple layers of configuration are involved. You may need professional help if your domain has been transferred between multiple registrars and has a messy record history, if you are using Cloudflare as an intermediary proxy and the configuration requires specific adjustments for Manus to work correctly, if you are setting up a subdomain for a business site that is part of a larger domain used by your company for email and other services, or if you have made multiple attempts at configuration and nothing has worked.
A professional who understands both DNS architecture and platform-specific requirements like those of Manus can diagnose the issue in a fraction of the time and implement a clean configuration that works reliably. The cost of getting it done right is almost always less than the lost business from a site that is invisible to your customers.
If you are an agency or freelancer managing client websites built on Manus, offering domain configuration as part of your service package is a high-value add-on. Many clients have no idea how DNS works, and setting up this connection correctly on their behalf saves them significant frustration and protects the investment they have made in their website.
How to Prevent This Problem in Future Projects
The best way to avoid custom domain issues on Manus is to plan the configuration before you launch rather than after. Set up your DNS records as early as possible so that propagation is already complete by the time your site is ready to go live. Use your domain registrar’s TTL settings to keep values low during the setup period, which speeds up propagation when you make changes.
Keep a record of every DNS setting you configure, including the exact values, the record types, and the date you added them. This makes troubleshooting far easier if something goes wrong later. When you add nameservers or records for email through services like Google Workspace or Microsoft 365, make sure those are documented separately so they are not accidentally deleted during a DNS cleanup.
Test your domain from multiple devices and networks after configuration. Check both the root domain and the www version. Confirm that https loads correctly with no certificate warnings. Verify that the right pages are displaying and that your Manus site content is visible, not a default page or an error.
Why Getting Your Domain Right Matters for Your Business
A custom domain is not just a cosmetic preference. It is a foundational element of how people find and trust your business online. A site that appears at a Manus-generated URL rather than your own branded domain looks unfinished and unprofessional to visitors. It signals that the business has not fully committed to its online presence, which creates doubt about credibility.
Beyond trust, your custom domain is also essential for search engine optimization. Search engines index your domain as an authoritative address for your content. If your site is not consistently reachable at your branded domain, you are missing out on the authority and ranking potential that your content should be building over time.
Every day that your custom domain is misconfigured or not showing your Manus site correctly is a day that potential customers cannot find you, cannot trust you, and cannot convert. Getting the domain configuration right is not a technical luxury. It is a business necessity.
Conclusions: The Fast Checklist for Fixing Your Manus Custom Domain
Check your DNS records at your registrar and compare them exactly to what Manus requires. Delete any conflicting or outdated records from previous hosting setups. Add the correct CNAME, A, and TXT records as specified by Manus. Configure both your root domain and your www subdomain. Set up a redirect so both versions point to the same destination. Wait for DNS propagation, which can take up to 48 hours. Confirm your SSL certificate has been issued by loading your site over https. If any step fails, contact Manus support with your exact DNS configuration for assistance or bring in a professional to handle the setup correctly.
A properly configured custom domain means your Manus website is visible, trusted, and working hard for your business every single day. If you have been struggling with this configuration and want it handled correctly without the back-and-forth troubleshooting, professional domain and DNS setup services are available to get your site live fast.