It is easy to miss from the inside, because the checkout page itself usually works. In our study of 201 live WooCommerce stores, four stores had no working route from the cart to checkout. On all four, the checkout loaded normally when its address was typed into the browser. No shopper does that. They use the links the store gives them.
This guide goes through the symptoms, eight causes and their fixes, and how to keep watch on this step afterwards.
First, Pin Down the Symptom
| What the shopper sees | Most likely cause |
|---|---|
| Button leads to the homepage | No checkout page is assigned in WooCommerce (cause 1) |
| Button leads to a 404 or the wrong page | Old or hardcoded link, or permalinks (causes 2 and 3) |
| Checkout opens, then jumps back to the cart | Cart errors or a lost session (causes 4 and 5) |
| Click does nothing | JavaScript error, or something is covering the button (cause 6) |
| There is no button | Theme template, block cart layout or a cart error (causes 4 and 7) |
| A login, "coming soon" or maintenance page appears | A redirect rule or site visibility setting (cause 8) |
Test as a guest in a private window, on a phone as well as a desktop. Then test every route to checkout your store offers, not just the cart page button:
- the "View cart" link in the notice after adding a product;
- the cart icon in the header;
- the mini-cart or side cart, and its own Checkout button;
- any "Buy now" button on the product page.
Each of these is a separate link that can break on its own.
1. No Checkout Page Is Assigned
WooCommerce builds the Proceed to checkout link from a setting, not from the page's address. Go to WooCommerce → Settings → Advanced → Page setup and look at Checkout page.
If the field is empty, or points at a page that was deleted or moved to the trash, WooCommerce has nothing to link to and falls back to the homepage. That produces the strangest version of this problem: every checkout link on the store, including the mini-cart's, sends shoppers to the front page. One store in the study did exactly that.
It usually happens after a redesign or migration, when the checkout page was rebuilt and the old one deleted.
Check: WooCommerce → Status, in the section "WooCommerce pages". It lists the cart, checkout and account pages and flags any that are missing or lack the required block or shortcode.
Fix: select the right page in Page setup and save. If the page is gone, create a new one containing the Checkout block or the [woocommerce_checkout] shortcode, then assign it. WooCommerce → Status → Tools → Create default WooCommerce pages recreates missing pages for you.
2. A Hardcoded or Outdated Link
Not every checkout link comes from WooCommerce. Theme headers, menu items, side-cart plugins and page-builder buttons often hold an address someone typed in once. After a slug change (/checkout/ to /kassa/), a move from staging, or a switch to HTTPS, those links point at a page that no longer exists.
The usual signs are a 404, a link that opens the staging site, or a header icon that opens something other than the cart. One store in the study had a bag icon that opened a "page not found" quote list and no cart link anywhere else.
Check: hover over each cart and checkout link and read the address. Search the database for the old slug or staging domain.
Fix: replace typed-in addresses with the store's real cart and checkout pages. In menus, add the page itself instead of a custom link, so the address follows the page if it changes.
3. Permalinks and Translated Pages
A 404 on a checkout page that exists is usually a rewrite problem. Settings → Permalinks → Save changes (without changing anything) rebuilds the rules and fixes most cases after a migration or plugin change.
On multilingual stores, check each language. If the checkout page has no translation, or the translated page isn't linked to the original in WPML or Polylang, shoppers in that language get a 404 or are dropped into the default language with an empty cart.
4. The Cart Has an Error WooCommerce Won't Let Through
WooCommerce checks the cart before it allows checkout. If an item went out of stock, a coupon became invalid, or a minimum order rule isn't met, the checkout sends the shopper back to the cart with a notice, and some themes hide the Proceed to checkout button until the error is cleared.
That is correct behaviour, but two things turn it into a dead end:
- The notice isn't visible. A theme that doesn't print WooCommerce notices on the cart page leaves the shopper with a button that keeps returning them to the same page and no explanation.
- The rule is wrong. A minimum order plugin misconfigured after an update, or stock set to zero by a failed inventory sync, blocks every order.
Check: read the top of the cart page for notices as a guest. If none show, switch to a default theme on staging and repeat.
Fix: correct the rule or stock data, and make sure the theme's cart template prints notices.
5. The Cart Empties on the Way to Checkout
WooCommerce redirects an empty cart away from the checkout page. If the cart was full a moment ago, the session did not survive the trip. The causes are the same ones that make carts appear empty:
- the cart or checkout page is cached by a plugin, the host or a CDN;
- the session cookie is dropped by a consent tool;
- the cart is on
wwwand the checkout link goes to the bare domain, or one is HTTP and the other HTTPS.
Fix: exclude cart, checkout and my-account from every cache layer, serve the store on one HTTPS domain, and treat WooCommerce cart cookies as strictly necessary. The longer walkthrough is in WooCommerce checkout not working, under "Checkout sends you back to the cart".
6. The Click Never Reaches the Button
Two different problems look the same to a shopper, because in both the click does nothing.
A JavaScript error. On the block cart, and on themes with a side cart, the button depends on scripts. Open the browser console on the cart page and click. A red error usually names the plugin. Script optimisation settings (delay, defer, combine) are the most common trigger; exclude WooCommerce and cart scripts from them.
Something is on top of the button. A sticky bar, a chat widget, a cookie banner, a promotional popup, or a page section with the wrong stacking order can sit over the link and take the click. Two stores in the study had this: a "View cart" link lying under a breadcrumb box, and a "View basket" link under a page section. It is common on phones, where fixed elements take up more of the screen.
Check: right-click the button and choose Inspect. If the browser highlights a different element from the button, that element is covering it. Repeat at phone width.
Fix: correct the overlapping element's position or z-index, or stop it from loading on cart and checkout.
7. The Button Is Missing
- Outdated theme template. Themes can override the cart templates, including the one that prints the button (
cart/proceed-to-checkout-button.php). WooCommerce → Status lists outdated overrides at the bottom of the system report. Update the theme, or test with Storefront on staging. - Block cart layout. On a block-based cart page, the button is its own block inside the Cart block. It can be deleted in the editor by accident. Edit the cart page and check that the "Proceed to checkout" block is there.
- A CSS change. A stylesheet update that hides or recolours the button (white text on a white background) removes it for shoppers while it still exists in the page.
- Express buttons only. If the cart shows wallet buttons and the standard button was hidden to "simplify" the page, shoppers without that wallet have no way forward.
8. A Redirect Sends Shoppers Somewhere Else
Rules that are meant for other pages sometimes catch the checkout:
- Site visibility. WooCommerce's "Coming soon" mode has an option to restrict only the store pages. With it on, the rest of the site looks live while cart and checkout show a coming-soon page to everyone who isn't logged in. Check WooCommerce → Settings → Site visibility.
- Forced login. A membership or "private store" plugin redirects guests to the account page. If guest checkout is supposed to work, exclude the checkout from the rule.
- Maintenance mode and redirect plugins. A leftover maintenance rule or a redirect that matches
/checkoutsends shoppers away. - Firewall or bot protection. A challenge page on the checkout address stops some real shoppers as well as bots.
Check: open the Network tab, click the button and read the chain of redirects. The first redirect that doesn't go to the checkout names the page responsible.
A Quick Diagnostic Order
- As a guest, add a product and try every route to checkout, on desktop and phone.
- WooCommerce → Settings → Advanced: is a checkout page assigned, and does it exist?
- WooCommerce → Status: are the WooCommerce pages and templates healthy?
- Hover each link and compare its address with the real checkout address.
- Read the cart page for notices, then the browser console for errors.
- Inspect the button to see whether another element covers it.
- Follow the redirects in the Network tab.
- Check what changed in the last few days: theme, cache, consent or redirect settings.
If shoppers reach the checkout but can't finish, the next guides are "There are no available payment methods" and the checkout not working checklist. If the product never reaches the cart, start with Add to cart not working.
Keep Watch on the Whole Path
A check that loads the checkout address directly will pass on a store with this problem. So will an uptime monitor. Only a check that travels the path the way a shopper does will notice.
A real-browser journey opens a product, clicks Add to cart, uses the store's own cart link and Proceed to checkout button, and expects the checkout form to appear. If a link leads to the homepage, a button is covered, or the cart empties on the way, the journey fails at that step with a screenshot. Run it every 15 minutes and after theme or plugin updates. That is how WooCommerce checkout monitoring works, and user journey monitoring explains the idea in general.
Summary
When Proceed to checkout fails, the checkout page is usually fine and the link to it is not. Check that a checkout page is assigned, that every cart and checkout link points to it, that the cart has no hidden errors, that the session survives, and that nothing covers the button or redirects the shopper. Test every route as a guest, on a phone too. Then monitor the path from product to checkout as one journey, because each link in it can break while the pages on both sides keep working.