GuideCurrent Aomark Writer help

Manage a Writer batch while keeping review in control

Aomark Writer · Updated September 28, 2026

Prepare topics in a spreadsheet, import the batch, track job states, and review each article before delivery.

Prepare the spreadsheet

Use Writer → Import and Download Template so the batch follows the current column names. Each row needs primary_keyword. Optional fields can define h1, secondary_keywords, headings, category, tags, slug, scheduled_at, word_count, content_type, tone, audience_level, and writing_rules. Choose fields that make the article brief clearer: for instance, a specific h1 and audience level can help distinguish two related topics. These fields guide a job; they do not replace source material or editorial review.

  1. Choose the destination site and check its default content style.
  2. Enter one primary_keyword per row and add only fields that apply to the article.
  3. Review dates, slugs and taxonomy against the destination site's conventions.

Import and inspect the response

Upload the CSV or XLSX on the Import page. Read the Hub's response for the result of the upload, then inspect the jobs that appear in Writer. This catches a wrong site, missing topic or unintended article setting before you move on to generation or scheduling. Content Style defaults to the selected site's style and can be overridden for the batch; output language comes from Site Settings.

  1. Upload the prepared file to the selected site.
  2. Read the Hub response and note any rows or fields that need attention.
  3. Open the resulting jobs and confirm the topic, site, content style and intended settings.

Track work by status

Use the Writer list's site selector, search, status filter and sort controls to monitor Draft, Generating, Generated, Scheduled, Published and Failed jobs. For example, filter to Generated when you are ready to review content, or to Failed when a job needs attention. List supports selecting rows; Calendar displays scheduled jobs by date and opens Review. Use these views to find work, while making article decisions in each job's Review screen.

  1. Filter to the site and status relevant to the batch.
  2. Search or sort to locate the intended job.
  3. Open Review for each article that is ready for editorial work.

Review before delivery

Batch preparation makes jobs easier to organize, but each article still needs an accuracy and quality review before it is sent to WordPress. Check the body, SEO fields, image, taxonomy, slug and schedule against that row's brief. A scheduled job's time uses the selected site's timezone; after choosing a date, use Calendar and the job details to check the displayed time and status.

  1. Review the body and correct claims or omissions.
  2. Save SEO fields and confirm Details for the destination.
  3. Choose draft, schedule or publish only after confirming the intended outcome for that article.

Handle failures deliberately

Use the Failed filter to locate jobs that need attention. Open the job and read its current status and message, then check the part of the workflow named by the message. A problem with an imported field may need a different correction from a problem delivering to WordPress. The delivery panel offers resend actions; confirm the status after retrying the action you intended.

  1. Open a failed job and read its current status and message.
  2. Check the destination, article fields and connection status relevant to that message.
  3. Retry only the affected action after addressing the reported problem, then confirm the updated status.

Continue with a focused tutorial

Import article jobs from a spreadsheet

Find and filter Writer jobs

Schedule an article job

Browse more guides · Explore Aomark SEO Writer

Related reading

Let’s build what’s next

Tell us about
your project.

A good conversation starts with a little context. Fields marked * are required.

Tell us about your business and what you want to improve. Please do not include passwords or private customer information.

Prefer email? contact@aomarkdigital.com

The conversation starts here

Thank you.
We’re on it.

Explore our work