Skip to main content

Query Library

Manage, organize, and reuse your saved query sets for systematic LLM testing and citation analysis.

Overview​

The Query Library is your central repository for all saved query sets. Browse, filter, and execute query collections you've generated or imported.

Accessing the Library​

Navigate to the Library page:

Dashboard → Library
URL: /dashboard/library

Library Overview​

Quick Stats​

Top section shows aggregate statistics:

Total Query Sets: Number of saved collections Total Queries: Sum of all queries across all sets Industries Covered: Unique industries represented

Example:

📚 Total Query Sets: 12
📝 Total Queries: 580
🏭 Industries Covered: 4

Query Sets Grid​

Main section displays all query sets as cards in a responsive grid.

Card Layout (Desktop): 3 columns Card Layout (Tablet): 2 columns Card Layout (Mobile): 1 column

Query Set Cards​

Each card displays:

  • Name: Query set title
  • Description: Optional context

Stats​

  • 📄 Query Count: "20 queries", "50 queries"
  • 📅 Created Date: "Oct 8, 2025"

Tags​

  • Industry Badge: Blue badge (e.g., "home-improvement")
  • Custom Tags: Gray badges (e.g., "plumbing", "diy")

Actions​

  • View Details button - See individual queries
  • Execute button - Run queries immediately

Browsing Query Sets​

Default Sorting​

Query sets displayed by:

  1. Most Recent First (newest at top)
  2. Alphabetical if same date

Filtering (Coming Soon)​

Planned filters:

  • By industry
  • By tag
  • By date range
  • By query count

Viewing Query Set Details​

Click View Details button or query set name.

Detail Page​

URL: /dashboard/library/[id]

Layout:

  1. Header

    • Query set name
    • Description
    • Back to Library button
    • Execute All Queries button

  2. Metadata Card

    • Total Queries: 20
    • Created: Oct 8, 2025
    • Industry: home-improvement
    • Tags: plumbing, diy, home-repair
    • Focus Area: DIY plumbing repairs (if set)

  3. Queries Table

    • Search box
    • Persona filter dropdown
    • Journey stage filter dropdown
    • Results count
    • Table with all queries

Query Table​

Columns:

  • Query - Full query text with intent
  • Persona - Badge (Consumer, Professional, Beginner)
  • Stage - Badge (Awareness, Consideration, Decision)
  • Category - Text (how-to, comparison, problem-solving)
  • Executed - Count with icon

Features:

  • Search: Filter queries by text
  • Persona Filter: Show only selected persona
  • Stage Filter: Show only selected journey stage
  • Line Clamp: Long queries truncated with "..."

Example Row:

Query: How do I fix a leaking faucet in my kitchen?
       Learn basic plumbing repair
Persona: [Consumer]
Stage: [Awareness]
Category: how-to
Executed: 2 times ↗

Filtering Queries​

Search Box:

  • Type: "faucet"
  • Shows: Only queries containing "faucet"
  • Real-time filtering

Persona Dropdown:

  • Options: All Personas, Consumer, Professional, Beginner
  • Select: Consumer
  • Shows: Only consumer queries

Journey Stage Dropdown:

  • Options: All Stages, Awareness, Consideration, Decision
  • Select: Decision
  • Shows: Only decision-stage queries

Combined Filters:

  • Search: "faucet"
  • Persona: Consumer
  • Stage: Awareness
  • Shows: Consumer awareness queries about faucets

Bulk Actions​

At bottom of table:

"Execute Filtered Queries" button

  • Runs only queries matching current filters
  • Redirects to Execute page with filtered subset
  • Useful for targeted testing

Executing from Library​

Execute All Queries​

From detail page header:

  1. Click Execute All Queries button
  2. Redirects to /dashboard/execute?setId=[id]
  3. Queries pre-loaded in batch mode
  4. Select providers and execute

Execute from Grid​

From library grid:

  1. Click Execute button on query set card
  2. Same flow as "Execute All Queries"

Execute Filtered Subset​

From detail page table:

  1. Apply filters (search + dropdowns)
  2. Click Execute Filtered Queries button
  3. Only filtered queries loaded

Example Use Case:

  • Filter: Persona = Beginner
  • Execute only beginner queries
  • Compare to Professional queries later

Managing Query Sets​

Editing (Coming Soon)​

Future feature:

  • Edit query set name
  • Update description
  • Add/remove tags
  • Add/remove individual queries

Deleting (Coming Soon)​

Future feature:

  • Delete query set
  • Confirmation dialog
  • Cascade delete all queries

Exporting​

From Detail Page:

  1. Navigate to query set detail
  2. Click Export button (coming soon)
  3. Download CSV with all queries

CSV Format:

Query Text,Persona,Journey Stage,Category,Intent,Execution Count
"How do I fix a leaking faucet?",Consumer,Awareness,how-to,"Learn basic repair",2
...

Organization Strategies​

Tag-Based Organization​

By Topic:

  • Tags: plumbing, electrical, carpentry
  • Quick filtering in library

