Build Structured WordPress Content Without Another Dedicated Plugin
WordPress works well for traditional posts and pages, but many real-world websites need information that cannot be managed effectively inside a single content editor. A property listing may need a price, number of bedrooms, bathrooms, address, map, gallery, availability, and agent. An event may need start and end dates, a venue, speakers, ticket pricing, and a registration link. A directory listing could require contact details, opening hours, categories, images, and relationships with other listings.
Putting all of this information into a WYSIWYG editor makes the content difficult to manage and even harder to reuse. Custom Fields turns each piece of information into structured data with an input designed for that specific value. Editors receive a clear interface for entering content, while developers and designers receive predictable data that can be used throughout the website.
The same approach can be used for directories, real estate websites, events, courses, vehicles, team members, portfolios, job listings, reviews, case studies, catalogs, and other structured WordPress projects. Instead of adapting your content to the limitations of the default editor, you can build an editing experience around the information your website actually needs.
Choose From 40+ Custom Field Types
Different kinds of information require different input controls, which is why Custom Fields includes much more than standard text boxes.
Basic data can use Text, Textarea, Number, Range, Email, Phone, URL, Password, Date, Time, Date & Time, and Color fields. Choice-based information can use Toggle, Select, Radio, Checkbox, Button Group, and Navigation Menu fields. Select fields and several relational fields can also support multiple selections where appropriate.
For richer content, you can use WYSIWYG, oEmbed, Link, Image, Gallery, File, Icon Picker, and Google Map fields. Relationship-driven websites can use Post Object, Relationship, Page Link, Term, and User fields, while more advanced content structures can be built using Group, Repeater, Flexible Content, and Clone fields.
Custom Fields also includes layout elements that improve the editing interface without storing unnecessary values. Messages, Separators, Tabs, Accordions, and static Output can divide complex field groups into understandable sections and provide editors with additional instructions or context.
Show Custom Fields Exactly Where They Belong
As a WordPress website grows, displaying every custom field on every editing screen quickly becomes unmanageable. A property editor should not see event fields, and an ordinary blog post should not be filled with fields intended for a particular landing-page template.
WP PowerSuite uses location rules to determine exactly when a field group should appear. Groups can target a post type or taxonomy and then be refined using conditions such as page template, post status, post format, assigned term, taxonomy, post ID, parent ID, current user role, current user ID, or individual term.
Multiple rules can be combined using Match All or Match Any behavior. This allows you to create both simple and highly specific editing experiences. A group might appear on every Property, only on Pages using a particular template, or only for editors with a particular role working with a particular type of content.
The presentation of each group can also be adjusted. Groups can appear after the title, in the normal editing area, or in the sidebar, with configurable priority and standard or seamless styling. Individual fields can use widths of 100%, 75%, 50%, 33%, or 25%, making it possible to arrange related inputs into a cleaner and more compact editing interface.
Create Smarter Editing Experiences With Conditional Logic
Complex content models often contain fields that are relevant only in certain situations. Displaying every possible input all the time makes forms longer and increases the chance of editors entering information in the wrong place.
Custom Fields supports conditional logic at the individual field level. A field can appear or remain hidden according to the value of another field in the same group, with multiple conditions combined using AND or OR logic.
For example, an Events post type could contain an Event Type choice. Selecting Online could reveal a Meeting URL field, while selecting In Person could instead reveal Venue, Address, and Map fields. A Property could show additional lease information only when its Listing Type is set to Rent. A Course could reveal certification fields only when certification is offered.
Fields can also include their own instructions, required state, defaults, placeholders, patterns, minimum and maximum values, step values, row settings, prepend or append content, and other type-specific configuration. Together, these controls let you build an editor that guides users through structured data instead of simply presenting them with a wall of inputs.
Build Repeatable and Flexible Content Structures
Many types of structured content naturally contain repeating information. A restaurant has several opening-hour rows. A product may have multiple specifications. An event can have many speakers. A team profile may contain several qualifications or social links.
Repeater fields let you define the structure once and allow editors to create multiple rows using that same collection of sub-fields. For larger datasets, repeaters support collapsed rows and pagination, helping keep the editing interface manageable even when many entries are present.
Flexible Content is designed for situations where repeated items do not all share the same structure. You can create several predefined layouts and allow editors to choose which layout they need. This gives content teams flexibility while developers retain control over the types of content that can be created.
Group and Clone fields provide additional ways to organize and reuse field structures. WP PowerSuite deliberately limits deeply nested composite fields so complex configurations remain predictable and maintainable rather than turning into unlimited layers of repeaters and flexible layouts.
Build Relationships Between Posts, Terms and Users
Structured websites frequently contain information that relates to other WordPress content. A property belongs to an agent. An event has speakers.
A course has instructors. A project may involve several team members. A book can have multiple authors.
Custom Fields provides dedicated Post Object, Relationship, Page Link, Taxonomy Term, and User fields for building these connections. Rather than storing a person's name or another post's URL as plain text, editors can select the actual WordPress object the current content relates to.
Relationship fields can include filters and minimum or maximum selection requirements, while Page Link can optionally work with archive destinations. Term fields can also work with taxonomy synchronization and term-creation workflows where appropriate.
Supported relational fields can use bidirectional synchronization. For example, if a Property is connected to an Agent, the relationship can also be maintained from the Agent side instead of requiring editors to independently manage both records. This makes it possible to build richer interconnected WordPress content models without manually duplicating relationship data.
Use Custom Fields With Elementor, Bricks, Divi & Beaver Themer
Structured data becomes especially powerful when a frontend template can automatically retrieve it.
Custom Fields integrates with popular WordPress dynamic-content workflows, including Elementor, Bricks, Divi, and Beaver Themer. You can design a template once and use custom field values to populate that template for every post of the same type.
For example, you could build one Property template containing dynamic values for Price, Bedrooms, Bathrooms, Gallery, Map, Availability, and Agent. Every Property then uses the same professionally designed layout while automatically displaying its own information. When an editor changes the Price field, the frontend template receives the updated value without requiring the page design to be edited.
This workflow works equally well for directories, courses, events, portfolios, team members, vehicles, case studies, and other custom post types. It separates content from presentation: editors manage structured information while designers control how that information appears.
Sensitive fields such as Password are deliberately excluded from public builder and display integrations.
Display Custom Field Values Almost Anywhere
A page builder is not required to use the data created with Custom Fields.
WP PowerSuite provides multiple ways to retrieve and display field values depending on how your WordPress site is built. The Custom Field block can be used in the Block Editor, while content tags allow supported values to be inserted into content and widgets.
Shortcodes such as:
provide another straightforward way to output individual fields.
[wpps_cf group="property" field="price"]provide another straightforward way to output individual fields.
Developers building custom themes or plugins can use PHP helpers including
wps_cf_get(), wps_cf_get_field(), wps_cf_get_term(), wps_cf_render_field(), and wps_cf_get_display(), along with helpers for common link and image workflows.Because field values are stored as native WordPress metadata, developers are not restricted to WP PowerSuite's own output methods. Standard WordPress post-meta and term-meta APIs can also be used where appropriate.
Create Custom Post Types and Fields Together
Custom Fields works naturally with the WP PowerSuite CPT Builder module. The two tools solve different parts of the same structured-content problem.
CPT Builder defines what kind of content exists. Custom Fields defines what information belongs to each item.
For example, you could create a Vehicles custom post type and then build fields for Make, Model, Year, Mileage, Fuel Type, Transmission, Price, Gallery, Dealer, and Availability. An Events post type could contain Start Date, End Date, Venue, Map, Speakers, Registration URL, and Ticket Price. A Team Members post type could include Position, Department, Photograph, Biography, Contact Information, and related Projects.
The CPT Builder integration can open Custom Fields with a new group already prepared for the relevant post type, reducing repetitive setup when developing structured WordPress websites.
Together, CPT Builder and Custom Fields provide the foundation for building data-driven WordPress sites while keeping both content types and their associated information inside WP PowerSuite.
Surface Important Custom Fields in WordPress Admin
Custom fields are not only useful on the frontend. Important structured data can also make WordPress itself easier to manage.
Fields configured with Show in List can appear as columns in the relevant WordPress post or taxonomy-term tables. Instead of opening every item individually, administrators can see important information directly from the list screen.
A Properties screen could show Price, Bedrooms, and Availability. An Events screen might display Event Date and Venue. A Jobs screen could expose Location and Application Deadline. Taxonomy-term metadata can be surfaced in the same way where appropriate.
This can significantly improve administrative workflows on data-heavy websites because the WordPress list screens become more informative and better suited to the type of content being managed.
Use Custom Fields With Gutenberg
WP PowerSuite supports both traditional WordPress meta boxes and the modern Block Editor.
Supported simple fields can appear in the Gutenberg document sidebar, keeping commonly used structured values conveniently available alongside the normal editing controls.
More complex fields—particularly nested and composite structures such as Repeaters and Flexible Content—remain in dedicated meta boxes where there is enough space to provide a usable editing interface.
This mixed approach avoids forcing complex field structures into a narrow sidebar while still giving simple fields a more native Gutenberg editing experience.
Import, Export and Reuse Field Groups
Building a sophisticated field group can take significant time, especially when it contains dozens of fields, location rules, conditional logic, relationships, and layout configuration.
Custom Fields supports JSON import and export, allowing field-group definitions to be transferred between WordPress installations or retained as configuration backups.
This can be particularly useful for agencies that repeatedly build similar website structures. A field group created for one type of project can be exported, imported into another installation, reviewed, and adapted rather than recreated manually from the beginning.
Imported groups are disabled by default, allowing administrators to review the configuration before it starts appearing on editing screens. The importer also normalizes several common ACF-style configuration keys, making compatible field definitions easier to adapt to the WP PowerSuite structure.
