**Purpose**

Identify authority opportunities and visibility gaps by analyzing SERP queries and extracting structured questions, answers, and authoritative sources consumable by LLMs and outreach workflows.

## Primary Function

Transform a search query into:

- Structured question–answer pairs
- Source-level authority signals
- Actionable inputs for Digital PR and AI Visibility (formerly LLM Visibility) campaigns

## UI Entry Point

**Left Sidebar → Authority → AI Visibility (formerly LLM Visibility) → QUEST**

## Inputs

1. Search query (free-text)
2. SERP-derived data sources
3. Platform query quota
4. Optional project or campaign context (downstream)

## Core Actions

### 🔎 Query Analysis

**Action:** Analyze a search query to extract authority-relevant information.

**User actions:**

- Enter query in the input field
- Click **Analyze query**

**Execution characteristics:**

- Query is processed against live SERP data
- Results are stored as a retrievable analysis unit
- Each query analysis is tracked independently

### 🧠 Question & Answer Extraction

**Action:** Generate structured Q&A pairs aligned with authoritative SERP patterns.

**User actions:**

- View extracted questions
- Review AI-generated expert-style answers
- Toggle **Highlight Sources** per question

**Execution characteristics:**

- Questions reflect real SERP and content patterns
- Answers are designed for citation, reuse, and outreach
- Source highlighting controls attribution visibility

### 🌐 Source Identification

**Action:** Surface authoritative domains and URLs used to construct answers.

**User actions:**

- View source list in right-side panel
- Select or deselect individual sources
- Select all or clear all sources

**Execution characteristics:**

- Sources are derived directly from SERP analysis
- Source selection directly affects downstream campaign creation

### 📣 Campaign Bridging

**Action:** Convert QUEST analysis into a Digital PR campaign.

**User actions:**

- Select one or more sources
- Click **Create Campaign with X Domains**

**Execution characteristics:**

- Selected sources are passed as campaign targets
- No outreach is executed at this stage
- Campaign creation occurs in Digital PR

## State Changes

### Query Lifecycle

- New → Analyzed → Stored
- Stored queries appear in QUEST history table

### Campaign Association

- Query remains available after campaign creation
- Campaign linkage is additive, not destructive

## Outputs

1. Structured Q&A datasets
2. Authority-aligned answer blocks
3. Curated list of authoritative domains
4. Campaign-ready source targets
5. LLM-consumable visibility inputs

## Dependencies

1. QUEST outputs are commonly consumed by:

   - Digital PR campaigns
   - Outreach targeting logic
   - AI Visibility (formerly LLM Visibility) strategies
2. QUEST does not require:

   - Email connections
   - Templates
   - Publishing or indexing actions

## Non-Goals

1. QUEST does not:

   - Send outreach emails
   - Publish content
   - Build backlinks directly
   - Modify existing authority assets
2. QUEST is not a content editor or CMS

## Notes & Tips

- 📝 Use QUEST queries that reflect **how users actually ask questions**, not just keywords.
- 📝 Source selection determines outreach scope downstream.
- 💡 QUEST is most effective when used before Digital PR execution, not after.
- 📝 Queries can be reused across multiple campaigns without re-analysis.

QUEST defines the **research and intelligence layer** of Authority in Search Atlas. It converts unstructured search queries into structured authority signals that can be reused across visibility, outreach, and AI-driven workflows.

No execution occurs within QUEST. Its sole function is to produce clean, source-aligned inputs that downstream systems can act upon with precision and control.

For execution and distribution, refer to Authority Building and Digital PR documentation.