WordPress Content Management n8n SEO

Automatically Archive Old WordPress Posts to Draft Status

Maintain your blog's health and SEO by automatically moving old, published posts to draft status based on your criteria. Save hours of manual content review while keeping your site fresh and relevant.

Download Template JSON · n8n compatible · Free
WordPress post archiving workflow interface in n8n

What This Workflow Does

This automation solves a common challenge for WordPress site owners: managing content lifecycle efficiently. As blogs grow older, many published posts become outdated, irrelevant, or underperforming—yet manually reviewing and archiving them is time-consuming.

The workflow automatically identifies posts meeting your archiving criteria (like age or performance metrics) and changes their status from published to draft. This maintains your content history and SEO value while cleaning up your active content library. Unlike deletion, archiving preserves all post data for potential future updates or reference.

How It Works

1. Criteria Setup

The workflow starts by defining your archiving rules—typically based on publication date (e.g., posts older than 24 months) but can also incorporate performance metrics if integrated with analytics tools.

2. WordPress Query

Using the WordPress REST API, the system queries your site for posts matching your criteria. This happens on a schedule you set (weekly/monthly recommended).

3. Status Update

Each identified post has its status changed from "published" to "draft" through API calls. The workflow can optionally notify you of changes or log them for review.

Pro tip: Start with conservative criteria (e.g., archive only very old posts) and refine based on results. Always test with a small batch first.

Who This Is For

This automation benefits:

  • Blog owners with large archives of older content
  • Content teams managing multiple WordPress sites
  • SEO specialists optimizing site structure
  • Businesses maintaining knowledge bases or documentation

What You'll Need

  1. A WordPress site with REST API access
  2. Admin credentials to generate API keys
  3. n8n instance (self-hosted or cloud)
  4. Basic understanding of WordPress post statuses

Quick Setup Guide

  1. Download the JSON template file
  2. Import into your n8n instance
  3. Configure your WordPress API connection
  4. Set your archiving criteria (date range, categories, etc.)
  5. Test with a small batch of posts
  6. Schedule the workflow to run automatically

Key Benefits

Saves 5-10 hours monthly by eliminating manual content review and status updates. What typically takes days of sporadic work happens automatically.

Improves site quality by systematically retiring outdated content while preserving it for potential updates. Readers only see your most relevant material.

Maintains SEO value better than deletion. Archived posts can be updated and republished without losing backlinks or search rankings.

Creates content lifecycle management as part of your regular operations rather than an occasional cleanup project.

Frequently Asked Questions

Common questions about WordPress post archiving and automation

Archiving preserves your content history and SEO value while removing it from public view. Deleting posts can break links and lose valuable data. Draft status maintains the content for future reference or updates while cleaning up your active content.

For example, a marketing agency might archive old case studies that reference outdated pricing or services. The content remains available internally for reference or potential updating, but doesn't confuse current prospects.

  • Preserves internal knowledge base
  • Maintains URL structure for potential updates
  • Easier to restore than recreating deleted content

Common criteria include publication date (e.g., older than 2 years), low traffic/engagement metrics, or outdated information. The best approach combines age with performance data to identify posts that no longer serve your current audience effectively.

A tech blog might archive posts about discontinued software while keeping foundational programming concepts. Combining date filters with Google Analytics data ensures you retire truly obsolete content rather than evergreen material.

  • Start with simple date-based rules
  • Add performance filters after initial testing
  • Consider content type (news vs evergreen)

Archiving reduces database queries for public content while maintaining all post data. This can improve site speed slightly, especially for sites with thousands of posts. The main benefit is content organization rather than significant performance gains.

An ecommerce site with 5,000 product posts might see faster category page loads after archiving discontinued items. However, the primary advantage is presenting only current products to shoppers while keeping old data for reporting.

  • Reduces frontend query load
  • Minimal impact on backend storage
  • Biggest gains on large sites

Yes, advanced workflows can integrate Google Analytics or other tracking tools to archive posts with declining traffic. This creates a self-optimizing content system that automatically retires underperforming content while keeping your best material visible.

A news publisher could automatically archive articles receiving less than 100 monthly views after 6 months, while keeping high-performing pieces available longer. This data-driven approach continuously optimizes the reader experience.

  • Requires analytics integration
  • Allows dynamic content lifecycle rules
  • Creates self-improving content library

Drafts are only visible to logged-in users with editing permissions, while private posts are visible to all logged-in users. For archiving, draft status is typically better as it completely removes the content from public view while keeping it accessible to editors.

A membership site might use private status for subscriber-only content, but draft status works better for archived material. This distinction prevents confusion between intentionally restricted content and retired posts.

  • Drafts hide content completely from public
  • Private shows to logged-in users
  • Choose based on your team's workflow

Monthly execution is ideal for most blogs. This provides regular content maintenance without overloading your system. For very large sites (10,000+ posts), weekly runs may be better. Always test with a small batch first to verify your criteria.

A university department website running quarterly archiving might miss seasonal content patterns. Monthly execution provides more consistent content quality while being easier to monitor than weekly runs.

  • Balance frequency with content volume
  • Monitor results before increasing frequency
  • Adjust based on content production rate

Absolutely. Our team specializes in building tailored WordPress automation systems for content lifecycle management, including custom archiving rules, performance-based triggers, and integration with your existing tools. We'll design a solution that fits your specific content strategy and technical requirements.

For example, we recently built a system for a legal publisher that archives case summaries based on court status changes and integrates with their subscription database. The automation saves their editorial team 20+ hours weekly while ensuring only current precedents remain public.

  • Custom criteria matching your content strategy
  • Integration with your existing systems
  • Ongoing optimization and support

Need a Custom WordPress Integration?

This free template is a starting point. Our team builds fully tailored automation systems for your specific needs.

Get Free Consultation → Browse More Workflows