Custom Domain
Maker supports custom domain mapping, allowing your projects to appear on your own branded domain.
Instead of using a default Maker link, your pages can live directly under your website—for example, pages.yourbrand.com.
What You Can Do
Connect a custom domain (e.g.,
maker.yourbrand.com)Show Maker-generated pages directly on your site—no iframe or embed code needed
Support full SEO benefits since the content is hosted under your domain
Design microsites, event pages, or landing pages without touching your website backend
Why Use This Instead of Embedding?
No iframes = faster load times & fewer issues
Keeps your content under your domain for SEO
Perfect for microsites or standalone campaigns
Recommended for AI visibility and consistent crawlability. Custom Domain is the simplest and most complete way to make a fully Maker-built page visible to AI assistants and every type of crawler. When you point a domain or subdomain at your Maker project, Maker serves the entire page as server-rendered HTML. The content is in the page from the first request -- no JavaScript required. Google, Bing, ChatGPT, Claude, and Perplexity all read it the same way they would read any other page on your site.
Google indexes JavaScript, so Simple Embed and Enhance work fine for Google SEO. The gap is AI assistants - ChatGPT, Claude, and Perplexity do not run JavaScript, so they cannot see content injected after page load. If AI visibility matters for a page, Custom Domain is the right setup.
Step-by-step
Publish a Project in Maker
Go to Domain Settings → Click “Connect Domain”
Enter your custom domain (e.g.,
pages.yourbrand.com)Verify your domain
Done! Your Maker content now appears on your domain.
Example:
Default:
yourbrand.maker.new/launch-page-2509Custom Domain:
pages.yourbrand.com/launch-page-2509
Root Domain vs. Project Path
Root project: Appears directly on the homepage of your domain (
pages.yourbrand.com)Other projects: Available under slugs like
pages.yourbrand.com/my-story
FAQs
Can I edit the project slug (like /launch)?
Slugs are auto-generated, but can be edited by clicking on the pencil icon.

Will this affect our main website?
No. You can reserve a subdomain (like maker.yourbrand.com) just for Maker projects. It won’t interfere with your blog or shop.
Will SEO still work?
Yes—if you connect your own domain. Maker content hosted under your brand's domain will get full SEO visibility.
Will AI assistants like ChatGPT, Claude, and Perplexity be able to read my Maker content?
Yes, when you use Custom Domain. AI crawlers fetch a page's raw HTML and do not run JavaScript. With Custom Domain, Maker serves fully rendered HTML, so AI assistants read your content the same way they would read any standard page. On JavaScript-based embed methods (Simple Embed, Enhance), AI crawlers see an empty slot where your content would appear.
My SEO team said our Maker content is not showing up in their crawl tools. What does Custom Domain do differently?
Google renders JavaScript and indexes the content normally, so this is not a Google issue. The more likely explanation is that most third-party SEO audit tools do not render JavaScript by default; they read raw HTML only, which is why Maker content delivered via JavaScript embed shows up as missing in their reports. AI assistants like ChatGPT, Claude, and Perplexity have the same limitation. Custom Domain serves fully rendered HTML from the first request, so audit tools and AI crawlers read your content the same way Google does.
What is the difference between Custom Domain and SSR Component for SEO?
Both deliver your content as native HTML and give you full SEO and AI crawlability. The difference is scope. Custom Domain is for pages that are entirely Maker-built, Maker owns the whole page. SSR Component is for Maker blocks living inside pages you manage in another CMS. If you are not sure which applies to your setup, reach out via in-app chat.
Does using a subdomain (like pages.yourbrand.com) still give full SEO credit?
Yes. Content hosted on a subdomain under your brand gets full SEO visibility. Search engines associate the subdomain with your domain, and your structured data, meta tags, and page content are all indexed normally. The key is that the content is served as native HTML, which is exactly what Custom Domain does.
Last updated
Was this helpful?