Blog

Search the WordPress.org directory for “social media” and you get share buttons, Instagram galleries, auto-posters, profile icons, login tools and catalog sync, all in one list. These are different products. They connect to different things, they break in different ways, and they cost different amounts to keep running.

So “which social media plugin is best” has no single answer. A better question is which job you need done, and how much upkeep you’re signing up for. The installation itself is the easy part, and our guide to installing a WordPress plugin safely covers it. This article covers the decision that comes before it.

Which social job do you actually need done?

Name the job before you look at any plugin. Practitioner threads are full of mismatched answers. In one, someone asked for Pinterest share buttons and was pointed to a feed plugin, which does the reverse.

The upkeep column matters more than the feature list. Anything that holds a token for someone else’s platform will break when that platform changes its rules, and you’ll be the one who notices.

Why share buttons are the easy part

Share buttons need no account and no API key. Each button opens the network’s share dialog with your URL already filled in. That’s why good free options exist. AddToAny, one of the most installed, showed 300,000+ active installs in the WordPress.org directory.

There are three things to know before you add them.

• Share counts are mostly gone. In a Jetpack support thread on WordPress.org, Jetpack’s team explained that Facebook no longer reliably makes share-count data available to third-party sharing buttons. Switching plugins won’t restore the numbers.
• Icon-only buttons need accessible names. W3C’s guidance on functional images says the text alternative should describe what the control does. “Share on Facebook” works. “icon” or “facebook-logo” doesn’t. Check that your plugin outputs a label, and add one if it doesn’t.
• Buttons add some weight. Isolated benchmarks of individual share plugins showed small effects. They used different metrics on different setups, so none of them ranks one plugin above another. Measure your own page before and after, on mobile.

Some practitioners take share buttons off entirely as mobile clutter, and nobody has published usage data that settles the argument. If your analytics show almost no social referrals, removing the buttons is a reasonable choice.

Why feeds need the most maintenance

Feeds bring the most visible value and the most support threads. Smash Balloon’s Instagram feed plugin is the most installed in the category, with 1,000,000+ active installs on WordPress.org. Its own documentation also lists the most failure modes, which tells you what running a feed actually involves.

The token expired or the platform changed its API

This is the most common cause. The plugin reaches Instagram or Facebook with an access token, and tokens expire, get revoked when someone changes a password or admin role, or stop working when Meta retires an API. Smash Balloon’s error reference covers API error 190: Error validating access token. The fix is to remove the source, save, and reconnect.

Update the plugin before you reconnect. When Meta retired the older Instagram connection method, reconnecting through an outdated plugin version didn’t help. Wake Forest University’s WordPress guide expects feed connections to need reconnecting roughly every six weeks and recommends turning on the plugin’s feed-issue email report. That interval is one institution’s experience, not a rule. Still, it’s a sensible calendar reminder.

The feed only updates when you clear the cache

This usually isn’t a broken plugin. Smash Balloon’s doc on this symptom names three causes: WP-Cron or the server cron isn’t running, the page cache lifetime is too long, or the feed’s own cache interval is too long. WP-Cron only runs when someone visits, so a quiet site can go hours without a refresh.

Clearing the cache by hand brings the feed back, and it also hides the cause. Check whether cron is running with a plugin such as WP Crontrol, or ask your host about a real server cron. Then shorten the cache lifetime for the feed page, or exclude that page from the page cache.

The feed is blank or the loader keeps spinning

Open the browser console first. Smash Balloon’s troubleshooting list includes another plugin’s JavaScript error, outdated or duplicate jQuery, lazy-loading conflicts, script combining by an optimization plugin, a wrong shortcode or feed ID (curly quotes pasted from a document break it), and a theme that never calls the hooks plugins rely on:

<?php wp_head(); ?>   <!-- inside <head> -->
<?php wp_footer(); ?> <!-- just before </body> -->

If you have to edit the theme, do it in a child theme so the next theme update doesn’t undo your fix. Don’t apply site-wide workarounds such as turning off lazy loading everywhere until the console has shown you that’s the cause. Firewalls can also block feeds: support threads point to Cloudflare rules, ModSecurity and Wordfence blocking requests or settings saves. For the wider method, see our guide on fixing plugins that stop working.

Connecting feeds for clients

Agencies don’t need client passwords. Spotlight’s directory listing describes an Access Token Generator that lets the client authorize the connection themselves, and it supports separate accounts and feeds for each site.

Why free auto-posting usually comes with limits

Auto-posting is where “free” most often stops meaning free. Commenters on r/Wordpress keep reporting the same pattern: the free tier covers one or two networks, and Instagram or LinkedIn needs a paid plan or an add-on. Others ended up switching between plugins until one covered the networks they actually used.

