P2 Premium Features#

P2 is designed for websites managing multiple campaigns, specialized content formats, WooCommerce, or editorial workflows based on briefs and audits.

Advanced Campaign Templates#

What is saved#

Templates store campaign configurations such as category/author mode, status, planner, approval settings, Brand Voice, target post type, mapping, and Content Briefs. Keyword queues, history, campaign IDs, and actual articles are not copied.

Saving a template#

1. Set up the source campaign with the desired configuration.
2. Go to NexaPress > Templates.
3. Enter a template name.
4. Select the source campaign.
5. Click Save Template.

Applying a template#

1. In the Templates table, select the target campaign.
2. Click Apply.
3. Open the target campaign and review all fields.
4. The target campaign's existing keywords are preserved.

Applying a template overwrites the configurations included in that template. Create a backup or export the data if the old configuration needs to be preserved.

Export and import#

Exporting generates a JSON file with the following schema:

{
"schema": "nexapress-campaign-template/v1",
"name": "Product Buying Guide",
"configuration": {}
}

To import, paste the complete JSON into the Import template box. NexaPress rejects unrecognized schemas, unsupported fields, unavailable post types, mismatched taxonomies, and out-of-bounds values.

Do not edit the JSON directly unless you understand the field structure. Do not include API keys, license keys, passwords, or other credentials in the template.

Custom Post Types and WooCommerce#

Functionality#

Campaigns can generate:

• WordPress Posts.
• Pages.
• WooCommerce Products (if WooCommerce is active).
• Public custom post types that have an admin UI.

Selecting Content Type#

1. Edit the campaign.
2. Select Content Type.
3. Fill in the mapping if necessary.
4. Save.
5. Run a test article.

If the target post type or plugin is disabled, NexaPress performs a safe fallback to post when the configuration is re-sanitized.

Custom field mapping#

The format is JSON: meta_name: data_source.

Allowed sources:

• title
• content
• summary
• keyword
• topics
• seo_title
• seo_description

Example:

{
"product_subtitle": "summary",
"primary_topic": "keyword",
"seo_teaser": "seo_description"
}

Mapping only writes post meta data; it does not automatically execute third-party plugin business logic. For WooCommerce, fields such as price, stock, gallery, downloadable product, variations, and attributes require additional WooCommerce configuration and should not be assumed to be populated solely by the AI-generated article.

Taxonomy mapping#

The format is JSON: taxonomy: source.

Allowed sources:

• keyword: campaign keyword.
• tags: tags from the article response.
• category: suggested categories from the response.

WooCommerce example:

{
"product_cat": "category",
"product_tag": "tags"
}

The taxonomy must be registered for the specific post type. Mapping a post taxonomy to a product taxonomy (or vice versa) will be rejected.

SEO Content Brief#

Purpose#

The brief establishes editorial parameters prior to content generation. It is submitted as a validated object to FastAPI and utilized for both the outline prompt and the individual section writers.

Fields#

How to create an effective brief#

Use concrete instructions:

Search intent: Commercial investigation
Outline:
- Compare three types of materials
- Explain costs and lifespan
- Provide a selection checklist
Entities: stainless steel, aluminum, powder coating
FAQ: at least three buyer questions
References: manufacturer specifications and official standards
Target length: 2200

Avoid contradictory briefs—for example, setting a 500-word target while mandating 20 lengthy sections. The brief guides structure and content, but it does not guarantee that the model can fulfill instructions that are impossible or conflict with safety guidelines.

Content Audit#

Purpose#

The Content Audit reads local data and displays signals that editors need to review. The audit does not automatically modify, delete, or apply "noindex" tags.

Findings#

How to use#

1. Go to NexaPress > Content Audit.
2. Review the findings for each article.
3. Click the title to open the editor.
4. Decide on an action based on intent and actual quality.
5. Use "Content Refresh" if a rewrite would help, then review the preview before applying changes.

The audit checks up to 500 of the most recent NexaPress content items per load and paginates results at 20 items per page. An absence of findings does not guarantee that an article is accurate or performing well.

The message "No findings. NexaPress content was checked, but none matched the current local audit rules." indicates that the query successfully scanned NexaPress content but found no instances of cannibalization, thin content, missing keywords, outdated content, or indexing failures based on current local rules. The Content Audit only displays articles with findings; articles in good standing do not appear as separate rows.