OctiAI

Categories

Enterprise Topical Authority Content Plan

Turn seed keywords and ICP into pillar pages, supporting content, and an internal linking graph for enterprise SEO.

What You'll Get

How to Use

Align CTAs with funnel stage

Match each page's primary CTA to its funnel stage (TOF, MOF, BOF). Use demo/POC CTAs only on MOF/BOF pages to protect conversion goals and follow your enterprise sales process.

Works Best With

One-shot topical-map prompts for enterprise GTM

Prompt Template


## Goal
Generate a machine-readable, conversion-focused topical map and prioritized internal-link graph for a B2B SaaS product targeting US enterprise buyers. Output must be JSON only, containing topic clusters, pillar/support pages, mapped search intent (TOF/MOF/BOF and informational/commercial/transactional), SEO title/meta/slug, primary CTA with conversion priority, and internal-link edges.

## Inputs
- Niche: {{niche}}
- ICP (enterprise personas): {{icp_enterprise_personas}}
- Region: US
- Seed keywords (comma-separated list): {{seed_keywords}}
- Monetization / go-to-market goals: {{monetization_goals}}
- Competitors (2-3 names): {{competitors}}
- Content / brand constraints (tone, compliance, forbidden claims, length limits): {{content_constraints}}

## Prompt
You are an expert B2B SaaS SEO strategist and content architect with enterprise GTM experience. Using the Inputs above, produce a single JSON object and nothing else. Follow these rules exactly:

1. Target audience: US enterprise buyers defined by {{icp_enterprise_personas}}. Optimize for lead generation, product-qualified-lead (PQL) conversion, and enterprise demo/POC requests tied to {{monetization_goals}}.
2. Use only facts from the Inputs; do not invent competitor details or market claims.
3. Build a topical map with prioritized clusters focused on the seed keywords {{seed_keywords}} and adjacent enterprise search demand relevant to {{niche}}.
4. Output must include:
   - clusters array: each cluster has id, name, overall_priority (High/Medium/Low), pillar_page, supporting_pages.
   - Each page object (pillar + supporting) must include: title (SEO title, ≤60 chars), meta_description (≤155 chars), url_slug (kebab-case, ≤60 chars), mapped_intent (informational/commercial/transactional), funnel_stage (TOF/MOF/BOF), primary_cta (one short phrase), conversion_priority (1-5 integer, 1 highest), recommended_internal_links (list of link edges from this page).
   - internal_link_graph: list of edges with source_slug, target_slug, anchor_text, priority (1-5).
5. Structural constraints:
   - Generate 3-8 clusters. Each cluster: 1 pillar_page and 3-8 supporting_pages.
   - Ensure distribution of funnel stages across site: at least 40% informational/TOF, at least 20% commercial/MOF, at least 10% transactional/BOF.
   - Title and meta lengths: enforce character limits above.
   - URL slugs must be unique and use only lowercase letters, numbers, and hyphens.
   - All mapped_intent values limited to: informational, commercial, transactional.
   - All funnel_stage values limited to: TOF, MOF, BOF.
6. Internal-linking:
   - Produce edges connecting supporting → pillar (primary), pillar → related pillar(s) where relevant, and cross-support links where they aid conversion flow.
   - Each edge must reference slugs that appear in the pages objects.
   - Prioritize links that drive enterprise CTAs (demo, POC, pricing, contact) and annotate conversion_priority impact.
7. Sort clusters by overall_priority (High → Low). Within each cluster, sort pages by conversion_priority ascending (1→5).
8. Use competitor names only as content/angle constraints; do not claim features unless provided.
9. Abide by content constraints in {{content_constraints}} (tone/compliance/forbidden claims).
10. Return JSON only. Do not include analysis, commentary, or extra fields.

Insert the Inputs values into the JSON output metadata and then produce the clusters and internal_link_graph.

## Output Format
Return a single JSON object with this exact structure and key names. Follow types precisely.

{
  "niche": "string",
  "region": "US",
  "icp": "string",
  "seed_keywords": ["string"],
  "monetization_goals": "string",
  "competitors": ["string"],
  "content_constraints": "string",
  "clusters": [
    {
      "id": "string (unique)",
      "name": "string",
      "overall_priority": "High|Medium|Low",
      "pillar_page": {
        "title": "string (≤60 chars)",
        "meta_description": "string (≤155 chars)",
        "url_slug": "string (kebab-case ≤60 chars)",
        "mapped_intent": "informational|commercial|transactional",
        "funnel_stage": "TOF|MOF|BOF",
        "primary_cta": "string",
        "conversion_priority": 1,
        "recommended_internal_links": [
          {
            "source_slug": "string",
            "target_slug": "string",
            "anchor_text": "string",
            "priority": 1
          }
        ]
      },
      "supporting_pages": [
        {
          "title": "string (≤60 chars)",
          "meta_description": "string (≤155 chars)",
          "url_slug": "string (kebab-case ≤60 chars)",
          "mapped_intent": "informational|commercial|transactional",
          "funnel_stage": "TOF|MOF|BOF",
          "primary_cta": "string",
          "conversion_priority": 2,
          "recommended_internal_links": [
            {
              "source_slug": "string",
              "target_slug": "string",
              "anchor_text": "string",
              "priority": 2
            }
          ]
        }
      ]
    }
  ],
  "internal_link_graph": [
    {
      "source_slug": "string",
      "target_slug": "string",
      "anchor_text": "string",
      "priority": 1
    }
  ]
}