The underlying reason sits with the platforms. Self-hosted tools that post to Meta’s networks need an approved developer app, and one Reddit user described waiting months for that approval. Before you install anything, write down the exact networks you post to. Then check that the free tier, or the plan you would buy, covers all of them. Also check whether “posting” means the full post with an image or just a link.

Auto-posters also depend on WP-Cron, the same as feeds. A scheduled share on a low-traffic site can go out late because nobody visited to trigger it.

Why the wrong image shows when your link is shared

Link previews come from Open Graph tags in your page’s head, mainly og:image and og:title. On most sites your SEO plugin writes these tags, not a social plugin. Installing a share plugin to fix a preview usually adds a second set of tags and makes things worse.

Google’s image documentation says its choice of preview image is automated and draws on several sources. og:image is one way to influence it, not a way to control it. Set a relevant image per post in your SEO plugin, give crawlers time to revisit, and never use noindex to “reset” a preview. Image optimization plugins that rewrite image URLs can also change these tags, so check the page source when the preview looks wrong. Our guide to doing SEO on WordPress covers where those settings live.

What to check before you install any social plugin

Spend a few minutes on the directory listing first. It saves more time than any feature comparison.

1. Confirm it does your job. Read the description for the one thing you named above. A plugin that bundles login, counters and sharing adds code for jobs you may not need.
2. Check maintenance. Look at “Last updated” and “Tested up to”. A feed or posting plugin that hasn’t been updated since the platform’s last API change will fail.
3. Check the free tier against your network list. Every network, not just the first one.
4. Decide where it loads. A feed belongs on the page it supports, such as a portfolio or a product page, not on every article template.
5. Test one workflow. Connect one account and publish one post or one feed. Check the result logged out before you add a second network.
6. Keep one plugin per job. Two share plugins or two plugins writing Open Graph tags cause conflicts, and removing the unused one closes off code you no longer need.

Social plugins look finished on the day you set them up, and then they need updates, reconnections and clean-up for as long as they’re installed. If you’d rather not do that yourself, SiteSelf handles plugin updates, settings and removals on request through chat, using its connector plugin for settings work and hosting access for file-level fixes. Reconnecting a social account still needs whoever owns that login.

If you run a WooCommerce store

Catalog sync to Facebook and Instagram shops gets mixed reports. Store owners on r/woocommerce describe one update to the official integration syncing every product, including disabled variations. Others report the integration working nearly out of the box. When you troubleshoot any social plugin on a store, WooCommerce’s documentation warns that Health Check’s Troubleshooting Mode does not switch payment gateways to sandbox, so an order placed during a test can take a real payment. WooCommerce recommends a backup and a staging site for conflict testing.

Frequently asked questions

People search for “multi site website” when they mean three different things. Usually they mean WordPress Multisite, where one installation runs a network of sites. Some of them mean several separate websites run by one person or team. Some are a business with several locations, asking whether each location needs its own site. Each meaning has a different right answer, so work out which one you have before you change anything.

Which kind of multi site website do you actually have?

Here are the three setups side by side.

The rest of this article is mostly about the first setup, because that is where the expensive mistakes happen. If you already know you want a network, our WordPress Multisite installation steps cover the setup in detail. If your sites are separate installs, see how to manage multiple WordPress websites.

What a Multisite network shares and what it keeps separate

A network shares the engine but not the content. WordPress keeps one copy of core, plugins and themes, and one user list. Each site gets its own posts, pages and settings in its own database tables, and its own uploads folder under /wp-content/uploads/sites/, named by site ID.

• Core: one copy. When you update WordPress, every site moves to that version at once.
• Plugins: installed once. A Super Admin can network-activate a plugin so it runs on every site, or a plugin can be activated on individual sites. The code is shared either way.
• Themes: installed once and enabled per site.
• Users: one list for the whole network. A role on one site gives no role on another until someone adds it.
• Content: separate per site. Sites cannot share posts or pages without a plugin or custom code.

This is what makes the decision hard. Shared code helps when the sites are meant to stay the same. Once the sites start to differ, it gets in the way.

When one network is the right call

Multisite fits when the sites are really one operation: one owner, one set of rules, the same theme and plugins, and one team running them. WordPress’s own Before You Create A Network page opens by asking whether you really need a network, and it warns against creating one just to get sites that look different.

Good fits that come up again and again: franchise locations on one template, a school district whose sites share a footer and admins, university departments, and closely related brand sites. Practitioners on X and Reddit sum it up the same way. If each site is basically the same site on the same theme and plugins, a network saves work. If not, it creates work.

