LeksaStudio Docs
ID EN
6 min readUpdated 4 Aug 2026

P1 Premium Features#

P1 features help teams manage when content is created, who reviews it, the writing style, and when old articles need updating. All P1 menu options adhere to license capabilities. Downgrading disables Premium functionality without accidentally deleting campaigns, profiles, audit workflows, or articles.

Content Planner#

Purpose#

The Content Planner restricts campaigns so they are only eligible to run on specific days and times. Campaign daily limits operate within the license quota; they do not increase the total quota.

Setup#

  1. Go to NexaPress > Campaigns.
  2. Edit a campaign.
  3. Enable Use this campaign schedule.
  4. Select the days (Monday–Sunday).
  5. Set the Start time and time zone.
  6. Set the Daily article limit.
  7. Save the campaign.
  8. Go to NexaPress > Planner to check the schedule and Eligible now status.

A campaign becomes eligible after the start time on the selected days, provided it still has keywords, has not exceeded the daily campaign limit, and has remaining server permissions/quota.

Example#

A campaign is set for Monday–Friday, 09:00, Asia/Jakarta, with a limit of 2. On Tuesday at 08:50, the campaign is not yet eligible. After 09:00, a maximum of two campaign articles can be successfully created that day, subject to available package quota.

Troubleshooting#

Check the Active status, time zone, server time, remaining keywords, quota, WP-Cron, and Content Planner capabilities.

Approval Workflow#

Purpose#

The Approval Workflow prevents campaign articles from being published immediately. Generated content is saved with a WordPress status of pending and enters the Editorial queue.

Usage#

  1. Edit a campaign.
  2. Enable Require approval before publishing generated articles.
  3. Run the campaign.
  4. Go to NexaPress > Editorial.
  5. Click the title to read and edit the article. 6. Select Approve & Publish if ready, or Reject if the item needs to be returned.

Each transition records the state, user/actor, UTC timestamp, and any notes provided. Approving changes the post status to "published." Rejecting removes the article from the pending-review queue but does not delete the article itself.

Team practices#

  • Authors create content, and editors verify facts.
  • Use specific reasons for rejection.
  • Double-check images, references, links, and disclosures.
  • Do not use "Approve" simply to clear the queue.

Brand Voice Profiles#

Purpose#

Brand Voice serves as supplementary instructions for the AI. The profile does not replace the main prompt or research facts; instead, it ensures consistency in tone, audience, terminology, forbidden words, and CTA direction.

Fields#

Field Suggested content
Name Brand/unit/audience name, e.g., LeksaStudio B2B
Tone Professional, warm, direct, technical, etc.
Audience Roles, knowledge level, reader needs
Preferred terminology Official terms; one per line or comma-separated
Forbidden terms Words that must not be used
Call to action CTA direction; not a URL or exaggerated promise

How to use#

  1. Go to NexaPress > Brand Voices.
  2. Fill in the profile details and click Save Brand Voice.
  3. Edit the campaign.
  4. Select the profile under Brand Voice.
  5. Save and run a test article.

Data is sent as brand_voice. FastAPI incorporates it into the outline prompt and writer prompt. Campaigns without a profile continue to use the standard workflow.

Example#

text
Tone: Professional, calm, and practical
Audience: MSME owners new to SEO
Preferred terminology: organic growth, content strategy
Forbidden terms: guaranteed success, guaranteed #1 ranking
CTA: Invite readers to perform a content audit

Content Refresh#

Purpose#

Content Refresh uses AI to re-draft a published NexaPress article without immediately overwriting the original. The system saves a preview and a source hash, allowing editors to compare the current version with the proposed new version beforehand.

How to use#

  1. Go to NexaPress > Content Refresh.
  2. Locate the article and click Generate AI Refresh Preview.
  3. The message Generating refresh preview in the background indicates the request has been queued. You may close or reload the page; WP-Cron will continue the process.
  4. Monitor the process under NexaPress > Logs. Rows with the code content_refresh show the status: queued, processing, success, or failed. Upon success, click View refresh preview from the log or View Refresh Preview from the Content Refresh list.
  5. On the preview page, compare the title, current article content, AI output, word count, word count difference, AI mode, and remaining quota.
  6. Click Apply Refresh & Update Published Post only if the changes are correct.

The button becomes available again after the page reloads, as multiple previews can be generated for a single article. Selecting Generate New AI Preview replaces the saved preview with the latest proposal; this action does not apply the content to the article itself.

Upon applying:

  • The plugin verifies that the article has not changed since the preview was generated.
  • A WordPress revision is created first.
  • The title and content are updated.
  • The refresh timestamp is saved for Analytics/Audit purposes.
  • The temporary preview is deleted.
  • You are redirected to the WordPress editor for a final check. At this stage, the new title and content have already been inserted into the article.

If the article is edited after the preview is generated, the "Apply" action is rejected. Generate a new preview to avoid overwriting the editor's changes.

Quota and security#

The refresh function utilizes the AI ​​Content API based on your selected mode and entitlement. Under Default AI, each successful preview consumes one article quota; generating a new preview for the same article uses a new quota unit. Requests that fail before generating a preview are released according to the quota reservation mechanism. Under BYOK, the process uses your own API key and does not deduct from the Default AI quota. The source URL must be accessible to the Content API. Production environments use a secure public host, whereas development environments require an explicitly allowed origin. Clicking Apply does not consume additional AI quota, as it merely applies a previously saved preview.

Content Analytics#

Purpose#

Analytics provides a local operational summary; it is not a substitute for Google Analytics or Search Console.

Current metrics:

  • Generated: content with campaign metadata.
  • Published: NexaPress content with "published" status.
  • Awaiting approval: content in a "pending review" state.
  • Refreshed: content that has undergone Content Refresh.

Use these metrics to monitor the production workflow. Traffic, impressions, clicks, conversions, and rankings require external analytics or search services.