Virtual Assistant Experienced with WordPress: What They Handle and What Requires a Developer

WordPress powers over 40% of websites on the internet. VAs with WordPress experience are widely available and can handle significant operational and content workload - if the boundary between VA work and developer work is clearly drawn.

What a WordPress VA Does

Content publishing:

• Formatting and publishing blog posts from your drafts or content docs
• Adding categories, tags, and featured images
• Scheduling posts for future publication
• Updating published posts (corrections, refreshes, SEO updates)
• Importing posts from Google Docs or other sources into the WordPress editor

Page management:

• Editing text and images on existing pages (via page builder: Elementor, Divi, Gutenberg)
• Creating new pages from templates
• Managing menu structure and navigation
• Updating headers, footers, and sidebars (within the theme's admin options)

Media library:

• Uploading and organizing images
• Resizing and compressing images for web use
• Adding alt text and captions
• Keeping the media library organized

Plugin and maintenance tasks:

• Running plugin updates (with a backup in place)
• Monitoring for plugin conflicts after updates
• Managing user accounts and permissions
• Basic spam management and comment moderation

WooCommerce (if applicable):

• Adding and updating product listings
• Processing orders and managing returns
• Updating pricing and inventory
• Running basic WooCommerce reports

What Requires a Developer, Not a VA

The line is clear: anything involving code goes to a developer.

• Editing functions.php or any PHP files
• Creating or modifying custom plugins
• Changing theme code (even small CSS edits, unless via the WordPress Customizer)
• Debugging broken functionality
• Server configuration (hosting, SFTP, database)
• Setting up custom post types or taxonomies programmatically
• Resolving white screen of death or 500 errors

A VA who claims to handle all of the above is either a developer (and priced accordingly) or overstating their capabilities. Expect VAs to operate in the WordPress admin panel, not in the file system.

WordPress.com vs. WordPress.org

Two distinct environments with different capability levels:

WordPress.com (hosted): Limited admin access, no plugin installation on lower plans, restricted theme customization. Most experienced VAs prefer WordPress.org because of the expanded functionality.

WordPress.org (self-hosted): Full admin access, unlimited plugins and themes, complete control. The environment most WordPress VAs are experienced with.

Confirm which environment your site is on before hiring. Some WordPress.org features (custom plugin installation, full theme access) are not available on WordPress.com Business or lower plans.

Evaluating WordPress Proficiency

Request admin-level walk-through. Ask the candidate to describe the process of publishing a new blog post with a featured image, categories, and scheduled date. Real WordPress users describe this fluently; those without genuine experience hesitate on specifics.

Ask about page builders. Which page builders have they used? Elementor, Divi, Beaver Builder, and Gutenberg (the native block editor) all have different interfaces. Proficiency in one does not guarantee proficiency in others.

Plugin familiarity. Ask what plugins they regularly work with. Common ones: Yoast SEO (or RankMath), WooCommerce, Contact Form 7, Gravity Forms, Smush (image compression), UpdraftPlus (backups). Depth of plugin familiarity signals WordPress operational depth.

Test task. Give the VA access to a staging or test site and ask them to complete a representative task: publish a post from a Google Doc, update a page section, add a product. Review the output for accuracy and formatting quality.

Stealth Agents places WordPress-experienced VAs. Specify your WordPress environment (hosted/self-hosted), active page builder, key plugins, and primary use case during intake.