Site count matters less than similarity. One wordpress.org moderator suggests separate installs for two to four sites, with Multisite becoming more appealing above that. That is one person’s opinion. Most practitioners decide by asking whether the sites are alike, not by counting them.

Interest is also cooling at the top end. In the State of Enterprise WordPress survey, the share of respondents who rated Multisite capabilities very or quite important fell from 56% in 2023 to 46% in 2024. The sample is small and the question measured importance, not usage, but the trend matches what practitioners are saying.

Why unrelated sites usually belong on separate installs

Every site on a network shares the same code and database, so they also share failures. One vulnerable plugin, one bad update, one weak password on a sub-site admin account or one traffic spike can reach every site. How far it spreads depends on the host. You still can’t fully isolate one site from the rest.

Agencies feel this most. A client wants a plugin nobody else needs, so it goes onto the shared codebase. Another client wants to leave, so you have to extract their site. Plenty of agencies have moved client sites off a single network for these reasons. Some went back to separate installs and some moved to isolated hosting. One Reddit user split off about 15 client sites but kept a network of around 50 nearly identical ones, which is the right pattern.

Leaving a network is harder than joining one. To extract a site you separate its database tables, media, users, URLs and plugin records. One estimate puts the first extraction at four to six hours, and it notes that some hosts charge per site to do it. Changing the network type later is also a migration. WordPress’s Multisite Network Administration page says that switching between subdomains and subdirectories takes more than editing SUBDOMAIN_INSTALL and the rewrite rules. The stored addresses, DNS, virtual hosts, TLS, redirects and cookies all have to change too.

The practical rule: if you might want separate sites later, start with separate sites. You can get the single-dashboard convenience with a management tool across isolated installs. Our explainer on what a multi site manager manages covers that choice. If you’d rather not handle the routine client requests yourself, SiteSelf for agencies handles the work on each connected site when you ask for it in chat.

Backups are the other hidden cost. In one wordpress.org thread about an 18-site network, a backup plugin’s free version could back up sub-sites manually, but it needed the paid version for scheduled backups and for the main site, and it could not back up the whole network as one package. Before you consolidate, test whether you can restore one site without touching the others. The usual steps to restore a WordPress site gain an extra step on a network: making sure you import only that site’s tables.

WooCommerce stores on a network do not share anything

Owners often expect one network to mean one catalogue. It doesn’t. WooCommerce’s installation docs say each sub-site stores its data in separate tables and runs on its own. Network activation does not share product databases, checkout sessions or user accounts. A customer who buys from two of your stores has two order histories.

Shared stock needs an extension, such as WooCommerce’s Central Stock or a sync plugin. For two related product lines, the usual advice on r/woocommerce is one store with categories and landing pages.

Does a business with several locations need several sites?

Usually not. Advice in small-business and marketing communities favours one site with a distinct page for each location or service. Separate sites duplicate the maintenance, make it harder to compare conversions, and split your search authority across several domains.

The location pages have to differ in more than the name. A page that is a clone of another with only the city swapped won’t do you any favours. Give each one real local content: staff, hours, the area served and reviews. Keep each one consistent with that location’s business profile.

What breaks after setup, and the order to check it

Most broken networks are infrastructure problems: DNS, the web server, certificates or cookies. A mapped domain only works when three layers agree: DNS and the host, the Site Address in WordPress, and SSL. Check them in this order.

1. DNS and host routing. Sub-sites on a subdomain network that return “Not Found” almost always come down to a missing wildcard DNS record, or a wildcard document root that doesn’t point at the WordPress directory. Creating an empty folder for each subdomain makes this worse. DNS changes can take up to 24 hours to propagate.
2. The Site Address. In Network Admin, go to Sites, then Edit, and set the Site Address (URL) to the full mapped URL, including https://. WordPress has supported this natively since version 4.5, according to the domain mapping handbook, so you don’t need an old mapping plugin.
3. SSL for every domain. The primary domain’s certificate does not cover mapped domains. A host rule that forces all traffic to the primary domain makes every mapped site unreachable.
4. Cookies. Only check these if login loops or “Cookies are blocked” errors remain on mapped domains. The handbook’s fix goes in wp-config.php after the network setup lines.
5. Rewrite rules. Replace the old WordPress rules with the exact ones that Network Setup generates, and back up the file first. On Apache, confirm that mod_rewrite is on and that AllowOverride permits .htaccess.

define( 'COOKIE_DOMAIN', $_SERVER['HTTP_HOST'] );

That line fixes one login problem. It does nothing for DNS, SSL or routing.

