Someone suggests your website should have an FAQ, or a booking calendar, or a strip of Instagram photos. You search for how to do it and get three kinds of answer at once: a block that is already in WordPress, a plugin with a long list of settings, and a developer offering custom work. All three can be right. The trouble is knowing which one fits the thing you actually want.
Before you add features to a WordPress site, it helps to know what each of those routes costs you in time, upkeep and risk, and to run through a short checklist so the new thing does not break something old. That decision is what this page is for. The how-to posts in this section then take the features one at a time.
Three ways to add a feature in WordPress
Almost every feature request lands in one of three places.
1. A block that is already there
The block editor ships with more than most owners realise. Columns, Buttons, Table, Gallery, Quote, Search, Social Icons, Details (a show-and-hide panel) and Embed cover a surprising number of “can we add…” requests. A three-plan pricing section is Columns, Lists and Buttons. A simple FAQ can be a set of Details blocks. A team page is Columns with an Image and a short paragraph in each.
Core blocks update with WordPress itself and add no extra plugin to watch. Their limit is that they are deliberately plain. If you need filtering, a database of entries, or something that changes on its own, a block on its own will not do it.
2. A plugin
A plugin makes sense when the feature needs to store or fetch data, run on a schedule or talk to another service. An events calendar that hides past events, a feed that pulls new Instagram posts, a cookie banner that holds back tracking scripts until a visitor agrees: these need code that runs in the background, and a well-kept plugin is the sensible way to get it.
The cost is ongoing. You have to update it, it can clash with another plugin, and its developer may one day stop maintaining it. Our post on checking a plugin before you install it covers what to look at on its directory page.
3. Custom work
Custom work is for features that are specific to how your business runs: a quote calculator using your own pricing rules, a link to the stock system you already use, a member area shaped around your clients. If you have tried two or three plugins and each one needs workarounds to fit, that is usually the sign. A developer can build it as a small plugin of its own, which keeps it separate from your theme. We describe what that involves on our custom WordPress plugin development page.
| Route | Good for | Ongoing upkeep | Watch out for |
|---|---|---|---|
| Core block | Layout and static content: FAQs, testimonials, price columns, team cards | Comes with WordPress updates | Changes in many places have to be made by hand unless you use a synced pattern |
| Plugin | Features that store data, fetch content or run in the background | Updates, compatibility, sometimes a licence | Overlap with plugins you already have, heavy scripts, abandoned code |
| Custom code | Rules and integrations unique to your business | Someone who understands the code must maintain it | Code pasted into the theme, which is lost when the theme updates |
A checklist before you add features to a WordPress site
It takes a few minutes, and it catches the usual problems before they reach visitors. Work through it in order.
- Write down the job, not the tool. “Visitors should be able to see our next three workshops and their dates” is a job. “Install an events plugin” is a tool. The job tells you how much you really need.
- Check what your theme and existing plugins already do. Many themes include testimonial, team or pricing layouts. Your SEO plugin may already offer breadcrumbs or an FAQ block. Your page builder, if you use one, probably has an accordion. Adding a second tool for something you already own is the most common cause of clutter.
- Try the core blocks first. Open a draft page and build a rough version with the blocks you have. Often it is enough. If it is not, you now know exactly what is missing, which makes choosing a plugin much easier.
- Decide who will keep it current. A team page goes stale when staff change. An events list is wrong the day after an event if nobody updates it. If no one owns the content, a simpler feature that nobody has to update may serve you better.
- Think about visitors on a phone. Most features look fine on a laptop. Ask how the same thing behaves on a small screen: do columns stack, does a table scroll, can a popup be closed with a thumb?
- Ask what it loads and what it shares. Feeds, review widgets, maps and embedded calendars load content from other companies’ servers. That can slow the page and, in some countries, needs consent before it loads. The cookie consent banner guide explains how the two fit together.
- Take a backup and plan the undo. Know how you would remove it again, and what it would leave behind.
Try it somewhere safe first
A new block on a draft page is low risk. You can build it, preview it and delete the draft without anyone seeing it. A new plugin is different, because activating it affects the whole site straight away, not just one page.
For anything beyond a simple plugin, test on a copy of the site. Many hosts offer a staging copy for this; our post on setting up a WordPress staging site explains how it works. If you have no staging copy, at least take a backup, activate the plugin at a quiet time of day, and check your contact form, checkout and home page straight after. Those are the places where a clash shows first and costs most.
Once it works, put the feature on one page and leave it there for a week or so before you roll it out across the site. Odd behaviour tends to show up in that time.
The features in this section
Each of these has its own step-by-step post. They are grouped by the kind of job the feature does, which is often more useful than the feature’s name.
Answering questions and building trust
- Adding an FAQ section with Details blocks or an accordion, and writing questions people really ask.
- Displaying testimonials from customers who have agreed to be quoted.
- Showing your Google reviews, a team page and a portfolio of past work each have a post of their own as well; you will find them listed in the main guide linked below.
Helping people decide and book
- Building a pricing table that stays readable on a phone and is easy to update.
- Adding an events calendar for classes, workshops or open days.
- Showing your opening hours in one place so they never disagree with each other.
Drawing attention and helping people find things
- Setting up a popup that visitors can close easily.
- Countdown timers for real deadlines, a search box in the header and breadcrumb trails are covered in separate posts too.
Bringing in content from elsewhere
- Adding an Instagram feed, and the trade-off between a live feed and a few embedded posts.
- Cookie consent, linked above, belongs here too, because it controls when outside content is allowed to load.
Our WordPress management guide lists every post in this section, and the other sections on looking after a site rather than adding to it.
When a feature needs to come out again
Features are easy to add and easy to forget. A plugin installed for one summer promotion can sit on the site for years, still loading its scripts on every page. Plan the exit when you plan the entry.
- Blocks come out cleanly. Delete them from the page and they are gone.
- Plugins often leave shortcodes in your pages, which show up as bracketed text once the plugin is removed. Before deactivating, search your pages for the plugin’s shortcode name so you know what to tidy up.
- Some plugins keep their data after deletion unless you tick a setting to remove it. Look in the plugin’s own settings before you delete it.
Mistakes that make a site harder to look after
None of these will break a site on the day you do them. The cost arrives later, when every change takes longer than it should.
- One plugin per small job. A plugin for the FAQ, another for testimonials, another for a team grid, when one block collection, or the core blocks, would handle all three.
- Pasting code into the theme’s functions file. It is wiped the next time the theme updates. If you must add a snippet, use a snippets plugin or a child theme.
- Copying the same block layout onto ten pages. When the content changes, you have ten places to edit. A synced pattern lets you edit it once.
- Not writing it down. Keep a short note of what you added, why, and which plugin does it. The next person to work on the site, possibly you in a year, will need it.
Frequently asked questions
How do I know if a plugin is too much for a small feature?
If the plugin adds its own admin menu, scripts on every page and a dozen settings for something you could build with two or three blocks, it is probably more than you need. Try a rough version with core blocks on a draft page first, and only reach for a plugin when the blocks clearly cannot do the job.
What should I do if a new plugin breaks something?
Deactivate it first and check whether the problem goes away. If you cannot reach the dashboard, renaming the plugin’s folder through your hosting file manager switches it off. Then restore from your backup if anything is still wrong, and try the feature again on a staging copy before going back to the live site.
Can I add a feature to just one page instead of the whole site?
Blocks only appear where you place them, so yes. Plugins are active across the whole site once switched on, even if you only use them on one page, and some still load their files everywhere. Some plugins have a setting to load only where needed, which is worth looking for.
Should my web developer add features, or can I do it myself?
Most features in this section are things an owner can add with blocks or a well-known plugin. Bring in a developer when the feature depends on your own business rules, connects to another system, or when the site has a history of breaking after changes and you want it tested on a copy first.
Most owners can make this decision on their own with the checklist above. If you would like a second opinion first, or something you added is now fighting with the rest of the site, that is the kind of question our WordPress support service is there for.
All guides in this section
- How to Add an FAQ Section in WordPress (With Accordion)
- How to Display Testimonials in WordPress
- How to Add a Pricing Table in WordPress
- How to Add an Events Calendar in WordPress
- How to Add a Team Page in WordPress
- How to Add a Portfolio to WordPress
- How to Add an Instagram Feed to WordPress
- How to Show Google Reviews on WordPress the Right Way
- How to Add a Cookie Banner in WordPress That Works
- How to Add a Popup in WordPress Without Annoying People
- Add a Countdown Timer in WordPress for a Real Deadline
- How to Add a Search Bar in WordPress (Header or Menu)
- How to Add Breadcrumbs in WordPress: Plugin or Theme
- How to Add Business Hours to WordPress and Keep Them Right
Next in this series: How to Add an FAQ Section in WordPress (With Accordion)
