Post Generation History

The Post Generation History acts as the definitive ledger for all editorial activities initiated through the AI Content Generation Wizard. This specialized interface provides administrators and content managers with a transparent, chronological record of every article, page, or custom post type produced by the AI engine. By maintaining a centralized log, the Antimanual plugin ensures that users can audit their content production pipeline, track resource utilization, and maintain high standards of editorial consistency.

Table of Contents

• Accessing the History Log
• Data Columns and Information Architecture
• Content Management and Actions
• Optimizing Workflow with Historical Data
• Frequently Asked Questions

Accessing the History Log

To access your generation records, navigate to the Antimanual dashboard and select the Generated Posts tab within the Content Generation module. This view is distinct from the standard WordPress “Posts” list as it filters specifically for items that originated from an AI-driven prompt. This separation is vital for teams that mix manual authorship with automated content production, allowing for isolated performance audits.

Data Columns and Information Architecture

The history interface is organized into a detailed list table designed for rapid scanning and data retrieval. Each entry contains specific metadata that helps you identify the context of the generation. Understanding these columns is essential for managing a high-volume content strategy:

• Title: The primary headline generated for the post. Clicking the title provides a direct link to the WordPress editor.
• Date: A precise timestamp of when the AI completed the generation process. This helps in tracking output frequency over weeks or months.
• Status: Displays the current state of the document (e.g., Draft, Pending, or Published). This is synchronized with the core WordPress post status.
• AI Model: Identifies which specific large language model was used for that task, such as GPT-4 or Gemini 1.5 Pro. This is useful for comparing the quality of output between different providers configured in your .

Content Management and Actions

Beyond simple record-keeping, the Post Generation History facilitates direct management of your assets. The Action column provides functional shortcuts to streamline your editorial workflow. Instead of navigating the main WordPress admin menu, you can perform the following tasks directly from the history log:

• Quick View: Opens a preview of the generated content to verify formatting and SEO structure.
• Edit: Launches the Gutenberg editor immediately, allowing you to refine the AI’s output, add internal links, or adjust images.
• Trash/Delete: Allows for the removal of unsuccessful generations or redundant drafts to keep the database clean.

When an article is created, it often follows the parameters set during the phase. If you notice consistent formatting issues in your history, it may indicate a need to adjust your global Tone and Style settings.

Optimizing Workflow with Historical Data

High-level users leverage the history log to conduct A/B testing on content quality. For example, by generating two posts on similar topics using different models (e.g., one with GPT-3.5 and one with GPT-4), the history log allows you to quickly access both for a side-by-side comparison. This data-driven approach ensures that you are utilizing the most cost-effective AI provider for your specific niche.

Furthermore, the history serves as a backup reference. If a scheduled post fails to publish due to server issues, the log identifies the “Pending” status, enabling manual intervention before the content cycle is disrupted. For more advanced scheduling features, refer to the documentation on .

Frequently Asked Questions

Does deleting a post from the WordPress ‘All Posts’ menu remove it from the Antimanual History?

No. The history log maintains a record of the generation event itself. However, the ‘Status’ column will update to reflect that the post has been moved to the trash or deleted from the site.

Can I see which user initiated the generation?

The current version of the history log tracks the global generation tasks. For multi-author environments, the post author assigned during the wizard steps is the primary indicator of ownership.

How many entries can the history log store?

There is no hard limit to the number of historical entries stored; however, for optimal dashboard performance, it is recommended to periodically clear logs for content generated more than six months ago.