After a migration, “Error establishing a database connection” can mean more than bad credentials. On a network it can also mean the requested domain is missing from wp_blogs. A common cause is a search-replace that only reached one site. WP-CLI’s search-replace works on the current site unless you add --network. Our guide to changing a WordPress domain safely covers the network case.

Plugins are the other common source of trouble. WP Activity Log 5.3.4 was reported to make a network’s main site show the wrong content, and the developer shipped a redirects fix in 5.3.4.1. Gwolle-Gb 5.1.0 failed to network-activate with a fatal error, and the person who reported it said 5.1.1 worked. Test on staging or on one sub-site before you network-activate anything.

When to stop and get help

Stop if you are editing server configuration on a host you don’t control, if the main site is now broken as well, or if you are about to run SQL from the handbook’s debugging page on a production database. Those examples cover specific cases and can do damage if copied blindly. Ask your host whether your plan supports Multisite before you start. Many setup problems on shared hosting turn out to be host limits.

Frequently asked questions

Most people who search for a landing-page theme have the same problem. The offer is ready and the ad goes live on Friday, but the site’s header won’t go away and the form breaks on a phone. A new theme looks like the fix. Usually it isn’t.

On a landing page, the theme supplies the frame: header, footer, content width, base typography and the page templates on offer. The page itself is built on top of that frame with blocks, a builder or a plugin. When the frame can’t step aside cleanly, switching themes rarely fixes it. The template and the build route do. If you want the build steps, our guide on how to build a landing page in WordPress walks through them. This article covers the choice that comes first.

What should a landing-page theme actually give you?

Three things. Theme demos rarely show any of them.

A blank or full-width template in the free version. A landing page usually needs one of two layouts. One drops the header and footer completely. The other stretches content edge to edge and keeps the site frame. Check that the free tier includes the template you need before you build on the theme. A Virtue theme user on the wordpress.org forums tried a blank-slate plugin and several other fixes to remove the header and footer from one page. In the end, page-specific CSS was the workaround, because the theme’s own landing template was a paid feature.

A light base. The theme loads on every page, so a heavy theme makes every landing page heavy too. Pressidium, a host, tested default installs on its own servers. Hello loaded in under 230 ms, Neve in under 250 ms, and Astra and GeneratePress in under 300 ms. OceanWP took about 500 ms. Read these as a direction, not a promise. They are a host’s own test on an empty site, and they say nothing about conversions.

A fit with the editing model. Who will change the headline next month, and with what tool? A marketer who iterates every week needs something different from a developer who builds once and hands off. Decide this before you pick a theme, because the theme often pulls a builder in with it.

If you want names to start from, roundups such as ThemeBurn’s keep coming back to Astra, GeneratePress, Kadence, Blocksy and Neve as free starting points. Hello is the usual choice under Elementor. ThemeBurn itself says there is no universal winner. These are affiliate-funded lists, so treat them as a shortlist and check each theme against the three points above. Our guide to installing a WordPress theme safely covers testing one without breaking the live site.

Which build route matches who edits the page?

Pick the route first. The theme follows from it. There are three common routes, and each one fails in its own way.

A block theme with no builder

On a block theme you can build the whole page in the WordPress editor. WordPress.com’s support guide describes the route: create a Page, add patterns or blocks, then create a separate template without a header or footer and assign it to that page. WordPress’s own default theme, Twenty Twenty-Five, ships patterns for landing and services pages. It is free and has more than a million active installs.

The catch: WordPress.org’s documentation says the Site Editor only appears when a block theme is active. If Appearance shows Customize and no Editor, you have a classic theme, and block-theme tutorials won’t match your screens. Classic themes handle templates in PHP files instead.

A lightweight theme plus a page builder

This is the most common setup in practice. HTTP Archive’s 2025 Web Almanac found that about 60% of WordPress sites use a page builder. The theme stays minimal and the builder does the layout. In Elementor, the page layout setting decides how much of the theme shows. Canvas removes the theme’s header, footer and sidebars. Full Width keeps the header and footer and widens the content. Theme uses the theme’s normal layout.

The tradeoff is lock-in. A page built in a builder is edited in that builder, and moving off it later means rebuilding the layout, not swapping a theme. Our article on whether you need a landing page builder covers when that cost is worth paying.

A dedicated landing-page plugin

Plugins such as PluginOps bundle templates and campaign features. Some store pages as their own content type, outside the normal Pages list. One PluginOps user on wordpress.org thought publishing had failed because the page wasn’t in Pages. It was live the whole time and reachable from the plugin’s View link. That matters later, when someone else needs to find the page or wants to make it the homepage.

