GoBuildWP ability reference

The core WordPress surface covers posts, pages, custom post types, taxonomies, media, comments, revisions, menus, users and allowlisted settings. These core operations need no companion plugin or licence. Specialised Free modules have their own dependencies: Elementor tools require supported active Elementor, and Site Editor operations depend on the appropriate theme and controllers. Free Elementor abilities read a document's element tree and write scoped edits back into it; their separate module makes that edition boundary clear.

Builder-native document and element operations for Elementor, Bricks, Divi, Oxygen, Breakdance, Beaver Builder, WPBakery, Etch and Mosaic. Each builder stores its own structured tree rather than plain post content, so these modules read the real schema before proposing a change instead of writing markup the editor cannot reopen.

Block libraries and theme frameworks: GenerateBlocks, Kadence Blocks, Spectra, Astra, GeneratePress, Kadence, OceanWP, Avada and the block-theme bridge. They expose block names, attribute schemas, global styles and template parts so generated layouts match what the installed theme actually supports. The brand kit sits alongside them, holding the colours, type scale and spacing ladder a site has actually committed to, so a new section is composed from the decisions already made rather than from whatever the model would have picked on its own. Kadence's Design Library sections can be inserted too, the free ones only, with their uniqueIDs renamed so each block keeps its own CSS.

Custom field and content-structure plugins, ACF, ACPT, JetEngine, Meta Box and Pods. Field groups, post types, taxonomies and option pages are read as typed definitions, which is what lets an agent write values that validate rather than guessing at meta keys. A plugin-neutral module writes the same fields across many posts at once through whichever of them is active.

WPForms, Gravity Forms, Fluent Forms, Formidable, Contact Form 7 and Ninja Forms, plus Forminator and WS Form. Field discovery, form creation, notification settings and entry reads, with the submission and confirmation paths left to be verified in the plugin itself after a change. The Forminator and WS Form modules are deliberately narrower: they read forms and entries with contact details always withheld, and change only titles, button text and field labels.

Yoast, Rank Math, AIOSEO, SEOPress, The SEO Framework, Slim SEO and SmartCrawl, plus the Redirection plugin and read-only Site Kit by Google data. Titles, meta descriptions, canonical URLs, robots directives, schema settings and redirects are read and written through each plugin's own storage, so nothing bypasses the SEO plugin that owns the output. Bulk SEO and automatic slug-change redirects work across whichever of them is installed. Content fixes sit here as well: they turn the free content audit's findings into link, redirect and description changes a person picks one by one.

WooCommerce products, variations, attributes, categories, orders, coupons and store settings, and FunnelKit funnels with their per-step conversions. Every catalogue, order and coupon write is bound by the safety profile and the connected user's shop capabilities, and sales reports read in the store's own timezone with refunds netted.

WPML, Polylang, Weglot and TranslatePress. Read the configured languages and existing translations, connect translated posts where supported, or change collected strings through the installed plugin's specific operations. These modules have different scopes; they do not all configure languages, create translation jobs or translate an entire page.

The Events Calendar, Paid Memberships Pro, Tutor LMS and BuddyPress. Events, venues, membership levels, courses, lessons and community objects, the areas where a careless write affects people's access rather than just a page's appearance.

Code Snippets, Dynamic Shortcodes and Bricksforge. These reach the parts of a site that execute code, so they are the first abilities a restrictive safety profile withholds and the clearest case for a staging site.

Backups, security plugins, plugin updates and audits that run on a schedule. Backup status is read from UpdraftPlus, Duplicator, BackWPup and All-in-One WP Migration, and a backup can be started where the plugin allows it; nothing restores, downloads or deletes one. Wordfence and Solid Security are read with IPs, usernames and emails masked, and hardened only from a plan a person confirms, with supported recovery for settings and blocks; starting a scan has side effects and no undo. Safe updates check selected pages and attempt files-only recovery when checks fail; recovery can fail, and database migrations and external effects remain. Routines run read-only audits on WP-Cron while storing reports and optionally sending notifications.

Diagnostics, integration health, the change ledger, rollback, approvals and agent memory. This group answers what GoBuildWP itself is doing: which modules loaded, what an agent changed, what is waiting for a human, and what it is allowed to remember. Caching and page speed live here too, because a cache is the thing most likely to make a correct write look like a failed one: 26 layers are detected by name, the 10 whose settings share meaning are mapped onto one vocabulary so a setting means the same thing whichever plugin implements it, and the rest are reached by their own option names. Nothing here invents a performance score. Time to first byte, cache hits and render-blocking assets are measured from the server; LCP and CLS come from a real browser, because they do not exist until something renders. Where the fix is not a WordPress setting at all, that is reported as its own finding with the steps for whoever owns the host or the edge.