Southern Lift Solutions · Build
Build, Monitoring, and Iteration
Use MCP to execute build tasks, monitor issues, and refine the workflow in one operational stage.
WordPress MCP
One place to run common WordPress tasks with better prompts
WordPress MCP gives the model a structured way to inspect and operate on a WordPress site: content, WooCommerce data, media, theme-level changes, monitoring, and repair work. Instead of vague requests, you define the exact scope, constraints, and expected output.
Analytics and reporting
Use WordPress MCP to query operational data from WordPress, WooCommerce, and plugin tables without leaving the workflow.
> Goal: answer a business question from the WordPress stack Run a WordPress MCP query against WooCommerce orders for the current week. Return: - total order count - revenue total - day-by-day breakdown - note any obvious anomaly compared with the previous week
Prompt references
- How many WooCommerce orders did we get this week? Break it down by day.
- Show the top 5 products by revenue in the last 30 days.
- Find abandoned carts created in the last 7 days and summarize recovery potential.
- List posts published this month that still have no featured image.
Content publishing
Draft, create, and update posts or pages with structured prompts that specify source copy, target sections, taxonomy, and publishing status.
> Goal: create or update content with explicit editorial controls Use WordPress MCP to create a draft blog post. Inputs: - title - target category - source brief - CTA to preserve - publish status = draft Return the created post ID, slug, and a short QA checklist.
Prompt references
- Create a new blog post from this client brief and save it as draft with excerpt, category, and SEO title.
- Rewrite the homepage hero copy to target architects and keep the CTA unchanged.
- Find posts without internal links to product pages and suggest the best insertion points.
- Export all January orders as CSV and place the file in the shared downloads folder.
WooCommerce catalog work
Create or update products, attach attributes, map media files to featured images, and keep product data complete before publishing.
> Goal: create a product safely and consistently Use WordPress MCP to create a WooCommerce product from the supplied product data. Before publishing, verify: - title - SKU - price - short description - long description - category - featured image Search Media for the closest filename match to the product name and assign it as featured image. If any required field is missing, stop at draft and report the gap.
Prompt references
- Create a WooCommerce product from this spec sheet and keep it as draft until all required fields are present.
- Match Media filenames to product names and set the closest match as each product featured image.
- Audit products missing dimensions, SKU, short description, or gallery images.
- Update sale pricing for the selected products and add the campaign end date.
Child-theme features and shortcodes
Use MCP prompts as execution briefs for theme-level features, shortcode creation, and controlled frontend changes tied to exact templates or hooks.
> Goal: implement a child-theme feature with clear boundaries Use WordPress MCP to build this feature in the active child theme only. Requirements: - do not edit parent theme files - do not modify plugin core files - place PHP, CSS, and JS in child-theme locations - explain which hooks, templates, or shortcodes were added Return changed files and manual QA steps.
Prompt references
- Build a child-theme shortcode for a project-spec download card with title, file, and CTA fields.
- Add a custom dynamic data tag for Bricks or Elementor using child-theme code only.
- Create a cache purge tool in the admin area for editors with proper capability checks.
- Change the admin color scheme for this site without modifying plugin code.
Page edits and site cleanup
Target exact sections, widgets, forms, or template blocks so routine editorial and repair work can be run with less ambiguity.
> Goal: make a scoped content or configuration change Use WordPress MCP to update one specific page section. Target: - page URL or ID - section name or selector - replacement copy - elements that must not change Return the exact fields updated and any content still needing manual review.
Prompt references
- Update the homepage proof section copy and keep the section layout unchanged.
- Find broken internal links and list the exact pages that need correction.
- Replace all http links with https where the destination already supports TLS.
- Disable comments everywhere except staff-only post types.
Localization and operations
Handle translation, cleanup, and operational checks with prompts that define target pages, languages, review mode, and plugin-safe constraints.
> Goal: translate or maintain the site without creating hidden regressions Use WordPress MCP to translate the selected pages into the target language. Keep: - existing slugs unless explicitly changed - CTA structure - forms and shortcodes - product data fields Return translated page IDs, untranslated strings that need manual review, and any plugin-specific blockers.
Prompt references
- Translate the selected service pages into Chinese and keep all CTA links and forms unchanged.
- List plugins that load the most JS on the homepage and flag obvious performance risks.
- Regenerate thumbnails for images uploaded in the last 24 hours only.
- Report disk usage by uploads, backups, cache, and plugin-generated files.
Forms, email, and automations
Use WordPress MCP to inspect form configuration, delivery paths, webhook actions, and common notification failures across plugins.
> Goal: diagnose or automate form submission flows Use WordPress MCP to inspect the target form and its notification pipeline. Check: - form plugin settings - SMTP or mail configuration - webhook destinations - validation rules - recent submission failures Return the likely failure point and the exact setting or code that should change.
Prompt references
- Why is the contact form not sending emails? Check plugin settings, SMTP, and recent error logs.
- Notify Slack on every new WooCommerce order with order number, total, and customer name.
- List all forms on the site and show where each one sends submissions.
- Find forms that are missing success messages, spam protection, or required-field validation.
SEO metadata and media library tasks
Handle metadata, alt text, image hygiene, redirects, and content discoverability with prompts aimed at repeatable SEO operations.
> Goal: improve SEO and media quality without broad manual review Use WordPress MCP to audit SEO and media completeness. Return: - pages missing metadata - images missing alt text - oversized files - redirect opportunities Group the output by issue type and prioritize high-traffic pages first.
Prompt references
- Find posts and pages missing SEO titles, meta descriptions, or Open Graph images.
- Generate alt text suggestions for uploaded images based on filename and attached content.
- List media files that are unused anywhere on the site and sort by file size.
- Create redirects for broken internal URLs that still receive traffic.
Performance, cache, and asset audits
Run focused prompts for plugin weight, asset loading, cache behavior, and page-specific performance bottlenecks.
> Goal: identify avoidable performance cost inside WordPress Use WordPress MCP to audit frontend assets on the target pages. Return: - plugin or theme source - asset file names - where each asset is enqueued - quick wins for conditional loading or cache invalidation Flag anything that affects the homepage, product pages, or checkout first.
Prompt references
- Which plugins load the most CSS and JS on the homepage?
- Build a cache purge tool for editors and restrict it to the right capability.
- Find pages with the largest number of enqueued frontend assets.
- Check whether WooCommerce or Elementor assets are loading on pages that do not need them.
Users, roles, and admin controls
Review capabilities, clean up admin access, and build role-based controls without editing plugin core or overexposing privileged actions.
> Goal: review or change permissions safely Use WordPress MCP to inspect users, roles, and capabilities relevant to this task. Do not grant broader permissions than necessary. Return: - affected roles - capability changes - admin screens impacted - rollback notes if access becomes too restrictive
Prompt references
- List all custom roles and capabilities currently registered on this site.
- Create an editor-only admin tool for exporting order summaries without granting full WooCommerce admin access.
- Find users who have admin access but have not logged in during the last 90 days.
- Restrict a custom settings page so only site admins and shop managers can use it.