Root Domain Hosting

Root domain hosting serves your Flint pages under a path on your root domain. Your main domain and Flint pages share the same hostname, so pages inherit your domain's existing authority in search indexes.

This option is available on Pro and Enterprise plans and requires configuring a reverse proxy with your CDN or web server. Not sure if root domain hosting is right for you? See the Subdomain vs Root Domain Hosting comparison guide.

Your Flint pages appear under a path on your main domain:

• •yourdomain.com/lp
• •yourdomain.com/pages
• •yourdomain.com/solutions

Visitors never leave your root domain.

Root domain hosting requires a reverse proxy. Requests to your chosen path are forwarded from your existing web infrastructure to Flint's servers.

Supported proxy providers:

• •Cloudflare - Configure via Cloudflare Workers or Page Rules
• •Nginx - Configure via proxy_pass in your server block
• •Vercel - Configure via rewrites in vercel.json
• •Netlify - Configure via _redirects or netlify.toml
• •AWS CloudFront - Configure via origin groups and behaviors

Each provider has its own setup steps. See the links above for per-provider guides.

Note on unsupported platforms: Platforms like Squarespace and Wix do not support custom reverse proxy configuration. If your main site runs on one of these platforms, subdomain hosting is the available option.

• •Requires a Pro or Enterprise plan; not available on Starter
• •Requires technical configuration of a reverse proxy (CDN, web server, or serverless function)
• •Some hosting platforms do not support reverse proxies at all
• •Misconfigured proxies can cause routing issues that affect your main site
• •Setup time and complexity vary by provider

If you are currently on subdomain hosting and want to switch to root domain hosting, your page URLs will change. Pages that were at pages.yourdomain.com/landing will move to yourdomain.com/pages/landing.

301 redirect strategy

Before switching, document your current published URLs. After the new setup is live, configure 301 redirects from each old URL to the corresponding new URL. This preserves link equity and prevents broken links for visitors.

Plan requirements

Root domain hosting requires a Pro or Enterprise plan. If you are currently on Starter, see the pricing page for plan options.

For step-by-step configuration instructions, see the guide for your provider:

• •Cloudflare
• •Vercel
• •Nginx - refer to your Nginx documentation for proxy_pass configuration
• •Netlify - refer to Netlify's documentation for redirect and rewrite rules
• •AWS CloudFront - refer to AWS documentation for origin groups and cache behavior configuration

Note on unsupported platforms

Squarespace, Wix, and similar hosted website builders do not support the custom reverse proxy configuration required for root domain hosting. If your main site runs on one of these platforms, use subdomain hosting instead.

Do I need to upgrade to use root domain hosting?

Yes. Root domain hosting is available on Pro and Enterprise plans only. Starter plan customers can use subdomain hosting. See the pricing page for plan details.

How does this interact with ABM pages?

ABM pages follow the same hosting setup as your other Flint pages. If your site uses root domain hosting, ABM pages are served from the root domain path. See the ABM workflow guide for configuration details.

Will analytics tracking break if I switch setups?

If your analytics tool is configured per domain or per property, you may need to update it after switching. Review your analytics configuration before and after any hosting setup change.