Ensure:
- Every slug referenced in internal_link_graph appears in clusters' pillar_page or supporting_pages.
- Character limits and enums are respected.
- JSON is syntactically valid and contains only the keys above (no extra commentary).

## Guardrails
- Do not hallucinate competitor product details, dates, or metrics.
- If seed keywords are sparse, expand with enterprise-focused long-tail variants but keep them relevant to {{niche}} and {{icp_enterprise_personas}}.
- Keep titles actionable and conversion-oriented; meta descriptions should summarize value and CTA.
- Use numeric conversion_priority (1 highest → 5 lowest) consistently.
- Do not produce HTML or explainers—JSON only.
- Validate uniqueness of url_slug values.
- Keep total supporting pages per cluster ≤ 8 and total clusters ≤ 8.
- If any input conflicts with constraints, prioritize compliance (e.g., shorten titles) and note nothing—still output JSON only.

## Examples
Minimal JSON skeleton example (replace with real outputs when running):

{
  "niche": "{{niche}}",
  "region": "US",
  "icp": "{{icp_enterprise_personas}}",
  "seed_keywords": ["{{seed_keywords}}"],
  "monetization_goals": "{{monetization_goals}}",
  "competitors": ["{{competitors}}"],
  "content_constraints": "{{content_constraints}}",
  "clusters": [
    {
      "id": "cluster-1",
      "name": "Cluster name",
      "overall_priority": "High",
      "pillar_page": {
        "title": "Pillar SEO title",
        "meta_description": "Pillar meta description",
        "url_slug": "pillar-url-slug",
        "mapped_intent": "commercial",
        "funnel_stage": "MOF",
        "primary_cta": "Request demo",
        "conversion_priority": 1,
        "recommended_internal_links": [
          {
            "source_slug": "pillar-url-slug",
            "target_slug": "supporting-page-1",
            "anchor_text": "Learn about X",
            "priority": 1
          }
        ]
      },
      "supporting_pages": [
        {
          "title": "Supporting page title",
          "meta_description": "Supporting meta",
          "url_slug": "supporting-page-1",
          "mapped_intent": "informational",
          "funnel_stage": "TOF",
          "primary_cta": "Download guide",
          "conversion_priority": 3,
          "recommended_internal_links": [
            {
              "source_slug": "supporting-page-1",
              "target_slug": "pillar-url-slug",
              "anchor_text": "See enterprise solution",
              "priority": 1
            }
          ]
        }
      ]
    }
  ],
  "internal_link_graph": [
    {
      "source_slug": "supporting-page-1",
      "target_slug": "pillar-url-slug",
      "anchor_text": "See enterprise solution",
      "priority": 1
    }
  ]
}

Variables

Usage Notes

Not for

Do not include

Enterprise Topical Authority Content Plan

Generate pillar & cluster pages, CTAs, funnel stages, and an internal link graph to build topical authority for enterprise sites.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

What you'll get

Output format

Markdown

Best used when

Avoid when

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Niche

Provide the key details needed for this variable.

Icp Enterprise Personas

Provide the key details needed for this variable.

Seed Keywords

Provide the key details needed for this variable.

Monetization Goals

Provide the key details needed for this variable.

Competitors

Provide the key details needed for this variable.

Content Constraints

Provide the key details needed for this variable.

Rules

Canonical Examples

Input: Niche: B2B SaaS - Supply Chain Risk Management; Region: US; ICP: Enterprise procurement leaders, CISOs, risk managers; Seed keywords: supply chain risk management, vendor risk score, third-party risk assessment, supplier risk monitoring; Monetization goals: drive product demos and POC requests; Competitors: Aravo, LogicGate, Coupa; Content constraints: Formal tone; no unverified claims; no pricing; enterprise-focused.

Loading result...

Failed to load output.


Pillar: vendor-risk-governance | Supports: vendor-risk-management-overview, third-party-risk-checklist, vendor-risk-score-methodologies, start-enterprise-poc

Why it works: Provides a realistic enterprise-focused topical map that prioritizes MOF/TOF content for procurement and risk teams, with a clear BOF path (POC) and strict constraints preserved.

Input: Niche: HR & Talent Management SaaS; Region: US; ICP: CHROs, HR Directors, Talent Leaders; Seed keywords: employee onboarding software, talent management system, HR analytics, employee lifecycle; Monetization goals: drive demos/POC for enterprise; Competitors: BambooHR, Workday, UKG; Content constraints: professional, data-backed, privacy-conscious.

Loading result...

Failed to load output.


Pillar: employee-onboarding-lifecycle | Supports: onboarding-software-overview, talent-management-overview, hr-analytics-essentials, start-enterprise-demo

Why it works: Offers an alternative enterprise GTM topical map centered on HR lifecycle and analytics, with a clear path to demos/POC while respecting privacy constraints.

Works Best With

One-shot topical-map prompts for enterprise GTM