Technical Setup: Routing and Deployment Model

Flint hosts Flint pages on Flint servers. There are two options for integration:

1. 1.Subdomain (e.g. assistant.yelp.com)
2. 2.Folder on Main Domain (e.g. yelp.com/assistant/*)

Subdomain:

• •Pro: Simple to setup with DNS record
• •Con: Significantly less optimized for SEO

Folder on Main Domain:

• •Pro: Usable for SEO, better branding
• •Con: More difficult infrastructure and security configuration

The simpler setup. Just add a CNAME record to your DNS and you're ready to go.

See the full Subdomain guide here →

Can be done via Cloudflare Worker, Vercel rewrite, or AWS CloudFront, depending on your setup.

Example: Vercel Configuration

To set up folder-on-main-domain routing for a Vercel hosted site, configure this within the vercel.json file:

{
  "rewrites": [
    {
      "source": "/lp",
      "destination": "https://yoursite.tryflint.com/lp"
    },
    {
      "source": "/lp/:match*",
      "destination": "https://yoursite.tryflint.com/lp/:match*"
    }
  ]
}

See the full Cloudflare Worker setup guide here →

See the full AWS CloudFront setup guide here →

After adding DNS records manually, Flint may not detect them automatically. If your domain still shows as unverified or is not resolving to your Flint site, follow these steps:

1. 1.Wait 5-10 minutes after saving your DNS records to allow initial propagation
2. 2.Go to Settings in the Flint dashboard and navigate to Domains
3. 3.Click Add Domain at the top of the page, even if your domain is already listed. This re-triggers the verification process and prompts Flint to re-check your DNS records
4. 4.If the domain is still showing as 'Needs configuration', wait 30 minutes and repeat step 3

Tip: Use dnschecker.org to verify that your DNS records have propagated globally before re-triggering verification in Flint. This helps confirm whether the issue is with DNS propagation or Flint's verification check.

When connecting a custom domain to Flint, make sure both the www and non-www versions (e.g., example.com and www.example.com) are configured.

1. 1.In your Flint site settings, add both domain variants.
2. 2.In your DNS provider, set up records for both — the root domain (example.com) as an A record or CNAME pointing to Flint, and the www version (www.example.com) as a CNAME pointing to Flint.
3. 3.After adding DNS records, click Add Domain in Flint for each variant to verify.

If one domain version works but the other shows a blank page, the non-working variant may be pointed at a different or deleted Flint project. Contact support@tryflint.com and we'll help you troubleshoot and get both domains working.

Flint can serve a sitemap for your custom domain. Sitemaps are set up by the Flint team — to enable yours, email us at support@tryflint.com and we will configure it for you. Once enabled, your sitemap will be available at [your-domain]/sitemap.xml.

For pages to appear in the sitemap, they must be:

• •Marked as indexable in page settings (Settings then Page Settings)
• •Published to production

Setting up Google Search Console:

1. 1.Go to Google Search Console and add your custom domain as a property
2. 2.Submit your sitemap URL: https://[your-domain]/sitemap.xml
3. 3.Google will begin crawling your published, indexable pages

Troubleshooting:

• •Sitemap returns 404: If your sitemap has not been set up yet, email support@tryflint.com and we will enable it for you.

• •0 pages discovered: Check that your pages are both published and set to indexable in page settings.

• •Cloudflare users: Ensure no Page Rules or Workers are blocking /sitemap.xml requests.