Don’t panic. Nothing is broken on your end.

This is one of the most common questions I see from bloggers, and the answer is almost always the same: WordPress favicon not updating in Google is a caching issue on Google’s side, not yours. Google holds onto favicons for 2-6 weeks before refreshing them in search results. Sometimes longer. Your replacement is sitting on your server right now, doing its job – the search index just hasn’t caught up.

Here’s the checklist I walk through to confirm the new favicon is live, plus the one Search Console trick that nudges Google to refresh faster.

Why is my WordPress favicon not updating in Google?

The short version: Google caches favicons aggressively, and there’s no setting to force an instant update.

When Googlebot crawls your homepage, it grabs your favicon and stores a copy in its image index. That cached copy is what shows up next to your site in search results. Google doesn’t re-fetch the favicon every time someone searches – that would be wasteful for a tiny image. Instead, it checks back on its own schedule, which is usually 2-6 weeks but can stretch longer for low-traffic sites.

So even though you’ve replaced the file, Google is still serving its cached version. There’s nothing wrong with WordPress, your theme, or your favicon file. The new icon will appear once Google decides to refresh.

I’ve seen this confuse bloggers for weeks. They re-upload the favicon 3 or 4 times, swap themes, and even contact their host – all because Google won’t update. The fix isn’t on your site. It’s on Google’s end, and you can speed it up with one Search Console request.

But before you do anything, you need to confirm the new favicon is actually live and reachable. That’s the next step.

How do I confirm my new favicon is actually live?

Don’t skip this part. If your favicon isn’t reachable at the right URL, no amount of waiting will help Google find it.

Open a new browser tab and type this exact URL: yoursite.com/favicon.ico (replace yoursite.com with your real domain). Press Enter. You should see your new favicon icon load on a blank page. If you see the old one, that’s just your browser cache – we’ll fix that in a second.

To bypass the browser cache, add a fake parameter to the end: yoursite.com/favicon.ico?v=2. The ?v=2 tells the browser “this is a different file, fetch a fresh copy.” If the new favicon loads with the cache buster but the old one loads without it, your browser is the problem, not your site.

If neither URL shows your new favicon – or you get a 404 error – then the favicon really isn’t set correctly in WordPress. That’s a different problem, and you’ll fix it in the next section.

One more test worth running. Open your site in an incognito window (Ctrl+Shift+N in Chrome) and look at the browser tab. The favicon there is the same one Google will eventually grab.

If it’s the new one, you’re good. If it’s the old one, your WordPress setting didn’t save.

Where do I update the favicon in WordPress?

WordPress calls the favicon a “Site Icon,” and the path to update it depends on whether you’re using a classic theme or a block theme.

For classic themes (Astra, GeneratePress, Kadence, OceanWP, and most older themes), go to Appearance > Customize > Site Identity. You’ll see a section called “Site Icon” with an Upload button. Click it, pick your new favicon, and click Publish at the top of the Customizer panel.

If you can’t find Customize in your menu, your theme might have hidden it – my guide on where the WordPress Customizer went covers how to bring it back. And if entire chunks of your dashboard sidebar have vanished, my fix for the WordPress left menu missing covers why Customizer items disappear with it.

For block themes (Twenty Twenty-Four, Twenty Twenty-Five, Ollie, and most themes from 2024 onwards), the Customizer is gone. Go to Appearance > Editor > Styles and look for a settings panel. The Site Icon option is sometimes tucked away here, but more often you need to go to Settings > General instead, or use the Tools menu in the Site Editor sidebar.

The easiest path on a block theme: go to Settings > General and scroll to the bottom. Some block themes (and WordPress 6.5+) added the Site Icon control there directly. If you don’t see it, install the free Site Icon plugin from the WordPress repository – it adds a dedicated upload screen that works on every theme.

Whichever path you used, save your changes and test the favicon URL again with the cache buster. If you upload a new file but Save Changes doesn’t seem to take effect, that can be its own headache – my Kadence Customizer not saving changes fix covers the most common causes.

How do I tell Google to refresh my favicon?

This is the part that actually speeds things up. Google Search Console has a feature called URL Inspection that lets you ask Google to recrawl a specific page.

Log into Google Search Console. If you don’t have it set up yet, that’s a separate (and important) task – it takes about 10 minutes and you’ll need it for tracking everything else, including how your meta descriptions perform in search.