Why “I set the homepage and nothing changed” is rarely the theme

WordPress has precedence rules, and they catch people out. Check these before you blame the theme.

• The block theme’s front-page template wins. WordPress’s template hierarchy uses a front-page.html template for the front page even when Settings, Reading names a static page. Edit or remove that template, or build your landing design into it. Our guide to setting a page as the front page covers the full setting.
• Elementor Landing Pages can’t be the homepage. Elementor’s help center says the feature is deprecated as of Elementor Pro 3.27. Those pages are a custom post type, so they never appear in the Reading dropdown. Save the design as a template, insert it into a regular Page, and set that page as the homepage.
• The WooCommerce Shop page is set somewhere else. WooCommerce assigns its Shop page under WooCommerce, Settings, Products, and it can render as a product archive rather than a normal page. The homepage is still set in Settings, Reading.
• A custom template is missing the content call. If Elementor says “Sorry, the content area was not found in your page. You must call the_content function in the current template, in order for Elementor to work on this page.”, the page template doesn’t output content. Elementor’s fix is to switch the page to Elementor Full Width or Canvas.

If the page looks right in the editor and wrong when live, you are probably looking at a stale cache, not a template problem. Clear the caches one layer at a time: plugin, host, CDN, then check in a private window. On Elementor sites, also regenerate the CSS files. Our guide to a WordPress page not updating goes through that order. Clearing caches won’t fix a page that has the wrong template assigned, so check the template first.

What a blank template takes away that you still need

Removing the theme’s frame is the point of a landing page, and it also removes things you need. Elementor’s own example landing page keeps a footer with privacy and terms links. If your page collects email addresses, put those links back by hand.

Headings are next. Many themes print the page title as an H1. If your hero also uses an H1, the page has two, and both screen readers and search engines lose track of the structure. Hide the theme title properly, or make the hero heading an H2. Our guide on hiding page titles safely shows how for each theme type.

Last, check the form and the colours yourself. No theme does it for you. W3C’s WCAG 2.2 guidance sets minimum contrast at 4.5:1 for normal text and 3:1 for large text. Every form field needs a visible label, not just placeholder text. Bold hero designs often fail both checks.

When the theme is fine and the page is slow

A light theme only sets the starting weight. Hero videos, oversized images, animation libraries, chat widgets and tracking scripts are added at page level, and they can make any theme slow. One Salient theme owner on Reddit found the landing-page demo slow on mobile. They dropped the separate landing page and improved the existing product page instead. Sometimes that is the better campaign page anyway.

Measure the finished page with your real form, analytics and consent banner loaded, not the theme demo. If you’d rather not do the template and layout work yourself, SiteSelf handles design changes on your existing site from a chat request. It checks the changed page and reports what it did. Pages owned by Elementor, Divi or Beaver Builder are refused, with the reason.

Frequently asked questions

A landing page that reports 2% might really be converting at 5%. Or its form might not have delivered a lead in weeks. Either way, a new headline is the wrong fix, and you can’t pick the right one until you know which situation you’re in.

Landing page conversion rate is the share of visitors who complete the one action the page exists for. The arithmetic takes seconds. The mistakes happen when you decide what counts as a visitor and what counts as a conversion. This article covers how to calculate the rate, what the benchmarks mean, and the order in which to check a page that isn’t converting. If you’re still building the page, start with our landing page design best practices and come back once it has traffic.

How do you calculate landing page conversion rate?

Divide conversions by visitors and multiply by 100. Say a page gets 1,200 visitors and 66 of them submit its inquiry form: 66 ÷ 1,200 × 100 = 5.5%.

The numerator needs to be the finished action, not an attempt at it. Count the outcome the business can use.

The denominator is also a choice. Ad clicks, page views, sessions and users are four different counts, and each one gives a different rate. Choose one on purpose and keep it, because a rate only means something when you compare it with the same rate from an earlier period.

Why does the same page show two different conversion rates?

Each tool counts its own thing, and none of them is lying. A WooCommerce store owner on the wordpress.org forums found that the BrikPanel analytics plugin showed about 400 visitors for 1,000 Meta ad clicks. With 20 orders, that is 2% against clicks and 5% against tracked visitors. The support reply explained that clicks, page views and visitors measure different things. It also found that some visitors arriving from Meta’s mobile app weren’t being counted. The developer then added a setting that counts a visitor when the page opens.

Google Analytics 4 adds two more variables:

• Which event you count. GA4’s built-in form_submit event fires for every form on the site, including newsletter boxes and search forms. Google’s help center shows how to build a separate event from form_submit, filtered by the form’s form_name, and mark that event as a key event. Expect a delay before a newly created event appears in reports.
• How it is counted. GA4 can count a key event once per event or once per session. If a visitor submits twice, “once per event” counts two conversions. Pick one method and keep it.

