Optimizing Important Search Terms

Certain search terms require special attention to ensure users find relevant, accurate content quickly. This guide outlines strategies for optimizing these critical search terms.

Term Categories

Commonly Pre-populated in NR1 Help Center

The NR1 Help Center auto-suggests certain terms as users type. These highly visible terms must return excellent results.

High-Priority Examples

• "APM" - Application Performance Monitoring
• "NRQL" - New Relic Query Language
• "SLA" - Service Level Agreement
• "Dashboards" - Custom dashboards
• "Alerts" - Alert policies and conditions

Optimization Strategy

1. Regular audits: Review results monthly
2. Promote current content: Latest docs and tutorials rank first
3. Remove outdated: Deprecate old versions
4. Add context: Include getting started guides

Vague Terms with Noisy Results

Some terms are inherently broad, returning many irrelevant results. These need careful curation.

Problematic Terms

"browser":
  could_mean:
    - Web browser compatibility
    - New Relic Browser monitoring product
    - Browser API
  solution: Create disambiguation page or smart result ranking

"alert":
  could_mean:
    - Alert policies
    - Alert conditions
    - Alert incidents
    - Alert channels
  solution: Rank by user journey stage

"API":
  could_mean:
    - New Relic REST API
    - GraphQL API (NerdGraph)
    - Agent APIs
    - Partner APIs
  solution: Use aliases for specific API types

Management Approach

1. Create landing pages for ambiguous terms
2. Use result ranking to prioritize most common intent
3. Add synonyms for specific variations
4. Monitor refinements to understand user intent

Frequently Searched Terms

High-volume searches need constant optimization to prevent user frustration.

Top Search Terms (Example)

Optimization Process

1. Export search analytics monthly
2. Identify top 20 searches
3. Audit current results for each
4. Optimize rankings based on click-through data
5. Add missing content where gaps exist

Glossary Terms

Fundamental concepts that new users need to understand quickly.

Core Glossary Terms

• Transaction tracing → Link to detailed explanation
• SLO (Service Level Objective) → Definition + setup guide
• APDEX → Explanation + configuration
• Distributed tracing → Concept + implementation
• Telemetry → Overview + data types

Best Practices

1. Direct definitions: Glossary page ranks first
2. Include abbreviations: Set up synonyms for short/long forms
3. Context guides: Follow with how-to content
4. Visual aids: Prioritize pages with diagrams

Additional Important Terms

Product Names and Features

const productTerms = {
  "New Relic One": {
    priority: "high",
    topResults: [
      "Platform overview",
      "Getting started guide",
      "Feature comparison"
    ]
  },
  "Telemetry Data Platform": {
    priority: "high",
    topResults: [
      "Architecture overview",
      "Data ingestion guide",
      "Query tutorial"
    ]
  },
  "Dashboards": {
    priority: "medium",
    topResults: [
      "Create your first dashboard",
      "Dashboard best practices",
      "Widget reference"
    ]
  }
}

Troubleshooting Keywords

Common problem-related searches need immediate, actionable results:

• "slow query" → Performance tuning guide
• "memory leak" → Diagnostic steps
• "high error rate" → Troubleshooting checklist
• "missing data" → Data collection verification

Integration Searches

Popular integration searches should prioritize:

1. Official setup guide
2. Configuration reference
3. Best practices
4. Troubleshooting guide
5. Community examples

Monitoring and Iteration

Key Metrics to Track

• Search volume per term
• Click-through rate on results
• Search refinements (indicating poor initial results)
• No results rate
• Time to click

Regular Review Schedule

TBD Enhancements