Skip to main content
This guide walks you through the current AI Search setup flow. By the end, you will have the project objects DevTune needs to run prompt-based AI Search tracking and interpret the results correctly.

​
Before You Start

You will need:
  • A DevTune project created through the onboarding wizard
  • An understanding of which brands and URLs represent you and your competitors
  • A first pass at the prompts you want to track
If you completed the onboarding wizard, much of this is already pre-populated. This guide covers how to review and refine it.

​
Where Setup Happens

AI Search setup spans two places:
  • Project settings - General, Brands, Platforms, Pages, Sharing, and Integrations
  • Search Probes → Prompts - Prompt and topic management
The biggest structural change is that tracked URLs and brand terms are now managed inside the Brands tab rather than separate top-level config tabs.

​
Step 1: Review the General tab

Open Project settings → General and confirm:
  • Project name
  • Description
  • Product context
If the product context is wrong or outdated, fix it before tuning anything else. It influences how DevTune evaluates relevance and generates recommendations.

​
Step 2: Configure Brands, tracked URLs, and brand terms

Open Project settings → Brands. This tab shows:
  • A brand list on the left
  • A detail panel for the selected brand on the right

​
Primary brand

Your primary brand is created during setup and represents your product. It defines which citations and mentions count as “yours.”

​
Competitor brands

Add competitor brands you want to track alongside your own. DevTune can also suggest competitors based on project context.

​
Tracked URLs

Within a brand’s detail panel, add the domains or URLs DevTune should match as citations, such as:
  • Marketing site
  • Docs
  • Blog
  • GitHub repository
  • Package registry pages

​
Brand terms

Also within the same detail panel, add the text terms that should count as brand mentions, such as:
  • Official product name
  • Common variations
  • Common abbreviations

​
Step 3: Enable AI Search platforms

Open Project settings → Platforms and enable the AI Search engines you want DevTune to query. Platform availability depends on your plan:
  • Starter / Plus - ChatGPT, Perplexity, Gemini
  • Pro / Agency / Enterprise - ChatGPT, Perplexity, Gemini, Google AI Mode, Microsoft Bing Copilot
Disabling a platform stops future runs on that engine but does not remove historical data already collected.

​
Step 4: Manage prompts and topics

Open Search Probes → Prompts to review the queries DevTune is sending. From this tab you can:
  • Add or edit prompts
  • Group prompts into topics
  • Review prompt-level performance
  • Use blue-ocean and red-ocean analysis to prioritize coverage
Prompts define the actual questions DevTune submits to the enabled AI platforms, so they are one of the highest-leverage parts of the setup.

​
Step 5: Let runs accumulate

Once brands, tracked URLs, terms, prompts, and platforms are configured, DevTune runs AI Search tracking on its managed schedule. As runs complete, you will see data appear in:
  • Dashboard
  • Prompts
  • Citations
  • Competitors
  • Explore

​
Optional: Connect AI Demand sensors

You can also open Project settings → Integrations and connect the sensors that measure AI demand: the tracking snippet for referral sessions, Cloudflare or edge middleware for crawler traffic, and GA4 and Search Console for conversion and classic-search comparison. None of this is required for Search Probes itself, but it gives you downstream demand context.

​
After Setup

​
Establish a baseline

Your first completed runs establish the baseline for:
  • Presence
  • Share of Voice
  • Brand mentions
  • Citation coverage

​
Expect some variability

AI Search results are not perfectly deterministic. Focus on patterns across multiple runs rather than any single response.

​
Troubleshooting

​
No results appearing

If you do not see results:
  • Confirm that at least one platform is enabled
  • Confirm you have prompts configured
  • Confirm your brands, tracked URLs, and brand terms are present
  • Give the scheduled runs time to complete

​
Unexpected results

If results seem off:
  • Review tracked URLs for typos or missing properties
  • Review brand terms for missing or overly broad matches
  • Confirm you are looking at the correct platform/date filters

​
Next Steps