By Client (for agencies):

  • Tags: client-acme, client-techcorp
  • Separate client work

By Campaign:

  • Tags: q1-2025, spring-campaign
  • Track seasonal initiatives

By Content Type:

  • Tags: blog-ideas, faq-content, comparison-pages
  • Content strategy planning

Naming Conventions​

Recommended Format:

[Industry] - [Focus] - [Date/Version]

Examples:

  • "Home Improvement - Plumbing DIY - Jan 2025"
  • "SaaS - Team Collaboration - v2"
  • "E-commerce - Camping Gear - Q1 Baseline"

Benefits:

  • Alphabetical sorting groups related sets
  • Date/version tracks iterations
  • Easy to scan and find

Query Set Types​

Baseline Sets:

  • Comprehensive industry coverage
  • 50-100 queries
  • All personas and stages
  • Run quarterly to track trends

Focused Sets:

  • Specific product or topic
  • 20-30 queries
  • Targeted persona
  • Run for specific initiatives

Competitive Sets:

  • Competitor brand mentions
  • Alternative queries
  • Comparison queries
  • Monthly competitive analysis

Testing Sets:

  • New content validation
  • 10-20 queries
  • Run after publishing new content

Execution Tracking​

Execution Count​

Each query tracks how many times it's been executed:

Displayed:

  • In query table: "2 times"
  • Icon: ↗ (trending up) if executed

Purpose:

  • Identify frequently tested queries
  • Avoid redundant executions
  • Prioritize untested queries

Last Executed​

Track when query was last run (coming soon):

Use Cases:

  • Find stale queries (not run in 30+ days)
  • Schedule regular re-runs
  • Monitor freshness

Library Workflows​

Weekly Testing Routine​

Monday:

  1. Review library
  2. Identify sets not run in 7+ days
  3. Execute 1-2 sets across new providers
  4. Analyze results in Analytics

Benefit: Consistent data collection, track trends

New Content Validation​

After Publishing:

  1. Create focused query set (10-20 queries on topic)
  2. Execute across all providers
  3. Check if new content is cited
  4. Identify citation gaps

Benefit: Measure content AEO effectiveness

Competitive Monitoring​

Monthly:

  1. Execute competitor-focused query sets
  2. Track competitor citation share
  3. Identify opportunity gaps
  4. Update content strategy

Benefit: Stay ahead of competitive AEO landscape

Best Practices​

Save Everything​

Do: Save all generated query sets Why: Hard to recreate exact queries later

Storage is cheap: No limit on query sets

Descriptive Metadata​

Do: Add descriptions and tags Why: Future you will thank present you

Example:

Name: "Home Improvement - Plumbing DIY - Baseline"
Description: "Comprehensive coverage of DIY plumbing queries.
              Generated to establish baseline citation rates.
              Run quarterly to track trends."
Tags: plumbing, diy, home-repair, baseline, q1-2025

Regular Cleanup​

Monthly Review:

  • Delete true test/junk sets
  • Consolidate duplicate sets
  • Update tags for consistency
  • Archive old baseline sets

Keep:

  • All baseline sets (historical comparison)
  • Client work (record-keeping)
  • Successful campaigns (learning)

Delete:

  • "test123" one-off experiments
  • Duplicate sets
  • Poorly generated sets

Version Control​

When refining a query set:

Option 1: Create new set with version

  • "SaaS Collaboration - v1"
  • "SaaS Collaboration - v2"
  • Keep both for comparison

Option 2: Use dates

  • "SaaS Collaboration - Jan 2025"
  • "SaaS Collaboration - Apr 2025"
  • Track quarterly evolution

Empty State​

When you have no query sets yet:

Display:

  • 📚 Library icon
  • "No Query Sets Yet"
  • "Generate your first query set to get started"
  • Generate Queries button

Action: Click button → Redirects to Generate page

Tips for Power Users​

Bulk Execution Strategy​

Scenario: 10 query sets, 20 queries each = 200 total queries

Strategy:

  1. Week 1: Execute Sets 1-5 with Claude
  2. Week 2: Execute Sets 6-10 with Claude
  3. Week 3: Execute Sets 1-5 with GPT-4
  4. Week 4: Execute Sets 6-10 with GPT-4

Benefit: Spread costs, allow time for analysis

Filtered Execution​

Scenario: 100-query set, want to test personas separately

Strategy:

  1. Filter: Persona = Consumer → Execute (33 queries)
  2. Filter: Persona = Professional → Execute (33 queries)
  3. Filter: Persona = Beginner → Execute (34 queries)

Benefit: Compare citation patterns by persona

Cross-Provider Comparison​

Scenario: Same query set, different LLMs

Strategy:

  1. Execute Set A with Claude only
  2. Wait for results
  3. Execute Set A with GPT-4 only
  4. Wait for results
  5. Execute Set A with Gemini only
  6. Compare in Analytics

Benefit: Identify provider-specific citation patterns

Next Steps​