Once you’re in Search Console, click URL Inspection in the left sidebar. Paste your homepage URL into the search bar at the top (just https://yoursite.com/, no trailing path). Hit Enter and wait for the results to load.

You’ll see a status message about whether the URL is indexed. Look for the Request Indexing button (sometimes labeled “Test Live URL” first). Click it.

Google will recrawl your homepage within 10 minutes to 24 hours. Because the favicon link is in your homepage’s HTML head, Google picks up the new favicon URL during that recrawl.

Important: Request Indexing on the homepage, not on individual posts. The favicon is referenced from your site’s root, so refreshing the homepage is what matters. (If you can’t even open your homepage to make a small edit, my fix for WordPress editor that won’t let you edit pages sorts that out first.)

While you’re in Search Console, resubmit your sitemap too. Click Sitemaps in the sidebar, find your sitemap entry (something like sitemap.xml or sitemap_index.xml if you use Yoast or Rank Math), and click the 3-dot menu next to it. Pick Resubmit. This nudges Google to recrawl your whole site, which can help if more than one page needs refreshing.

If you haven’t picked an SEO plugin yet, my Rank Math vs Yoast SEO comparison covers which one is easier for sitemaps and beginner-friendly settings.

How long until the new favicon shows in search?

Realistic timeline: 2-6 weeks for most sites, even after Request Indexing.

I know that sounds frustrating when you’ve done everything right. But Google’s favicon refresh schedule is separate from its page index. Even if Google recrawls your homepage tomorrow, the favicon image cache is updated on its own track. Most bloggers I’ve worked with see the new favicon appear in search results around the 3-week mark.

For high-traffic sites that get crawled often, it can be as fast as 5-7 days. For brand-new sites or low-traffic blogs, it can stretch to 8 weeks. There’s no public way to check exactly when Google will swap the cached image.

What to do if 8+ weeks pass and the old favicon is still showing:

1. Reconfirm the favicon is live at yoursite.com/favicon.ico (cache busted)
2. Check that the favicon HTML tag is in your page source (View Source, search for icon)
3. Request Indexing one more time in Search Console
4. Check the Coverage report in Search Console for any homepage crawl errors
5. Make sure your robots.txt isn’t blocking /favicon.ico (rare, but it happens)

If everything checks out and Google still won’t update, post in the Google Search Central forum. Google staff sometimes respond and can manually flag the issue. I’ve seen it happen for sites stuck past the 10-week mark.

What if my favicon broke entirely?

A different but related problem: your favicon shows as a blank white square or a generic globe icon in search results. That’s not a caching issue. Your favicon file itself has a problem.

The 3 most common causes:

Wrong file format. WordPress accepts PNG, JPG, GIF, and ICO for favicons, but Google has a strong preference for PNG or ICO. If you uploaded a JPG, the transparent areas around your logo might render as white in search. Convert your logo to PNG with a transparent background (Canva, Figma, and Photoshop all export PNG with transparency).

Wrong dimensions. Google recommends a minimum of 48×48 pixels, and the favicon size must be a multiplier of 48 (so 96×96, 144×144, 192×192, or 512×512). WordPress itself recommends 512×512.

If you uploaded a tiny 16×16 favicon (the old standard), Google might reject it. Re-export at 512×512.

Transparency rendered as white. This was the exact issue I keep seeing on the WordPress forums. The PNG had transparency, but the search result showed a transparent area filled with white.

The fix is to design the favicon with a solid background color baked in. Don’t rely on transparency for the search result thumbnail. A square logo with a colored background renders consistently across light and dark modes.

If you need a quick way to make a clean square logo, Canva AI for featured images covers the same workflow I use for favicons.

One more thing worth checking. If your favicon looks pixelated or fuzzy in search results, that’s a resolution problem. WordPress automatically generates smaller versions from your 512×512 upload, but if you originally uploaded something tiny and let WordPress upscale it, the result is blurry.

Re-upload a sharp 512×512 source file. The same logic applies to other blurry images on your site – resolution at upload time matters more than display size.

FAQ

How long does it take for Google to update a favicon?

In my experience, Google holds onto its cached favicons for 2-6 weeks. It doesn’t fetch the icon every time someone searches. You just have to wait for Google to recrawl your homepage on its own schedule.

How do I force Google to update my favicon?

There isn’t a magic button to update it instantly. But I always use the URL Inspection tool in Google Search Console to request indexing for my homepage. That tells Google to crawl the site again, which speeds up the process.

Why is my WordPress favicon showing in the browser but not in Google?

This happens because your browser and Google maintain separate caches. Your browser grabbed the fresh file when you visited the site, but Google’s search index is still serving the old image from its servers.

What are Google’s favicon requirements?

Google wants a square image that’s a multiple of 48 pixels, like 96×96 or 144×144. WordPress usually recommends uploading a 512×512 file, which works perfectly. Just make sure you save it as a PNG or ICO file.

Your new favicon is on its way

Here’s what I want you to take away from this. When your WordPress favicon isn’t updating in Google, it’s almost always a patience problem, not a technical one. The new icon is live on your site. Google just hasn’t picked it up yet.

Confirm the favicon loads at yoursite.com/favicon.ico?v=2. Confirm it’s set in Customize > Site Identity (or the block theme equivalent). Then go to Search Console and Request Indexing on your homepage. After that, the only thing left to do is wait 2-6 weeks.

While you’re tweaking your branding, this is also a good moment to double-check your WordPress site title and make sure both pieces match in search results. And if you ever update something on the site and panic that nothing is showing, my guide on WordPress changes not appearing on the live site covers cache layers that hide perfectly good edits.

Your favicon will show up. Just not today.

Take a breath. You didn’t break anything, and your work isn’t lost.

When WordPress changes are not showing up on the live site, the cause is almost always cache. There isn’t just one cache either – there are 3, stacked on top of each other, and each has to be cleared before your edit reaches a real visitor. The fix takes 5 minutes once you know which buttons to press.

Why are my WordPress changes not showing up?

The short answer: something between you and your visitor is serving an older copy of the page.

Cache is just a saved snapshot. Instead of building your homepage from scratch every visit, WordPress (and your host, and your browser) saves a finished HTML version and hands it out for the next 60 minutes or so. It makes the site fast. But it also means your edit can sit there for an hour before anyone sees it.

There are 3 cache layers I check, in this order:

1. Browser cache – your own Chrome or Firefox is showing you a saved copy
2. Server cache – your host or a caching plugin is serving an old HTML snapshot
3. CDN cache – Cloudflare or your host’s edge network is holding the old version

Most of the time, the culprit is layer 2. But you have to rule out layer 1 first, because if your browser is the problem, you’ll keep “fixing” the server cache and seeing no result.

How do I do an incognito test?

This is the single best diagnostic step, and it takes 10 seconds.

Open a new incognito window (Chrome: Ctrl+Shift+N, Firefox: Ctrl+Shift+P) and visit your site. If the new version shows up in incognito but not in your normal browser, the problem is your browser cache. Skip to the next section.

If incognito shows the OLD version too, your browser is innocent. The stale page is coming from somewhere outside your computer – your server cache or your CDN. Move on to layer 2.

I run this test every single time, before I touch any plugin settings. It saves me from chasing problems that don’t exist. And it works on phones too – just open a private tab in Safari or Chrome mobile.

One small catch: incognito only bypasses your browser cache, not the server or CDN. So if all 3 layers are stale, incognito will also show the old version – which still tells you the problem isn’t local to your machine.

How do I clear my browser cache?

If incognito fixed it, this is the fast layer.

For most edits, a hard refresh is enough. On Windows or Linux, press Ctrl+Shift+R. On Mac, press Cmd+Shift+R. This tells your browser to ignore its saved copy and ask the server for a fresh one.

If that still shows the old page, do a deeper clear. In Chrome, press Ctrl+Shift+Delete (Cmd+Shift+Delete on Mac), set the time range to “Last hour,” check “Cached images and files,” and click Clear data. Reload your site and the new version should appear.

One thing I learned the hard way: browser cache is also why your phone, laptop, and work computer can all show different versions of the same site. Each browser has its own cache. To confirm a fix is really live, ask a friend on a different network to check, or use webpagetest.org to load the URL fresh from a remote server.

How do I clear my WordPress server cache?

Layer 2 is where most “WordPress changes not showing up” problems actually live. Server cache comes from 2 places: your hosting company, and your caching plugin. Often both at once.

Your host’s cache

Managed WordPress hosts run their own cache layer that you can’t turn off. Here’s where to find the purge button on the popular ones:

• SiteGround: Dashboard > SG Optimizer > Caching > Purge SG Cache
• WP Engine: Top admin bar > WP Engine > Caching > Purge all caches
• Kinsta: Top admin bar > Kinsta icon > Clear Cache
• Cloudways: Cloudways panel > pick your app > Application Settings > Purge Varnish Cache
• Bluehost / HostGator: Dashboard > Bluehost menu > Caching > Purge All

On a generic shared host like Hostinger, Namecheap, or DreamHost, the host cache is usually off by default and the caching plugin is doing all the work.

Your caching plugin

If you installed a caching plugin to make the site faster, that’s another snapshot layer to clear. The 3 you’ll most often see:

• WP Rocket: Top admin bar > WP Rocket > Clear and preload cache
• LiteSpeed Cache: Top admin bar > LiteSpeed Cache icon > Purge All
• W3 Total Cache: Top admin bar > Performance > Purge All Caches

Not sure which caching plugin you have? Go to Plugins > Installed Plugins and look for anything with “cache” in the name. WP Super Cache, WP Fastest Cache, and Cache Enabler all work the same way: there’s a “purge” or “clear” button somewhere obvious.

After clearing both your host cache and your plugin cache, do another incognito test. If the new version is there, you’re done. If you’re still seeing the old page, layer 3 is involved.

One trick I rely on: when I’m making 10+ small edits in a row, I temporarily turn the caching plugin off until I’m done, then turn it back on and clear once. Saves 20+ purge clicks per session. Just remember to switch it back on – I’ve left WP Rocket disabled for a week before, and the site got noticeably slower until I caught it.

How do I clear my CDN cache?

A CDN (Content Delivery Network) is the third layer – it stores copies of your site on servers worldwide so visitors get a fast load no matter where they are. The most common one for small WordPress sites is Cloudflare. Some hosts also have their own edge caching that acts the same way.

Not sure whether you have a CDN? Check your domain’s DNS – if your nameservers point to Cloudflare, you have Cloudflare in front of your site. Or ask your host’s support chat: “Do you have edge caching enabled on my account?”

Clearing Cloudflare cache

This is the one I clear the most:

1. Log in at dash.cloudflare.com and pick your site
2. Click Caching in the left sidebar, then Configuration
3. Click Purge Everything and confirm in the popup

It takes about 30 seconds for the purge to roll out worldwide. Then test in incognito again.

Host edge caches

Kinsta, WP Engine, and Cloudways all run their own CDN-style caches that aren’t the same as the WordPress cache covered above. If clearing the regular host cache didn’t work, look for a separate option called “CDN cache,” “edge cache,” or “static cache” and clear that too. WP Engine splits “Page cache” and “CDN cache” into 2 separate purge buttons inside the same menu.

If you have a dedicated CDN plugin (Cloudflare’s official plugin, or BunnyCDN), most add a purge button to your WordPress admin bar. Use that – it’s faster than logging into the CDN dashboard.

What if I still don’t see my changes?

If you’ve cleared all 3 layers and the old version is still showing, I look at 4 less-common culprits:

1. Object cache. Some hosts run Redis or Memcached for database queries. If your text changes are there but a setting (like a customizer color) won’t apply, this is often why. WP Rocket has a “Clear object cache” option, or your host can flush it – just open a support ticket and ask them to “flush Redis.” If you ever see a 500 internal server error after a Redis flush, that’s a separate fix.

2. CSS/JS minification cache. Caching plugins often combine and minify your CSS files into one, and that combined file can stay stale after a theme tweak. In WP Rocket, go to Settings > WP Rocket > File Optimization and toggle CSS minification off, save, then back on – that forces a rebuild. Same idea for LiteSpeed and other caching plugins.

3. Customizer not saving. If your changes never actually saved, that’s a different problem. The Kadence Customizer occasionally fails to save in Chrome – my fix for Kadence Customizer not saving changes covers that. If the customizer is broken so badly the site won’t load, my notes on what to do when WordPress recovery mode isn’t working get you back in.

4. You’re editing the wrong page. I’ve done this. WordPress lets you have a “Home” page in Pages > All Pages that isn’t actually your homepage – if Settings > Reading points to a different page, your edits go nowhere visible. Same trap can hit the blog page if your posts aren’t showing up.

One more edge case: search engines. Google can take 1-3 weeks to recrawl your page, so even after the live site updates, your search snippet or old logo can stick around in Google’s results until they refresh. That’s not something you can fix from your dashboard.

FAQ

Why is my WordPress not updating changes?

I see this happen most often because of caching. Your browser or server is holding onto an older snapshot of your page instead of fetching the new one. Clearing your caches usually fixes it instantly.

How long does WordPress take to publish changes?

When you hit Update, your changes save to the database instantly. If you don’t see them on the front end right away, a caching layer is delaying the display. Once you clear that cache, the live site updates immediately.

Why do my changes appear in preview but not on the live site?

WordPress preview mode is smart enough to bypass your site’s cache so you can see your work. The live site, however, serves the cached version to keep things fast for visitors. You just need to purge your server cache to force the live site to catch up.

Why is WordPress not saving my changes?

If the dashboard itself isn’t saving and you get an error when you click Update, you might be out of server memory or have a plugin conflict. But if it says “saved” and you just can’t see it on the front end, it’s almost definitely a caching issue.

Your changes are there – the cache is just hiding them

Here’s the takeaway. When WordPress changes are not showing up on the live site, your work isn’t lost and your site isn’t broken. There’s just a stale snapshot somewhere between you and your visitor.

Run the incognito test first. Then clear browser, then server (host plus plugin), then CDN. One of those purges will reveal your edit. And once you’ve done it 2 or 3 times, the whole sequence takes under 5 minutes.

Before bigger changes – swapping a theme, editing the header, redoing your homepage – I’d also back up your WordPress site first. Cache is easy to fix. Accidentally deleting a section is harder.

Here’s the thing. The main setting is in one obvious place. But there are 4 tricky cases where that setting does nothing, and nobody tells you about them until you’re already frustrated.

I’ll walk you through the main fix first, then all the weird edge cases that trip people up.

Where is the WordPress site title setting?

The main site title lives under Settings > General in your WordPress dashboard. That’s the one setting that controls the default title used across your site.

But here’s the part that confuses people. What you see on your actual website might come from somewhere else entirely. It could be a logo image, a block in the Site Editor, or an override from your SEO plugin. Each of those takes priority over the General setting.

So the fix depends on where your title is actually coming from. Let’s start with the basic setting and work through the others. And if you’d rather remove the page title entirely on individual pages, that’s a different setting in your theme.

How do I change the site title in Settings > General?

This is the 30-second fix that works for most sites.

Log in to your WordPress dashboard. In the left sidebar, click Settings, then General. The very first field at the top is Site Title. Type your new title in that box.

Scroll to the bottom of the page and click Save Changes. That’s it. Open your site in a new tab to confirm the title updated in the browser tab and anywhere the theme displays it.

If your title updated – great, you’re done. If nothing changed on the front end, one of the 4 cases below is the culprit. Keep reading.

What if my theme shows a logo image instead of the title?

This one trips up most beginners. You change the title in Settings > General, refresh your site, and nothing looks different. Why? Because your theme is showing a logo image, not text.

Most modern themes let you upload a logo that replaces the site title text in the header. The Settings > General title is still there under the hood – search engines and browser tabs still use it – but visitors see your logo instead.

To update or remove the logo, go to Appearance > Customize and look for a section called Site Identity, Header, or Logo. If you’re on a newer block theme, the Customizer might not exist. In that case, check my guide on where the WordPress Customizer went for the block theme equivalent.

Inside Site Identity you’ll usually see:

• Logo – upload or remove the image
• Site Title – a text field (this often syncs with Settings > General)
• Display Site Title and Tagline – a checkbox to toggle the text on or off

If your logo already has the brand name baked into the image, you have to edit the image file itself. WordPress can’t change text inside a PNG or JPG. Open the logo in Canva, Photoshop, or any image editor, fix the text, and re-upload it through the same Site Identity panel. While you’re tweaking branding, you might also want to change page background colors so the logo sits on the right color behind it.

What about block themes (Twenty Twenty-Four, etc.)?

Block themes like Twenty Twenty-Four, Twenty Twenty-Five, and any theme that uses Full Site Editing changed the rules. The Customizer is gone. The header is controlled by the Site Editor and a specific block called Site Title.

Here’s how to update it on a block theme.

Go to Appearance > Editor in your dashboard. This opens the Site Editor. Click Patterns in the sidebar, then find your header template part (usually just called Header). Click the header to open it for editing.

Look for the Site Title block in the header layout. Click it once to select it. In the right sidebar, you’ll see block settings – but here’s the important part: the text you see is pulled from Settings > General automatically. You can’t just type over it in the block.

To change the actual words, go back to Settings > General, update the Site Title field, and save. Then return to the Site Editor and refresh. The block updates automatically.

If you want to remove the title entirely and just show a logo, delete the Site Title block from the header. If you want to change the font or color, click the block and use the Styles panel on the right. While you’re in the Site Editor, you might also want to add items to your menu to match the new branding. If you accidentally break the layout while poking around, I wrote a guide on fixing global template changes that’ll walk you through reverting.

How do I change the site title that appears in Google search results?

This is the sneakiest case. You change the site title in Settings > General. The header on your site updates. But Google still shows the old title in search results, or the browser tab shows something weird like “Home – Old Site Name”.

That’s your SEO plugin overriding WordPress.

Most SEO plugins – Yoast, Rank Math, SEO Simple Pack, All in One SEO – let you set a separate “site name” or “title template” that takes priority over the built-in WordPress title tag. When the plugin is active, WordPress hands off title duties to it, and the Settings > General value gets ignored for the browser tab and search snippets.

Here’s where to look in each major plugin.

Yoast SEO. Go to Yoast SEO > Settings > Site basics. There’s a field called Site title that controls what shows up in search results and social previews.

Rank Math. Go to Rank Math > Titles & Meta > Global Meta. Look for the Title Separator and Site Name fields. The Homepage tab has a separate title template.

SEO Simple Pack. Go to SEO PACK > General settings. The Website name field at the top overrides WordPress. Clear it to fall back to your Settings > General value.

All in One SEO. Go to All in One SEO > Search Appearance > Global Settings. Update the Site Title field there.

If you’re not sure which plugin is overriding things, open your site in a new tab, right-click the page, and choose View Page Source. Search for <title> near the top of the code. Whatever text is between those tags is your real title. If it doesn’t match Settings > General, it’s coming from your SEO plugin.

Not sure which SEO plugin to keep? I compared Rank Math vs Yoast for beginners if you’re still choosing.

Site title vs tagline – what’s the difference?

These two fields sit right next to each other in Settings > General, and people mix them up constantly.

The Site Title is your site’s name. “The WP Ninja”, “Jane’s Kitchen Blog”, “Acme Plumbing”. It’s what shows in the browser tab and usually the main header text.

The Tagline is a short description that sits under or near the title. It’s meant to be a 5-10 word pitch. WordPress fills it with “Just another WordPress site” by default, which is the most common mistake I see. If you’ve never changed it, Google might be showing that default tagline in your search results right now.

Here’s a quick comparison.

Both fields feed into SEO. The title usually appears at the end of every page’s browser tab (like “About Us – Your Site Title”). The tagline sometimes appears in the homepage meta description if you haven’t set a custom one – which is why writing a good meta description matters even more if you leave the tagline blank.

My rule: always change both from the defaults, even if you don’t use the tagline in your header design. It still shows up in places you can’t see.

Frequently Asked Questions

How do I change the site title and tagline in WordPress?

The easiest way I know is to go to Settings > General in your dashboard. You can type your new title right into the text boxes at the top of the page. Don’t forget to scroll down and click save!

Where are the General Settings in WordPress to change the title?

You’ll find the General Settings menu hiding near the bottom of your left-hand admin sidebar. I click on “Settings” and then “General” to access the 2 main text fields for the title and tagline.

How does changing my WordPress site title affect SEO?

Changing your title directly changes how you show up in Google search results. I try to include my brand name and at least 1 relevant keyword, so people know exactly what my site is about before they even click.

Why is my WordPress site title not changing after I save it?

When this happens to me, it’s almost always a caching issue. I’ll clear my caching plugin and refresh my browser, and my new title usually appears on the live site right away.

Closing thoughts

The short answer: change your site title in Settings > General, click save, done. That fixes it for 80% of people.

But if you hit one of the 4 tricky cases – a logo image, a block theme, an SEO plugin override, or confusion with the tagline – now you know exactly where to look. The hardest part is figuring out which one is the culprit, and “View Page Source” is your best friend for that.

One last tip. Whenever you change your site title, always check 3 places afterward: the browser tab, the header of your live site, and an incognito Google search for your domain. If all three match what you typed in Settings > General, you’re in good shape.

The toggle is buried in a panel that most beginners never open. But once you know where it is, you can strip the header off any page in about 5 seconds. Here’s exactly how.

How Do I Disable the Header on a Single Page?

This is a one-page, one-toggle fix. It won’t affect any other page on your site.

1. Open the page in the WordPress block editor.
2. Click the Page Settings icon in the top-right toolbar – it looks like a small page with a pencil.
3. Scroll down to the bottom of the panel.
4. Find “Disable Header” and toggle it to On.
5. Click Update (or Publish if it’s a new page).

That’s it. The entire header – logo, navigation menu, everything – disappears from this page on the front end. Your other pages stay exactly the same.

I use this on every landing page I build. When someone arrives from an ad or an email link, I don’t want them clicking away to my blog or About page. I want them focused on the one action the page is designed for.

Here’s what the front end looks like with the header turned off – no top bar, no logo, no menu. The page starts straight at your content:

Compare that to a normal page with the full Kadence header on top. The toggle gives you back about 80px of vertical space and removes every navigation link that could pull a visitor away.

Can You Hide the Footer Too?

Yes – and it’s in the same panel. Right next to the “Disable Header” toggle, you’ll see a “Disable Footer” option. Toggle that on, and the footer disappears too.

Combining both gives you a completely blank canvas. No header, no footer, no navigation – just your content and nothing else. If you’re also seeing white space between your Kadence blocks, that’s a separate spacing issue worth fixing on these clean layouts. This blank canvas setup is exactly what you need for:

• Sales pages where every click should go to the buy button
• Coming soon pages during a site launch
• Squeeze pages collecting email signups

You don’t need a page builder like Elementor or a “Canvas” template for this. Kadence gives you the same result with 2 toggles that are already built into the free theme.

Does This Work on Posts Too?

Yes. The same Page Settings panel shows up on posts, pages, and most custom post types. So if you have a special announcement post or a sponsored post with a custom layout, you can disable the header on that single post without affecting the rest of your blog.

I’ve used this on 2 or 3 posts where I wanted a unique look – like a long-form guide with its own navigation built into the content. Removing the site header made the page feel more like a standalone resource than a regular blog post.

Don’t Forget Your H1

Here’s the one thing that trips people up. When you disable the header in Kadence, the page title might also disappear. That page title is usually your only H1 tag – the heading that tells Google what the page is about.

A page without an H1 is invisible to search engines in a meaningful way. Google’s own documentation recommends exactly one H1 per page for clear content structure.

The fix takes 10 seconds:

1. Edit the page in the block editor.
2. Add a Heading block near the top of your content.
3. Make sure it’s set to H1 (not H2 or H3).
4. Type a descriptive title that includes your target keyword.

This H1 doesn’t have to match the page title you disabled. In fact, you can write it specifically for SEO – longer, more keyword-rich, better optimized than a generic “Landing Page” title ever would be.

I cover this H1 issue in much more detail in my guide on how to remove the page title in Kadence. It’s the number one mistake beginners make when hiding any part of their header or title area.

How Do I Remove the Header on a Specific Page in WordPress?

If you’re not using Kadence, this gets harder. Most WordPress themes don’t have a built-in “Disable Header” toggle. The usual workarounds are:

• CSS hack: Add .page-id-42 .site-header { display: none; } to Additional CSS (fragile, breaks with theme updates)
• Page builder templates: Elementor has a “Canvas” template, but that requires Elementor
• Header/footer plugins: Plugins like “Hide Header and Footer on Pages” exist, but that’s another plugin to maintain

Kadence’s approach is the cleanest I’ve found. One toggle per page, built into the theme, no code, no extra plugins. It’s one of the reasons I recommend Kadence for landing pages and sales funnels – the distraction-free setup is already there. And if you want to change your sidebar layout on these pages too, Kadence gives you per-page control over that as well.

If you’re also dealing with your menu overlapping your logo on smaller screens, fixing the mobile breakpoint is a separate 10-second fix in the Customizer.

Free vs. Pro – Do You Need to Upgrade?

For hiding the header, absolutely not. The “Disable Header” and “Disable Footer” toggles are 100% free in Kadence.

Kadence Pro does add one related feature worth knowing about: Conditional Headers. Instead of hiding the header entirely, Conditional Headers let you swap in a different header design based on the page type or user role. For example, you could show a simplified header on landing pages and a full navigation header everywhere else.

But that’s a different use case. If you just want the header gone on specific pages, the free toggle does exactly that. Don’t spend money on a problem that’s already solved.

5 Use Cases for Headerless Pages

Here are the pages where hiding the header makes the biggest difference:

1. Link in Bio page. Create a page at yoursite.com/links, disable the header and footer, and stack button links vertically. I wrote a full tutorial on how to build a free Linktree alternative in WordPress – the header toggle is the first step.

2. Landing pages for ads. When you’re paying for traffic from Google or Facebook ads, every navigation link is a potential leak. Removing the header keeps visitors focused on your call-to-action button instead of wandering off to your blog.

3. Sales pages for digital products. Long-form sales pages work best when there’s nothing to click except the buy button. No menu, no footer links, no distractions.

4. Coming soon or maintenance pages. While you’re building your site, a clean page with just your logo and an email signup form looks far more professional than a half-built homepage with a full navigation menu.

5. Email opt-in squeeze pages. Similar to landing pages, but specifically designed to collect email addresses. One headline, one form, one button – the header just gets in the way.

What About Transparent Headers?

Hiding the header and making it transparent are two different things. A transparent header keeps the navigation visible but removes the background color, letting your hero image show through. The menu is still there – it just blends into the page design.

You can control this per page too. In the same Page Settings panel, there’s a “Transparent Header” dropdown. Change it from “Default” to “Disable” to turn off the transparent effect on a specific page, or “Enable” to force it on.

Use a transparent header when you want navigation but a cleaner look. Use “Disable Header” when you want the navigation gone entirely.

Frequently Asked Questions

Can you hide the menu on a WordPress landing page?

Yes. In Kadence, open your landing page in the block editor, click the Page Settings icon (top right), and toggle “Disable Header” to On. This removes the entire header – logo, menu, everything – from that one page. No code needed, and it’s free.

How do I use a blank canvas in Kadence?

Toggle both “Disable Header” and “Disable Footer” in the Page Settings panel. This gives you a completely blank page with just your content – no navigation, no footer widgets, no site branding. I use this for landing pages, sales pages, and Link in Bio pages.

Do I need Kadence Pro to hide the header?

No. The “Disable Header” toggle works in the free version of Kadence. Kadence Pro adds Conditional Headers (swapping different header designs by page type), but for simply hiding the header on specific pages, the free theme handles it perfectly.

Will hiding the header hurt my SEO?

Only if you forget to add an H1. When the header is disabled, the page title (which is your H1) might disappear too. Add an H1 Heading block manually in your page content with your target keyword. That takes 10 seconds and keeps your SEO intact.

Does disabling the header affect my other pages?

No. The “Disable Header” toggle only affects the single page where you enable it. Every other page on your site keeps its normal header and navigation. You can toggle it on or off per page without any site-wide impact.

Can I have a different header for just one page?

In the free version, your options are showing the full header, hiding it completely, or switching to a transparent header on a per-page basis. For a completely custom header design on just one page, you’d need Kadence Pro’s Conditional Headers feature.

How do I hide the header using CSS if the toggle doesn’t work?

If a plugin is interfering with Kadence’s toggle, you can add .page-id-12 .site-header { display: none; } to your Additional CSS in the Customizer. Replace 12 with your actual page ID. But I’d try deactivating plugins first – the toggle should work on its own.

Wrapping Up

Hiding the header on specific Kadence pages is one of those features that’s incredibly useful once you know it exists. And most beginners never find it because it’s tucked inside the Page Settings panel instead of the Customizer.

Here’s my quick workflow for headerless landing pages:

1. Open the page and click the Page Settings icon (top right).
2. Toggle Disable Header to On.
3. Toggle Disable Footer to On (optional, but I usually do).
4. Add an H1 Heading block at the top of your content for SEO.
5. Click Update and preview the page.

The whole process takes under a minute. No CSS, no plugins, no page builder required – just Kadence’s built-in toggles doing exactly what you need.

If you’re using a block theme like Twenty Twenty-Four, the Customizer is hidden on purpose. WordPress replaced it with something called the Site Editor. Here’s where everything went and how to get it back when you need it.

Why Is the WordPress Customizer Missing?

Starting with WordPress 5.9, WordPress introduced Full Site Editing (FSE) and a brand new tool called the Site Editor. Block themes – like WordPress’s own Twenty Twenty-Four – use the Site Editor instead of the Customizer. So when you activate a block theme, WordPress hides the Customizer link from your menu. This shift is part of the bigger Classic Editor vs Gutenberg story that’s been playing out since 2018.

But here’s the important part: the Customizer isn’t gone from WordPress itself. It’s just hidden because block themes don’t need it. “Hybrid” themes like Kadence, Astra, and GeneratePress still rely heavily on the Customizer for their header builders, footer builders, color settings, and font controls.

If you’re using one of those themes, the Customizer link should still be right there under Appearance > Customize.

The confusion usually starts when someone switches from a hybrid theme like Kadence to a block theme like Twenty Twenty-Four. One day the link is there, the next day it’s gone. That’s exactly what happened to me when I was testing themes – and it took me a solid 10 minutes of Googling to figure out what was going on.

Where Did Everything Move?

The good news is that every feature from the Customizer still exists somewhere in the Site Editor. The bad news is that nothing is in the same place. Here’s a quick map of where to find things.

Menus

Your navigation menus moved to Appearance > Editor > Navigation. The menu editing experience is completely different now – you build menus with blocks instead of the old drag-and-drop interface. It takes some getting used to, but it’s actually more flexible once you learn it.

Colors and Fonts

These are now at Appearance > Editor > Styles. Click the Styles panel (the half-moon icon) and you’ll see options for colors, typography, spacing, and layout. The controls are more visual than the old Customizer dropdowns.

Additional CSS

This one is buried. Go to Appearance > Editor > Styles, click the Edit Styles pencil icon, then click the three-dot menu in the top right corner, and select Additional CSS. It works exactly the same as before – paste your CSS snippet and it applies site-wide. WordPress just hid it behind 3 extra clicks.

Widgets

Widgets don’t have their own page anymore. In block themes, sidebars and widget areas are replaced by template parts that you edit with blocks directly in the Site Editor. If your block theme has a sidebar, you’d edit it by going to Appearance > Editor > Template Parts and modifying the sidebar template.

How Do I Access the WordPress Customizer in 2026?

Here’s the shortcut that solves this immediately. Just type this URL directly into your browser:

yoursite.com/wp-admin/customize.php

Replace yoursite.com with your actual domain. This forces the Customizer open even on block themes. WordPress doesn’t delete the Customizer when you switch to a block theme – it just hides the menu link. The direct URL still works.

I bookmarked this URL on 2 of my test sites. It’s faster than digging through the Site Editor when I just need to paste a quick CSS snippet.

One thing to know: when you open the Customizer on a block theme, some sections might be empty or limited. That’s because block themes handle those settings through the Site Editor instead. But the Additional CSS section still works perfectly through this URL, which is the main reason most people need the Customizer in the first place.

Which Themes Still Use the Customizer?

Not all themes are block themes. In fact, most of the popular third-party themes still use the Customizer as their main settings hub.

If you switched from Kadence or Astra to a default block theme, that’s almost certainly why the Customizer disappeared. And if you prefer the Customizer workflow, sticking with a hybrid theme like Kadence is a perfectly valid choice. Kadence gives you a full header builder, footer customization, and sticky header options – all through the Customizer.

If you’re using the Customizer and your changes aren’t sticking, that’s a separate issue – I wrote a fix for Kadence Customizer not saving changes that covers the most common causes.

There’s also a bonus side effect worth knowing about. Certain plugins – like WooCommerce – force the Customizer menu link to reappear even on block themes. So if you install WooCommerce and suddenly see “Customize” under Appearance again, that’s why.

Should You Learn the Site Editor or Stick with the Customizer?

This depends entirely on your situation. Here’s how I think about it.

Stick with the Customizer if:

• You’re already using a hybrid theme like Kadence, Astra, or GeneratePress
• Your site is set up and working the way you want
• You don’t want to relearn how to manage menus, colors, and layouts

Learn the Site Editor if:

• You’re starting a brand new site and want to use a modern block theme
• You like the idea of editing every part of your site with blocks
• You want to design custom page templates without code or page builders (just be careful not to accidentally edit a global template and break your site)

The Customizer isn’t going away anytime soon. Millions of active sites depend on it, and WordPress has committed to keeping it functional. But new features and improvements are going into the Site Editor, not the Customizer. So if you’re building something from scratch, the Site Editor is where things are headed.

And honestly? The Site Editor in 2026 is much better than it was when it first launched. The early versions were rough – slow, buggy, and confusing. But WordPress has put 4+ years of work into it now, and it’s genuinely usable. I still prefer Kadence’s Customizer for header and footer building, but the Site Editor’s Styles panel for colors and fonts is actually quite nice.

Frequently Asked Questions

Where is Additional CSS in block themes?

Go to Appearance > Editor > Styles, click the Edit Styles pencil icon, then click the three-dot menu in the top right and select “Additional CSS.” It works the same as the old Customizer version – you just have to click through 3 more screens to get there. Or skip all of that and go directly to yoursite.com/wp-admin/customize.php – the Additional CSS section still works through the direct URL.

Is the WordPress Customizer deprecated?

Not officially. WordPress still supports the Customizer and it works on every theme that uses it. Block themes hide the menu link, but the Customizer itself is fully functional. WordPress hasn’t announced any plans to remove it – with 5+ million sites using the Classic Editor plugin alone, removing the Customizer would break too many sites.

Can I use both the Customizer and the Site Editor?

It depends on your theme. Hybrid themes like Kadence primarily use the Customizer, so you’d use that for most settings. Block themes use the Site Editor. You can force-open the Customizer on a block theme using the direct URL (/wp-admin/customize.php), but most settings will be handled through the Site Editor. There’s no conflict between them – they just manage different things.

Do I need a plugin to bring back the Customizer?

No. If you’re on a hybrid theme, the Customizer is already there. If you’re on a block theme, use the direct URL trick (/wp-admin/customize.php) to access it. There are plugins that add the Customizer menu link back, but they’re unnecessary. The direct URL does the same thing without adding another plugin to your site.

Why is the Customize option missing in WordPress?

I noticed this happens whenever I activate a new Block Theme like Twenty Twenty-Four. WordPress hides it because they want me using the new Site Editor instead.

How do I enable the Customizer in a block theme?

I usually just type /wp-admin/customize.php at the end of my URL to force it open. Alternatively, installing a plugin like Yoast SEO often brings the menu link back.

Where is the Theme Customizer in WordPress 6.x?

If I’m using a classic theme, it’s right under Appearance > Customize. If it’s gone, I know I’m probably dealing with a Full Site Editing theme.

How to fix WordPress Customizer not showing?

When I know I’m on a classic theme and it’s still missing, I check my plugins. A security plugin is usually blocking my access, or I’m not logged in as an admin.

Wrapping Up

The WordPress Customizer isn’t gone – it’s just hidden when you use a block theme. WordPress replaced it with the Site Editor, which handles menus, colors, fonts, and templates in a completely different way.

Here’s the quick version:

1. Using Kadence, Astra, or GeneratePress? The Customizer is still under Appearance > Customize. Nothing changed for you.
2. Using a block theme? Your settings moved to Appearance > Editor. Check the Styles panel for colors and fonts, Navigation for menus.
3. Just need the Customizer right now? Go to yoursite.com/wp-admin/customize.php directly. It still works.

Don’t panic if you can’t find it. And don’t install a plugin to bring it back. Either learn where things moved in the Site Editor, or switch to a hybrid theme that still uses the Customizer the way you’re used to. Both are perfectly fine options.

Take a breath. Your posts are almost certainly still there.

I’ve watched this happen to 4 different bloggers in the last year, and not once was anything actually missing. The posts were sitting in Posts > All Posts, right where they always were. The problem was a setting that told WordPress to stop displaying them publicly. In the most common case, this is a 2-click fix.

Here’s the checklist I walk through when WordPress blog posts are not showing up on the front end.

Why aren’t my WordPress blog posts showing up?

The short answer: WordPress stopped knowing where to put them.

When you install WordPress, your homepage shows your latest posts automatically. But the moment you set a static homepage, WordPress assumes you’ll tell it where the blog should go. Forget that second step and your posts vanish from the front end – even though they’re still in the database.

Log into your dashboard and click Posts > All Posts. If your articles are listed there with “Published” next to them, nothing is lost. You just need to show WordPress where to display them again.

Here are the 5 things I check when posts disappear, in the order I check them:

1. A static homepage is set, but no posts page is assigned in Settings > Reading
2. Posts are saved as Draft or Private instead of Published
3. The permalinks structure broke and the blog page returns a 404
4. The blog page exists but isn’t linked in the menu anywhere
5. A block theme (like Twenty Twenty-Four) is using a template that doesn’t pull posts

The first one fixes about 70% of the cases I’ve seen. So let’s start there.

How do I set a specific page to show my blog posts?

This is the fix that catches most people. It takes 3 clicks.

Go to Settings > Reading. You’ll see “Your homepage displays” at the top with 2 radio buttons: “Your latest posts” and “A static page.”

If you picked “A static page” at some point (or your theme’s starter template picked it for you), you’ll see 2 dropdowns underneath: Homepage and Posts page. The Homepage dropdown is probably set to your welcome page. The Posts page dropdown is probably set to “- Select -” and that’s the problem.

Here’s what to do:

1. Create a blank page called “Blog” (or “News” or “Articles”) under Pages > Add New. Don’t add any content. Just publish the empty page.
2. Go back to Settings > Reading.
3. In the Posts page dropdown, select the “Blog” page you just created.
4. Click Save Changes at the bottom.

That’s it. Visit yoursite.com/blog and your posts will be back.

One warning: don’t add content to that page. WordPress ignores anything you put inside the page you assigned as your Posts page and overrides it with the post archive automatically.

I’ve seen people spend an hour typing their blog intro in there and wondering why it never shows up. Leave it empty.

What if my posts are saved as drafts instead of published?

This one catches me embarrassingly often. I write a post, hit Preview to check it, close the tab, and forget to actually click Publish.

Go to Posts > All Posts. Above the posts list, you’ll see tabs: All | Mine | Published | Scheduled | Draft | Trash. Click Draft and see what’s waiting there.

If you see posts in Draft, they’re not public yet. Hover over the title, click Quick Edit, change the Status dropdown from “Draft” to “Published,” and click Update. Or open the post in the editor and click the big blue Publish button in the top right.

Also check the Scheduled tab. A scheduled post has a future publish date, which means WordPress is holding it back until that date arrives. If you set the date wrong (say, 2027 instead of 2026), the post won’t show up for a very long time. Change the date and click Update.

One more sneaky one: the Private status. If a post is set to Private, only logged-in admins can see it. When I’m logged in, the post looks fine to me, but readers get nothing.

To check, click into the post and look at the Visibility setting in the right sidebar. It should say “Public,” not “Private.” Once your posts are back on the page, you might notice the layout feels cramped – my guide on changing the blog post container width covers how to give them room to breathe.

How do I check if permalinks broke my blog page?

Sometimes your Blog page loads but clicking any post shows a 404. Or the /blog/ URL returns 404 even though the page exists. This is almost always a permalinks issue.

Permalinks are the URL structure WordPress uses for your posts (like yoursite.com/my-post-title/). The rules that make these URLs work live in a file called .htaccess. When that file gets out of sync after a migration or a security plugin edit, WordPress forgets how to find your posts.

The fix is weirdly simple. Go to Settings > Permalinks. Don’t change anything. Just click Save Changes at the bottom.

That single click tells WordPress to rewrite the .htaccess rules from scratch. Your posts and pages should reappear. If you want the full walkthrough on this, I wrote a dedicated guide on fixing WordPress 404 errors on every page that goes deeper into what’s happening under the hood.

If you’re on an Nginx host (common with managed WordPress hosting like WP Engine or Kinsta), the .htaccess trick won’t help – Nginx uses its own rewrite rules. In that case, open a support ticket with your host and ask them to “flush the rewrite rules.” They know what that means. While you’re rebuilding the blog page, you might also want the featured images to stretch full width so posts feel more polished.

What if the blog page isn’t linked in my menu?

Here’s a silly cause that’s easy to miss. Your posts are published and your settings are correct, but there’s no way for visitors to find the blog page from your homepage.

Go to Appearance > Menus (or Appearance > Editor > Navigation on a block theme). Look at your primary menu. If “Blog” isn’t listed, add it. My guide on how to add items to your WordPress menu covers both the classic and block editor paths.

While you’re there, check your homepage content too. Most starter themes include a Latest Posts block that pulls in your articles automatically. If your homepage was built from scratch or switched to a page builder, that block might be gone. Drop one in so visitors see fresh content without hunting.

What if I’m using a block theme with templates?

Block themes (any theme that uses the Site Editor at Appearance > Editor) handle posts differently from classic themes. Themes like Twenty Twenty-Four, Twenty Twenty-Five, and Ollie fall into this category.

With a block theme, the layout for your blog page comes from a template called “Blog” or “Home” inside the Site Editor. If you (or a theme update) replaced that template with a custom layout that doesn’t include a Query Loop block, your posts won’t render.

Go to Appearance > Editor > Templates and find the template called “Blog,” “Home,” or “Index.” Click to edit it. Look for a block called Query Loop – this is the block that actually fetches and displays your posts. If it’s missing, you can add it back.

Click the + button, search for “Query Loop,” and insert it into the template. Pick a layout pattern when prompted (I usually go with the simple list view). Save the template. Your posts should appear.

If you accidentally broke the template and can’t figure out what changed, you can usually reset it. In the Site Editor, click the 3-dot menu next to the template name and look for “Clear customizations” or “Reset to default.” This rolls the template back to whatever the theme shipped with. I have a separate guide on fixing global template changes that ruined your site if this happened across more than one template. And if you miss the old writing experience entirely, my comparison of Classic Editor vs Gutenberg in 2026 walks through when to switch back.

Should I restore from a backup?

Only as a last resort. Before restoring anything, confirm your posts are actually missing from the database – not just missing from public view.

Go to Posts > All Posts and check the count at the top. If you see “25 items” and your titles are listed, the posts exist. Restoring a backup would be overkill and you’d lose any changes made since that backup ran.

Restoring only makes sense if Posts > All Posts shows an empty list or a much lower count than expected. That points to something (a bad migration, database corruption, or an actual hack) removing data from the wp_posts table. In that case, restore the database only from your backup plugin. If you don’t have a backup yet, that’s the first thing to fix – my guide on backing up your WordPress site before changes takes 5 minutes.

Frequently Asked Questions

Why are my WordPress blog posts not showing up?

In my experience, this usually happens because of a mix-up in your reading settings or a permalink issue. Sometimes, WordPress gets confused about which page is supposed to display your content.

How do I set a specific page as my blog page?

I always head straight to Settings > Reading in my WordPress dashboard. From there, I change the “Posts page” dropdown to my dedicated blog page and hit save. It takes about 15 seconds to fix.

Why did my published posts disappear from my site?

If they vanished suddenly, I’d bet your site’s permalink structure got corrupted after a plugin update. Going to Settings > Permalinks and clicking “Save Changes” usually brings all 50 of your missing posts right back.

How do I check if permalinks broke my blog page?

I like to test this by trying to view a single post directly from the dashboard. If the post loads but the main blog page gives a 404 error, I know the permalinks need to be flushed.

You didn’t lose your posts

Here’s what I want you to take away from this. When blog posts vanish in WordPress, it’s almost always a configuration issue, not a data loss issue. Your words are still there. You just need to tell WordPress where to put them.

Start with Settings > Reading. If that doesn’t solve it, check draft status, permalinks, your menu, and your block theme templates in that order. One of those 5 checks will bring your posts back.

And once they’re back, install a backup plugin so you never have to second-guess yourself next time. A 5-minute setup now saves you an hour of panic later.

You refresh. Still there. You try /wp-admin. Same message.

Your site is locked out – visitors can’t read it, and you can’t fix it from the dashboard.

This one is driving everyone crazy, and it shows up in the WordPress support forums almost every day. Here’s the good news. It’s usually a 10-second fix, and you don’t need a developer.

I’ve walked through this exact problem 3 times on my own sites. Let me show you what to do.

What does “Briefly Unavailable for Scheduled Maintenance” actually mean?

When WordPress updates a plugin, theme, or the core software, it drops a tiny file called .maintenance in your site’s main folder. That file is a flag. It tells WordPress “don’t let anyone in right now, I’m in the middle of changing files.”

The message visitors see is pulled straight from WordPress core. It’s meant to last 10-60 seconds while the update finishes. Then WordPress is supposed to delete the .maintenance file automatically and let traffic back in.

The problem is when the update crashes, times out, or gets interrupted. WordPress never reaches the “delete the file” step. The flag stays up forever. Your site keeps showing the message even though the update finished (or failed) hours ago.

That’s why you’re stuck. The fix is just to delete that one file manually.

How do I fix WordPress stuck in maintenance mode?

You have 3 ways to reach that file and delete it. Pick whichever matches what you already have access to.

If your host gave you a control panel login, use Option 1 – it’s the fastest. If you set up an FTP client ages ago, use Option 2. If you have no technical access at all, skip to Option 3. Stuck updates often leave other settings in a weird half-saved state too – I’ve seen this overlap with Customizer not saving changes on Kadence sites.

Option 1: Using your host’s File Manager (non-technical)

Most WordPress hosts (Bluehost, SiteGround, Hostinger, HostGator, and many others) give you a browser-based File Manager inside a control panel like cPanel, Plesk, or their own dashboard. No software to install.

Log in to your hosting account and look for File Manager on the dashboard. If you can’t find it, search your host’s help docs for “file manager” – they’ll show you the exact path.

Once File Manager opens, navigate to your site’s root folder. This is usually called public_html. If you host multiple sites on the same account, your WordPress site might be in public_html/yoursite.com/ instead. The right folder is the one containing wp-config.php, wp-admin, and wp-content.

Here’s the part that trips people up. Files starting with a dot (like .maintenance) are hidden by default.

In File Manager, open the Settings or View menu and check the box for Show Hidden Files (dotfiles). Save. The .maintenance file should now appear alongside your other site files.

Right-click the .maintenance file and choose Delete. Confirm. That’s it.

Go back to your site and refresh. It should load normally. If it doesn’t, try opening it in an incognito/private window to rule out browser caching.

Option 2: Using an FTP client

If you already use an FTP client to manage your site, the steps are similar. Any SFTP/FTP tool works – pick whatever you’re comfortable with.

Connect to your site using the FTP credentials your host provided. These are usually in the welcome email you got when you signed up, or available in your hosting dashboard under “FTP Accounts.”

Once connected, open the folder that contains wp-config.php. Again, this is your WordPress root – probably public_html or something named after your domain.

Turn on hidden files in your FTP client’s view settings. Most clients call this option “Show hidden files” or “Force showing hidden files” and bury it under a View, Server, or Preferences menu. Without this, you’ll scroll through the folder and swear the .maintenance file isn’t there. It is. You just can’t see it yet.

Once hidden files are showing, find .maintenance in the file list. Right-click it and choose Delete. Confirm when prompted.

Refresh your site. It should be back online.

Option 3: Ask your host (last resort)

If you genuinely don’t have any file access – no cPanel, no FTP, nothing – contact your hosting support. Tell them exactly this: “My WordPress site is stuck showing ‘Briefly unavailable for scheduled maintenance.’ Can you delete the .maintenance file in my site’s root folder?”

Any half-decent WordPress host will recognize the problem immediately and fix it in under 5 minutes. It’s one of the most common tickets they get.

Managed WordPress hosts like Kinsta, WP Engine, and Flywheel often have this in their help docs with a one-click button. Check their knowledge base before opening a ticket – you might fix it yourself in 30 seconds.

Why did this happen in the first place?

The .maintenance file gets stuck for 4 main reasons. None of them are your fault, but knowing the cause helps you dodge a repeat.

Your browser closed or crashed mid-update. If you closed the tab, your laptop went to sleep, or your internet dropped while WordPress was updating a plugin, the update process never finished. The file stays.

The update hit a PHP timeout. Most shared hosts limit PHP scripts to 30 or 60 seconds. If a plugin update takes longer than that (especially for big plugins like WooCommerce or Elementor), the server kills the process before WordPress can clean up. Suddenly you’re locked out over a 2-second timeout.

A plugin or theme had a fatal error during install. If the new version contains a bug or conflicts with another plugin, the update crashes. WordPress can’t recover gracefully, so the flag stays up.

Your server ran out of memory. Budget hosts sometimes cap PHP memory at 64MB or 128MB. Large updates need more. When memory runs out, everything stops where it is – including the cleanup step.

The common thread: something interrupted WordPress while it was still mid-update. The fix is always the same (delete the file), but the causes are worth knowing. Stuck updates can also cause weirder side effects – some people notice posts missing after the site comes back, which I cover in why blog posts disappear.

How do I prevent my WordPress site from getting stuck in maintenance mode?

6 small habits take care of most of these triggers. I follow all of them now, and I haven’t hit this error in years.

Update one plugin at a time. When WordPress shows you 12 plugin updates, it’s tempting to click “Update All.” Don’t. Update them one by one. If plugin #7 crashes, you’ll know exactly which one caused the problem instead of guessing across all 12.

Don’t close the tab during updates. It sounds obvious, but this catches people constantly. Even if the update bar looks frozen, give it 60-90 seconds before you do anything. Walk away, come back, refresh once.

Back up before you update. I wrote a full guide on backing up your WordPress site – it takes 5 minutes with a free plugin and saves hours of panic. Always back up before major plugin or core updates.

Update during low-traffic hours. If you’re going to update anything big, do it when your site is quiet. Less traffic means more server resources available to WordPress, and less chance of a timeout.

Ask your host to raise PHP memory and timeout limits. Most hosts bump these on request for free. Ask for 256MB memory and a 300-second max execution time. That kills the most common cause of stuck updates.

Keep up with updates generally. Letting 30 updates pile up is asking for trouble. The bigger the update queue, the higher the chance something in there conflicts. I wrote more about updating plugins without breaking your site – follow that routine and you’ll avoid most of these rescue scenarios. And if an update ever nukes your layouts, my guide on fixing global template changes walks through the recovery path.

After you fix the .maintenance issue, also clear your browser cache. Some browsers stubbornly remember the maintenance message and keep showing it to you even after the site is fine. Hard refresh with Ctrl+F5 (or Cmd+Shift+R on Mac), or open an incognito window to confirm.

If the update that caused the problem also left your site slower than before, that’s a separate issue. I cover troubleshooting steps in why is my WordPress site so slow. And if pages start throwing 404s after you fix the maintenance mode, a quick permalink refresh usually clears that up too.

Frequently Asked Questions

How do I fix WordPress stuck in maintenance mode?

The fastest way I fix this is by deleting the .maintenance file from the site’s root folder. I just log in using my host’s File Manager or an FTP client and delete it. Once it’s gone, my site comes back online in seconds.

Why is my WordPress site stuck in maintenance mode?

This happens to me when an update gets interrupted halfway through. It usually triggers if I close my browser tab too early or try to update 10 plugins at the exact same time.

How long does WordPress maintenance mode last?

By default, WordPress only keeps this mode active for about 10 minutes. But if that .maintenance file gets stuck on your server during a failed update, your site won’t come back until you manually delete it.

Can I still access my WordPress dashboard if it’s stuck?

No, you won’t be able to log in normally. Both your live site and your /wp-admin/ login screen will show the same error message. You’ll have to use your hosting control panel to bypass the dashboard and fix the files directly.

What happens if I delete the .maintenance file?

Deleting it just tells WordPress to stop showing the error screen and go back to normal. It doesn’t break anything, but I always double-check my plugins afterward to see if the update actually finished.

That’s it

The “briefly unavailable for scheduled maintenance” error looks terrifying because your whole site is offline. But it’s one of the gentler WordPress problems – no data loss, no complicated fix, no developer required.

Delete the .maintenance file, clear your browser cache, and your site is back. Then figure out which plugin caused the timeout so you can update it more carefully next time (or report the bug to the plugin author).

And please, please back up your site before the next big update. Future you will say thank you.

The fix takes 30 seconds and doesn’t require any code. Go to Settings > Permalinks and click Save Changes. That’s it. Most of the time, that one click brings every page back.

Here’s why it works, what to do when it doesn’t, and how to stop a WordPress 404 error on all pages from wrecking your afternoon again.

Why is my WordPress site showing 404 on every page?

When your homepage works but clicking any link throws a 404, WordPress is getting confused about how to translate pretty URLs into actual posts.

Behind the scenes, WordPress keeps a tiny instruction sheet called rewrite rules. These rules tell your server that yoursite.com/about-me/ really means “load the About Me page.” When that instruction sheet goes stale or gets overwritten, every URL except the homepage stops working.

This happens after 4 common events: migrating your site to a new host, changing your permalink structure, a plugin modifying your .htaccess file, or a failed WordPress update. The posts and pages themselves are safe in the database. WordPress just forgot how to find them.

That’s why the fix is so quick. You’re not repairing anything – you’re handing WordPress a fresh copy of the instruction sheet.

How do I fix 404 errors in 30 seconds?

This is the fix that solves the wordpress 404 error all pages problem about 80% of the time. It’s built right into the dashboard.

Step 1: Log in to your WordPress dashboard

Go to yoursite.com/wp-admin and log in. Your admin area should still work even when the frontend is throwing 404s. If you can’t reach the admin either, skip down to the .htaccess section below.

Step 2: Open the Permalinks settings

In the left sidebar, click Settings > Permalinks. You’ll see a page with radio buttons for different URL structures (Plain, Day and name, Post name, and so on).

Step 3: Click Save Changes

Don’t change anything. Just scroll to the bottom and click the blue Save Changes button.

That click is the whole fix. WordPress regenerates its rewrite rules and updates your .htaccess file with fresh instructions. Open your site in a new tab and click around – every page should load now.

What did that actually do?

Saving the Permalinks page triggers something called “flushing the rewrite rules.” Don’t let the word flushing scare you – nothing gets deleted.

Flushing means WordPress rebuilds its URL map from scratch. It looks at your current permalink setting, figures out the correct pattern for each post and page, and writes those rules into your .htaccess file. The old stale rules get replaced with working ones.

Think of it like printing a new map after the road signs changed. Your destination hasn’t moved, but you needed updated directions to find it.

What if the permalinks fix didn’t work?

If Save Changes didn’t bring your pages back, something’s preventing WordPress from writing to your .htaccess file. You’ve got 3 follow-up checks.

Check 1: Fix the .htaccess file manually

Your .htaccess file sits in the root folder of your WordPress install. It’s a tiny text file that tells your server how to handle URL requests. When it gets corrupted or goes missing, no amount of Permalinks saving will help.

You’ll need to access it through your host’s File Manager or an FTP client. Open the File Manager in your hosting control panel (cPanel, Plesk, or your host’s custom dashboard), navigate to your site’s root folder (usually public_html or www), and look for a file called .htaccess. If you don’t see it, enable “Show hidden files” in the File Manager settings.

Before touching anything, back up your site or at least download a copy of the current .htaccess. Then replace the contents with this default WordPress code:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Save the file, then load your site. If the 404s are gone, the old .htaccess was the culprit.

Check 2: Deactivate plugins in bulk

Some security plugins and caching plugins rewrite .htaccess rules that conflict with WordPress. iThemes Security, WP Rocket, and W3 Total Cache are 3 common offenders when configured aggressively.

Go to Plugins > Installed Plugins, check the box at the top to select every plugin, pick Deactivate from the bulk actions dropdown, and click Apply. Then reload your site. If the 404s disappear, reactivate plugins one at a time until you find the conflict.

When you identify the culprit, check its settings for options labeled “Hide login URL,” “Custom permalinks,” or “Block XML-RPC.” One of those is usually the switch causing the conflict.

Check 3: Switch to a default theme temporarily

Rarely, a custom theme with broken page templates can cause site-wide 404s. Go to Appearance > Themes and activate Twenty Twenty-Four (or any default WordPress theme).

If your site suddenly works, the problem lives inside your current theme. Contact the theme developer or switch to a different theme. I wrote about a related issue in fixing global template changes ruining your site if your theme edits started breaking things recently.

Why is my WordPress site showing a 404 error on just one page?

If only one or two pages throw 404s while the rest of your site works fine, this is a different problem. The rewrite rules are healthy – something specific happened to those individual pages.

The post was deleted or moved to Trash. Go to Posts > All Posts and click the Trash tab. If your missing page is there, hit Restore. This is the most common reason a single URL stops working. I covered the broader case of WordPress blog posts disappearing separately.

The slug got changed. Every post has a URL ending called a slug. If you edited a post title and WordPress auto-updated the slug, or if you manually changed the slug, the old URL now points to nothing. Edit the post, click the URL in the right sidebar, and set the slug back to the original.

The post status changed to Draft. Published posts are public. Draft posts return a 404 to visitors (you can still see them while logged in). Check the post editor and make sure the status shows Published, not Draft or Pending Review.

The category or tag archive is empty. If you deleted all posts in a category, the /category/whatever/ URL will 404. Add a post to that category or delete the empty category.

What about redirecting the old URL?

If a page’s slug legitimately needed to change (like fixing a typo), don’t leave the old URL broken. Set up a redirect so anyone with the old link lands on the new page.

The free Redirection plugin handles this in 30 seconds. Install it, go to Tools > Redirection, enter the old URL in the Source field and the new URL in the Target field, and click Add Redirect. Visitors (and search engines) following the old link will bounce to the new one automatically. If you’re already using an SEO plugin like Rank Math or Yoast, they include redirect managers too – no need to stack a third plugin.

How do I stop 404 errors from happening again?

Most site-wide 404 outages come down to 3 habits that prevent them entirely.

Always save Permalinks after migrating. Moving your site to a new host or changing your domain? The first thing to do after the move is log in and hit Settings > Permalinks > Save Changes. Do it before you test anything else. It takes 5 seconds and avoids a panic.

Back up before changing permalink structure. Switching from Plain (?p=123) to Post name URLs is a good upgrade, but test it on a fresh backup first. If something misfires, you can restore in 2 minutes instead of debugging for 2 hours.

Keep plugins updated. Outdated security and caching plugins sometimes write bad .htaccess rules. Updates from the plugin authors usually fix these bugs fast. I wrote a guide on updating plugins without breaking your site that covers this safely.

Avoid editing .htaccess directly unless you have to. If you must edit it, keep a backup copy. One stray character in that file can knock your whole site offline, and 404s are usually the first symptom. Badly configured caching plugins can also be behind why your site is running slow as well as 404s – two problems with one cause.

Quick checklist

Here’s the fix-it order I run through when a client calls me with a wordpress 404 error all pages issue:

1. Log in to WordPress, go to Settings > Permalinks, click Save Changes (fixes 80% of cases)
2. If that fails, reset .htaccess to the default WordPress code
3. Deactivate all plugins and reactivate one at a time to find conflicts
4. Switch to a default theme to rule out theme problems
5. For single-page 404s, check the Trash, check the slug, and check the post status

Most of the time, step 1 is the only step you’ll need. The rest are backup plans. While you’re tidying up, it’s also worth checking that none of your menu items got accidentally nested – see preventing accidental dropdown menus for that fix.

Frequently Asked Questions

Why are all my WordPress pages showing 404 except the home page?

I’ve found this almost always happens when your .htaccess file is missing or corrupted. Since the home page is a physical file, it loads fine, but all your other 50+ pages need that file to tell the server where to look.

How do I fix a 404 error on all pages?

My favorite 10-second fix is to flush the permalinks. I just go to Settings > Permalinks in my dashboard and click “Save Changes” without touching anything else. That forces WordPress to rewrite its routing rules and usually fixes the problem instantly.

What if saving permalinks doesn’t work?

If that doesn’t do the trick, I usually check for plugin conflicts next. I’ll temporarily disable my caching or security plugins, as they sometimes write bad rules to the server. If your site starts working after that, you’ve found the culprit.

Can a plugin cause a sitewide 404 error?

Absolutely. I’ve seen security plugins and caching tools break a site’s routing rules by adding conflicting code to the .htaccess file. Turning off those 2 types of plugins is the quickest way to test if they’re causing the headache.

That’s the full playbook. Next time your WordPress site throws 404s on every page, start with Settings > Permalinks > Save Changes. Nine times out of ten, you’re back online before your coffee gets cold.

But there’s a catch that trips up almost every beginner. The sticky header works fine out of the box, except it doesn’t automatically set a background color for the “stuck” state. If you’re using a transparent header (or even if you’re not), this one missing setting can make your menu text unreadable. I’ll walk through the full setup plus that fix in about 2 minutes.

Here’s the difference it makes – same page, same scroll position. On the left, no sticky header (the navigation is long gone). On the right, sticky enabled – the menu stays pinned and is still one click away:

How Do I Enable the Sticky Header in Kadence?

The setting lives inside the Customizer, right next to your other header options.

1. Go to Appearance > Customize > Header > Sticky Header
2. Find the dropdown labeled “Enable Sticky Header?”
3. Select “Yes – Only Main Row”
4. Click Publish to save

That’s the option most sites should pick. It sticks just your logo and main navigation to the top of the screen. Your top bar (if you have one with a phone number or social icons) scrolls away normally.

The other options in the dropdown let you stick the Top Row, the Bottom Row, or the Whole Header. I’d avoid “Whole Header” unless your top bar is very short. Sticking the entire header eats up more screen space, and on smaller laptops that becomes noticeable fast.

Should I Enable the Shrink Effect?

Right below the sticky dropdown, you’ll find an option called “Enable Main Row Shrinking”. When you turn this on, the main row gets smaller once it becomes sticky – the logo shrinks and the padding tightens up.

I’d recommend enabling it. Here’s why:

• It saves vertical screen space. A full-height header hovering over your content feels heavy. The shrunk version is more subtle.
• The transition is smooth. It doesn’t jump or flash – it just quietly reduces in size as you start scrolling.
• It gives visitors a visual signal that the header has switched to its “sticky” state, which feels more intentional than a header that just stays exactly the same.

You can see the difference here. Left is the full-height header at the top of the page (with top bar, logo, and menu). Right is the shrunk sticky state after scrolling – just the main row, tightened up:

The shrink amount isn’t something you can customize in the free version – Kadence handles it automatically. But in my testing, the default shrink ratio looks good on most sites without any tweaking.

What About “Enable Reveal Sticky on Scroll Up”?

This is one of those settings that sounds like jargon until you see it in action. Turn it on and the sticky header only appears when the visitor scrolls back up. As they scroll down (reading your content), the header slides away. Scroll up even slightly, and it slides back in.

I like this option on long-form article pages where you want readers focused on the content, but still want navigation a single scroll-up away. It feels like the header “knows” when they need it.

On ecommerce or landing pages, I’d skip it – you usually want the CTA in the header always visible, not hidden while scrolling down.

Set a Background Color (The Step Most Tutorials Skip)

This is the fix that separates a polished sticky header from a broken-looking one. And almost no tutorial mentions it.

Here’s the problem. When your header becomes sticky, it keeps whatever background it had in its normal state. If your header already has a solid white or dark background, you’re probably fine. But if you’re using a transparent header – where the header overlays your hero image – the sticky state inherits that transparency. Now you’ve got transparent menu text floating over your body content. Unreadable.

Even if you’re not using a transparent header, I’d still set an explicit background color for the sticky state. It prevents odd rendering on some browsers and gives you full control.

Here’s how:

1. In the same Sticky Header panel, click the Design tab at the top
2. Find Sticky Header Background and click the color swatch
3. Pick a solid color – white for light sites, dark gray or black for dark designs, or a brand color if you want the sticky state to feel distinct

That’s the entire fix. Takes about 10 seconds, and it saves you from a header that looks fine at the top of the page but turns into a mess the moment someone scrolls. While you’re in the Customizer, it’s worth checking my other quick wins like adding a back to top button and disabling breadcrumbs on specific pages – all similar 2-minute tweaks.

Should I Use a Sticky Header on Mobile?

Kadence has a separate Mobile Sticky section below the main settings, with its own dropdown. And here you get more than a simple on/off toggle – there are 6 choices:

• No – sticky header disabled on phones
• Yes – Only Main Row – sticks just the main navigation row
• Yes – Top Row & Main Row – sticks both top and main
• Yes – Whole Header – pins every row
• Yes – Only Top Row – sticks just the top bar
• Yes – Only Bottom Row – sticks just the bottom row

On a phone screen, a sticky header takes up roughly 15-20% of the visible area. That’s a lot of screen space lost when your visitor is trying to read an article or browse your products.

My recommendation: set Mobile Sticky to “No” on most sites. Most mobile users are used to scrolling back to the top (or using the browser’s built-in navigation), so a sticky header isn’t as critical as it feels.

The exception is if your main nav holds a critical CTA – like a “Book Now” button on a service business site. In that case, pick Yes – Only Main Row and nothing more. Never use “Whole Header” on mobile unless you enjoy watching half the screen disappear.

Why Isn’t My Sticky Header Working?

If you’ve turned on the sticky header but it doesn’t seem to do anything, check these 3 things before you start troubleshooting CSS or reinstalling Kadence.

1. Your caching plugin is serving a stale page.

This is the most common cause, and it catches people every time. Plugins like LiteSpeed Cache, WP Rocket, and W3 Total Cache store a cached version of your pages. When you enable the sticky header, the Customizer saves the setting – but your visitors (and you, if you’re logged out) still see the old cached version where the sticky JavaScript hasn’t loaded yet.

Fix: Clear your cache. In LiteSpeed Cache, go to LiteSpeed Cache > Toolbox > Purge All. In WP Rocket, click the “Clear Cache” button in the admin bar. Then test your site in an incognito window.

2. You selected the wrong header row.

Kadence’s header has 3 rows: Top, Main, and Bottom. If your logo and menu live in the Main Row but you set the sticky option to “Only Top Row,” nothing visible sticks. Double-check that your sticky setting matches where your navigation actually lives.

3. Another plugin is overriding your header.

Some page builder plugins – especially Elementor with its Theme Builder feature – can replace Kadence’s header entirely with a custom-built one. If you’ve set up an Elementor header template, Kadence’s sticky setting won’t apply because Kadence’s header isn’t even on the page anymore. Check if you have any header/footer override templates active in your page builder.

Free vs Pro: What’s Actually Different?

Here’s the honest breakdown. The free version of Kadence covers sticky headers really well. Most sites won’t need anything more.

Everything I’ve covered in this article – enabling the sticky header, picking which rows stick, enabling the shrink effect, Reveal on Scroll Up, setting the background color, and device-specific controls – all works in Kadence Free. No upgrade needed.

Kadence Pro adds a few advanced extras:

• A completely custom sticky header layout – build an entirely different header for the sticky state (like one with a “Buy Now” button that only appears after scrolling)
• Conditional display rules for Hooked Elements if you want to inject custom sticky content on specific pages only

But for a standard blog, portfolio, or small business site? The free sticky header does everything you need. I’ve been running it on 4 sites without any reason to upgrade just for this feature.

Quick Troubleshooting Reference

Frequently Asked Questions

Does a Kadence sticky header affect page speed or Core Web Vitals?

The sticky header itself adds minimal overhead – it’s just a CSS position: sticky rule with a small JavaScript handler for the shrink effect. But it can cause CLS (Cumulative Layout Shift) if the header height changes when it becomes sticky. Enabling the shrink effect and setting an explicit background color keeps things smooth.

Can I make only part of my header sticky in Kadence?

Yes. Kadence gives you 5 “Yes” options in the Enable Sticky Header dropdown – Only Main Row, Top Row & Main Row, Whole Header, Only Top Row, and Only Bottom Row. Most sites should stick only the Main Row – that’s where your logo and navigation live.

What does the “Reveal Sticky on Scroll Up” option do?

With this option on, the sticky header only appears when the visitor scrolls back up. It stays hidden while scrolling down, which keeps the reading experience clean, and reappears the moment they scroll up to look for navigation. Great for long-form articles, less useful for conversion-focused pages.

Does the Kadence sticky header work with Elementor?

Only if you’re using Kadence’s native header. If you’ve built a custom header with Elementor’s Theme Builder, Kadence’s sticky header setting won’t apply because Elementor replaces Kadence’s header entirely. You’d need to use Elementor’s own sticky option instead.

Can I set a different logo for the sticky state?

In the Sticky Header panel there’s a “Different Logo for Stuck Header?” option. Turn it on and you can upload a separate logo that only appears once the header is sticky. It’s useful for sites with long horizontal logos that don’t scale well when the header shrinks – you can swap to a compact version for the sticky state.

Wrapping Up

Setting up a Kadence sticky header takes about 2 minutes. Enable the main row sticky option, turn on Main Row Shrinking, and set a background color for the sticky state. That third step – the background color – is what separates a header that actually works from one that frustrates your visitors.

And the best part? Every feature I covered here is available in the free version of Kadence. You don’t need Kadence Pro for a fully functional sticky header.

If you’re in the Customizer tweaking your header, it’s a good time to clean up other visual details too. Changing the footer copyright text is another 2-minute job that makes your site look more polished. Small touches add up.

The good news: Kadence makes it easy to disable breadcrumbs, and you don’t need the Pro version to do it. I’ll walk you through 3 approaches – site-wide, per-page, and restyling the ones you keep.

Why Would I Want to Disable Kadence Breadcrumbs?

Breadcrumbs serve two purposes. First, they give visitors a clickable path back to parent pages. If someone is reading a post in your “WordPress Tips” category, they can click back to that category without hunting for it in your menu. Second, Google uses breadcrumbs to understand your site structure and sometimes displays them in search results instead of the raw URL.

But not every page benefits from breadcrumbs. A 5-page brochure site with Home, About, Services, Blog, and Contact doesn’t need them – the navigation is already obvious. And breadcrumbs on a landing page? They give visitors an exit ramp you didn’t intend.

Here’s when breadcrumbs typically get in the way:

• Homepage – showing “Home” by itself (or worse, “Home > Home”) adds nothing
• Landing pages and sales pages – you want visitors focused, not clicking away
• About and Contact pages – the path is self-explanatory
• Any standalone page where the breadcrumb trail is just one level deep

How Do I Disable Breadcrumbs on All Pages?

The fastest fix for most sites is the global Customizer toggle. This kills breadcrumbs on every page (or every post) at once.

1. Go to Appearance > Customize
2. Navigate to Posts/Pages Layout
3. Click Page Layout (for pages) or Post Layout (for blog posts)
4. Scroll down to the Title Elements list at the bottom of the panel
5. Click the eye icon next to Breadcrumb to toggle it off
6. Click Publish to save

Here’s the Page Layout panel with breadcrumbs enabled – you can see the breadcrumb trail “Home / About” on the frontend preview:

And here’s the same panel after toggling the Breadcrumb element off. The frontend updates immediately – no more breadcrumb above the page title:

Here’s what’s nice about this: pages and posts have separate controls. So you can disable breadcrumbs on all your pages (where they’re usually unnecessary) but keep them on blog posts (where they actually help readers navigate between categories). Or vice versa.

What About Blog Posts?

Blog posts use a separate layout panel. Go to Customize > Posts/Pages Layout > Post Layout and you’ll find the same Title Elements list with its own Breadcrumb toggle.

For most blogs, I’d leave breadcrumbs on for posts. A post like “Blueberry Buttermilk Pancakes” in the “Breakfast” category genuinely benefits from a trail like Home / Breakfast / Blueberry Buttermilk Pancakes. Readers can jump back to the category and browse related recipes.

While you’re in the Title Elements section, you might also want to remove the author meta from your blog posts – that’s the same panel.

How Do I Disable Breadcrumbs on Just One Page?

The global method is an all-or-nothing switch. If you want breadcrumbs gone from just your homepage or a single landing page, Kadence gives you a per-page override.

1. Open the page in the WordPress block editor
2. In the right sidebar, look for the Kadence tab (it sits alongside the Document and Block tabs)
3. Find the Title Elements or Page Layout section
4. Toggle the Breadcrumb element off
5. Update the page

This setting applies to just that one page. The per-page override always wins over the global Customizer setting – so you can leave breadcrumbs enabled site-wide and disable them only on your homepage and landing pages.

I’d recommend doing this for your homepage and any landing pages first. Those are the pages where breadcrumbs almost never make sense. While you’re cleaning things up, you might also want to remove the page title on certain pages – it’s another quick visual fix in the same panel.

How Do I Customize Breadcrumbs Without Removing Them?

Maybe you don’t want to remove breadcrumbs entirely – you just want them to look different. Kadence has a dedicated panel for styling.

1. Go to Appearance > Customize > General > Breadcrumbs
2. Adjust the separator character, home link, font, and colors
3. Click Publish

One option I always turn on: Use icon for home? – this swaps the word “Home” for a small house icon at the start of the trail. It looks cleaner and takes up less space, especially on mobile.

These settings apply everywhere breadcrumbs are enabled. So if you’ve disabled them on pages but kept them on posts, only your posts will show the updated style.

What Is the Breadcrumb Engine Setting?

At the top of the General > Breadcrumbs panel, there’s a dropdown called Breadcrumb Engine. This is one of the most useful settings in Kadence – and one of the least documented.

By default it’s set to Default, which uses Kadence’s own breadcrumb logic. But if you have Rank Math, Yoast SEO, or SEOPress installed, you can switch the engine to one of those plugins. Kadence will then display breadcrumbs using that plugin’s structured data and configuration – but still styled with Kadence’s theme settings.

Why does this matter? Two reasons:

• It prevents double breadcrumbs. If your SEO plugin outputs its own breadcrumb markup, switching Kadence to use that plugin’s engine unifies everything into a single trail instead of two stacked ones.
• It keeps breadcrumb SEO consistent with your site-wide SEO config. Rank Math and Yoast both have granular breadcrumb settings (like which categories to show, what the home label says). Picking the engine there means those settings flow through to your theme.

Watch Out for Double Breadcrumbs

This one catches people all the time. If you’re using an SEO plugin like Rank Math or Yoast SEO, it might inject its own breadcrumb markup into your pages. Combined with Kadence’s built-in breadcrumbs, you’ll end up with two breadcrumb trails stacked on top of each other.

You’ve got two fixes:

Fix 1 (recommended): Set the Breadcrumb Engine in Kadence to match your SEO plugin. That uses your plugin’s breadcrumb data but hides its duplicate output. One trail, styled by your theme.

Fix 2: Disable breadcrumbs in your SEO plugin entirely.

• Rank Math: Go to Rank Math > General Settings > Breadcrumbs and turn it off
• Yoast SEO: Go to Yoast > Search Appearance > Breadcrumbs and disable it

Pick one approach and stick with it. I’d go with Fix 1 – it gives you the SEO-plugin configuration with Kadence’s theme styling.

Should I Keep Breadcrumbs at All?

It depends on your site’s structure.

Keep breadcrumbs on:

• Blog posts with multiple categories – they help readers browse related content
• WooCommerce product pages – shoppers use them to navigate back to categories
• Archive and category pages – they show visitors where they are in the hierarchy
• Any site with more than 2 levels of nested pages

Remove breadcrumbs from:

• Simple sites with 5-10 pages and a clear menu
• Single-page or minimal sites
• Landing pages designed for conversions
• Pages where the breadcrumb trail is only one level deep (“Home > Contact” doesn’t tell anyone anything useful)

And about SEO – yes, breadcrumbs do help Google understand your site structure. Google can display them in search results as a clean path instead of showing your URL. But this only matters on pages with meaningful hierarchy. A breadcrumb showing just “Home” on your About page doesn’t give Google any useful information. Don’t keep breadcrumbs everywhere just for SEO reasons. Keep them where they actually help visitors navigate.

Quick Reference

Frequently Asked Questions

Does disabling Kadence breadcrumbs hurt my SEO?

Not in most cases. Breadcrumbs help Google understand deep site hierarchies, but pages like your homepage, About, and Contact have obvious structure already. I only keep breadcrumbs on blog posts and product pages where the category path actually adds value.

Can I disable breadcrumbs on specific categories only?

Not directly from the Customizer – it’s an all-or-nothing toggle for posts. But if you use Rank Math or Yoast SEO, switching the Breadcrumb Engine to that plugin gives you category-level breadcrumb controls. For the free Kadence version without an SEO plugin, the per-page toggle is your best option.

Why do I see two sets of breadcrumbs on my Kadence site?

That happens when both Kadence and an SEO plugin (Rank Math or Yoast) are outputting breadcrumbs at the same time. Either switch Kadence’s Breadcrumb Engine to match your plugin, or disable breadcrumbs in the plugin. Don’t let both render at once.

Will disabling breadcrumbs affect my WooCommerce product pages?

WooCommerce has its own breadcrumb system that’s separate from Kadence’s page breadcrumbs. Disabling Kadence breadcrumbs on pages won’t touch your shop or product page breadcrumbs unless you specifically disable them on those pages too.

Does the home icon toggle work on mobile?

Yes. The home icon replaces the “Home” text everywhere breadcrumbs appear – desktop, tablet, and mobile. It’s a small SVG icon, so it scales cleanly at any size and saves horizontal space on narrow mobile screens where long breadcrumb trails tend to wrap awkwardly.

The per-page approach is what I’d start with. Turn off breadcrumbs on your homepage and landing pages first, then decide if you want them globally or not. It’s one of those small tweaks that makes your site look more polished in under a minute.