---
title: 'AviaryAI: Thin Content Blocking Indexing'
type: article
created: '2026-02-04'
updated: '2026-02-04'
source_docs:
- raw/2026-02-04-aviaryai-weekly-call-119843123.md
tags:
- seo
- thin-content
- indexing
- webflow
- client:aviaryai
layer: 2
client_source: null
industry_context: null
transferable: true
---

# AviaryAI: Thin Content Blocking Indexing

## Overview

As of early February 2026, AviaryAI's website had near-zero organic traffic (~5 visits/month) and only 2 indexed keywords. The root cause was identified as thin content: core pages contained fewer than 200 words of text, which falls below Google's threshold for indexing. This article documents the diagnosis, remediation plan, and constraints identified during the [[wiki/clients/aviaryai/_index|AviaryAI]] engagement.

## Root Cause

Google requires a minimum content density to consider a page worth indexing. Pages with fewer than ~300 words are typically treated as thin content and excluded from the index entirely. AviaryAI's Webflow site was built with a visually rich, scroll-based design that prioritized aesthetics over text content — resulting in pages that rendered well but contained almost no indexable copy.

> "There's not even 200 words on this page. So unless we get over 300, we won't even get it to index." — Mark Hope, 2026-02-04 call

This is a common pattern with modern no-code/CMS sites where design-first workflows deprioritize body copy.

## Competitive Context

A competitor analysis covering Glia, Posh, and Interface revealed that AviaryAI's competitors face similar thin-content problems. Most competitors rank primarily for their own brand name and generic banking keywords, with minimal presence on use-case-specific terms. This creates a meaningful opportunity: AviaryAI can capture use-case keyword traffic that competitors have not targeted.

## Remediation Plan

### 1. Expand Core Page Copy

Add 300+ words of relevant, keyword-informed text to each core page. This is the minimum threshold to make pages eligible for Google indexing. The goal is not to rank immediately but to remove the indexing blocker.

### 2. Launch a Keyword-Targeted Blog

Publish blog posts targeting long-tail keywords identified in the keyword research phase. Blog content should:

- Target terms that are not primary product/category keywords (to avoid cannibalization of future product pages)
- Address specific use cases where competitors have no presence
- Build domain authority incrementally

The existing blog had 4 posts at the time of the call; expanding this was identified as the fastest path to organic traffic growth.

### 3. Force a Google Crawl

After content is added, submit core pages for indexing via Google Search Console to accelerate discovery rather than waiting for the natural crawl cycle.

## Site Structure Constraints

Not all pages are available for restructuring. The following constraints were established by the AviaryAI team:

| Page | Status |
|---|---|
| Homepage | **Off-limits** — structure and messaging to remain consistent |
| Safety & Security page | **Off-limits** — no major structural changes |
| All other pages | **Fair game** for restructuring and content expansion |

The homepage is intentionally focused on the voice agent product (not the knowledge base platform) to maintain a clear, simple narrative. Any SEO work must respect this positioning.

## Additional Technical Issues

A separate but related issue was identified: the Webflow site had insufficient HTTP security headers (only an STS policy was in place). While not a direct indexing blocker, missing headers are a negative signal for Google and should be remediated. Standard Webflow deployments do not allow server-level header configuration via SSH, so the fix requires Webflow-specific approaches.

## Action Items (as of 2026-02-04)

- [ ] **Mark Hope** — Force crawl of core pages; audit content; add 300+ words to thin pages
- [ ] **Mark Hope** — Add security headers to Webflow site
- [ ] **Sebastian Gant** — Write first 1–2 keyword-targeted blog posts using mapped long-tail terms

## Generalizable Pattern

This situation is a common early-stage startup SEO failure mode: the site is built to convert visitors who already know the company, not to attract visitors who don't. Design-first Webflow builds frequently produce thin-content pages. The fix is straightforward but requires buy-in to add copy that may feel redundant to internal stakeholders who already know the product well.

**See also:**
- [[wiki/knowledge/seo/thin-content-remediation|Thin Content Remediation Playbook]]
- [[wiki/clients/aviaryai/2026-02-04-weekly-call|AviaryAI Weekly Call — 2026-02-04]]
- [[wiki/clients/aviaryai/_index|AviaryAI Client Overview]]