Skip to main content
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.

Accessing Configuration

Navigate to Project Settings from the project sidebar. The page currently has four tabs:
  • General
  • Brands
  • Platforms
  • AI Traffic

General Tab

Use the General tab for the core project record:
  • Project name
  • Description
  • Product context
This is the right place to update the product narrative DevTune uses when it evaluates relevance and generates recommendations.

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
  • Grok

Plan availability

  • Starter / Plus - ChatGPT, Perplexity, Gemini
  • Pro / Agency / Enterprise - All five platforms
Locked platforms remain visible so you can see what is available on higher tiers.

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
  • 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
  • Treat AI Traffic as instrumentation, not just reporting

Next Steps