The way your form submits matters too. In a wordpress.org thread, the Fathom Analytics integration for Gravity Forms recorded AJAX submissions but missed forms set to redirect after submitting. The workaround was to count views of the thank-you page as the conversion.

The fix for all of this is a reconciliation. Compare the analytics count with the entries your form plugin stored, or with the orders WooCommerce recorded, for the same dates. When the two don’t match, fix the tracking before you change anything on the page.

What is a good landing page conversion rate?

No published benchmark is specific to WordPress, and the three most-cited figures were measured in different ways.

A median and an average are different statistics. A few very successful pages pull an average up but barely move a median. Platform data and survey answers also cover different groups. Unbounce and HubSpot both describe 10% as a rough sign of a good page. Treat that as orientation, not as a target. In Databox’s survey of 90 companies, 21.52% didn’t know their own rate.

The comparison that tells you something is your own page against itself, split by traffic source and device. This matters most for ad budgets. If you plug a generic 5% into a campaign plan, a cold audience can turn a modest budget into very few leads. Spend a small test budget first and measure what an actual customer costs, not only what a lead costs.

Why isn’t my landing page converting? Check these in order

The order goes from quick checks that settle the question to slow ones that only suggest an answer. It reflects how often practitioners report each cause in forums and threads. It isn’t based on a survey.

1. Does the form actually deliver the lead?

Submit the form yourself on the published page, logged out, on a phone. Then check three things separately: the message shown on screen, the entry stored in the form plugin, and the email in your inbox. These fail independently. One reported pattern shows a success message to the visitor while no notification email is ever sent.

• Contact Form 7: “There was an error trying to send your message” usually means mail_failed, so WordPress couldn’t send the email. If you use WP Mail SMTP, open Tools, then Debug Events, and look for authentication failures or an expired Google connection. Set the From address to one on your site’s domain and put the visitor’s address in Reply-To.
• WPForms: an intermittent “Form Cannot Be Submitted” error has been traced to page caching serving an expired anti-spam token. Exclude the page from the cache or adjust the token lifetime.
• Elementor forms: a “Form Invalid” error can come from duplicate or blank field IDs. Give every field a unique ID.

Retest after every plugin update, because form plugins change. Our guide to adding a contact form to WordPress covers the setup side. If you’d rather not trace it yourself, SiteSelf can find and fix a broken form on your live site and report what it changed and what it checked.

2. On a store, does checkout finish?

WooCommerce’s documentation lists the usual causes of an endless checkout spinner: caching, firewall or security rules, JavaScript or extension conflicts, server errors and external services. Check Orders before you retry, because the order may already exist. Exclude Cart, Checkout, My Account and the AJAX and Store API requests from caching.

If the Checkout block shows no payment options, an active gateway may not be compatible with the block. Classic checkout is the documented fallback, but switching straight to it can hide the real cause. Guest checkout is controlled under WooCommerce, then Settings, then Accounts and Privacy.

3. Does it work on a phone, and quickly?

Google treats a page as giving a good experience when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 ms or less, and Cumulative Layout Shift is 0.1 or less, measured at the 75th percentile of visits. In 2024, HTTP Archive found that only 40% of WordPress sites passed all three on mobile, up from 28% in 2023.

Three WordPress mistakes come up again and again:

• Lazy-loading the hero image. It is usually the largest element on the first screen, and delaying it delays LCP.
• Testing speed straight after a cache purge. The first request is a cache miss, so run the same tool from the same location several times.
• Fixing only the tablet layout. In WordPress’s responsive styles (block themes, WordPress 7.1 and later), the Mobile setting falls back to the base style, not to Tablet. A tablet fix never reaches phones.

Our guide to making a WordPress site mobile friendly goes through the layout checks.

4. Does the page match the promise that brought people?

Message match is the most consistent theme in practitioner reports. One common mismatch is several ad groups for different services all pointing at one generic page. In a December 2025 r/smallbusiness thread, an owner said ad return rose from about 2x to about 3x after building a dedicated page. In r/woocommerce, a store owner said that sending influencer traffic straight to the cart moved conversion from 2% to 5%. Both are uncontrolled before-and-after reports, so read them as examples, not as expectations.

Traffic can be the problem rather than the page. In a March 2026 r/woocommerce thread, a store with 3,000 to 4,000 monthly visitors was converting at about 0.8%. The replies pointed at unqualified search traffic and unclear shipping costs before the design. Analytics give you numbers but not reasons. Session recordings and a short test with five to ten real customers show you where people hesitate.

