> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/features/custom-domain.md). # Custom Domain {% hint style="info" %} Instead of using a default Maker link, your pages can live directly under your website—for example, `pages.yourbrand.com`. {% endhint %} ### 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 1. **Publish a Project** in Maker 2. **Go to Domain Settings** → Click “Connect Domain” 3. **Enter your custom domain** (e.g., `pages.yourbrand.com`) 4. **Verify your domain** 5. **Done!** Your Maker content now appears on your domain. > Example: > > * Default: `yourbrand.maker.new/launch-page-2509` > * Custom Domain: [**`pages.yourbrand.com/launch-page-2509`**](http://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` *** *** {% embed url="" %} *** ### FAQs
Can I edit the project slug (like /launch)? Slugs are auto-generated, but can be edited by clicking on the pencil icon.
slug update.png
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](https://docs.maker.co/features/ssr-component-support) 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.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.maker.co/features/custom-domain.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.