# Paced Rollout Waves and Deterministic Recipe Solidification

Canonical URL: https://indexkeep.com/method/rollout-waves/
Author: Indexkeep Research | Published: 2026-11-20 | Snapshot: Niche 2026-10 traffic snapshot

> Distributing submissions across healthy multi-week waves while pairing deterministic DOM form recipes with Chrome MV3 human-in-the-loop completion.

## 1. Multi-Week Wave Pacing

        Indexkeep organizes target directories into scheduled weekly rollout waves:

        
          - **Wave 1 (Foundation & Launchpads):** Prioritize high-authority Tier S entities (Crunchbase, AlternativeTo, StackShare, SaaSHub) alongside primary developer and AI directories to anchor brand identity.

          - **Waves 2–4 (Vertical Expansion):** Schedule 12–20 vetted Tier A and Tier B directories per week matching product category tags and fee preferences.

          - **Steady-State Keep:** Monitor live receipts weekly, verify Google indexation, and sync copy drift as product versions ship.

        

        

## 2. Three-Tier Execution Model

        Directories differ sharply in authentication and anti-bot design. Indexkeep assigns each site to its natural execution layer:

        
          - **Auto Recipe:** Standard unauthenticated, CAPTCHA-free forms executed cleanly against versioned `DirectoryRecipe` definitions.

          - **Extension Assist (Chrome MV3 Side Panel):** Opens the active target tab, fills pre-adapted product copy from the workspace queue, and pauses smoothly when OAuth, payment, or human verification appears.

          - **Guided Manual Playbooks:** Side-by-side copy panels and submission checklists for flagship ecosystems including Product Hunt, G2, Capterra, Hacker News Show HN, and GitHub Awesome PRs.

        

        

## 3. Explore to Solidify Flywheel

        When onboarding an unfamiliar directory, browser exploration identifies form selectors, field semantics, and expected confirmation rules once to draft a deterministic JSON `DirectoryRecipe` v1 schema. Subsequent submissions across products reuse that deterministic recipe directly without per-run LLM inference, refreshing selectors only when DOM drift occurs.

## Key Notes
- Wave pacing: Week 1 foundational Tier S/A hubs, Weeks 2-4 12-20 vertical directories per week, followed by steady-state HTTP/rel/drift monitoring.
- Chrome MV3 security model: permissions=["storage","sidePanel","activeTab","scripting"] with zero wildcard host_permissions.

## Questions & Answers
### Why does Indexkeep pace directory submissions across weekly waves?
Multi-week rollout waves produce a natural backlink growth curve, keep email confirmation queues manageable, and allow teams to calibrate positioning after early Tier S feedback.

### What browser permissions does the Indexkeep Chrome extension require?
The WXT Manifest V3 extension requests only storage, sidePanel, activeTab, and scripting permissions, with an empty host_permissions list so tab inspection runs solely when explicitly triggered on the active directory tab.
