Docs Niche Taxonomy

Niche Taxonomy

Target the right audience with structured niche context that guides AI generation.

What Is a Niche Taxonomy?

A niche in Contento pSEO is a structured topic definition that tells the AI generator exactly who the target audience is, what problems they face, how they monetize, and what subtopics to cover. Niches are the vertical axis of the content matrix: when you create a collection, the engine cross-multiplies your chosen niches with the content schema to produce unique pages for each niche + subtopic combination.

A well-defined niche ensures that generated content is specific, relevant, and keyword-targeted rather than generic. The niche context is injected directly into the AI prompt, steering tone, examples, and recommendations toward the correct audience.

The 8 Niche Categories

Contento ships with 150 niches organized into 8 top-level categories:

Category	Example Niches	Count
Software / SaaS	Developer Tools, Project Management, CRM, DevOps, API Platforms	~25
Content Creation	Blogging, Podcasting, Video Production, Newsletter Growth, Social Media	~20
E-Commerce	Dropshipping, Print on Demand, Amazon FBA, Shopify Apps, Marketplace Selling	~20
Professional Services	Legal Tech, Accounting SaaS, HR Platforms, Consulting Tools, Freelancing	~18
Health & Wellness	Fitness Apps, Telehealth, Mental Health, Nutrition Tracking, Sleep Tech	~18
Finance	Personal Finance, Crypto, Investing Platforms, Insurtech, Neobanking	~18
Education	EdTech, Online Courses, Language Learning, Coding Bootcamps, LMS Platforms	~16
Local Business	Restaurants, Real Estate, Home Services, Auto Repair, Salons & Spas	~15

Niche Context Structure

Each niche stores a context JSON object with these fields, which are injected into the AI prompt during generation:

Field	Type	Description
`audience`	string	Who the content is for (e.g., "SaaS founders and product managers")
`pain_points`	string[]	Top 3-5 problems the audience faces
`monetization`	string[]	How products in this niche make money (e.g., "freemium", "per-seat SaaS")
`content_that_works`	string[]	Content formats that perform well (e.g., "comparison posts", "tool roundups")
`subtopics`	string[]	10-30 specific subtopics for cross-product expansion

System Niches vs. Custom Niches

The 150 built-in niches are system niches — read-only, maintained by Contento, and updated with new releases. You can use them as-is or fork them for customization.

System niches — Pre-defined, read-only. Updated automatically on upgrade.
Custom niches — Created by you. Full control over all fields including context.
Forked niches — A copy of a system niche that you can edit. The original is preserved.

Forking a Niche

To customize a system niche without losing the original, run contento niches fork <id>. A new custom niche is created with the same context data; edit it with contento niches edit and reference it by its new ID in your collections.

$ contento niches fork niche_01... --name "My DevTools"
  ✓ Forked "Developer Tools" as "My DevTools" (niche_4f2a...)

$ contento niches edit niche_4f2a... --add-subtopic "WASM toolchains"
  ✓ Subtopic added (21 total)

Custom niches are stored locally in ~/.contento/niches/ as plain JSON — you can edit the files directly or commit them to a repo for team use.

Creating a Custom Niche

Create a niche from scratch via the CLI:

# Create a custom niche via the CLI
contento niches list --category "Software"
contento niches fork --id niche_01... --name "Custom DevTools"

# Full niche JSON structure (shown with --json flag):
contento niches list --id niche_01... --json

{
    "name": "Developer Tools",
    "slug": "developer-tools",
    "category": "Software / SaaS",
    "context": {
      "audience": "Software developers, DevOps engineers, and engineering managers building production applications",
      "pain_points": [
        "Too many tools with overlapping features",
        "Difficulty evaluating tools without lengthy trials",
        "Integration complexity across the development stack",
        "Cost justification to management for developer tooling",
        "Keeping up with the rapidly evolving ecosystem"
      ],
      "monetization": [
        "Freemium with usage-based pricing",
        "Per-seat SaaS subscriptions",
        "Open-source with paid cloud hosting",
        "Enterprise license tiers"
      ],
      "content_that_works": [
        "Tool comparison posts (X vs Y)",
        "Curated best-of lists by use case",
        "Getting started tutorials",
        "Integration guides",
        "Annual state-of-the-ecosystem roundups"
      ],
      "subtopics": [
        "API testing tools",
        "CI/CD pipelines",
        "code review platforms",
        "container orchestration",
        "database management tools",
        "debugging tools",
        "dependency management",
        "feature flag platforms",
        "IDE extensions",
        "infrastructure as code",
        "logging and monitoring",
        "low-code development",
        "open source alternatives",
        "performance profiling",
        "secret management",
        "serverless frameworks",
        "static analysis tools",
        "terminal emulators",
        "version control hosting",
        "workflow automation"
      ]
    }
  }

Example: Full Niche JSON

Here is the complete structure of the Developer Tools system niche as returned by the API:

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "name": "Developer Tools",
  "slug": "developer-tools",
  "category": "Software / SaaS",
  "isSystem": true,
  "context": {
    "audience": "Software developers, DevOps engineers, and engineering managers",
    "pain_points": [
      "Too many tools with overlapping features",
      "Difficulty evaluating tools without lengthy trials",
      "Integration complexity across the development stack",
      "Cost justification to management for developer tooling",
      "Keeping up with the rapidly evolving ecosystem"
    ],
    "monetization": [
      "Freemium with usage-based pricing",
      "Per-seat SaaS subscriptions",
      "Open-source with paid cloud hosting",
      "Enterprise license tiers"
    ],
    "content_that_works": [
      "Tool comparison posts",
      "Curated best-of lists",
      "Getting started tutorials",
      "Integration guides"
    ],
    "subtopics": [
      "API testing tools",
      "CI/CD pipelines",
      "code review platforms",
      "container orchestration",
      "database management tools",
      "debugging tools",
      "dependency management",
      "feature flag platforms",
      "IDE extensions",
      "infrastructure as code",
      "logging and monitoring",
      "low-code development",
      "open source alternatives",
      "performance profiling",
      "secret management",
      "serverless frameworks",
      "static analysis tools",
      "terminal emulators",
      "version control hosting",
      "workflow automation"
    ]
  },
  "createdAt": "2026-01-15T00:00:00Z",
  "updatedAt": "2026-01-15T00:00:00Z"
}

CLI Commands

Command	Description
`contento niches list`	List all niches (filterable by --category, --search)
`contento niches view <id>`	View niche details with full context
`contento niches fork <id>`	Fork a system niche for customization
`contento niches create`	Create a custom niche
`contento niches edit <id>`	Edit a niche (subtopics, keywords, audience)

See the CLI reference for all available flags and options.