Skip to main content
If AI doesn’t know you, it won’t recommend you. You need to educate AI about your business by creating content so it can train on it and fetch it to users via web search.
The most effective way to create content is to answer the specific questions users are already asking. Instead of guessing topics, this workflow lets you instantly generate blog posts from your tracked prompts, ensuring every piece fills a specific gap in your visibility.

​
Create content from prompts

  • Navigate to the Prompts tab in the sidebar
  • Click the three dots beside the prompt you want to create content for
  • Choose Create blog
  • You’ll be taken to the Review drafts section, which contains all the blogs you’ve generated that require review
  • Accept or reject the blog
    • If you accept, your blog will be published on the Custom domain you connected (e.g. ai.yourdomain.com/article-slug)
    • If you reject, give feedback so our AI learns

​
Set up custom domain

All content you publish is hosted on a Custom domain you connect. Before publishing, add your domain in Settings so your content appears at a URL like ai.yourdomain.com and is discoverable by AI via web search.

​
Add a DNS record

​
The Prompting Company

  • Open Domains settings. Connect your domain opens with Dedicated domain via DNS selected
  • Enter a custom domain you want your content to be hosted on (e.g. ai.yourdomain.com) and click Add domain
  • Open the domain’s DNS settings to get the CNAME record you need to add to your DNS provider

​
Your DNS provider (e.g. Cloudflare, GoDaddy, Namecheap, etc.)

  • Go to DNS > Manage DNS
  • Add a record with the following values:
  • Turn off Proxy
  • Choose the lowest TTL

​
Host content on a subpath (optional)

Instead of a subdomain like ai.yourdomain.com, you can publish content on a path of your main site, like www.yourdomain.com/info. Your content then sits on the same domain as the rest of your site, rather than on a separate subdomain. A subpath works by adding a reverse proxy rule on your side: requests to /info and /info/* on your site get forwarded to an origin we host for you. Visitors and crawlers only ever see your domain.
This is a configuration change on your hosting or CDN, not a code change to your site’s pages. On Vercel/Next.js or Netlify it’s a small config file change that ships with your next deploy.

​
Connect the subpath

  1. Open Domains settings. Connect your domain opens with Subpath on your domain selected
  2. Enter your Domain. Include www. if your website uses it (e.g. www.yourdomain.com, not yourdomain.com)
  3. Pick a Path prefix. /info works well, but you can use any path that doesn’t already exist on your site (e.g. /learn, /resources)
  4. Click Add domain
  5. Open the domain’s menu and choose Proxy settings

​
Add the proxy rule

Proxy settings shows your public content address (e.g. https://www.yourdomain.com/info), the origin to forward requests to, and the exact config for your website stack: Next.js, SvelteKit, Vercel, Netlify, Cloudflare, Nginx, Caddy, or Amazon CloudFront. Add that config to your site, or use Copy prompt to hand the setup to your coding agent. Whichever stack you use, the rule must:
  • Forward /info and /info/* to your origin, keeping the path and query string as-is
  • Send your origin hostname as the Host header, not your own domain. If this is wrong, the origin can’t match the request and returns errors.
  • Pass the visitor’s User-Agent and Accept headers through unchanged, so AI crawler traffic is attributed correctly
If you use a CDN like Cloudflare in front of your site, add the rule there, since it receives requests first.

​
Allow AI crawlers

If your site uses bot protection (e.g. Cloudflare Bot Fight Mode or a WAF), make sure it doesn’t challenge or block AI crawlers on /info and /info/*. These pages exist for crawlers to read, so a blocked crawler means the content never gets picked up. At minimum, allow: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, Bingbot, Googlebot. Also check that your robots.txt doesn’t disallow /info.

​
Verify

Once the rule is live, click Verify connection in Proxy settings to check that your public content address loads through your proxy. Your domain’s card in Settings > Website > Domains also shows a Sitemap status, which checks /info/sitemap.xml and whether your main site’s robots.txt lists that sitemap (see below). You can also check that both a browser and a crawler get a 200:
If the second command returns 403 or a challenge page, your bot protection is still blocking crawlers.

​
Indexing on a subpath

Use your subpath sitemap in the indexing steps below: https://www.yourdomain.com/info/sitemap.xml. If your main domain is already verified in Google Search Console, you don’t need a new property. Just submit the sitemap there. Also add it to your main site’s robots.txt:

​
Submit indexing to Google & Bing

Ensure your custom domain is indexable by Google and Bing by submitting it for indexing. Replace ai.yourdomain.com with your domain in the URLs below. Google:
  • Go to Google Search Console
  • Click Add property
  • Choose Domain (the left option) and enter your domain (e.g. ai.yourdomain.com)
  • Follow the instructions to add DNS records
  • Go to the Sitemaps tab and submit https://ai.yourdomain.com/sitemap.xml
Bing: