Ever launched a WordPress site only to realize you forgot to set up a CDN, disable XML-RPC, or configure proper user roles?
These oversights lead to security breaches, poor performance, and frantic last-minute fixes.
This prompt is your solution. It generates a comprehensive, phase-by-phase professional checklist for any WordPress project, ensuring nothing gets missed. Move beyond basic tutorials and get a tailored action plan.
📋 The Prompt
**Project Context:** [e.g., Building a new e-commerce site for a fashion brand, Migrating a large corporate brochure site to a new host, Performing a security and performance audit on an existing membership site]
**Provide the checklist in clear phases:**
1. **Pre-Development & Planning:** Cover discovery, hosting selection (with specific technical requirements), local environment setup, and tooling.
2. **Core Development & Setup:** Detail WordPress installation, theme selection/development criteria, essential plugin categories (with examples like security, caching, SEO), and initial configuration.
3. **Content & Functionality:** Outline page structure, user role configuration, form integration, and specific functionality blocks needed.
4. **Pre-Launch Audit:** Create a rigorous list covering security hardening, performance optimization (include Core Web Vitals metrics), SEO readiness, compliance (GDPR/accessibility), and cross-browser/device testing.
5. **Launch & Post-Launch:** Detail deployment steps, DNS propagation checks, post-launch monitoring setup, and client training/documentation handoff.
**Instructions:** For each phase, list specific, actionable items. Avoid vague statements. Where applicable, recommend tools or plugins (e.g., 'Configure a caching plugin like WP Rocket or LiteSpeed Cache'). Tailor the checklist depth and technicality to the provided **Project Context**.
How It Works
This prompt works because it structures the AI’s thinking. Instead of asking for a generic list, you’re hiring a virtual senior architect with a strict deliverable format.
The Project Context is the key. By specifying a scenario like ‘migrating a large corporate site,’ the AI instantly knows to prioritize zero-downtime migration plugins, database serialization checks, and post-migration redirect maps. It shifts the checklist from generic to laser-focused.
The five-phase structure forces systematic thinking. It prevents the common pitfall of jumping straight to ‘install plugins’ without proper planning. The Pre-Development phase alone—covering hosting specs and local tools—can save countless headaches. This mirrors a professional agency workflow.
Notice the command to ‘Avoid vague statements.’ This is crucial. It transforms ‘improve security’ into actionable items like ‘Install a web application firewall (WAF) via a plugin like Wordfence and configure login attempt limiting.’ The prompt demands executable steps, not just topics.
By asking for tool and plugin examples, you get practical recommendations integrated into the workflow. This turns the checklist into a buying and research guide. For performance, this prompt naturally dovetails with our WordPress Speed Hacks AI guide, providing the ‘what’ that guide helps you implement.
Ultimately, this prompt delivers a strategic blueprint. It’s the foundational document you can share with your team or client to ensure alignment, much like the broader frameworks discussed in our Ultimate AI Prompt Strategy Guide.
Pro Tips & Variations
Advanced Customization: Inject specific constraints into the Project Context. Try ‘…for a site that must achieve a 95+ PageSpeed score’ or ‘…using a headless WordPress setup with Next.js.’ The AI will tailor the performance and development phases dramatically.
Common Mistake: Leaving the Project Context too vague. ‘Building a blog’ yields a basic list. ‘Building a monetized newsletter blog with subscription tiers using Paid Memberships Pro’ generates a checklist with specific plugin integration and payment gateway setup steps.
For Audits: Change the first line to ‘You are a WordPress security and performance auditor.’ Then, use a context like ‘Auditing an existing WooCommerce site with slow sales.’ The checklist will focus on forensic items: checking for outdated PHP, analyzing database bloat, and reviewing failed login logs. This is the deep-dive follow-up to the Advanced Performance Optimization prompt.
Iterate on Output: Use the first output as a draft. Then, prompt the AI: ‘Based on this checklist, now create a detailed sprint plan for Phase 2: Core Development, assigning hypothetical team roles (developer, designer).’ This breaks the plan into actionable tickets.
Integration Tip: Copy the generated ‘Pre-Launch Audit’ phase into a separate AI chat and command: ‘Convert each of these 15 audit items into a direct command I can paste into my AI coding assistant to fix the issue.’ This creates a powerful repair script.
Frequently Asked Questions
Can this prompt really replace a project manager?
No, and it’s not designed to. It replaces the tedious, error-prone process of creating project documentation from scratch. It gives a PM or lead developer a robust, structured foundation to delegate tasks, track progress, and ensure scope coverage, dramatically increasing their efficiency.
How do I use this for maintaining an existing site?
Set your Project Context to ‘Quarterly maintenance and update audit for an existing [type] site.’ The AI will generate a phase-based checklist focused on update procedures (staging first!), backup verification, post-update regression testing, and performance benchmark comparisons.
The list is huge. How do I prioritize?
The phased structure is your prioritization. Complete Phase 1 before touching Phase 2. Within phases, the AI typically lists items in logical order. For advanced prioritization, ask the AI in a follow-up: ‘Highlight the 5 most critical security items from the Pre-Launch Audit phase that must be done before any others.’
Can it generate checklists for specific page builders like Elementor or Divi?
Absolutely. Include the page builder in your Project Context: ‘…Building a new site using Elementor Pro.’ The Core Development phase will then include items like ‘Install and license Elementor Pro,’ ‘Configure Elementor performance settings (disable unused assets),’ and ‘Plan global style kit and template library.’
Is this checklist suitable for client presentations?
Yes, with minor editing. It demonstrates extreme professionalism and thoroughness. Consider using a follow-up prompt: ‘Convert the Phase 1: Pre-Development checklist into a client-friendly questionnaire to gather required project information.’ This turns the checklist into a collaborative tool.
