AI Search configuration is now centered on Project Settings rather than a collection of older standalone config tabs. This page explains how the current settings model works.Documentation Index
Fetch the complete documentation index at: https://docs.devtune.ai/llms.txt
Use this file to discover all available pages before exploring further.
Accessing Configuration
Navigate to Project Settings from the project sidebar. The page includes these tabs:- General
- Brands
- Platforms
- Content Preferences when enabled for your account
- AI Traffic
General Tab
Use the General tab for the core project record:- Project name
- Description
- Product context
Brands Tab
The Brands tab combines what used to be separate areas for competitor setup, citation sources, and brand terms.Layout
The tab uses a master-detail pattern:- The left side lists your primary brand and competitor brands
- The right side shows the selected brand’s detail panel
What you can manage
For each brand, you can manage:- Tracked URLs / citation sources
- Brand terms
- Brand type (primary or competitor)
Suggested competitors
Where DevTune has enough context, it can suggest relevant competitors to add. This helps teams move faster than manually building the competitor set from scratch.Platforms Tab
The Platforms tab controls which AI Search platforms DevTune queries during scheduled runs. Supported platforms:- ChatGPT
- Perplexity
- Gemini
- Google AI Mode
- Microsoft Bing Copilot
Plan availability
- Starter / Plus - ChatGPT, Perplexity, Gemini
- Pro / Agency / Enterprise - All five platforms
Content Preferences Tab
The Content Preferences tab lets your team tell DevTune which content formats fit this project. By default, every content format is allowed. When the tab is enabled for your account, you can:- Allow only specific formats
- Block formats you do not want DevTune to recommend
- Add project-level style notes
AI Traffic Tab
The AI Traffic tab is separate from AI Search, but it lives on the same Project Settings page because it shares the same project context. Use it to:- Generate the tracking snippet
- Copy installation code
- Enable or disable collection
Why the Structure Changed
The current setup model is simpler than the older one:- Brands is now the home for both tracked URLs and brand terms
- Platforms is isolated to runtime coverage
- Content Preferences controls the content formats DevTune may recommend when available
- General holds project context
- AI Traffic is kept nearby because it is another project-level signal surface
Best Practices
- Review General whenever your product positioning changes
- Review Brands whenever you launch new content properties or start tracking a new competitor
- Review Platforms when you change plans or want to narrow scope
- Review Content Preferences when your content strategy changes or a format should no longer be recommended
- Treat AI Traffic as instrumentation, not just reporting
Next Steps
- Tracked URLs - Manage tracked URLs inside the Brands tab
- Brand Terms - Manage mention matching inside the Brands tab
- Prompts - Manage the prompt side of AI Search tracking
- Running Search Tests - Understand what happens after setup