How Agents Run SEO Keyword Research Loops

An SEO agent that only drafts blog titles from memory misses the part buyers pay for: fresh keyword volume, live SERP competitors, and difficulty signals tied to each customer account. Naïve gives multi-tenant products the AgentSEO primitive (/seo) so a research loop runs on governed data instead of a shared scraper key in a prompt.

This guide shows a keyword research loop you can run per tenant: seed topic in, structured opportunity out — scoped with naive.forUser(clientId), compatible with usage-metered plans, and wired into the broader autonomous company model (Company → Employee → Primitive).

Loop architecture

Each step uses the same tenant scope. If you also run AEO brand tracking, add a parallel branch with /aeo after step 4.

Setup

npm install @usenaive-sdk/server

import { Naive } from "@usenaive-sdk/server";
 
const naive = new Naive({ apiKey: process.env.NAIVE_API_KEY! });

Provision the customer once:

const client = await naive.users.create({
  external_id: "acme_corp_uuid",
  email: "seo@acme.example",
  label: "Acme Corp",
});

Use naive.forUser(client.id) for every SEO call in the loop.

The loop

async function runKeywordResearchLoop(tenantId: string, seed: string) {
  const seo = naive.forUser(tenantId).seo;
 
  const volume = await seo.searchVolume([seed, `${seed} software`, `${seed} platform`]);
  const competitors = await seo.serpCompetitors([seed]);
  const overview = await seo.labs("google", "keyword-overview", { keywords: [seed] });
 
  return {
    seed,
    volume,
    competitors,
    overview,
    generatedAt: new Date().toISOString(),
  };
}

• Signatures match the seo sub-client.
• CLI equivalent for debugging: naive seo keywords google search-volume --keywords "<seed>" --location-code 2840.
• Credit costs per endpoint are listed on the SEO getting-started page.

Scheduling and orchestration

Run the loop on a cron, a queue worker, or your orchestration employee:

1. Cron — nightly refresh for every active tenant.
2. Event-driven — customer adds a new seed keyword in your UI.
3. CEO agent — kanban task "Research Q3 content cluster" dispatches the loop per brand.

Log each run in your app and optionally attach Naïve audit logs for compliance.

Multi-tenant and metering

For a SaaS product, the loop is identical for every customer; only tenantId changes. When you sell tiers:

• Enable /seo per tier via Account Kits.
• Cap calls per month via Customer Billing quotas — the 2001st searchVolume returns 429 rate_limited, not a silent overage.

See How to Build a Usage-Metered AI SEO SaaS for the full billing wiring.

Related reading

• Introducing AgentSEO — primitive overview
• Build a multi-tenant AEO platform — SEO + AEO together
• Track brand mentions in AI search — companion AEO loop
• SEO docs