Which changes are worth testing, and when can you trust the result?

W3C’s forms tutorial says people are more likely to abandon forms that ask for irrelevant or excessive information. So cut fields you don’t use. Cutting is not automatically a win, though. In CXL’s landing page case study, the longer original form beat a shorter version by 13.56%. A new headline raised opt-ins but produced 21.7% fewer conversions further down the funnel. Measure qualified leads or revenue, not only submissions.

CXL’s rule for a test is at least 7 days and 250 conversions per variant. A page converting 5% of 1,000 monthly visitors produces 50 conversions a month, so two variants would need ten months. At that volume, an A/B test mostly measures noise. A better approach is to change one thing at a time, compare it with your saved baseline, and write down the date and what changed so you don’t confuse a promotion or a broken week with a design win.

When should you stop and get help?

Stop when the SMTP log shows errors at the mail provider that you can’t resolve. Your host or email provider has to fix those. Stop when checkout requests return server errors, or when the problem only appears with a specific combination of plugins. Don’t deactivate plugins on the live site to find a conflict, because your visitors see every step. Use a staging copy, or the Health Check plugin’s troubleshooting mode, which disables plugins only for your own logged-in session.

Frequently asked questions

A visitor types an email address, clicks Subscribe and sees “Thanks.” The address may still never reach your list. The submission, the subscriber record and the confirmation email are three separate things. On WordPress, any one of them can fail while the other two look fine.

That is why this guide treats an opt-in form as a pipeline, not a widget. It covers which form types and setups exist, what conversion numbers mean, how to ask for consent cleanly, and why forms that look fine still lose people. If you only need a general enquiry form, our guide to adding a contact form in WordPress covers that separately.

What counts as an opt-in form, and which setup do you need?

An opt-in form is any form where a visitor agrees to join an email list. It can sit inline in an article, open as a popup or slide-in, run as a bar across the top of the page, or be a checkbox on another form such as contact or checkout.

WordPress has no single opt-in feature, so the setup depends on what you already use:

For one footer signup, a provider embed is often enough. A plugin earns its place when you need triggers, targeting by page, or testing. A slim announcement-style bar is another option, covered in our guide to adding a hello bar to WordPress.

What conversion rate should you expect?

Expect a few percent for popups. Then treat any benchmark as a direction to test, not as a target. The large datasets come from vendor platforms, not from WordPress sites, and they measure different things.

Omnisend analysed 1.24 billion popup displays from 2025 and reported a 2.1% average conversion rate. Popups that appeared after a 6 to 10 second delay converted at 2.4%, against 1.9% for those shown in the first second. Sleeknote’s dataset of more than 516 million views reports 4.42% for timer-triggered popups and 2.64% for scroll-triggered ones. Those two vendors define and sample differently, so don’t average them together.

The number that matters more is further down the funnel. One marketer on r/marketing described roughly 3% popup signup and 3% lead-to-sale conversion. After removing the popup, overall lead-to-sale conversion stayed about the same. Another described a lead-magnet page converting around 30% that produced zero booked sales calls. Count confirmed subscribers and what they later buy, not raw submissions.

Should it be a popup or an inline form?

Use both if you like, but keep the popup out of the way of the content. Google’s Search Central guidance names newsletter signup as a legitimate reason to use a dialog. It also warns that intrusive interstitials, the overlays that hide the page, make content harder to reach and can hurt search performance. It recommends a small banner that leaves the content usable instead of a full-page overlay.

In practice, that gives four rules:

• Delay the popup. Don’t fire it the moment the page loads.
• Use exit intent on desktop and a time or scroll trigger on mobile, a split many practitioners recommend.
• Cap how often the popup repeats, and make the close button as obvious as the submit button.
• Put an inline form after the reader has seen something useful, not only in the footer.

Popups are a real tradeoff, not a settled question. Some teams report measured revenue gains from a modal. Others see shoppers deliberately abandoning carts to wait for the discount email. Run a split test long enough to measure sales, not just signups.

How do you ask for the address and the consent?

Ask for an email, with name optional, and say exactly what the person will get. Every extra field is another place to quit. In one r/marketing report, a quiz with 16 or more questions lost 22% of users at the email question. Name the thing (“the Sunday briefing, one email a week”) and make the button say the action (“Send my first briefing”), not “Submit”.

The consent checkbox has accessibility rules that people often break. W3C’s Web Accessibility Initiative says each control needs a label that is programmatically tied to it, so a screen reader announces what the checkbox means. WCAG 2.2 success criterion 3.3.1 requires that a detected error is identified and described in text, so a red border on its own is not enough:

