SEO Department

A complete SEO department you can clone as a Kortix project. It comes with five agents, five SEO-specific skills, persistent SEO memory, and a set of scheduled workflows that cover the day-to-day operating rhythm of a serious organic growth team.

What you get

  • seo-director: owns strategy, triage, reporting, prioritization, and approval gates.
  • technical-seo: audits crawlability, indexation, schema, performance, sitemaps, robots, redirects, and internal links.
  • content-strategist: turns keyword and performance signals into briefs, refresh plans, editorial backlog items, and publish-ready drafts.
  • serp-analyst: watches competitors, SERP features, brand terms, snippets, and material ranking movement.
  • seo-repo-watchdog: monitors PRs, pushes, route changes, metadata, schema, redirects, sitemaps, robots, content templates, and rendering changes for SEO regressions before they ship.
  • Schedules: daily SERP watch, weekly technical audit, weekly content refresh, daily repo SEO sweep, monthly growth report, plus inbound request and repo webhooks.
  • Skills: seo-operating-system, technical-seo-audit, seo-repo-monitoring, content-seo-workflow, and serp-intelligence.

After cloning

  1. Start the setup session. The installed files are the SEO department's operating system; your company still needs to bring its real website context. The setup agent reads install.md for the template-specific install guide.
  2. Give the director the core inputs: primary domain, target market, website repository, default branch, CMS/content source, analytics/Search Console, priority pages, competitors, brand terms, and approval channel.
  3. Connect the data sources you use: GitHub/repository access, Google Search Console, analytics, CMS, Slack/Teams, and any rank-tracking or crawl provider. Set SEO_PRIMARY_DOMAIN, SEO_REPO_URL, and SEO_DEFAULT_BRANCH.
  4. Read .kortix/memory/SEO.md and fill in the starting ICP, priority markets, key product pages, and current SEO constraints.
  5. Wire repository PR/push events to the repo-seo-watch webhook and set SEO_REPO_WEBHOOK_SECRET if you want automatic code review. Leave it off if you only want scheduled sweeps.
  6. Turn on the triggers in kortix.yaml once the connectors are ready.
  7. Ask the director for a kickoff: "Build the first 30-day SEO plan for our domain and tell me what needs approval."

Company Intake

The first session should not be a blank chat. Ask the director to set up the SEO department and it will request the repo and private data sources, mint setup links for missing connectors/secrets, and fall back to a public-data audit if some access is not ready yet. Setup happens in that same install session; the specialist agents are future operating roles and trigger targets, not extra setup sessions to spawn.
When adding this template into an existing project, the template files first land through a change request. The installer should ask to apply that CR and, after approval, start the first seo-director setup session from the merged main branch instead of leaving the user to do that handoff manually.

Safety model

The department can research, audit, draft, report, and open change requests by default. It does not publish live content, change production SEO settings, contact external sites for outreach, buy tools, or alter paid campaigns without explicit approval or a project-level policy that says it may. The repo watchdog can comment, report, draft fixes, and open change requests, but it never merges or pushes directly to the default branch.
Skills6
deep-research

Deep research agent skill. Use when the user needs thorough, scientific, truth-seeking research on any topic -- investigating claims, finding primary sources, synthesizing evidence, producing cited reports. Triggers on: 'research this', 'investigate', 'deep dive', 'find sources', 'what does the evidence say', 'literature review', 'fact check', 'analyze the research on', any request requiring multi-source investigation with citations.

search

Find and read information on the open web — fan-out web/news/finance search plus full-page fetching and source extraction. Use to answer current questions, gather and cite sources, verify a claim, or pull text from specific URLs. Triggers: 'search the web', 'look this up', 'find sources on', 'what's the latest on', 'fetch this page', 'is it true that…', 'compare X vs Y'.

research-report

Use for writing substantial research reports in markdown with inline citations, tables, and optional charts. Best when the user wants a deliverable file plus a concise chat summary.

xlsx

Use for spreadsheet creation, analysis, financial models, and polished workbook outputs.

website-building

Use for distinctive production-grade websites, landing pages, and interactive web experiences with strong design and QA discipline.

web-publishing-and-deployments

Publish a website or web app from the sandbox to a public URL, and deploy to cloud providers — get a live link to share, ship a static site or SPA, put a built site online, or deploy a framework app / container. Use when the user says 'publish this', 'deploy it', 'put it online', 'give me a live URL', 'host this', 'share a preview link', or wants to make a site/app they (or you) just built reachable on the web. Covers the zero-account instant path (Cloudflare) and permanent hosting (Vercel, incl. any Dockerfile), and points at find-skills-sh for other providers and deeper provider-specific skills.

Agents5
seo director

Runs {{projectName}} as a full SEO department lead: company onboarding, strategy, triage, prioritization, reporting, and approval-safe execution across repo monitoring, technical SEO, content, and SERP intelligence.

technical seo

Technical SEO specialist for {{projectName}}: crawlability, indexation, performance, schema, redirects, sitemaps, robots, canonicals, and implementation-ready fixes.

content strategist

Content SEO lead for {{projectName}}: topic strategy, briefs, content refreshes, internal linking, editorial backlog, and publish-ready drafts.

serp analyst

SERP intelligence analyst for {{projectName}}: competitor movement, SERP features, brand protection, snippets, intent shifts, and opportunity alerts.

seo repo watchdog

Repo-aware SEO watchdog for {{projectName}}: reviews pull requests, pushes, routes, metadata, schema, redirects, sitemaps, robots, content templates, and performance-sensitive code before SEO regressions ship.

Triggers7
seo request intake

Turns an inbound stakeholder request into an SEO plan, brief, audit, or approval-ready task.

daily serp watch

Monitors target topics, competitors, brand terms, snippets, and material ranking changes.

weekly technical audit

Checks crawlability, indexation, performance, schema, sitemaps, robots, redirects, and internal links.

repo seo watch

Reviews PR and push events for SEO regressions before route, metadata, sitemap, robots, redirect, schema, or rendering changes ship.

daily repo seo sweep

Checks the default branch for newly shipped SEO-affecting code and keeps the repo SEO ledger current.

weekly content refresh

Finds decaying pages, prepares briefs, updates content candidates, and keeps the editorial backlog sharp.

monthly seo growth report

Produces the executive SEO report: wins, losses, risks, roadmap, and next-month commitments.

Other projects1
Kortix Starter

The default Kortix project — a general knowledge worker preloaded with the full skill kit (research, documents, slides, spreadsheets, the web, and more), ready to work from the first session.

Kortix · 88 skillsInstall
SEO Department — Kortix Marketplace | Kortix