Blog

  • How to improve SEO performance on WordPress

    Key takeaways

    • Check indexability before anything else: the Reading setting, X-Robots-Tag headers, robots.txt and CDN or firewall rules. A page Google cannot index cannot rank.
    • Google’s ‘good’ Core Web Vitals are LCP of 2.5 seconds or less, INP of 200 ms or less and CLS of 0.1 or less, measured on field data. Google says good scores do not guarantee top rankings.
    • The 2024 Web Almanac found only 43% of sites passed Core Web Vitals on mobile. Fix the real bottleneck, and never lazy-load the hero image.
    • Pages that already sit around positions 4 to 20 are the practitioner favourite for quick gains. Refresh them before you publish new posts.
    • Give titles, canonicals, robots directives, schema and the sitemap to one SEO plugin. On WooCommerce, keep Cart, Checkout and My Account out of every cache layer.

    A WordPress site can have a green SEO plugin score, a 95 in PageSpeed Insights and a sitemap submitted to Google, and still get no search traffic. Each of those numbers measures one thing. None of them measures whether Google can index your pages, whether those pages answer what people search for, or whether real visitors get a usable page.

    Better SEO performance comes from doing the work in the right order. Fix whatever stops Google from seeing the right pages. Then improve the pages that are close to ranking. Then fix the speed problems real visitors have. Measure each step before you start the next. If you have not set up the basics yet (an SEO plugin, a sitemap, permalinks), start with our step-by-step WordPress SEO setup and come back here.

    What order should you fix things in?

    Start with indexing and finish with measurement. Google, WordPress and WooCommerce documentation all point to the same sequence, and so do the support threads:

    1. Indexability. Public pages are not set to noindex and are not blocked.
    2. Crawling, canonicals and the sitemap. Google can find each page through normal links and knows which URL is the main one.
    3. Content and titles. The pages that matter are useful, distinct from each other and well linked.
    4. Real-user speed. Problems confirmed in field data, fixed at their source.
    5. Tested cache and plugin changes. Especially anything that touches a store checkout.
    6. Measurement. Search Console and analytics, compared against a baseline you recorded first.

    No study has measured the payoff of this exact order. The logic is simple, though. Rewriting a title does nothing for a page Google has been told not to index, and a faster page does nothing for a page nobody searches for.

    Make one kind of change at a time. If thirty edits go live in the same week and rankings drop in week three, you cannot tell which edit caused it.

    Is Google actually allowed to index your pages?

    Check this first, because it is the most common silent failure. The site looks fine to you while Google is told to stay away.

    The Reading setting. Go to Settings, then Reading, and look at “Discourage search engines from indexing this site”. WordPress.org’s Reading screen documentation explains that this box asks search engines not to index the site. It does not stop visitors, so you will not notice it is on. It is often ticked during development and never unticked at launch.

    Header-level noindex. A noindex can also come from an HTTP header, X-Robots-Tag: noindex. Hosts and staging tools sometimes set it. It does not appear in the page source, so view source will not show it. Open the browser’s Network tab, click the page request and read the response headers.

    robots.txt. Google’s noindex documentation explains a trap here. If robots.txt blocks a URL, Google may never fetch the page, so it never sees a noindex on it. Use robots.txt to control crawling and noindex to control indexing, and do not stack them.

    CDN and firewall rules. Practitioners keep reporting the same pattern: a site with excellent speed scores loses rankings because Cloudflare, a WAF rule or a bot filter is challenging Googlebot. Optimisation plugins that intermittently return 503 errors cause the same problem. To check, run URL Inspection in Search Console and use the live test. If Google cannot fetch the page, fix that before anything else.

    Once the block is gone, request indexing once and then wait. Unticking the box does not make pages appear within hours, and requesting indexing again and again does not speed it up.

    Which Search Console statuses matter, and which are noise?

    Open Indexing, then Pages, and read the reasons, not the totals. Three statuses cause most of the confusion.

    • Discovered – currently not indexed. Google knows the URL exists but has not crawled it yet. On a new or weakly linked site, add internal links to the page and give it time.
    • Crawled – currently not indexed. Google fetched the page and decided not to index it. This usually points to quality, not a technical fault: the page is thin, duplicates another page, or nothing links to it.
    • Alternate page with proper canonical tag. Usually just information. Google found a duplicate, such as a URL with tracking parameters, and indexed the main version instead.

    Fix by cause, not URL by URL. Group the excluded pages by reason, fix one group, then export the report again. Do not remove noindex from archives you excluded on purpose. Whether thin tag archives belong in the index is a judgment call, and how tag archives affect SEO walks through it.

    Are your links, canonicals and sitemap working together?

    Google finds pages mainly by following links. A sitemap only helps. Google’s link best practices ask for ordinary <a href> links with descriptive anchor text. Links that only appear after a JavaScript click may never be crawled. Every page you want to rank should be linked from at least one other page, ideally one that already gets traffic.

    The sitemap is a list of hints. Learn WordPress puts it plainly: a sitemap helps search engines find your content but does not boost rankings by itself. It should list only canonical URLs. If a page is missing from Yoast’s sitemap, check whether it is set to noindex, has a canonical pointing elsewhere, or redirects. Those are the reasons Yoast’s help pages list.

    For duplicates, choose the main URL. Then redirect the copies to it or point them at it with rel="canonical". Do not use robots.txt or noindex to pick a canonical. A canonical tag is a hint, and Google can choose a different URL anyway.

    Give every SEO output to one system. Two plugins, or a theme plus a plugin, both writing titles, meta descriptions or sitemaps is a common self-inflicted problem. Support threads show the symptoms: “Duplicate meta descriptions” warnings, or a sitemap error that says “XML declaration allowed only at the start of the document” because something prints output before the XML. If you switch SEO plugins, migrate the custom titles and descriptions before you deactivate the old one. One Reddit user removed Yoast first and lost traffic along with the fields.

    Never change URLs without a redirect map. A redesign or a permalink change with no redirects turns pages that earn traffic into 404s. Map every old URL to its closest new one before launch. Our guide to redirecting a page without losing traffic covers the mechanics.

    Which pages should you improve first?

    Improve the pages that already nearly rank, before you write new ones. Practitioners agree on this more than on any other tactic. There is no controlled study behind it, but the reasoning holds: those pages are already indexed and already showing up in results.

    1. In Search Console, go to Performance, open the Pages or Queries tab, and filter average position to roughly 4 to 20.
    2. Sort by impressions. Pages with high impressions and low clicks are your shortlist.
    3. For each page, list the queries it appears for that the text does not actually answer. Add a section for each one, with a heading in the reader’s words and the answer in the first two sentences.
    4. Replace stale facts, prices and screenshots.
    5. Add internal links to the page from related pages that get traffic.
    6. If the page gets impressions but few clicks, rewrite the title so it says plainly what the page delivers. Compare “Drain Cleaning | Acme Plumbing” with “Same-Day Drain Cleaning in Austin | Acme Plumbing”.
    7. Request indexing once, note the date, and leave the page alone for a few weeks.

    Publishing more is not the fix. One r/Wordpress owner had 148 articles, 36 of them written in a single month, and almost no traffic. Replies told him a bigger hosting plan would not change that. Where several pages target the same intent, merge them into one stronger page and redirect the others to it.

    Keep titles and alt text specific rather than stuffed with keywords. Google may rewrite titles and write its own snippets from the page content anyway. For decorative images, empty alt text (alt="") is correct.

    How much does speed matter for SEO performance?

    Speed counts, but less than most audits suggest. Google’s Core Web Vitals documentation sets “good” at Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of real visits. Google’s page experience guidance also says good scores do not guarantee top rankings. Practitioners report raising PageSpeed from the 50s to 90+ and seeing no real change in search traffic.

    Use the Core Web Vitals report in Search Console, which is real-visitor data, to decide whether you have a problem. Use Lighthouse only to work out why. The 2024 Web Almanac found that 43% of sites had good Core Web Vitals on mobile and 54% on desktop, so failing on mobile is normal. It is still worth fixing, for visitors and conversions as much as for rankings.

    MetricUsual WordPress causeFixTrap
    LCPOversized hero image, found lateResize and compress it, and keep it in the initial HTMLLazy-loading the hero, or preloading several images that compete for bandwidth
    INPLong JavaScript tasks from plugins and trackersRemove or defer scripts that load on pages that never use themAssuming minify-and-combine fixed responsiveness
    CLSImages and embeds without dimensions, late bannersSet width and height, and reserve space for ads and noticesReserving so much space that it leaves blank gaps

    web.dev’s LCP guide is explicit that the main image should not be lazy-loaded. Optimising pictures in WordPress covers the image side in detail.

    Before you install a speed plugin, check what your host already caches. A caching plugin on top of server caching often adds conflicts rather than speed. To find the actual bottleneck, deactivate extensions one at a time on a staging copy and retest, then try a default theme. Speeding up a WordPress site safely goes through that process.

    On WooCommerce, test caching on the checkout. WooCommerce’s documentation tells you to exclude Cart, Checkout and My Account from page and edge caching. Exclude them in every layer: plugin, host and CDN. Purge everything, then test both as a logged-out visitor and as a shopper with items in the cart. A cached checkout leads to stale prices, an endless spinner, or one customer seeing another’s session.

    How do you know whether it worked?

    Record a baseline before each change: impressions, clicks, average position and conversions for the pages you are about to touch. Then compare the same pages, not site-wide totals. Technical fixes usually show after Google recrawls, often within days to a few weeks. Content improvements take weeks to months. Nobody can promise a timetable, and anyone who guarantees rankings is selling something.

    Read the numbers in combination. Rising impressions with flat clicks means people see the page but don’t choose it, which points to the title, the snippet, or an AI answer above it. Rising clicks with flat leads means the page attracts the wrong intent. Track the business outcome, such as enquiries, calls or orders, alongside the search numbers.

    If traffic drops after a rebuild, check redirects and indexing before you blame seasonality. Comparing year on year in Search Console usually settles it.

    How does this work change when an agent does it?

    Most of this work is diagnosis, followed by a small edit: a title, a redirect, a noindex flag, a link. The edit takes minutes. For a business owner without a web team, the slow part is the queue: finding someone, explaining the problem, waiting for the slot, and checking that it was actually done.

    Example request: “Our drain cleaning page sits around position 9 with lots of impressions and few clicks. Rewrite its SEO title and meta description to match ‘same-day drain cleaning in Austin’, add a link to it from the services section on the homepage, and tell me what changed.”

    SiteSelf would find the page, read its current title and description in your SEO plugin, and tell you what it is about to change and whether the change can be undone. Then it would make the edits on the live site. Afterwards it fetches the changed pages, checks that the new title tag and the link actually render, and reports back in chat. What it did is recorded. This work needs only the SiteSelf Connector plugin from the WordPress.org directory. Speed and caching work, such as server cache rules or code changes, needs hosting (SSH) access.

    The limits are worth knowing. The agent does not read Search Console yet, so you bring the numbers. It does not watch rankings afterwards, and nothing runs unless you ask for it. Pages owned by Elementor, Divi or Beaver Builder are refused at the moment of work, with the reason. The SEO fixes through chat page shows what is in scope, and the pricing page explains how credits work.

    Frequently asked questions

    Does installing an SEO plugin improve rankings?

    No. Yoast SEO, Rank Math and All in One SEO give you controls for titles, canonicals, sitemaps and schema. Rankings come from what you do with those controls and from the content itself. Run only one, so you don’t get duplicate tags.

    Will a better hosting plan increase my traffic?

    Only if speed or reliability is the actual problem. A host change can cut load times sharply, but it does nothing for pages that are blocked from indexing, thin, or not matched to what people search for. Check indexing and content first.

    Is a 90+ PageSpeed score worth paying for?

    Pay to fix problems that show up in Search Console’s Core Web Vitals report, which uses real-visitor data. Pushing a lab score from 80 to 95 rarely moves rankings, and adding a new tracking script can undo it the following week.

    Should I change permalinks on an established site?

    Only with a good reason and a redirect for every old URL, tested before launch. Without redirects, pages that already earn traffic turn into 404s and lose their history. Test structural changes on a WordPress staging site first.

    Does structured data get me rich results?

    It makes a page eligible for them, not guaranteed to get them. On WooCommerce, the price and availability in the markup must match what the page shows. Validate with the Rich Results Test, and avoid adding a second schema plugin on top of the one you already run.

    What should I ask for if I hire someone for SEO?

    Ask for a baseline before work starts, a list of the specific pages and fixes covered, who will make the changes, and how results will be checked. Make sure you keep ownership of your accounts and files. Be wary of guaranteed rankings and cheap link packages.

  • Can’t open page on your WordPress site? Fix it by symptom

    Key takeaways

    • Test in a private window and on a phone with Wi-Fi off before you touch the site. If the page loads there, the problem is your browser or network, not WordPress.
    • A critical error or white screen usually comes from a plugin, theme or PHP update. WordPress Recovery Mode, added in version 5.2, emails the admin a link that names the failing extension.
    • Re-saving Settings, then Permalinks, fixes 404s on pages that exist. It does nothing for deleted pages, DNS problems or fatal errors.
    • A WooCommerce Cart or Checkout page only works once it is assigned under WooCommerce, then Settings, then Advanced, then Page setup. Creating the page is not enough.
    • Health Check troubleshooting mode changes only your own session and does not put payment gateways into sandbox mode, so a test order can take a real payment.

    A customer says the checkout won’t open on their phone. You try the link and get a white screen, a gray box with an error code, or Safari’s “Safari can’t open the page.” All three look like the same complaint. They have different causes, and the wrong fix can turn one broken page into a broken site.

    No WordPress error is actually called “can’t open page.” It’s a description of what someone saw. Before you change anything, find out which layer is failing: the visitor’s device, the network, the server, WordPress itself or a single page.

    Whose problem is it? Five minutes of checks decide that

    Write down two things before you start clicking: the full URL from the address bar and the exact message, word for word. Then run these checks in order.

    1. Open the homepage and one other page. If only one URL fails, it’s a page or routing problem. If everything fails, it’s the site, the server or the domain.
    2. Open the failing URL in a private window. This drops your cookies and logged-in state. Pages that fail only for logged-out visitors are more common than people expect.
    3. Try your phone with Wi-Fi switched off. Mobile data takes your router, office network and DNS resolver out of the picture.
    4. Ask someone on a different network to try it. What one browser shows doesn’t prove the site is down. In one Reddit thread, an owner kept seeing a critical error while a commenter could load the site normally.
    What you seeWhere the fault usually isFirst check
    “Safari can’t open the page”, ERR_NAME_NOT_RESOLVED, a timeoutDevice, network or DNSAnother device on another network
    “There has been a critical error on this website”, a white screen, HTTP 500PHP fatal error in a plugin, theme or custom codeRecovery Mode email, then the error log
    404 on a page you know existsRewrite rules, slug, or a deleted or private pageSettings, then Permalinks, then Save
    Blank or 404 Cart, Checkout or My AccountWooCommerce page assignment, endpoints, cacheWooCommerce Page setup
    ERR_TOO_MANY_REDIRECTS, “Your connection is not private”Competing redirect rules or an SSL certificateCDN SSL mode and redirect rules
    “Error establishing a database connection”, 502, 503Database, host or server resourcesHost status and logs
    403 ForbiddenFile permissions, .htaccess rules or a firewallHost and security plugin logs

    If the page opens on mobile data but not on your Wi-Fi, the site is fine. The fix is on your side: pause any VPN or security extension, flush your DNS cache and restart the router. Our guide to fixing DNS errors on your site covers the case where the domain itself doesn’t resolve for anyone. For whole-site outages, the walkthrough on why WordPress is not loading goes further than this article.

    A critical error or white screen means read the error before you disable anything

    Practitioners most often report this cause, usually right after a plugin, theme or PHP update. No dataset ranks these causes, though. WordPress’s own common-errors handbook lists plugin incompatibilities, PHP errors, memory limits and corrupted files without saying how often each one happens.

    The generic message isn’t a diagnosis, but WordPress usually has the real one. Since version 5.2, Recovery Mode emails the site admin when a fatal error happens. The email has a special login link that shows the error and lets you pause the plugin or theme that caused it. Check the admin inbox, including spam, before anything else.

    If no email arrives, read the newest lines of your host’s PHP error log for “Fatal error” or “Parse error” and note the file path. A path inside wp-content/plugins/ or wp-content/themes/ names the culprit. If the host has no log, have WordPress write one by adding these lines to wp-config.php above the “stop editing” line:

    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );

    Reload the failing page once, then read wp-content/debug.log. WP_DEBUG_LOG only works when WP_DEBUG is on. Keep display off, because errors shown on a public page can expose file paths and other details. Remove the lines once you have your answer.

    If you can’t reach wp-admin, rename the plugin’s folder over SFTP or in the host’s file manager to deactivate it. Renaming the whole plugins folder is the blunt version. It leaves must-use plugins and cache drop-ins such as advanced-cache.php and object-cache.php running. In a 2026 WordPress.org thread about a client site moving hosts, those leftover drop-ins came up as a likely trap. Re-enable plugins one at a time or in small groups, and don’t leave everything off. One agency in another thread found that an automatic deactivation had quietly taken contact forms offline across client sites.

    More detail, including memory errors, is in our guide to fixing a WordPress fatal error.

    One page returns 404 while the rest of the site works

    If the page exists in the editor but its address returns 404, the rewrite rules are usually stale. Go to Settings, then Permalinks, and click Save Changes without editing anything. WordPress regenerates its rules. WordPress’s handbook says to ask your host to check mod_rewrite if that doesn’t work.

    Re-saving only fixes routing. It won’t bring back a deleted page, fix a mistyped slug or make a private page public, so check the page’s status and slug first. If a custom post type shares a name with the page, rename one of them. On Apache, back up .htaccess before you edit it and keep any custom redirect rules. On Nginx, .htaccess does nothing, so the host has to check the server rules.

    Don’t change the permalink structure to make a 404 go away. Every URL on the site changes, and old links break. Our guide to permalinks that are not working covers the harder cases.

    A WooCommerce Cart or Checkout page that is blank or missing

    WooCommerce’s documentation lists four usual causes: a missing or unassigned page, permalink problems, stale caches and plugin or theme conflicts. A page called “Checkout” does nothing until WooCommerce knows it is the checkout. Create the page with the Checkout block (or the Cart or My Account block), then assign it under WooCommerce, then Settings, then Advanced, then Page setup, and save.

    The order-received page and the My Account sections are endpoints, not separate pages. If one of them returns 404, re-save permalinks and check the slugs under WooCommerce, then Settings, then Advanced, then Endpoints. Exclude Cart and Checkout from page caching, because they hold session-specific content.

    Be careful testing conflicts on a live store. WooCommerce warns that Health Check troubleshooting mode can give false positives with some plugin, theme and hosting combinations. It also doesn’t put payment gateways into sandbox mode, so a test order can take a real payment. A WordPress staging site is the safer place for that test.

    Redirect loops and certificate warnings come from rules that disagree

    ERR_TOO_MANY_REDIRECTS means two rules keep sending the request back and forth. A common pattern behind Cloudflare is the Flexible SSL mode combined with a server that redirects HTTP to HTTPS. Cloudflare’s documentation says to use Full or higher when your server has a certificate, and to look for redirect rules that conflict. Check WordPress, your host and the CDN, then retest in a private window, because browsers cache redirects and can make a correct fix look like it failed.

    “Your connection is not private” points to a certificate that has expired, is missing or doesn’t match the domain. Your host or CDN issues the certificate, so the fix lives there.

    The whole site is unreachable or shows a database error

    If no page opens on any network, look outside WordPress first. Check that the domain hasn’t expired, that DNS still points at your host, and whether the host is reporting an outage. No WordPress setting can fix any of these.

    “Error establishing a database connection” can mean wrong credentials in wp-config.php, a database server that is down, or a database too large or locked to answer. In one 2026 WordPress.org thread, the host blamed a 35.68 GB wp_options table, mostly transient data, plus MyISAM table locking. The advice there was to find what was writing the data, back up, and plan the cleanup with the host. Deleting rows at random can do real damage.

    “Briefly unavailable for scheduled maintenance” that never clears usually means an interrupted update left a .maintenance file in the site root. Delete that file once you’ve confirmed no update is still running.

    It opens for you but fails for visitors or for Google

    A logged-in admin often sees a different site from everyone else. In one r/woocommerce thread, a store loaded only for logged-in users and showed 404s in the console for everyone else. Disabling an offload plugin and repairing permissions didn’t help. The cause turned out to be the theme’s full-page preloader, and switching themes fixed it. Test logged out, every time.

    Cache is the other usual suspect. A caching plugin, the host’s server cache or CDN, and the visitor’s browser can each serve an old copy. Clearing your own browser only clears one of the three.

    If people can open the page but Google reports it can’t, run the URL through Search Console’s URL Inspection tool and use Test live URL. Google’s help page lists the usual blockers: a password, a robots.txt rule, or a noindex tag, which allows access but keeps the page out of the index.

    When to stop and get help

    Stop when the next step means editing the database, changing file permissions across the site, or running conflict tests on a store that takes payments. Stop too when the log points at the server rather than a plugin. Hosts usually handle infrastructure but send plugin and theme faults back to you, so open the ticket with the URL, the exact error, the time it started and what changed just before.

    Whoever does the work should log every change and take a backup first. A restore is fast, but it throws away everything changed since the backup and doesn’t always fix the problem. Read the logs before you decide.

    If you’d rather hand the job over, SiteSelf takes the URL and the error through chat and troubleshoots the WordPress site directly. It needs hosting (SSH) access to read logs and edit files.

    Frequently asked questions

    How do I know if my site is down for everyone or just me?

    Load it on a phone with Wi-Fi off, then ask someone on a different network to try. If it loads anywhere, the site is up and the problem is local: your browser, an extension, your router or your DNS resolver.

    Why does the public site work but wp-admin won’t open?

    Common causes are security or login-hiding rules, redirect conflicts and a mismatch between the WordPress Address and the Site Address. Our guide to fixing WordPress login by symptom works through each one.

    Should I restore a backup or keep troubleshooting?

    Read the error log first. It usually takes minutes and changes nothing. A restore discards orders, posts and settings changed since the backup, and if the cause is the server or a PHP version change, the restored site can fail the same way.

    Can I use Health Check troubleshooting mode on a live store?

    You can, and visitors won’t see the change because it only affects your session. WooCommerce warns that it can give false positives and does not sandbox payment gateways, so take a backup and don’t place test orders unless your gateway is in test mode.

    Does clearing my browser cache fix a page that won’t open?

    Only when the problem is a stale copy or a bad cookie in your browser. It doesn’t touch the caching plugin, the host cache or the CDN, and it can’t fix a server error.

  • How WordPress tags affect SEO and what to do

    Key takeaways

    • Google ignores the meta keywords tag, so a WordPress tag is not a ranking keyword. Its only SEO effect comes from the /tag/name/ archive page it creates.
    • For a small site with years of unmanaged tags, noindex tag archives by default and make deliberate exceptions. A publisher or store with curated tags should judge each archive on its own.
    • Noindex only works on pages Google can crawl, so don’t block tag URLs in robots.txt. Use a 301 only when a close replacement exists, and never send every deleted tag to the homepage.
    • In Yoast, the sitewide tag setting and each tag’s own Advanced setting are separate. AIOSEO handles paginated pages with separate settings, so check the source of /tag/name/ and /tag/name/page/2/, not just the toggle.

    Adding more tags won’t make your WordPress posts rank better. Setting every tag archive to noindex won’t save a weak site either. Both shortcuts skip the one decision that matters: does this tag’s archive page deserve to be a search result?

    Each tag you create gives WordPress a new public URL, usually /tag/tag-name/, plus /tag/tag-name/page/2/ and onward once enough posts share it. A site with 40 posts and 200 tags has made 200 listing pages, and most of them show one or two excerpts. That is where tags and SEO actually meet.

    Do WordPress tags help SEO at all?

    Not directly. A WordPress tag is a non-hierarchical taxonomy term for grouping posts. It is not a keyword field. Google’s list of supported meta tags says Google doesn’t use the meta keywords tag for ranking, and a post tag carries no more weight than that. Typing “best plumber London” into the tag box doesn’t tell Google anything about your post.

    A lot of the confusion comes from the habit of treating tags like hashtags or the old meta keywords field. Tags are for readers. They link related posts across categories, and our guide to tags vs categories in WordPress covers that split in detail. Any SEO effect comes from the archive pages: they are either useful landing pages or thin lists that repeat content already on your site.

    Thin archives are not a penalty. Google’s canonicalization documentation describes grouping similar pages and picking one to show. Thin archives still cost you something. Your blog’s search results fill up with near-empty listing pages, and you get one more set of URLs to keep tidy.

    Which tag archives should stay in Google?

    Keep a tag archive indexable when it collects a real group of posts that someone would search for as a group, and when no category already shows the same list. Everything else should be noindexed, merged into another tag or deleted.

    Tag situationExampleAction
    Several posts on a lasting topic, not covered by a category“Sourdough” tagging recipes, equipment reviews and lessonsKeep indexable. Add a real description and check that your theme displays it.
    Synonym of an existing tag“boiler-repair” next to “boiler-repairs”Move the posts to the stronger tag, delete the other one and 301 its URL to the survivor.
    Same name as a categoryA “Recipes” tag and a “Recipes” categoryDelete the tag. The category archive covers it.
    Used on one or two posts“Boiler servicing” on a single articleDelete the tag, or noindex it if readers still use it to get around.
    Useful for browsing, weak as a search resultA “Holiday hours” groupingKeep the tag and noindex the archive.

    Sources disagree about where the default should sit. Yoast’s current help pages present indexable taxonomy pages as possible landing pages. Its 2023 beginner’s guide said most WordPress SEO experts hide tag archives, and many freelancers noindex all tags as standard. One r/Wordpress commenter said they disable tags on about 90% of client sites. Both camps use the same test, though: is the page useful? For a small business site with years of unplanned tags, both answers lead to the same place. Noindex the tag archives and make exceptions on purpose. Publishers and stores that maintain their tags should judge each one.

    No one has an official minimum number of posts per tag. Rules like “five posts before indexing” are habits some teams use, not Google requirements.

    How to audit your tags in one pass

    1. List every tag. Go to Posts > Tags and sort by the Count column. A crawler such as Screaming Frog also finds tag URLs that are still linked somewhere.
    2. Add Search Console data. In Performance, filter pages to URLs containing /tag/ and note impressions and clicks. An archive that gets impressions deserves a closer look before you remove it.
    3. Group the problems. Mark synonyms, tags that share a category’s name, and tags used once or twice. Compare the posts each tag actually lists, not just the names.
    4. Look for overlap with your posts. If a tag archive and an article both get impressions for the same queries, the article is usually the better answer and the archive is in the way.
    5. Give each tag one action: keep, improve, noindex, merge or delete. For merges, write down the replacement URL.
    6. Back up first. WordPress keeps revisions for posts, but not for deleted tags. Export names, slugs and post assignments before you delete anything.

    Which fix matches which tag

    Keeping a page out of search, replacing it and removing it are three different jobs, and each one has its own tool.

    • Noindex keeps an archive out of results while visitors can still use it. Google has to crawl the page to see the instruction. Its robots meta tag documentation warns that a URL blocked in robots.txt can still appear in results. Don’t block tag pages in robots.txt as well.
    • A 301 redirect is for a merged synonym. Send the old archive straight to the tag that replaced it. Our explainer on how a 301 redirect affects SEO covers chains and testing.
    • A 404 is fine for a deleted tag with no close replacement. Redirecting every old tag to the homepage helps nobody, and the 404s that then show up in Search Console are expected.
    • A canonical is only for pages that really are duplicates. Google says canonical annotations are the preferred way to signal duplicates and that noindex is not the tool for it. Pointing every tag canonical at the homepage or the blog page is a misuse.

    Leave tag slugs and the tag base under Settings > Permalinks alone. Keywords in a URL path barely help rankings, and every changed URL needs a redirect.

    Where the noindex settings live

    In Yoast SEO, open Yoast SEO > Settings > Categories & tags and turn off showing tags in search results. For one tag, edit it under Posts > Tags, open the Yoast SEO Advanced section and set “Allow search engines to show this content in search results” to No, as Yoast’s noindex guide describes. All in One SEO and Rank Math have similar taxonomy settings under their search appearance and titles screens, but the menu names are different.

    A noindexed archive should also be taken out of your XML sitemap. Yoast does this automatically. If a noindexed URL stays in a sitemap, Search Console reports “Submitted URL marked noindex”. Yoast’s advice is to first confirm the noindex was intended.

    Why tag pages still say “index” after you turned it off

    The settings screen shows what you saved. The page source shows what Google actually receives, so check that.

    In one Yoast support thread, a user turned off “Show tags in search results”, cleared every cache and switched plugins off one at a time. The tag pages still output index, follow, and URL Inspection still said the page was allowed for indexing. Support explained that individual tags can carry their own setting and that Search Console data isn’t real-time. A tag sitemap returning 404 did not prove the tags were noindexed.

    Pagination can behave differently from page one. In an All in One SEO thread, page one of a tag archive output max-image-preview:large while page two output noindex, nofollow, max-image-preview:large. The fix was unchecking “No Index Paginated” and “No Follow Paginated” under Search Appearance > Advanced. Another AIOSEO report in late 2024 found paginated canonicals missing a slash, as in /tag/slugpage/2, and support supplied a code snippet. If you see that, update the plugin before writing workarounds.

    To check a change:

    1. Open /tag/name/ logged out and view source. Find <meta name="robots" and rel="canonical".
    2. Repeat on /tag/name/page/2/.
    3. Check the response headers for X-Robots-Tag. Some hosts, Kinsta among them, add this header on staging, and it can survive a careless push to live. If your whole site has dropped out of search, also check Settings > Reading.
    4. Run URL Inspection’s live test. Then give Google time to recrawl before you decide the change failed.

    WooCommerce product tags are a separate decision

    Product tags can be real shopping pages. WooCommerce’s documentation describes tags that group products across categories, and it ships templates for product-by-tag archives. A product keeps one URL however many categories and tags it belongs to, so tagging doesn’t duplicate product pages.

    Use categories for product types and tags for groups shoppers would browse across categories, such as a material or a season. Use attributes when shoppers need to filter, because attributes don’t need archive pages of their own. Filter-combination URLs fall under Google’s faceted navigation guidance, which is a separate problem from tag archives. Adding 15 or 20 tags to every product is the same keyword-field mistake with more items to undo. After a WooCommerce update, check that your SEO plugin still outputs the right metadata. Yoast SEO 26.9 temporarily restored old behaviour after WooCommerce 10.5 changed its permalink logic.

    How to stop tag sprawl from coming back

    Sprawl is a habit problem more than a WordPress problem. Write a short rule into your editorial checklist: reuse an existing tag before creating a new one, and only create a tag when you can already name a few posts that belong in it. Give one person ownership of the tag list, and look at Posts > Tags once a quarter. For the wider set of checks around this, see our step-by-step WordPress SEO guide.

    If you’d rather hand off the noindex settings, redirects and checks, SiteSelf handles SEO settings and redirects through chat on your existing site and reports what it checked on the live page.

    Frequently asked questions

    Can tag pages compete with my own posts in Google?

    They can. Some site owners suspect it when tag URLs start getting impressions for queries their articles should win. No one has measured how often it happens. Search Console’s Performance report shows which URLs get impressions for a query. If a tag archive keeps showing up in place of the matching article, noindex the archive.

    How many tags should a post have?

    Google sets no limit. A handful that match how readers browse is plenty. More tags per post mostly means more thin archives.

    I deleted tags and Search Console now shows 404s. Is that a problem?

    No. A 404 is the correct response for a tag that no longer exists. Redirect only the ones that had links or traffic and have a close replacement.

    Does noindexing a tag remove it from my site?

    No. The tag stays on your posts and the archive still works for visitors. Noindex only asks search engines to leave the page out of results.

    Should I remove the tag cloud from my footer?

    It’s a common cleanup step, but it’s about navigation, not a ranking rule. If you keep tag links, make the link text say what’s on the other end. WCAG 2.2’s link purpose criterion asks for exactly that.

  • Fix a WordPress contact form not sending email

    Key takeaways

    • A true return from wp_mail(), a green Contact Form 7 notice or a passing SMTP test only means the message was handed off. None of them proves it reached an inbox.
    • Contact Form 7 shows the same error text for spam blocks and mail failures. The border colour tells them apart: orange is a spam module, red is a failed mail call.
    • Installing WP Mail SMTP changes nothing until you pick a real mailer. Its default PHP Mailer option leaves delivery exactly as it was.
    • Put an address on your own domain in From and the visitor’s address in Reply-To. A visitor’s Gmail address in From looks like spoofing to the receiving server.
    • In one review of 150 confirmed public cases, the missing email was sitting in spam only 8 times. Check spam, but don’t stop there.

    The visitor sees a success message, but the email never reaches your inbox. Often nobody notices for weeks, until enquiries slow down or a customer phones to ask why nobody replied. The form plugin is rarely broken. The message stopped somewhere between the form and the inbox, and the fix depends on where.

    WordPress doesn’t run a mail server. WordPress’s mail handbook says wp_mail() hands messages to PHP’s mail() by default, which depends on a mail transfer agent on the server. Hosts often block, limit or misconfigure that agent. The receiving provider, such as Gmail or Microsoft 365, then decides whether to accept the message. If the form itself was set up recently, check it against our guide to adding a contact form in WordPress before going further.

    Why “message sent” doesn’t mean the email arrived

    A success message means the form handed the email off. It doesn’t mean anyone received it. The wp_mail() reference says a true return only means WordPress processed the request without error. A passing test in an SMTP plugin or a “Sent” line in a log has the same limit.

    Every case of “no email arrived” fails at one of four stages:

    StageWhat you seeWhere to look
    Submission blockedSpinner, error, or orange notice in Contact Form 7Browser Network tab, spam protection settings
    Form never requested mailSuccess, but nothing in any mail logThe form’s notification or Mail settings
    Handoff failedRed notice, or an error in the SMTP logSMTP plugin log, host mail settings
    Lost after handoffLog says sent, inbox is emptySpam folder, mail routing, SPF/DKIM/DMARC

    How to find the failing stage in five minutes

    Run these checks before you change any settings. Each one rules out a stage.

    1. Submit the form yourself in a private window and note the time. If you test while logged in, caching and security token problems that hit real visitors stay hidden.
    2. Read the response. Contact Form 7’s FAQ explains what the border colour around its message means. Orange means a spam module (Akismet, reCAPTCHA or the disallowed list) flagged the submission. Red means the wp_mail() call failed. Green means the handoff finished, so look further down the path. The text alone tells you nothing, because Contact Form 7 deliberately shows “There was an error trying to send your message” for both spam and mail failure.
    3. Check whether the entry was saved. Contact Form 7 doesn’t store submissions on its own. Its FAQ points to the Flamingo plugin for that. If your form plugin stores entries and this one is missing, the problem is in the form.
    4. Test the whole site’s mail. Use “Lost your password?” on the login screen. If WordPress says “The email could not be sent. Your site may not be correctly configured to send emails,” the problem affects every email the site sends, not just this form. Our password reset guide covers what that screen tells you.
    5. Open the mail log, if an SMTP or mail logging plugin keeps one. If there’s no entry for your test, the form never asked for an email. An entry with an error means the handoff failed. An entry marked sent means the message was lost later.

    When the form never asked for an email

    Many missing emails were never sent at all, and SMTP settings can’t fix those. In one developer’s review of 150 confirmed public cases, the form never triggered an email in 24 of them. Spam protection was involved in 10 of those 24.

    Spam protection rejecting real visitors

    reCAPTCHA keys have to match the current domain. Keys left over from an old domain after a migration will fail quietly. Contact Form 7 says a missing reCAPTCHA token can also come from the script not loading or the theme misbehaving. Running reCAPTCHA v2 and v3 together causes conflicts too. Don’t just switch spam protection off. Find the module that’s responsible, or the inbox fills with spam instead.

    Requests blocked before WordPress sees them

    Open the browser’s developer tools, go to the Network tab, and submit again. A 403 response with the body -1 means the submission was stopped by a security plugin, a firewall or a cached page carrying an expired security token. Exclude the form page from caching, or allow that request in the security plugin.

    Mail settings inside the form

    Check the form’s own notification settings:

    • The notification is turned on.
    • The To field is a valid address.
    • No conditional rule sends mail for only one dropdown choice.
    • In Contact Form 7’s Additional Settings, there is no skip_mail: on line. It turns off mail completely.

    A new field also needs its own mail-tag in the email body. A field written as [text your-new-field] only shows up in the email if the body contains [your-new-field].

    If you suspect a conflict, turn on WP_DEBUG_LOG, which writes errors to wp-content/debug.log. Look for a fatal error at the time of your test. Then disable plugins one at a time on a staging copy of the site, using the method in fixing plugins that stop working.

    When WordPress can’t hand the message off

    A red notice or an SMTP error means WordPress tried to send and failed. The error text usually tells you which part failed.

    ErrorWhat it means
    Could not instantiate mail functionPHP mail can’t run on this host. Switch to authenticated sending.
    SMTP Error: Could not connect to SMTP hostWrong host, port or encryption, or the host or a firewall blocks the port
    535 Incorrect authentication dataThe mail server rejected the login. You may need an app password.
    Invalid address: (From)The sender address was rejected before sending

    The fix people report most often is to stop relying on the host’s PHP mail. Send through an authenticated SMTP or API mailer instead, using a plugin such as WP Mail SMTP, FluentSMTP or Post SMTP. Installing one isn’t enough. WP Mail SMTP’s troubleshooting docs say its default “PHP Mailer” option doesn’t improve delivery. You have to choose a real mailer and enter that provider’s settings.

    WP Mail SMTP’s connection guide recommends TLS on port 587, or SSL on port 465 if your provider requires it. It says not to use port 25. If your host blocks SMTP ports, use an API mailer, which sends over HTTPS. For Gmail or Google Workspace through “Other SMTP”, the settings are:

    • Host smtp.gmail.com, TLS on port 587, with authentication on.
    • Your full address as the username.
    • An app password, not your normal password. Google only lets you create app passwords after 2-Step Verification is turned on.

    Regular passwords fail with Gmail, Yahoo, Zoho and iCloud.

    When the email left but never reached the inbox

    If the log says sent and the inbox is empty, check four things in this order: the From address, the plugin settings, mail routing, then DNS records.

    The visitor’s address is in From

    This is the classic mistake. If From shows the visitor’s Gmail address, your server is claiming to send on behalf of gmail.com, and receiving servers treat that as spoofing. Contact Form 7’s mail setup best practice is to use an address on your site’s domain in From and put the visitor in Reply-To:

    From: Your Company <wordpress@yourdomain.com>
    Additional headers: Reply-To: [your-email]

    Replies still go to the visitor. If the owner would rather read mail in Gmail, forward the domain mailbox there.

    The SMTP test passes but the form still fails

    The SMTP plugin’s test email uses that plugin’s own From address. The form uses its own, which may not match. WP Mail SMTP’s docs warn that another plugin’s settings can stop that plugin’s emails. Its Force From Email option makes every email use one sender. Turn it on, or set the form’s From address to match the mailer account.

    Mail reaches Gmail but not your company address

    That pattern usually means your host thinks it handles your domain’s mail when Google Workspace or Microsoft 365 actually does. The server delivers the email to a local mailbox nobody reads. In cPanel, go to Email, then Email Routing, and choose Remote Mail Exchanger if your mailbox lives somewhere else. Only change this once you know where your mailbox actually is. The wrong setting causes the same problem in reverse.

    SPF, DKIM and DMARC don’t match the sender

    WordPress’s mail handbook names SPF and DKIM, and whether the sender is authorised for the domain, as deliverability factors. The records have to cover the service that actually sends. If WP Mail SMTP sends through Brevo, SPF and DKIM need Brevo’s values, and DMARC has to align with the From domain. Before you edit DNS, list every legitimate sender: the website, your mailbox provider and any newsletter tool. Publishing a new SPF record that leaves one out breaks that sender.

    Check the spam folder, but don’t stop there. In the same 150-case review, the email was in spam only 8 times.

    Do WooCommerce order emails fail the same way?

    Yes, because WooCommerce sends through wp_mail(). WooCommerce’s email troubleshooting docs add store-specific checks. The transactional-emails log under WooCommerce, then Status, then Logs, shows each email as Sent, Failed, Disabled or Skipped. A Pending Payment order doesn’t send the email you might expect, so check the order status before you blame delivery.

    How to catch the next failure sooner

    Mail often breaks quietly after a plugin update, a mailbox password change or a host move. After any of these, submit the form yourself, check the inbox and the spam folder, and run a password reset. Keep stored entries, through Flamingo or your form plugin, so a lost email doesn’t mean a lost lead. Stored entries hold personal data, so limit who can see them and delete old ones.

    When to stop and get help

    Stop when the next step means work you can’t see or undo:

    • reading server mail logs
    • changing mail routing
    • editing DNS records that other services rely on
    • a red error that the settings above don’t explain

    Contact Form 7’s own guidance for red errors is to have the host check its logs. Ask your host whether PHP mail works, which outbound ports are open, and whether they offer a transactional mail service. If your logs show the message was accepted and the recipient’s provider filtered it, keep the log as proof. The rest is that provider’s filtering, not your site. If you want someone else to trace this, SiteSelf’s agent can diagnose and fix the broken form on your site and report what it changed and checked. The connector plugin covers form and mail settings. Reading logs needs hosting access.

    Frequently asked questions

    Do I need an SMTP plugin at all?

    Only if the host’s mail is blocked, limited or unauthenticated, which is common on shared hosting. Some managed hosts provide their own transactional mail service. Ask your host before adding a plugin.

    Contact Form 7 warns “Sender email address does not belong to the site domain.” Is sending broken?

    No, it’s a configuration warning, not a failure. It tells you From uses an address outside your domain. Fix it with a domain address in From and the visitor in Reply-To.

    Should I add the site’s address to my safe senders list?

    It can hide the symptom, but spoofed mail using that address then gets through too. Fix the From address and authentication instead.

    Why did the form stop working when nothing changed on the site?

    Something outside the site often changed: a mailbox password, the host’s mail settings, or how the receiving provider filters mail. In one WordPress.org thread, the cause was Gmail no longer delivering copies of mail the owner had sent to themselves.

    Can I see a message whose email never arrived?

    Only if the form stored it. Contact Form 7 needs Flamingo for that. Many other form plugins keep entries by default. Without storage, the message is gone.

  • How to disable auto updates in WordPress safely

    Key takeaways

    • WP_AUTO_UPDATE_CORE set to ‘minor’ stops major core jumps and keeps security releases. It does nothing to plugins or themes.
    • AUTOMATIC_UPDATER_DISABLED stops every background update, including security and translation updates. WordPress’s own handbook strongly discourages turning off security updates.
    • DISALLOW_FILE_MODS is not an auto-update setting. It also removes manual install and update from wp-admin.
    • Put auto_update_plugin and auto_update_theme filters in a must-use plugin, not in wp-config.php, where WordPress warns they can conflict with WP-CLI.
    • If updates keep happening after you turn them off, a host updater, a host must-use plugin or a vendor security channel is usually running them.

    A plugin updates at 3 a.m. The homepage still loads, but checkout doesn’t. By morning the site owner wants one thing: no more updates nobody scheduled. That’s a fair goal. The risk is reaching for a switch that turns off more than you meant to, or one that doesn’t actually stop the update that hurt you.

    WordPress updates core, plugins, themes and translations on separate schedules, and each has its own control. This guide covers which control does what, how to apply each one, how to check that it worked, and why some sites keep updating after every setting says no. If you only want to turn off auto-updates for a single plugin from the dashboard, our shorter guide on switching off automatic updates walks through those screens.

    Which setting stops which kind of update?

    Match the control to the update you want to stop. Most damage comes from using a control that is too broad, or one aimed at the wrong layer.

    What you want to stopControlWhat it also does
    One plugin or theme“Disable auto-updates” link on Plugins or ThemesNothing else. The plugin stays active.
    Major core releases onlydefine( 'WP_AUTO_UPDATE_CORE', 'minor' );Keeps minor and security core releases running
    All core auto-updatesdefine( 'WP_AUTO_UPDATE_CORE', false );Also stops core security releases
    Specific plugins or themes, in codeauto_update_plugin / auto_update_theme filters in a must-use pluginReturning false also blocks WordPress.org’s critical security pushes for those items
    Every background updatedefine( 'AUTOMATIC_UPDATER_DISABLED', true );Stops security and translation updates too

    Two rules come out of this table. WP_AUTO_UPDATE_CORE covers core only, so setting it to false leaves plugin updates running. That surprises a lot of people. And none of these controls removes the Update buttons. With auto-updates off you can still update by hand from Dashboard → Updates.

    What you need before you change anything

    The per-item toggles need only an administrator login. The constants and filters need file access to the site root through SFTP, SSH or your host’s file manager. The theme file editor won’t reach wp-config.php.

    Take a backup of the files and the database first, and make sure you know how to restore it. A typo in wp-config.php can white-screen the whole site. Then look at your hosting panel for an “automatic updates” or “autoupdate” section. If your host runs its own updater, change that setting first. Otherwise you’ll edit WordPress files and wonder why nothing changed.

    How to stop one plugin or theme from auto-updating

    Use this when one item has broken the site before: a page builder add-on, a payment gateway, a theme with a child theme on top. These controls have been in WordPress since version 5.5.

    1. Go to Plugins → Installed Plugins.
    2. In the Automatic Updates column, click “Disable auto-updates” next to the plugin. To change several at once, tick them and use the bulk action.
    3. For a theme, go to Appearance → Themes, open the theme’s details and click “Disable auto-updates.”

    That change affects that one item. Core, translations, other plugins and your host’s updater all carry on as before. If the site holds back only one risky plugin, stop here. You don’t need any code.

    How to stop major core updates but keep security releases

    This is the compromise most practitioners recommend: let WordPress apply security and maintenance releases on its own, and run major version jumps yourself after testing.

    1. Open wp-config.php in the WordPress root, next to the wp-admin and wp-content folders.
    2. Search the file for WP_AUTO_UPDATE_CORE. If the line is already there, edit it. Don’t add a second one. PHP keeps the first definition and raises a warning for the duplicate.
    3. Above the line that reads /* That's all, stop editing! */, add:
      define( 'WP_AUTO_UPDATE_CORE', 'minor' );
    4. Save the file, then load the homepage and /wp-admin/. A white screen almost always means a missing quote or semicolon. Fix it or restore the file.

    The constant overrides the core auto-update setting on the Updates screen. Setting it to false turns off all core auto-updates, security releases included. The developer handbook advises against that, and it’s hard to justify on a site where nobody is assigned to apply security releases by hand.

    How to hold specific plugins in code with a must-use plugin

    Use code when you manage several sites, when you want the policy kept in version control, or when clients shouldn’t be able to switch it back from the dashboard. WordPress’s handbook says these filters belong in a must-use plugin. Added to wp-config.php, they can cause conflicts, including with WP-CLI.

    Create wp-content/mu-plugins/update-policy.php. Make the mu-plugins folder if it doesn’t exist. This example holds two plugins by folder name and leaves every other plugin as configured in the dashboard:

    <?php
    /**
     * Plugin Name: Update policy
     * Description: Holds named plugins back from auto-updates.
     */
    add_filter( 'auto_update_plugin', function ( $update, $item ) {
        $hold = array( 'woocommerce', 'your-payment-gateway' );
        if ( isset( $item->slug ) && in_array( $item->slug, $hold, true ) ) {
            return false;
        }
        return $update;
    }, 10, 2 );

    To stop all plugin or theme auto-updates, the single-line versions are add_filter( 'auto_update_plugin', '__return_false' ); and add_filter( 'auto_update_theme', '__return_false' );.

    Know what you’re giving up. The handbook says the WordPress.org security team can trigger background updates of plugins and themes in special cases, to fix a critical vulnerability. Returning false from these filters blocks those updates too. Keep the hold list short and review it.

    How to turn off every background update, and when that’s right

    One line in wp-config.php stops all automatic updates, “core or otherwise,” in the handbook’s words:

    define( 'AUTOMATIC_UPDATER_DISABLED', true );

    This is a legitimate choice for teams that already patch on a real schedule: a large multisite with server-side security, a site deployed from version control, a staging-first agency workflow. It’s a poor choice as a reaction to one bad night. It turns off security and translation updates along with everything else, and the handbook strongly discourages switching off security updates.

    If you set it, also set a recurring calendar entry with a named person on it. Turning off auto-updates is safe only when someone actually does the manual updates. Practitioners who do this well run updates on a fixed rhythm, weekly or every ten days, not when they happen to remember.

    Don’t stack the filters on top of this constant. The constant already stops everything, so the filters will look broken, and the next person who reads the code won’t know which rule is in charge.

    Why DISALLOW_FILE_MODS is the wrong switch

    Some guides suggest define( 'DISALLOW_FILE_MODS', true );. It’s a hardening setting, not an auto-update setting. The wp-config handbook says it blocks plugin and theme installation and updates in the admin, along with the file editor. You lose the manual updates you were trying to keep.

    Plugins that disable update checks have a similar problem. Disable All WordPress Updates, for example, turns off the checks and hides the notices, so updates you’ve missed never show up. Its author still tells users to keep everything current. Turning off automatic installs is a policy. Hiding available updates means nobody can see what the site is missing.

    How to confirm the change worked

    Go to Tools → Site Health. The Status tab warns when background updates are disabled and names the constant or filter responsible. That warning is expected if you set AUTOMATIC_UPDATER_DISABLED. If you expected it and it’s missing, the constant didn’t load. Check for a duplicate or a typo. If you see the warning but didn’t set anything, something else did. The next section covers what.

    On the Info tab, open the Must-Use Plugins panel. Everything listed there runs on every request and can override your settings. Then check Dashboard → Updates, which shows the core auto-update mode in effect. Finally, wait for one real update cycle. Plugin and theme auto-updates run on WP-Cron, twice a day by default. Confirm that the held item stayed pending and that everything else behaved as before.

    Why WordPress keeps updating after you turned it off

    When the settings say off and updates still arrive, find out which updater ran before you change anything else. These are the usual sources, most common first.

    Your host runs its own updater

    Managed hosts often update sites from their own control panel, and WordPress settings don’t control those jobs. Kinsta’s documentation says enabling its automatic updates disables WordPress’s plugin auto-updates, and it advises against running competing update systems. You can switch Kinsta to manual under Sites → your site → Plugins and themes → Automatic updates. Other hosts document updaters that override wp-config.php or can be paused but not fully turned off. Read your host’s documentation, or ask support which system is running.

    A host must-use plugin forces the setting

    In one resolved WordPress.org support thread, Site Health reported that automatic_updater_disabled was on. Deactivating normal plugins didn’t help, because the cause was a must-use plugin the host had installed. When the host removed it, the per-plugin toggles came back. The same mechanism can force updates on as easily as off.

    A vendor or WordPress.org pushes a security fix

    WooCommerce’s FAQ says a store connected to WooCommerce.com with an active subscription, on WooCommerce 11.2 or later, may receive a developer-published security fix even when auto-updates weren’t enabled. If the site blocks automatic updates, the fix won’t install, and you can apply it manually from Plugins. Separately, WordPress.org can push critical plugin and theme fixes, as described above.

    A second update manager is running

    An update-management plugin, a maintenance dashboard you connected years ago, or a premium plugin’s own updater can each run updates on a separate schedule. Check the update manager’s logs and remove any update system you don’t use. Run one at a time.

    What to do instead of turning updates off

    Turning off auto-updates stops the surprises. You still have to do the updates. Updates that fail on their own, from cron, file ownership or a leftover .maintenance file, keep failing when you run them by hand. Our guide to why WordPress updates fail covers those faults.

    WordPress already softens some of the risk. Its plugin team introduced phased releases in 2025, which delay plugin automatic updates by 24 hours while still allowing manual updates. That gives early reports of a bad release a day to come in. For anything higher-risk, the routine that works is short:

    1. Back up the database and wp-content, and know the restore works.
    2. Run major core, WooCommerce and heavily customized plugin updates on a WordPress staging site first.
    3. Update one thing at a time, so a break points to one cause.
    4. Test what the site exists to do. WooCommerce’s update guide lists product pages, cart, checkout, payment, shipping, tax and emails, and says to complete any database update notice.
    5. Write down what changed, when and who checked it.

    Rollback restores service. It isn’t somewhere to stay. An older version keeps whatever vulnerability the update fixed. Use it to bring the site back up, fix the conflict on staging, then move forward. If you’d rather not run that routine yourself, SiteSelf handles WordPress plugin updates on request: it says what it’s about to change, checks the updated page and reports back. Editing wp-config.php needs hosting (SSH) access.

    Frequently asked questions

    Does disabling auto-updates hurt SEO?

    Google doesn’t publish a ranking penalty for turning off auto-updates. The SEO risk comes through security. A hacked site can be flagged, and Google points owners to the Security Issues report in Search Console. Unpatched plugins make that more likely, which is a reason to keep security updates running.

    How do I turn auto-updates back on?

    Reverse the change you made. Remove the constant or the filter, or click “Enable auto-updates” on the item. Search wp-config.php for leftover AUTOMATIC_UPDATER_DISABLED or WP_AUTO_UPDATE_CORE lines, including ones a previous developer or host added, and check the mu-plugins folder.

    Can I keep updates off on staging but on in production?

    WordPress has no built-in setting for that. Teams usually handle it with a separate wp-config.php per environment, which keeps the setting out of the database that gets copied between environments. Check that your staging tool doesn’t overwrite wp-config.php when it pushes to live.

    How do I stop translation updates only?

    WordPress’s documented controls don’t offer a simple translation-only switch. AUTOMATIC_UPDATER_DISABLED stops translations along with everything else. If you need finer control, some update-management plugins have a separate translation setting. Check the plugin’s listing before relying on it.

    Will a failed automatic update roll itself back?

    WordPress has added rollback for failed automatic plugin updates, which restores the previous version when an update causes a fatal error. It doesn’t catch a checkout that quietly stops working, and restoring files doesn’t undo database changes. A backup taken before the update is still what lets you fully undo it.

  • How to fix WordPress stuck in maintenance mode

    Key takeaways

    • Find out where the page comes from before you delete anything. The exact text “Briefly unavailable for scheduled maintenance. Check back in a minute.” comes from WordPress core. A branded page comes from a plugin, and a page that only some devices see is usually a cache.
    • WordPress only honours .maintenance while the $upgrading timestamp inside it is under 10 minutes old. If the core message lasts much longer, look for a cache or for retries that keep recreating the file.
    • Getting the site back is not the same as finishing the update. Check the version of the plugin, theme or core that was updating, then retry it.
    • A lockout that comes back on every update points to a cause further up: a plugin bug (Starter Templates’ “Update failed: -1” in 2023, fixed in 3.1.26), file ownership or server limits. In one reported case an auto-update failed on folder ownership 59 times out of 62 in a month.

    You clicked Update on a plugin, the spinner kept going, and the page never came back. Now the site says “Briefly unavailable for scheduled maintenance. Check back in a minute.” The minute has turned into twenty, and visitors see the same message.

    WordPress puts the site into maintenance mode on purpose during every core, plugin and theme update. It writes a hidden file called .maintenance to the installation root and deletes it when the update finishes. If the update is interrupted or fails, the file can be left behind. Removing it is the standard fix. The steps around that are what decide whether you get a working site or a half-updated one. If the update itself failed with an error, our guide to recovering from a failed WordPress update covers the full recovery order.

    Which maintenance page are you actually looking at?

    Look at the page before you touch any files. Several different things produce a page that looks like maintenance mode, and deleting .maintenance only fixes one of them.

    What you seeLikely sourceWhere to turn it off
    Plain text: “Briefly unavailable for scheduled maintenance. Check back in a minute.”WordPress core’s update lockDelete .maintenance from the WordPress root
    A designed page with your logo, a countdown or an email signupA maintenance or coming-soon pluginThat plugin’s own Status setting
    A page branded by your hosting companyA maintenance switch in the host’s control panelThe host dashboard
    The page appears on one device or one URL but not othersA page, server or CDN cache holding an old copyPurge each cache layer
    The site is stuck after a rollbackThe rollback tool’s own lock fileFor WP Rollback, .wpr-maintenance

    Check while logged out, in a private browser window. Maintenance plugins usually let logged-in administrators through, so your view and your visitors’ view can be completely different.

    How to clear the core lock without breaking an update

    Delete only .maintenance, and only once you are sure the update has stopped. WordPress’s own update documentation describes maintenance mode as normal and short during an update. It says to remove the file only after the update has failed and is no longer running. If you delete it while files are still being replaced, visitors can reach a half-installed plugin or theme.

    You need file access: your host’s file manager, SFTP or SSH. You do not need wp-admin.

    1. Wait, then confirm nothing is running. Don’t close any tabs mid-update. Ask anyone else with admin access whether they started an update. If the message appeared seconds ago, give it a few minutes.
    2. Take a backup if you can. Your host’s snapshot tool is fine. It gives you a known state to return to before you retry anything.
    3. Open the real WordPress root. That is the folder containing wp-config.php, wp-admin and wp-includes. It is often public_html, but not always. Sites installed in a subfolder or on an addon domain live elsewhere.
    4. Show hidden files. The name starts with a dot, so many file managers and SFTP clients hide it by default. Kinsta’s documentation points this out. Turn on “show hidden files” or the equivalent option.
    5. Delete .maintenance and nothing else. Don’t touch wp-content/maintenance.php if you have one. That file only customises the message and is not the lock.
    6. Reload the site logged out. Use a private window. If you run a caching plugin or a CDN, purge it.

    Over SSH, the delete is one command run from the root:

    ls -la | grep maintenance
    rm .maintenance

    Some developers also check wp-content/upgrade after a failed update. Leftover folders in there suggest the update stopped partway through. This is practitioner advice rather than something in WordPress’s documentation, but it is a quick way to see whether anything was left half-done.

    Why ten minutes matters

    The file contains a timestamp called $upgrading. WordPress’s developer reference for wp_is_maintenance_mode() says core treats the file as active only while that timestamp is less than 10 minutes old. After that, core stops showing the message, even if the file is still there.

    So if you see the core message well past ten minutes, something else is involved. Usually it is one of two things: a cache serving a stored copy of the page, or an update being retried and writing a fresh .maintenance each time. Deleting the file again won’t fix either.

    What to check when deleting the file changes nothing

    If there is no .maintenance file, or deleting it changed nothing, work through the other sources in this order.

    A maintenance or coming-soon plugin is still on

    These plugins have their own switch, separate from core. In LightStart (formerly WP Maintenance Mode), Themeisle’s documentation puts it at Dashboard > LightStart > General > Status. Turn it off and save. The same documentation notes that logged-in admins may see the normal site while visitors see the maintenance page.

    If the plugin is blocking the login page, rename its folder in wp-content/plugins over SFTP or the file manager. That deactivates it. In one WordPress.org thread, LightStart kept redirecting the login page because a second plugin had hidden the login URL and LightStart didn’t know to let that URL through. Renaming the LightStart folder got the owner back in. Afterwards, rename the folder back and fix the settings. Our article on when to use a maintenance mode plugin covers how these plugins decide who gets through.

    Your host has its own switch

    Some managed hosts add a maintenance toggle to their control panel or to a helper plugin they install. If the page carries your host’s branding, turn it off there, not in WordPress.

    A cache is serving the old page

    In one WordPress.org case, the homepage kept showing the maintenance page on phones and other people’s devices. That carried on after the plugin was turned off and even after its folder was removed. A cache-bypass URL showed the normal site, which pointed to the server’s cache. Purge every layer: the caching plugin, the host’s server cache (Nginx, LiteSpeed) and the CDN. Then test in a private window. The checks in fixing a page that is not updating follow the same order.

    A rollback tool left its own lock

    WP Rollback uses its own .wpr-maintenance file. In one support case, a FooGallery rollback from 3.3.7 to 3.3.3 actually worked, but the site stayed in maintenance mode. The plugin’s author explained that the file clears itself after 10 minutes, or you can delete it.

    Why it comes back on every update

    If you have to delete the file after every update, the file is not the problem. Something is making the update fail, and each failed attempt leaves a new lock behind. Practitioners report three causes most often.

    A plugin that breaks the updater. In early 2023, a bug in Starter Templates caused “Update failed: -1” errors. Owners found every plugin update dropping their site back into maintenance mode. The plugin’s support team marked it resolved in version 3.1.26. That bug is long fixed, but the pattern still applies. Deactivate the suspect plugin, update it, and reactivate it. The Health Check & Troubleshooting plugin can disable plugins for your own session only, so you can test without changing what visitors see.

    File ownership and permissions. If WordPress can’t write to the plugin folders, the update fails after maintenance mode has already started. Mike Sewell described a client site where the auto-updater retried one plugin update twice a day. Each time it entered maintenance mode for about 4 seconds, then failed on folder ownership. It failed 59 of 62 attempts in a month. The only sign was an uptime monitor reporting brief outages. Your host can fix ownership. Another sign of the same problem is WordPress asking for FTP credentials when you click Update.

    Timeouts and memory limits. These come up most during bulk updates on modest hosting. Update one plugin at a time, and ask your host what PHP limits your plan allows.

    In every case, the error log names the cause faster than guessing does. On WordPress.org, a volunteer gave exactly this advice to an owner whose plugin updates kept locking the site after a core update: check the PHP error log or debug.log.

    How to confirm the site is really back

    When the maintenance page goes away, you have your site back, but the update may not have finished. Before you call it done:

    • Load the homepage and one inner page in a private window.
    • Open Dashboard > Updates and Plugins. Check the version of whatever was updating. If it is still on the old version or shows an error, retry that single update.
    • Submit a form and confirm the email arrives.
    • If a fatal error appears, WordPress’s recovery mode email gives you a link to pause the broken plugin. The white screen fix guide walks through it.

    On WooCommerce, WooCommerce’s update guide says to put the store in Coming soon mode during updates. It also says to run any required database update and to test store workflows, including checkout, before reopening. A store that loads but can’t take payment is worse than one that is visibly closed.

    How to stop the next update from locking the site

    Most stuck sites come down to how the update was run. Back up first. Test risky updates on a staging copy of the site. Update one plugin at a time, and load the site after each one rather than updating ten at once. WooCommerce’s guide likewise warns against running several major updates together unless you have tested that exact set. For stores, use Coming soon mode during the update.

    If you’d rather not do this yourself, SiteSelf runs plugin updates one at a time on request. It fetches the page afterwards and reports what changed. File work, like removing a stuck lock, needs hosting (SSH) access.

    When to stop and get help

    Stop deleting files and contact your host or a developer in these cases:

    • The same update fails twice at the same point.
    • Your hosting control panel is unreachable too, which suggests an outage at the host rather than in WordPress.
    • File permissions won’t let you delete the file.
    • Your host reports suspicious code.

    In that last case, don’t simply restore a backup, because the backup may contain the same infection. Bring the error log with you. It turns a vague report into a fix someone can act on.

    Frequently asked questions

    Is it safe to delete the .maintenance file?

    Yes, once the update has stopped. The file only tells WordPress to show the maintenance message. Removing it changes no plugin, theme or database content. The risk is timing: deleting it during an active update can expose half-replaced files.

    How long should maintenance mode normally last?

    For a normal update, seconds. WordPress’s documentation calls it a short time, and in the ownership case above it lasted about 4 seconds per attempt. Core stops honouring the file after 10 minutes, so anything much longer means something else is involved.

    I can’t find the .maintenance file. Where is it?

    It is in the folder that holds wp-config.php, not inside wp-content. It is hidden because the name starts with a dot, so turn on hidden files in your file manager or SFTP client. If it really isn’t there, the page is coming from a plugin, your host or a cache.

    Why does the site look fine to me but not to visitors?

    Maintenance plugins usually let logged-in users through, and caches can store different copies for different devices. Always check logged out in a private window, and on a phone if the report came from one.

    Does maintenance mode hurt SEO?

    A few minutes won’t. A long outage can, because search engines slow down crawling when they keep getting server errors. Our article on the 503 response code explains which status a planned outage should return.

    Should I turn off automatic updates to stop this?

    Some owners do, and run updates by hand during quiet hours. That gives up automatic security fixes, though. If auto-updates keep failing, fix the cause first, usually ownership or a broken plugin, and decide on auto-updates after that.

  • How to create a WordPress staging site safely

    Key takeaways

    • Use your host’s staging tool if your plan includes one. If not, use a plugin such as WP STAGING, whose free version clones to a subfolder and keeps push-to-live for Pro. Build the copy by hand only if you’re comfortable with databases and WP-CLI.
    • WordPress’s ‘Discourage search engines’ setting doesn’t stop anyone from opening the site. Password-protect the copy. Don’t also block it in robots.txt, because that stops Google from reading a noindex tag.
    • A clone keeps live payment keys, outgoing email, cron jobs and webhooks. Switch gateways to sandbox mode and turn off outgoing mail before anyone places a test order.
    • Kinsta’s docs warn that a full database push can lose purchases, comments, sign-ups and new content added since the copy was made. For plugin updates, test on staging and then run the same update on live.

    Most hosts and plugins can copy a WordPress site to a staging URL in a few minutes. The problems come afterwards. Anyone who finds the copy can open it. It still holds your live payment keys and email settings. And pushing it back to live can erase every order, comment and sign-up that came in while you were testing.

    This guide covers the three ways to create the copy, the four things to lock down before you test on it, and how to deploy back without overwriting live data. Before you start, take a fresh backup of the live site and make sure you can actually restore that WordPress backup. Staging is for testing. It doesn’t replace a backup.

    Which staging method fits your site

    Use your host’s tool if your plan has one. If it doesn’t, or the tool fails on your site, use a plugin. Build a copy by hand when you need full control or nothing else works. That order comes up again and again in practitioner threads, and it also matches how much can go wrong with each method.

    MethodAccess you needGood fitWatch out for
    Host staging toolHosting dashboard loginManaged WordPress plans that include stagingOnly on some plans. Can fail on individual sites. Resources and caching may differ from live.
    Staging pluginWordPress adminShared hosting without a staging buttonRuns on your live site’s disk, PHP and database. Push to live is often a paid feature.
    Manual copySSH or file manager, plus database accessDevelopers who want a separate database and subdomainSlowest method, and the easiest to get wrong. A careless search-replace breaks settings.

    How to create the staging copy

    With your host’s staging tool

    Look in the hosting dashboard for “Staging”, “Environments” or “Clone”. On Kinsta, for example, you go to Sites, open the live environment and choose Create new environment, then pick the clone option. Most hosts put the copy on its own subdomain and connect it to a separate database for you, so this is the quickest route.

    If the tool fails on one site but works on others, try a plugin instead of running the same clone again. Repeating a clone without changing anything usually fails the same way.

    With a staging plugin

    With WP STAGING’s free version, go to WP Staging, then Staging Sites, then Create New Staging Site. Give it a name and start the clone. The copy lives in a subfolder of your domain, such as /development. By default its tables sit in your existing database under a separate prefix.

    That shared database keeps the copy separate in software, but not physically. Subdomain clones, a separate database and pushing to live are Pro features. Long-time users say this kind of plugin works best on small, clean sites, and that large sites sometimes need a manual search-replace after the clone.

    By hand

    1. Create a subdomain such as staging.example.com in your hosting panel.
    2. Copy the WordPress files into the subdomain’s folder, including all of wp-content.
    3. Export the live database. Create a new, empty database with its own user, and import the export into it. Don’t reuse the production database credentials.
    4. Edit the staging wp-config.php so it points at the new database and labels the environment:
      define( 'DB_NAME', 'example_staging' );
      define( 'DB_USER', 'staging_user' );
      define( 'WP_ENVIRONMENT_TYPE', 'staging' );
    5. Replace the live URL with the staging URL using a tool that understands serialized data. Run it once with --dry-run to preview the changes, then run it again without that flag to apply them:
      wp search-replace 'https://example.com' 'https://staging.example.com' --skip-columns=guid --dry-run
    6. Password-protect the subdomain before anyone else logs in.

    Step 5 is where most hand-built copies break. WordPress stores some settings as serialized PHP, and the stored value includes each string’s length. If you swap a URL in phpMyAdmin, the length no longer matches and widgets or options stop loading. WordPress’s migration handbook also says to leave the guid column alone. If those IDs change, feed readers can show old posts as new.

    Lock the copy down before you test anything

    A fresh clone is a working copy of your live site. It can do anything live can do: send email, charge cards and fire webhooks. Make these four changes before anyone uses it.

    Put a password in front of it. WordPress’s own documentation says that Settings → Reading → “Discourage search engines from indexing this site” asks search engines not to index the site. It doesn’t stop anyone from visiting it. Real access control means server-level password protection (basic auth), which shows a login prompt before WordPress even loads. Our guide to adding password protection to a site covers the options. Don’t also disallow the copy in robots.txt. Google’s documentation says a crawler blocked by robots.txt can’t read a noindex tag, and the blocked URL can still show up in search results.

    Switch payments to sandbox. Set every payment gateway to test or sandbox mode. WooCommerce’s documentation says test orders can trigger order emails and appear in analytics like real orders, and that other integrations may not be able to tell them apart from real ones.

    Stop outgoing mail and integrations. Turn off outgoing email on the copy. If you send mail through an SMTP provider’s API, remove or change the API key there too, because some plugins that block WordPress mail don’t stop mail sent through the provider. Check webhooks to fulfillment, accounting and CRM tools. In one wordpress.org support thread, a copied database still had live API and webhook access.

    Handle WooCommerce Subscriptions. Subscriptions decides it’s on a staging site by comparing the current URL with the URL it stored when it was first activated. So activate it on live before you clone, then check the mode under WooCommerce → Status. In staging mode it skips payments and subscription emails, but scheduled renewals and events still run. Make sure the live site answers on only one URL. If it works on both www and non-www, Subscriptions can mistake the live site for staging.

    Setting WP_ENVIRONMENT_TYPE to staging helps too, but only as a label. WordPress recognizes local, development, staging and production, and plugins can read the value. That tells everyone which site they’re looking at. It doesn’t stop a plugin that ignores the label from sending mail.

    What a working staging copy looks like

    Open the homepage, a post, a product page and the login screen. Every page should load on the staging address, with the same theme, plugins and content as live. Click the main menu and two links inside page content. If any of them opens the live domain, the search-replace missed something.

    On a store, place one order in sandbox mode and take it through to the thank-you page. Then check the live order list. It should not have gained an order. Your inbox should get the test email only if you redirected mail to yourself. No customer address should receive it.

    Then test the actual change. Do one thing at a time, in this order: core, then theme, then plugins. That way, when something breaks, you know which change caused it. For store updates, WooCommerce’s update guide lists what to check: product pages, cart, checkout, payments, shipping, taxes, order emails and any extensions you rely on.

    When the clone fails: the usual causes

    The clone stalls partway or times out. The site is too big for the PHP execution time limit, or a large table such as orders or analytics logs is slowing it down. Ask your host to raise the limit, or lower the plugin’s batch size. You can leave out log tables, but don’t leave out anything your test needs.

    A memory error. In one wordpress.org support thread, a clone failed because WordPress’s own memory limit was 40 MB even though PHP allowed 256 MB. Adding define( 'WP_MEMORY_LIMIT', '256M' ); to wp-config.php raises WordPress’s limit.

    The copy redirects to live, or every page except the homepage returns 404. Check the siteurl and home values in the copy’s options table. Then go to Settings → Permalinks and click Save Changes. Next, look at .htaccess or the Nginx config, then at caching, SSL, redirect and security plugins.

    A blank page or “critical error” after a clone that reported success. Turn on debug logging and read wp-content/debug.log. It usually names a theme or plugin file. Make sure the copy runs the same PHP version as live before you start deactivating plugins.

    The plugin can’t use a separate database. WP STAGING can’t create the database itself. Create it first, and give its user the CREATE, INSERT and ALTER privileges.

    How to move tested changes to live without losing orders

    A full database push replaces data. It doesn’t merge it. Kinsta’s push documentation warns that a full push can lose purchases, comments, new content, sign-ups and forum posts added since you made the staging copy. On r/woocommerce, one store owner reported duplicated and reset order numbers after pushing from host staging. WordPress has no built-in way to merge two databases that have both changed, so the safe approach is to pick the method that fits the kind of change.

    Change you testedHow to deploy it
    Plugin, theme or core updateDon’t push anything. Run the same update on live, then recheck.
    Theme files or custom codePush files only.
    A new plugin or a settings changeInstall it or change the setting on live by hand. Files don’t carry database settings.
    A redesign with new pagesPause content edits on live, push only the tables you’ve named, and never push orders, users or comments.

    A files-only push has its own limit. Kinsta notes that pushing files doesn’t create a new plugin’s database tables, and dashboard settings are usually stored in the database. Avoid the opposite mistake too: don’t push the whole database just to carry over one setting.

    If you push database tables to a store, first find out where the store keeps its orders. Stores using High-Performance Order Storage keep orders in their own wc_orders tables. Older stores keep them in wp_posts and wp_postmeta, mixed in with your pages. If you can’t name every table a push will overwrite, don’t run it.

    For updates, the test-then-repeat approach is the simplest safe option on a busy site, because it never touches the live database. If you would rather hand the update cycle off, the plugin updates and maintenance page explains how SiteSelf reviews, applies and checks updates on request.

    Four checks on the live site after a deploy

    1. Search visibility. Open Settings → Reading on live and make sure “Discourage search engines” is unticked. That setting is stored in the database, so a push can bring it over from staging and leave production hidden from search.
    2. Protections. Kinsta says .htpasswd files and some bot-protection settings don’t transfer in a push. Check that live still has the protections it had before.
    3. Money paths. Make sure the gateways are back in live mode on production. Run through checkout up to the payment step, and confirm today’s orders are still in the order list.
    4. Links and redirects. Click the menu, a few in-content links and any redirects you rely on. None should point at the staging address.

    Once the work ships, delete the staging copy or lock it away. An unmaintained clone of your site is another login page for attackers to find, and it falls further out of date every week. If something did go wrong, restore the backup you took before the deploy instead of editing live tables under pressure. Our guide to restoring WordPress from backup covers that.

    Frequently asked questions

    Can I create a WordPress staging site for free?

    Often, yes. Many hosting plans include staging, WP STAGING’s free version makes subfolder clones, and you can always build one by hand. What free options usually leave out is the push back to live. With WP STAGING, that’s a Pro feature.

    Should staging be on a subdomain or a subfolder?

    Both work. A subdomain keeps the copy’s address and rewrite rules separate from live. A subfolder copy can clash with the root .htaccess rules and cause wp-admin problems. Neither is clearly safer. Choose the one your tool supports and protect it the same way.

    How do I refresh a staging site that has gone stale?

    Use your host’s pull, refresh or clone-from-production option, or make a new clone with the plugin. Staging doesn’t update itself when live changes. Refreshing replaces whatever is on the copy, so export any unfinished work first. Refresh just before your final test, not weeks earlier.

    Do I need staging for simple content edits?

    Usually not. Text and image changes are easier to make on live, and WordPress keeps post revisions so you can roll them back. Staging is for updates, design changes, new plugins and anything that touches checkout.

    Can I test checkout on a local copy instead?

    You can test layout and code locally. Checkout is different. Payment gateways, webhooks, email and SSL usually need a public URL to behave like they do on live, so test them on online staging with the gateway in sandbox mode.

    Can deleting a staging site break the live site?

    It shouldn’t if the copy uses its own database. Plugin staging that shares the live database deserves more care. One r/Wordpress user reported a live “Error establishing a database connection” after deleting a staging site made with a one-click installer, although the cause was never confirmed. Take a backup before you delete.

  • WordPress user roles explained by what each can do

    Key takeaways

    • A single WordPress site has five default roles: Administrator, Editor, Author, Contributor and Subscriber. Super Admin exists only on Multisite.
    • WordPress checks capabilities such as publish_posts, upload_files and manage_options. It does not check the role name, so plugins that add or demand capabilities change what a role can do.
    • WooCommerce adds Customer and Shop Manager. Shop Manager can handle products, orders, coupons, reports and customer details, so it is not a read-only staff role.
    • wp role reset –all and User Role Editor’s Reset both wipe capabilities that plugins and site owners added. Back up first and reset one role at a time.
    • Hosting-portal access, page privacy and firewall 403 errors sit outside WordPress roles. Changing a role will not fix them.

    A writer can’t upload her own hero image. A store assistant can issue refunds nobody meant him to touch. A contractor still has Administrator two years after the project ended. Each of these is a role decision, and most were made in a hurry from the dropdown on the Add New User screen.

    Roles look like job titles. They are permission bundles, and the bundle on your site may not match the one in the documentation. This article covers what each default role can do, why plugins change the answer, and how to give people the narrowest access that still lets them work. On a Multisite network the same rules apply to each site separately, which is why our article on what a multisite manager manages treats users and roles as two separate things.

    What a WordPress user role actually is

    A role is a named set of capabilities. A capability is one permission: publish_posts, upload_files, manage_options (site settings), edit_theme_options (the Site Editor, menus and widgets), install_plugins, promote_users (changing other people’s roles). When someone clicks a button, WordPress checks the capability, not the role’s name.

    That difference matters. WordPress.org’s Roles and Capabilities documentation says plugins and themes can add roles and capabilities, so two sites can both have an “Editor” that behaves differently. The role’s name tells you the starting point. The capability list tells you what the person can actually do.

    What each default role can do

    On a single self-hosted site there are five default roles. A sixth, Super Admin, appears only on Multisite.

    RoleCan do by defaultCannot do by defaultUsual fit
    Super Admin (Multisite only)Everything, across the whole networkNothing withheldThe network owner
    AdministratorSettings, plugins, themes, users, all contentOn Multisite, some capabilities are reserved for the Super AdminWhoever maintains the site
    EditorPublish and manage all posts and pages, including other people’s; moderate commentsPlugins, themes, users, site settingsContent lead
    AuthorPublish and manage their own posts; upload mediaPages; other people’s postsWriter who publishes their own work
    ContributorWrite and edit their own postsPublish; upload mediaWriter whose work gets reviewed
    SubscriberRead; manage their own profileAnything else in the dashboardMembers, commenters

    Online guides disagree on whether WordPress has five or six roles because some describe WordPress.com, the hosted service. Its support documentation lists an extra Viewer role that self-hosted WordPress doesn’t have. When a guide’s advice doesn’t match your dashboard, check which platform it was written for.

    Most role decisions happen between Editor, Author and Contributor

    Contributor and Author differ in two capabilities: publishing and uploading. A Contributor’s draft arrives without its images because the role has no upload_files. If your writers supply their own photos, Author is usually the right role. Moving files back and forth by email for every post is the wrong fix.

    Author and Editor differ in scope. An Editor can change or delete anyone’s posts and every page on the site. People often hand Editor to every writer because one of them needs to update the About page. Authors can’t edit pages by default, so that one task pulls the whole team up a level. Give Editor to the person who owns the content, and keep the rest of the team on Author or Contributor.

    Why a role’s name doesn’t tell you what someone can do

    Plugins add their own capabilities, and the default roles don’t have them. In a WP Job Manager support thread, users with a custom Consultant role got “Sorry, you are not allowed to access this page” when they opened job listings. The missing capability was edit_job_listings. Granting the general edit_posts capability made the error go away, but it also gave those users access to posts they were never meant to edit.

    Some plugins lock features behind a broad capability. In another support thread about a slider plugin, an Editor couldn’t even see the slider menu because the plugin required manage_options. Giving Editors that capability would let them use the sliders. It would also open every site setting to them. When a plugin forces that choice, the better answer is to ask its author for a feature-specific capability.

    WooCommerce is the biggest example. Its Roles and Capabilities documentation says it adds a Customer role and a Shop Manager role, and gives Administrators store capabilities. Shop Managers can manage products, orders, coupons, reports and customer details. That makes it a powerful role, not a safe default for someone who only needs to pack orders.

    WooCommerce also shows that one account can hold more than one role. Its guide to Shop Manager editable roles says Shop Managers can edit Customer-only accounts by default. To edit any other account, every role on that account has to be on an allowlist. The woocommerce_shop_manager_editable_roles filter changes that allowlist. It does not give Shop Managers any WordPress user-management capabilities.

    How to choose the right role for each person

    Start from the tasks, not the job title. “Marketing assistant” can mean writing blog posts at one company and running the store at another.

    1. List what the person does in a normal week. For example: publish posts, swap a banner image, edit product descriptions, reply to comments.
    2. Pick the lowest default role that covers the whole list. If two roles both work, take the lower one.
    3. If one task is missing, grant that one capability. Add it to a custom role. Don’t move the person up a whole role, and don’t hand out manage_options or Administrator to cover one task.
    4. Test it as that user. Create a test account with the role and log in from a private browser window. If you test from your Administrator account, you won’t see the gaps a real user hits.
    5. Write down why each role above Author was granted. A note such as “Editor for launch week” makes it easier to remember to take temporary access back.

    Check one more setting. Under Settings → General, New User Default Role decides which role every new registration gets. If “Anyone can register” is turned on, that role goes to strangers, so keep it at Subscriber, or Customer on a store. Changing it only affects future signups. You change existing accounts under Users → All Users.

    How to change a role and see what it really grants

    In the dashboard, go to Users → All Users. Tick one or more users, choose a role from the “Change role to…” dropdown, and click Change. To change one user, you can also open their profile and use the Role field. You need the promote_users capability to do either, and by default only Administrators have it.

    The dashboard won’t show you the full capability list for a role. With SSH access and WP-CLI you can see it directly:

    wp role list
    wp cap list editor
    wp user list --role=administrator --fields=ID,user_login,user_email
    wp user set-role 42 author

    The third command is the useful one for an audit. It lists every Administrator, and on older sites that list is usually longer than anyone expects.

    When a custom role is the right answer, and what breaks it

    Create a custom role when no default role fits without giving too much away. Examples include a copy editor who fixes other people’s posts but can’t publish new ones, or store staff who need orders but not settings. The common tools are role-editor plugins. User Role Editor lists 700,000+ active installations in the WordPress.org directory, and Members lists 300,000+. Most people clone an existing role and remove capabilities from the copy.

    In code, register the role once, when the plugin is activated. The Plugin Handbook warns that removing and re-adding roles on every load when nothing has changed can “degrade performance considerably.”

    register_activation_hook( __FILE__, function () {
        add_role( 'copy_editor', 'Copy Editor', array(
            'read'                 => true,
            'edit_posts'           => true,
            'edit_others_posts'    => true,
            'edit_published_posts' => true,
        ) );
    } );
    
    register_deactivation_hook( __FILE__, function () {
        remove_role( 'copy_editor' );
    } );

    Custom roles break in three common ways:

    • Resets. Hostinger’s WP-CLI guide warns that wp role reset --all resets every role, including roles created by plugins, and removes custom capabilities. User Role Editor’s own documentation says its Reset returns roles to a fresh-install state and loses changes made by you or by plugins. Take a backup, then reset only the role that is broken: wp role reset editor.
    • Another plugin overwrites your changes. If a role change looks saved and then disappears, another plugin may be re-registering that role. In a Members support thread about this, the advice was to disable plugins one at a time until the change stays.
    • Hiding a menu is not restricting access. Admin menu editors hide items in the dashboard. A user who knows the URL can still reach the screen if their role has the capability. Use menu hiding for a tidier dashboard and capabilities for security.

    What WordPress roles don’t control

    Several problems look like role problems but aren’t.

    Hosting accounts. Hosts run their own user systems. Kinsta’s guide to client access management treats MyKinsta access and WordPress roles as two separate things to assign. WP Engine has its own User Portal users and roles. Removing someone’s WordPress account doesn’t remove their hosting, SFTP or database access. When someone leaves, check both.

    Who can see a published page. Roles control what logged-in users can do in the dashboard. They don’t decide who can view a public URL or whether search engines index it. For private content, use a login or a password. Our guide on password protecting a WordPress page explains which one fits which situation.

    Some “not allowed” errors. A 403 can have causes other than a missing capability. In a Ditty support thread, the reply explained that the editor saves through the REST API. A 403 there could be rest_forbidden, which means a capability really is missing. It could be rest_cookie_invalid_nonce, which means the session has expired and logging out and back in fixes it. Or it could be a firewall’s block page. Check the response in your browser’s network tab before you change anyone’s role.

    Who should hold Administrator on a client site

    This is where roles become a business question. Agencies worry that a client with Administrator rights will install a plugin and break the site, leaving them with repair work they can’t bill for. Owners worry about being locked out of a site they paid for. Both concerns are reasonable, and neither is solved by sharing one Administrator login.

    The setup that holds up: the client owns the domain and hosting and has an Administrator account of their own, even if they rarely use it. Their day-to-day staff get Editor or a narrower role. The agency’s developers get named accounts, not a shared one. Plugin changes are agreed before they happen and made after a backup. Every account is removed when the engagement ends. The weak spot that our article on common WordPress security issues keeps coming back to is the old contractor whose admin login still works.

    Clients often push for Administrator because every small change otherwise waits in the agency’s queue. Handling those routine client requests is the work SiteSelf’s page for agencies describes.

    Frequently asked questions

    Can a WordPress user have more than one role?

    Yes, at the data level. The standard dashboard shows one role per user, but plugins can assign several, and WooCommerce’s documentation describes accounts with more than one role. The user gets the combined capabilities of all their roles.

    What role should a freelance writer get?

    Contributor if someone reviews their drafts before publishing, Author if they publish their own posts. Contributor can’t upload images, so pick Author if they supply their own photos. Editor is too much for a writer who only handles their own work.

    Does a developer need Administrator?

    For plugin, theme or settings work, usually yes, because those tasks need Administrator-level capabilities. Give them a named account of their own, agree on the scope of work, take a backup first, and remove or downgrade the account when the work is done. Code and file work may also need hosting access, which is a separate account.

    Can I give WooCommerce staff a “view orders only” role?

    Not with the built-in roles. WooCommerce adds only Customer and Shop Manager, and Shop Manager covers far more than orders. Clone Shop Manager with a role editor, remove what the job doesn’t need, and test the result with a staff account before you hand it over.

    Does WordPress record who changed a user’s role?

    Core WordPress doesn’t keep an activity log of role changes. If you need that record, install an activity log plugin. Check the Administrator list regularly with wp user list --role=administrator, because a new Administrator you didn’t create is also a sign of a hacked site.

    Why do my role changes not stick?

    Another plugin is probably re-registering the role when it loads. Disable plugins one at a time until the change stays, then make the change through that plugin’s own settings or hooks. Don’t use a full reset to fix it, because a reset wipes every other custom capability too.

  • How to edit a menu in WordPress, classic or block

    Key takeaways

    • If Appearance shows Editor but no Menus, you have a block theme. WordPress.org says block themes on WordPress 6.0 and later don’t get the classic Menus screen by default.
    • On a classic theme, a saved menu only appears after you tick a Display location under Menu Settings and click Save Menu.
    • On a block theme, the menu shows only when a Navigation block in the header points to it, and a homepage template can have its own Navigation block pointing to a different menu.
    • Clicking Edit on a Page List turns it into separate links, and new pages stop being added to the menu automatically.
    • When a change doesn’t show, check the plugin cache first, then the host or CDN cache, then the browser. Look at the page in a private window before you edit anything again.

    You publish a new Services page and go looking for the screen that puts it in the header. Maybe you find Menus, drag the page in, save, and the header stays the same. Maybe Appearance has no Menus item at all, just something called Editor. Neither means WordPress is broken. Your site uses one of two menu systems, and most menu problems come from editing in one system while the site displays the other.

    The fix is to find out which system your theme uses, edit the menu there, and then confirm that the saved menu is the one visitors actually get. If you’re adding a page for the first time, our guide to adding pages in WordPress covers that part. This article starts once the page exists.

    Which screen edits your menu depends on your theme

    Open the Appearance menu in the dashboard. If it has Editor but no Menus, you have a block theme, such as Twenty Twenty-Four. If it has Menus and usually Customize, you have a classic or hybrid theme. WordPress.org’s Menus screen documentation says 5.9 was the last version that showed that screen on every site by default. From 6.0 on, block themes manage navigation through the Navigation block. Some classic and hybrid themes, and some plugins, still bring the old screen back, so trust what your own dashboard shows over any tutorial.

    Your setupWhere to editWhat makes it appear
    Classic themeAppearance > MenusA ticked Display location
    Classic theme, with live previewAppearance > Customize > MenusA Menu Location set in the Customizer, then Publish
    Block themeAppearance > Editor > NavigationA Navigation block in the header (or another template part) pointing to that menu
    Header built in Elementor, Divi or a similar builderThe builder’s header template and its menu widgetWhichever menu the widget is set to

    Before you change anything, write down three things: the theme name, its type, and the screen you’re using. If the result looks wrong later, that note tells you where to look first.

    How to edit a menu on a classic theme

    You need an Administrator account, or any role with the edit_theme_options capability. By default, Editors can’t change menus.

    1. Go to Appearance > Menus. Pick the menu from “Select a menu to edit” and click Select. Sites often have several menus, so check the name. Editing the existing menu keeps its location, so the header stays filled while you work.
    2. Show any hidden panels. Click Screen Options at the top right. Some panels, such as Tags, are hidden by default. Turn on Link Target there too if you’ll need “open in new tab”.
    3. Add items. From Pages, Posts, Custom Links or Categories on the left, tick what you want and click Add to Menu.
    4. Reorder and nest. Drag items up or down. To make a dropdown, drag an item slightly to the right under its parent until it’s labelled “sub item”. Our guide to building a drop-down menu covers the details.
    5. Assign the location. Under Menu Settings, tick the Display location your theme uses: Primary, Header or whatever your theme calls it. This is the step people miss most often.
    6. Click Save Menu. This screen doesn’t save automatically. If you leave the page, your changes are lost.
    7. Check the live site in a private window. This screen has no preview. The Customizer route has one, if you’d rather see the change before it goes live.

    Renaming, removing and new-tab links

    To change the text visitors see without renaming the page, click the arrow on the item and edit Navigation Label. The page title stays the same. Remove in the same panel takes the item out of the menu and leaves the page alone. Once Link Target is turned on in Screen Options, each item gets an “Open link in a new tab” checkbox.

    When a page exists, choose it from the Pages panel instead of pasting its address as a Custom Link. WordPress.com’s support docs point out that a pasted address never changes, so it leads to a 404 if the page’s URL changes later. A menu item picked from the Pages panel stays tied to the page.

    How to edit a menu on a block theme

    WordPress.org’s Site Editor navigation docs list every menu in one place, but they also make a point people miss: creating or editing a menu there doesn’t put it on the site. A Navigation block inside a template part has to use it.

    1. Go to Appearance > Editor > Navigation and select the menu.
    2. Edit the items. Add a page, post or custom link with the + button. Open List View to drag items and nest them into submenus. Nested items are much easier to select there than on the canvas.
    3. Rename or retarget a link by selecting it. You can edit the label text directly, and the link settings have an “Open in new tab” toggle.
    4. Save. The menu is now stored, but it may not be displayed yet.
    5. Check where it’s placed. Open Patterns or Template Parts, then Header (wording differs a little between versions). Select the Navigation block and confirm in the block settings that it uses the menu you just edited. Save the header.
    6. Set mobile behaviour. In the same block settings, Overlay Menu set to Off shows the full menu at every screen size with no hamburger icon. Mobile folds it behind a hamburger icon on small screens.
    7. Check other templates. A homepage or landing template can contain its own Navigation block that points to a different menu.

    Why new pages stopped appearing in the menu

    A new Navigation block often starts as a Page List, which adds every published page automatically. The Navigation block documentation explains that clicking Edit on it converts it into individual Page Link blocks. You can then remove or reorder single items, but newly published pages stop showing up on their own. That’s expected behaviour. From then on, add new pages to the menu yourself.

    Adding WooCommerce product categories

    WooCommerce’s documentation describes two routes. On a classic theme, turn on Product categories in Screen Options, and a Product Categories panel appears beside Pages. On a block theme, add a block inside the Navigation editor and search for Product Category Link.

    Your category tree doesn’t come with them. One store owner on r/woocommerce found that parent and child categories went into the menu as one flat list. The fix was to drag each subcategory under its parent by hand.

    Why a saved menu doesn’t show on the site

    A menu that saved correctly but looks unchanged is usually not broken. Somewhere between the editor and the visitor, the site is showing something else. Check in this order and stop when you find the cause:

    1. Wrong editor. You edited in Menus while a block theme’s Navigation block draws the header, or the other way round.
    2. Not placed. On a classic theme, no Display location is ticked. On a block theme, the header has no Navigation block, or its block points to another menu.
    3. A different template. If the menu changed everywhere except the homepage, open that template under Appearance > Editor > Templates, select its Navigation block, choose the shared menu and save.
    4. A separate mobile menu. A mobile-menu plugin can show its own menu. In one wordpress.org thread, phones kept showing an old menu until the plugin was set to use the same WordPress menu as the desktop header.
    5. Cache. Clear the caching plugin first, then the host or CDN cache, then the browser. In another wordpress.org case, clearing the plugin and browser caches wasn’t enough, and only the host clearing its own server cache fixed it.
    6. A stale link. If one item leads to a 404, it’s probably a pasted address for a page whose slug changed. Remove it and add the page again from the list.

    Open the page in a private window before you edit anything again. If it looks right there, the problem is cache and the menu is fine. Making the same edit over and over just makes it harder to tell what happened. If the page still looks old after every cache is cleared, our guide on a WordPress page not updating goes through the next layers.

    Check it like a visitor before calling it done

    The editor canvas shows roughly what the site looks like. It isn’t a phone. Open the published site on a real phone, open every submenu, and tap every link you changed.

    Then put the mouse down. The W3C’s menus tutorial says fly-out menus must work with a keyboard as well as a mouse, shouldn’t disappear the moment the pointer leaves them, and need touch targets large enough to tap. Tab from the top of the page and watch for a visible focus outline. Open a submenu with Enter or Space, and close the mobile overlay with Escape.

    Before a large reorganisation, take a screenshot of the item list. Page and post revisions don’t bring back menus, as our guide to undoing changes in WordPress explains. Without a record, an undo means rebuilding the menu from memory.

    When to stop and get help

    Label changes, reordering and adding a link are safe jobs to do yourself. Stop when the problem stops being about the menu:

    • The Menus screen loads blank or shows PHP warnings such as “Cannot modify header information”. That points to a conflict in a theme or plugin. Isolate it on a staging copy, not by switching off plugins on the live site.
    • Saving returns a 404 or “Bad Request”. On large menus, a server security rule can reject the save request. Your host can check its logs and relax the rule for the save, then turn it back on afterwards.
    • Opening Menus causes “There has been a critical error on this website.”
    • Your account can’t see the menu screens at all. Ask an administrator to check that your role has edit_theme_options.
    • The header is built in a page builder, or the change means rebuilding a template rather than a list of links.

    If you’d rather describe the change than click through it, SiteSelf makes menu edits like these on the live site through chat. It connects through the SiteSelf Connector plugin, fetches the changed page to check it, and reports what changed, which is how it handles everyday website edits.

    Frequently asked questions

    Can I get the old Menus screen back on a block theme?

    Not by default. WordPress.org’s docs say block themes on 6.0 and later manage navigation through the Navigation block. Some plugins bring the classic screen back, but on a block theme the header still shows whatever its Navigation block points to.

    Does removing a menu item delete the page?

    No. Removing an item only takes the link out of the menu. The page stays published at its address, and other links to it still work.

    I want to edit the dashboard sidebar, not the site menu. Is that the same thing?

    No. The admin sidebar is a separate system, usually changed with a plugin such as an admin menu editor. Hiding a dashboard link doesn’t stop someone from opening that page by its URL. User roles and capabilities decide who has access.

    Why does my menu look different on my phone?

    Check the Navigation block’s Overlay Menu setting, and whether a mobile-menu plugin is showing a different menu. Then test the published site on a real phone, not the editor’s mobile preview.

  • How to reduce bounce rate on a WordPress website

    Key takeaways

    • In GA4, a bounce is a session that was not engaged. A session counts as engaged if it lasts longer than 10 seconds, records a key event or views two or more pages, so a reader who stays 30 seconds and leaves is not a bounce.
    • A sudden jump or drop usually comes from a tracking change, such as a consent plugin or a plugin that fires events. Check that before you change the site.
    • Contentsquare’s 2025 benchmark found a 53% bounce rate on pages with poor LCP and 49% on pages with good LCP. Speed matters, but nobody can promise how much it will move your number.
    • Speed fixes can break WordPress sites. Keep WooCommerce Cart, My Account and Checkout out of the page cache, don’t lazy-load the hero image, and turn on optimization options one at a time.
    • Judge a fix by what the page is for (calls, leads, orders), measured against the same page’s own baseline.

    A 70% bounce rate on a blog post and a 70% bounce rate on a paid landing page are different problems. On the blog post, readers may have found their answer and left happy. On the landing page, you are probably paying for clicks from people who leave right away. So before you compress an image or install another plugin, work out which of those you’re looking at.

    The steps below work in order. First check what the number measures. Then find the pages where it matters, fix the cause your data points to, and confirm the result against what the page is supposed to do. That last step usually means conversions, which our guide to measuring landing page conversion rate covers in more detail.

    What GA4 actually counts as a bounce

    In Google Analytics 4, bounce rate is the share of sessions that were not engaged. Google’s Analytics Help page on engagement rate and bounce rate says a session counts as engaged if it lasts longer than 10 seconds, records a key event, or has at least two page or screen views. A bounce is a session that does none of the three.

    This is a different measure from the old Universal Analytics one, which counted any single-page visit as a bounce. If you compare today’s figure with a blog post from 2019 or an industry benchmark, you may be comparing two different metrics.

    What the visitor didPagesTimeKey eventGA4 result
    Read a guide for 30 seconds, closed the tab130 sNoEngaged
    Landed, left after 4 seconds14 sNoBounce
    Opened two product pages in 6 seconds26 sNoEngaged
    Copied your phone number in 5 seconds and called15 sNoBounce

    Look at the last row. A visitor who got exactly what they came for still counts as a bounce unless a key event fires. Marking any event as a key event also makes the session engaged. You can lower the number without changing anything about the visit, and that is not a fix.

    Why your bounce rate suddenly jumped or dropped

    If the rate moved sharply overnight, check your tracking before you look at visitor behaviour. Real behaviour rarely changes that fast. A tracking setup changes the moment someone clicks save.

    The WordPress.org support forums have plenty of examples. In one Complianz support thread, a site owner saw bounce rate go from an average of 25% to about 80% over a similar 30-day period, after plugin updates and a rerun of the consent setup wizard. Other owners report the opposite: bounce falling from around 60% to under 10% the day they installed a plugin that sends extra events. Neither case proves a cause. Both tell you where to look first.

    Check these, starting with the most recent change:

    • A new or reconfigured cookie consent plugin. It changes which sessions get tracked at all.
    • An analytics or marketing plugin that sends scroll, timer or click events.
    • A second copy of the GA4 tag, added by a theme, a plugin or Google Tag Manager.
    • A new redirect that sends visitors through an extra URL before the real page.
    • A spike from one referrer or country, which often means bot traffic.

    Find the pages worth fixing first

    A site-wide average mixes your guides, your product pages and your contact page into one number, and that number points at nothing. Start where visitors enter the site.

    1. In GA4, open Reports, then Engagement, then Landing page. If your property doesn’t show it, an admin can add it from the report Library.
    2. Bounce rate isn’t always a default column. Use Customize report to add it next to engagement rate, average engagement time and key events.
    3. Sort by sessions. A page with 40 visits and a 90% bounce rate is noise. A page with 4,000 visits and 65% is worth your week.
    4. Add Session source/medium as a secondary dimension, then compare by device. A page can be fine on desktop and fail completely on mobile visits from paid social.
    5. Use at least four weeks of data, and write down the starting numbers for each page you pick.

    Now ask what each page is for. A how-to article that answers the question on its first screen can bounce heavily and still do its job. A service page fed by paid ads, or a product page, is supposed to lead somewhere. A high bounce rate on those pages is the one worth fixing.

    Fix the cause your data points to

    The pattern in your data narrows down the cause. Very short mobile sessions point to slow loading or a broken layout. Visits from one ad campaign that leave without scrolling point to a promise the page doesn’t keep. A spike on one template after an update points to a conflict.

    Make the page match what brought the visitor

    Message mismatch is a common cause, and it’s the one no speed plugin can fix. A typical example on Reddit’s small-business forum: a gardening business sends its Google Ads traffic to the homepage, sees bounce above 80%, and gets one booking. The ad promised hedge trimming. The homepage talked about the company.

    Give each ad group or offer its own page. Make its headline repeat what the ad said, and answer the visitor’s questions in the order they would ask them. A page headed “Emergency plumber in Leeds, same-day callouts” with a tap-to-call button keeps visitors that “Welcome to our services” loses. If the gap only appears for one campaign, the fix may be the campaign’s targeting rather than the page.

    Put the answer on the first screen

    Within a few seconds, visitors should be able to see what you do, roughly what it costs, and what to do next. A good test: time someone who has never seen the site. On articles, put the answer first and the background after it. On product pages, show the price and whether it’s in stock. On lead pages, show the form or the button above the fold, with no slider or second offer competing for attention.

    Speed up the slow pages, without breaking them

    Speed and bounce rate move together, but the gap in the best data is smaller than most guides suggest. Contentsquare’s 2025 Digital Experience Benchmarks covered 90 billion sessions on 6,000 sites. Pages with poor Largest Contentful Paint had a 53% bounce rate, against 49% for pages with good LCP. That is a correlation across the whole web, using the one-page definition of a bounce. Treat a slow page as a real cause, but don’t expect a fixed percentage back.

    Use field data from PageSpeed Insights and look at mobile on its own. Google’s web.dev counts a page as good when LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less, measured at the 75th percentile of real visits.

    On WordPress the usual causes are a hero image several megabytes in size, plugins nobody uses any more, a heavy theme or page builder, cheap shared hosting, and third-party scripts such as chat widgets. Our guide to speeding up a WP site without breaking it goes through each one. The rules that keep speed work from causing new bounces:

    • Back up the site first, or work on a staging copy.
    • Check what caching your host already does before you add a plugin. Two caching layers can conflict.
    • On WooCommerce, keep Cart, My Account and Checkout out of the page cache. WooCommerce’s developer docs list all three.
    • Don’t lazy-load the hero image. It is usually the LCP element, so delaying it makes the page feel slower.
    • Turn on minification, JavaScript delay and unused-CSS removal one option at a time, and test menus, forms and checkout after each one.
    • If the layout breaks with WP Rocket, add ?nowprocket to the end of the URL. WP Rocket’s troubleshooting guide uses that to show whether its optimizations are the cause.
    • Run speed tests more than once. The first request after a cache purge is uncached and slower.

    If you’d rather not do this work yourself, SiteSelf can fix slow WordPress pages for you from chat, using hosting access, and report what it changed and checked.

    Test it on a real phone

    A fast page with a menu that won’t close loses visitors just as quickly as a slow one. On a real phone, open and close the menu, submit each form with a deliberate mistake in it, and watch the first screen while the page loads. Look for a cookie banner covering the call to action, or a chat widget pushing the headline down. Content should fit a 320-pixel-wide screen without scrolling sideways, which is the WCAG 2.2 reflow width. Pop-ups that show up before the visitor has read anything, or that are hard to close, cost more than they bring in. If they still earn their place, trigger them on exit intent instead. For layout problems, see making a mobile-friendly website.

    Make sure the page loads at all

    Broken pages almost never appear in bounce-rate case studies, yet they lose every visitor who reaches them. A 404 from an old link, a redirect loop after an SSL or CDN change, or the “There has been a critical error on this website” screen all show up as bounces. Check Tools, then Site Health, look at your 404s, and open your top landing pages while logged out. If a page throws errors, our guide to fixing WordPress issues without guessing covers how to track down the cause.

    Give the visitor a next step

    A visitor who isn’t ready to buy still needs somewhere to go. Inside an article, link to the related service or the next question, a few paragraphs in. End with one specific action, such as “Get a quote for your postcode”. Commenters in WordPress forums are skeptical that a sidebar of related posts helps much. Links inside the text get clicked more because they appear right where the visitor has the next question.

    How to tell whether the fix worked

    Change one thing per page and note the date. Wait until the page has had enough sessions that one quiet day can’t swing the figure, then compare it with that page’s own baseline, split by the same source and device. If you changed the headline, the images and the caching in the same week, you won’t know which change did anything.

    Then check the number that matters for that page. If bounce rate drops and calls, leads or orders don’t move, nothing improved for the business. If a new tracking event lowered the bounce rate, nothing improved for visitors either.

    Stop and get help if the site shows a critical error, checkout stops working after you changed caching, or you can’t tell whether a plugin or the theme is causing the problem. WooCommerce’s own advice is to test for conflicts on staging, switching to a default theme and reactivating plugins one at a time. On a live store, that is not something to try during business hours.

    Frequently asked questions

    What is a good bounce rate?

    There’s no single number you can rely on. Published benchmarks use different definitions and different sites, and the right number depends on what the page is for. Compare a page with similar pages on your own site and with its own past figures.

    Is a high bounce rate always bad?

    No. Someone who gets the answer from one article and leaves may be completely satisfied. It matters most on product, service and campaign pages, where you expect the visitor to take a next step.

    Does bounce rate affect Google rankings?

    We haven’t found a Google statement saying GA4 bounce rate is used for ranking, and practitioners disagree about it. Fix the page for the people visiting it. If the same problems are hurting search, those fixes help there too.

    Should I add scroll or timer events to lower bounce rate?

    Only if those events measure something you actually care about. Adding events just to count more sessions as engaged makes the report look better and hides the pages that need work.

    Do I need a caching plugin?

    It depends on your host. Many managed WordPress hosts already cache pages on the server, and adding a plugin on top can cause conflicts. Read your host’s documentation before you install one.

    Why is bounce rate higher on mobile than desktop?

    Phones have slower processors and less steady connections, so heavy images and scripts hurt more there. Mobile layouts also hide problems a desktop check misses, like a sticky header or cookie banner covering the button.