<input type="checkbox" id="news-optin" name="news_optin">
<label for="news-optin">Email me the weekly briefing (optional). Unsubscribe anytime.</label>

Keep the marketing checkbox unticked and separate from the thing the visitor asked for, such as a quote or an order. On the legal side, the FTC’s CAN-SPAM guidance covers US commercial email and requires a working opt-out and a valid physical postal address. Rules elsewhere, including the EU, are stricter. Have your wording checked for the countries you email.

Double opt-in sends a confirmation link and holds the contact as pending until someone clicks it. It costs some signups and filters out typos and fake addresses. Some services require it. Decide based on list quality, not on whether it hides a delivery problem.

How to set one up on WordPress

1. Set up the list first. In your email service, choose single or double opt-in, and check which fields the list marks as required.
2. Build the form. Use your provider’s embed, your existing form plugin’s integration, or a popup plugin. Map only the fields the list needs.
3. Place it. Add it with a block, shortcode or widget area, and set the display rules: which pages, which trigger, how often.
4. Exclude it from caching and script optimisation if your cache plugin or CDN offers per-page or per-script exclusions.
5. Test as a stranger. Open a private window, use a new address you control, submit, confirm, and check that the contact shows as subscribed in your email service. Repeat on a phone and using only the keyboard.

A correct result: the confirmation email arrives in the inbox, not spam. The contact moves from pending to subscribed. The first real email has a working unsubscribe link.

Why a form that says “thanks” still loses subscribers

Most failures come from configuration, caching or email delivery, not from a broken plugin. The message visitors see, such as “An error occurred, please try later”, rarely names the cause. The plugin’s integration log usually does. MC4WP, for example, keeps its log under MC4WP, then Other. Here are the causes in rough order of how often they turn up in support threads.

A required field the form doesn’t send

If the email service marks a field as required and the form doesn’t include it, the service rejects every submission. Hookedoncode described an email-only form failing because Mailchimp required First Name. Making that field optional in Mailchimp fixed it after two hours of searching and three minutes of work. Duplicating the broken form copies the same problem, so fix the original.

Cached pages and deferred scripts

The form works while you’re logged in and fails for the public. Page caching can serve an expired WordPress security token, called a nonce, to logged-out visitors. Script optimisers can defer or combine the JavaScript that submits the form. MailPoet’s changelog records 2026 fixes for signup forms failing when cached nonces expire. Gravity Forms has a whole FAQ page on cache and script optimiser problems. Turn optimisation off once to confirm the cause. Then exclude only the form page and the form’s scripts, not the whole site.

A pending contact that looks like a failure

With double opt-in, the popup can record a conversion while the email service holds the contact as pending. A support reply on the OptinMonster forum explains exactly this with Mailchimp. Check the contact’s status before you assume the form is broken.

The confirmation email never arrives

In one MC4WP thread, the log said success but confirmations were landing in spam. The owner traced it to a Mailchimp sending domain that hadn’t been verified. If your site sends the email itself through an on-site plugin, WordPress mail needs authenticated SMTP or an email API. Some hosts restrict ports: WP Engine blocks port 25 and recommends port 2525, with 587 and 465 also allowed. Fix delivery rather than switching off double opt-in.

Styling that makes a working field look broken

A wordpress.org thread about a “broken” Mailchimp footer form turned out to be white text on a white background. A few lines in Appearance, then Customize, then Additional CSS fixed it. Before you blame the connection, type into the field and highlight it.

A missing checkout checkbox on WooCommerce

Extensions that hook into classic checkout may not appear in the Checkout block. WooCommerce documents that its Subscribe to Newsletter extension supports both classic and block checkout. Its troubleshooting docs warn that switching checkout type can hide a compatibility problem instead of fixing it. Check the extension’s compatibility first, and switch only as a deliberate workaround.

Conflicts and firewall rules

If none of the above explains it, isolate the problem. The Health Check plugin’s troubleshooting mode turns off plugins and switches the theme for your admin session only, so visitors see the normal site. Security plugins and server firewalls such as Wordfence or ModSecurity can also block a form’s POST request. Test with protection briefly off, then allowlist the specific request and turn protection back on. Check the plugin’s changelog for your installed version too. Sometimes the bug is real and already fixed.

Stop and get help when the log shows API errors you can’t read, when the problem only shows up on the live server, or when the fix means editing theme code. If you’d rather not chase it yourself, SiteSelf can handle fixing a broken WordPress form on request. Cache and code fixes need hosting access, and your email platform’s settings stay yours to change.

Frequently asked questions