AviaryAI Organic Keyword Strategy & Content Roadmap

Overview

This article captures the keyword analysis, SEO insights, and content prioritization strategy developed for AviaryAI as of January 2026. The strategy is built around AviaryAI's core positioning as an outbound AI voice agent for credit unions, with content mapped to high-intent and high-growth keyword clusters. Navigation and page structure decisions are closely tied to this analysis.

See also: ^[1] | ^[2]

Keyword Insights

High-Intent Terms to Own

• "AI voice agents" — Core term with meaningful search volume. AviaryAI's outbound differentiation should be reinforced on every page targeting this cluster. Owning this term is the primary organic objective.
• Credit union-specific terms — Search volume is relatively low in absolute terms, but intent is extremely high. These terms will not be primary volume drivers; ABM and partner channels are better suited for credit union-specific lead generation. A dedicated page is still warranted.

High-Growth Opportunities

• "Loan servicing" / "loan payment reminder" — Up nearly 1,000% YoY, likely driven by macroeconomic conditions (rising auto loan delinquencies, buy-now-pay-later defaults). This cluster maps directly to AviaryAI's Collections and Dormancy use cases and represents a significant near-term content opportunity.
• Collections / delinquency / debt collection — Among the highest-volume use case keyword clusters. Strong alignment with existing journey drafts (see ^[3]).
• Conversational AI — Massive YoY growth, as expected. Too broad to target directly, but useful for passive targeting via headers and supporting content.
• TCPA compliance — Meaningful search volume; reinforces trust and credibility. Should be woven into compliance/security page content and ad copy.

Declining Terms

• "Onboarding" — Down significantly YoY, likely reflecting a weak job market. The recommended reframe is "early member engagement" — same use case, better-aligned search behavior. The New Member Onboarding journey draft should adopt this language.
• Knowledge base — High volume but declining, crowded category with dominant players, and misaligned audience intent. Not a primary organic target. The product should be positioned as a feature of the Voice Agent, not a standalone SEO target (see navigation strategy below).
• Call center / contact center — Category searches trending down YoY. Relevant for blog content positioning AI voice agents as a solution, but should not be a heavy focus. Aligns with the lowest-budget PPC discovery campaign.

Competitor Opportunity

• "Glia alternative" / "Glia vs. competitors" — Glia has the highest brand search volume among competitors (~40,500 searches). Writing a comparison or alternative blog post is a low-cost, high-intent SEO opportunity. Paid competitor targeting against Glia is expensive; organic is the preferred approach here.
• A competitor analysis tab (using SpyFu) will be added to the organic strategy document to surface additional keyword gaps and page structure insights from competing products.

Website Navigation Strategy

Core Principle: Voice Agent First

The site must maintain a "Voice Agent first" narrative. Adding a Knowledge Base product as a co-equal nav item risks diluting the core message and has historically created confusion about AviaryAI's primary offering.

Decided approach:
- The main navigation will lead with Voice Agent (not a dual-product "Products" dropdown).
- The Knowledge Base will be referenced on the Voice Agent page as a supporting feature — linked but not elevated to top-level navigation.
- This allows the Knowledge Base page to exist and be indexed/ranked without competing with the Voice Agent for homepage attention.

Safety & Security must remain a top-level navigation item. It is a trust signal that credit union buyers actively look for, and it should appear prominently across all relevant pages.

Proposed Navigation Structure (Draft)

Products → Voice Agent (Knowledge Base linked within)
Use Cases → Collections | Dormancy | New Member Engagement | [others]
Industry → Credit Unions
Resources → Blog | ROI Calculator (hidden, sales use) | Journey Pages (hidden)
Safety & Security (top-level)

A Miro sitemap will be built to visualize and iterate on navigation options before implementation. See action items below.

Content Priorities

Tier 1 — Immediate (Sales Enablement)

These are the highest priority because they unblock the sales team, not because of search volume.

These will be published as hidden pages — not linked from main navigation — for use as sales assets on calls. They may later inform public-facing use case pages. Justin Dwyer submitted first drafts; AviaryAI to provide client logos (SVG preferred) and stats (AUM + member count).

Tier 2 — Near-Term (Organic Foundation)

• Miro sitemap — Visualize navigation options; share with Aaron and Justin for feedback.
• Blog topic calendar — Map longer-tail keywords to a publishing schedule. Topics to include loan servicing, collections, TCPA compliance, AI voice agent comparisons, and early member engagement.
• Competitor comparison tab — Add to organic analysis document using SpyFu data on Glia and other top competitors.
• "Glia Alternative" blog post — High-intent, low-competition organic opportunity.

Tier 3 — Longer-Term (Public Organic Pages)

• Public-facing use case pages (Collections, Dormancy, Member Engagement) built from journey draft content.
• Knowledge Base feature section on Voice Agent page.
• ROI Calculator as public lead magnet (email gate) — after internal sales tool is validated.

Keyword-to-Page Mapping (Summary)

Action Items

• [ ] Build Miro sitemap/nav board; share with Aaron and Justin (@Sebastian Gant)
• [ ] Build blog topic calendar from keyword data; share with Aaron and Justin (@Sebastian Gant)
• [ ] Add competitor comparison tab (SpyFu data) to organic analysis doc (@Sebastian Gant)
• [ ] Publish journey drafts (Collections, Dormancy, New Member) as hidden pages with logos, AUM, and member count (@Sebastian Gant)
• [ ] Send client logos (SVG) + AUM/member counts for journey pages (@Justin Dwyer)
• [ ] Reframe "New Member Onboarding" language to "early member engagement" across all assets (@Sebastian Gant)

Related

• ^[1]
• ^[2]
• ^[4]
• ^[5]