> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryprofound.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Article Title Suggestion node

> Generate an AEO-optimized article title from your topic, audience, and content goals

The **Article Title Suggestion** node generates an AEO-optimized, high-quality article title based on your topic, audience, and content goals. Unlike a simple LLM prompt, this node applies a structured, multi-step workflow to evaluate your inputs, apply editorial and SEO best practices, and output a single, strong title crafted for visibility, trustworthiness, and user intent match.

Add this node to your Workflows when you need reliable, polished titles that set up your content for success—whether for editorial planning, SEO, or Answer Engine Optimization.

## When to use this node

Use Article Title Suggestion for tasks such as:

* Quickly generating compelling, search-aligned titles before content production
* Developing titles that are optimized for AI answer engines and user prompts
* Testing variations of messaging for different audiences or company contexts
* Feeding optimized titles into downstream steps (e.g., content briefs or full articles)

This node is designed to be used early in a content strategy or creation workflow.

## Node configuration

Selecting the Article Title Suggestion node opens its configuration panel on the right side of the Workflow Builder.

### Topic (required)

Provide the subject or theme the article should cover, such as:

* “Emerging trends in healthcare technology”
* “How to optimize your Shopify store for conversion”
* “AI visibility strategy for enterprise brands”

This is the primary driver of the generated title.

### Content Type

Select the type of content the title should be optimized for, such as **General** (default), **Listcle, Blog Post,** and more.

The node adjusts tone, structure, and style based on this setting.

### Company Name

If provided, the title will account for brand context when relevant. This is useful when creating articles for a specific company blog or brand voice.

### Audience Segment

Specify the target audience for the content—e.g., “B2B marketing leaders,” “healthcare professionals,” or “startup founders.”

The node uses this to improve alignment, terminology, and specificity.

### Target Prompt

Enter the user prompt (as used in AI search or on-platform interaction) that your content should optimize for. This helps ensure that the title is directly tied to the way users pose questions or seek information, for example:

* “What is AI visibility and why does it matter for enterprises?”

### Output Label (required)

Assign a label for the generated title. This label becomes available to downstream steps, such as:

* [Create Content Brief](/agents/workflows/nodes/content-creation/create-content-brief)
* [Generate Article](/agents/workflows/nodes/content-creation/generate-article)
* [AEO Content Scorecard](/agents/workflows/nodes/content-optimization/aeo-content-scorecard)
* Custom Prompt LLM steps

## How the node works behind the scenes

Article Title Suggestion runs a multi-step workflow that evaluates your inputs and produces one optimized title. While this process is abstracted into a single step, the internal logic includes:

1. **Input evaluation**
   * The node checks whether inputs like company name, audience segment, or target prompts are provided.
   * It adjusts title generation logic accordingly (e.g., more generic if fields are blank).
2. **Context and metadata preparation**
   * Current-year or temporal context may be added when relevant for accuracy or search alignment.
   * Input variables are transformed or normalized for consistent title generation.
3. **Title generation logic**
   * A structured set of editorial, SEO, and AEO rules is applied, such as:
     * Ensuring clarity and authority
     * Avoiding exaggerated or misleading phrasing
     * Matching user intent and search demand
     * Maintaining strong keyword alignment
     * Producing titles appropriate for your audience segment
4. **Optimized variant selection**
   * If multiple internal candidates are produced, the node selects the strongest one based on clarity, engagement potential, and AEO alignment.
   * Only **one title** is returned to maintain consistency and support downstream workflows.

This workflow ensures titles are more consistent and high-quality than ad-hoc LLM prompt outputs.

## Output

The output is a **single AEO-optimized article title**, suitable for

* Direct use in content production
* Passing into a brief or article generation workflow
* Use in editorial calendars
* SEO or topic clustering workflows

## Example usage

### 1. Create an optimized title before generating a content brief

1. Add the **Article Title Suggestion** node.
2. Provide topic, target prompt, and optional audience and company name.
3. Set an output label (e.g., `title`).
4. Pass `title` into the [Create Content Brief](/agents/workflows/nodes/content-creation/create-content-brief) node.

### 2. Build a content pipeline

1. Article Title Suggestion → [Create Content Brief](/agents/workflows/nodes/content-creation/create-content-brief) → [Generate Article](/agents/workflows/nodes/content-creation/generate-article)
2. Add [AEO Content Scorecard](/agents/workflows/nodes/content-optimization/aeo-content-scorecard) afterward to evaluate the final article.

### 3. Generate multiple titles for testing

Duplicate the node with changes to Topic, Audience Segment, or Target Prompt to compare results.

## Best practices

* Include a **Target Prompt** when writing for AI-driven search; this increases intent alignment.
* Use **Audience Segment** for B2B or specialized verticals to ensure relevancy.
* Keep the **Topic** specific enough to guide the node but broad enough to allow creative generation.
* Downstream steps should reference the output label directly (e.g., for content brief creation).