
Your menu works perfectly on a computer, but on a phone the links do nothing when tapped. When wordpress menu links not working on mobile happens, visitors cannot reach your pages at all: taps open nothing, submenus refuse to expand, and the menu button itself may not respond. The links are rarely broken. The fault is usually how the menu handles touch, an invisible layer covering the links, or a script that loads too late on mobile.
This guide works through the causes in order, from testing taps correctly to rebuilding the mobile menu. Test on a real phone wherever possible, because desktop browser tools only imitate touch. Work through the fixes one at a time, and tap-test the menu after each one. A link that opens its page on a real phone is the only proof that counts.
Table of Contents
- Why This Error Happens
- Quick Checks
- Diagnosing the Problem
- Fix 1: Test the Menu on a Real Phone and a Second Browser
- Fix 2: Tap Parent Items Twice: Once to Open, Once to Follow
- Fix 3: Check the Menu Link URLs for Typos and Placeholder Links
- Fix 4: Clear the Mobile Browser Cache and the Site Cache
- Fix 5: Check the Mobile Menu Toggle Opens the Overlay Correctly
- Fix 6: Fix Submenus That Will Not Open on Touch Screens
- Fix 7: Remove Custom Code That Blocks Taps on Menu Links
- Fix 8: Fix a Sticky Header or Overlay Covering the Menu Links
- Fix 9: Test for a Plugin Conflict Affecting the Mobile Menu
- Fix 10: Stop Optimisation Plugins Delaying the Menu Scripts
- Fix 11: Test the Menu With the Theme Default Mobile Menu
- Fix 12: Fix Anchor Links That Point Nowhere on Mobile Pages
- Fix 13: Check the Responsive Breakpoint and Viewport Settings
- Fix 14: Rebuild the Mobile Menu With the Navigation Block Overlay
- Fix 15: Update the Theme, Plugins and WordPress, Then Retest on Mobile
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Official Resources
Why This Error Happens
Desktop menus rely on hover: the mouse rests on a parent item, the submenu opens, and a click follows the link. Phones have no hover — a finger either taps or it does not — so mobile menus need tap handling, overlay panels, and scripts that run early. When any part of that chain fails, taps do nothing, even though the same links work with a mouse. These are the reasons that happens most often.
1. Parent Items Need Two Taps on Touch Screens
A parent menu item is both a link and a submenu trigger. On touch screens, the first tap usually opens the submenu, and only the second tap follows the parent link. Visitors who tap once and see a submenu open, or tap a parent and nothing happens, often conclude the menu is broken. The menu is behaving as designed — but the design is confusing, and many themes handle it badly, leaving parent links unreachable.
2. Hover-Only Submenus Have No Touch Equivalent
Some menus open submenus only on mouse hover, with no tap handler at all. On a phone, tapping the parent follows the parent link immediately, or does nothing, and the submenu never appears. The submenu items are unreachable, not broken: they exist in the menu, but no touch gesture can reveal them. Themes and menu plugins that never added touch support are the usual source of this fault.
3. An Invisible Overlay Sits on Top of the Links
Popups, sticky headers, cookie banners, chat widgets, and full-screen overlays can sit invisibly on top of the menu. The links look tappable, but every tap lands on the layer above them, so nothing happens. The covering layer may be transparent, or positioned off-screen with a stray edge over the menu. This cause is invisible by nature, which is why it survives so many setting changes.
4. The Menu Script Loads Too Late or Not at All
Mobile menus need JavaScript to open the overlay, expand submenus, and handle taps. Optimisation plugins that delay, defer, or combine scripts can push the menu script so late that taps happen before the script runs — or break the script entirely. A JavaScript error from any plugin can have the same effect. The menu looks complete, but its behaviour never starts.
5. The Link Targets Do Not Exist or Point Nowhere
Menu links to deleted pages, mistyped addresses, placeholder # links, and anchors that exist only on the desktop layout all fail silently on mobile. A # link does nothing by design, and an anchor to a section hidden on mobile scrolls nowhere. The menu is working correctly — it is the destination that is missing — but the symptom is identical to a broken menu.
6. The Theme Mobile Breakpoint Hides or Breaks the Menu
The breakpoint is the screen width where the theme switches from the desktop menu to the mobile menu. A breakpoint set wrong, a missing viewport tag, or custom CSS that hides the mobile menu can leave phones showing a broken desktop menu, or no menu at all. The fault appears only in a narrow band of screen sizes, which is why it escapes testing on one phone and appears on another.
Quick Checks
Two minutes before the deep fixes.
- Test the menu on a real phone, not only in desktop browser tools that imitate a phone.
- Check whether the menu button opens the menu at all, or opens it but the links do nothing.
- Check whether submenu parents behave differently from plain links when tapped.
- Check whether the fault affects all phones, or only one phone or one browser.
- Check whether the menu worked before, and what changed since — a new plugin, a theme update, or new custom code.
- Think about what changed — did wordpress menu links not working on mobile begin after an optimisation plugin, a header change, or a theme update?
Diagnosing the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| Menu button does nothing when tapped | Overlay or script fault | Fix 5 |
| Parent tap opens submenu, link never follows | Two-tap parent behaviour | Fix 2 |
| Submenu never opens on touch | Hover-only submenu | Fix 6 |
| Links look fine but taps do nothing | Invisible overlay covering links | Fix 8 |
| Menu worked before an optimisation plugin | Delayed or broken menu script | Fix 10 |
| One link dead, others work | Bad URL or missing target | Fix 3 |
| Menu broken only at some screen widths | Breakpoint or viewport fault | Fix 13 |
| Menu broken on phones, fine on desktop | Theme mobile menu fault | Fix 11 |
Fix 1: Test the Menu on a Real Phone and a Second Browser
Desktop browser tools imitate phone screens, but they do not truly imitate touch, and they run on a fast connection with a desktop browser engine. A menu that fails in the emulator may work on a real phone, and the reverse is also true. Testing on a real phone, in a second browser, establishes the truth before any fix is attempted.

- Open the site on a real phone, using the phone’s main browser.
- Tap the menu button and wait for the menu to open fully.
- Tap a plain menu link — one with no submenu — and note whether its page opens.
- Tap a parent item once, note what happens, then tap it again and note the result.
- Repeat the test in a second mobile browser on the same phone.
- If a second phone is available, repeat the test there too.
- Write down exactly which taps fail, on which phone and browser, for the fixes below.
- A fault on one phone only points at that phone’s browser or cache, not at the site.
- A fault on every phone points at the theme, a plugin, or the menu setup.
- Note whether the page loads slowly before the menu works — slow loading hints at the delayed-script cause in Fix 10.
- Screenshots or a short screen recording of the failing taps help enormously if you later ask a developer for help.
Fix 2: Tap Parent Items Twice: Once to Open, Once to Follow
Many mobile menus use the first tap on a parent item to open its submenu, and the second tap to follow the parent’s own link. Visitors who tap once, see the submenu, and tap the parent again expecting the submenu to close will instead leave the page. Visitors who tap once and wait will think the link is dead. Understanding the two-tap pattern separates designed behaviour from a real fault.
- Open the menu on a real phone and find a parent item with a submenu.
- Tap the parent item once and watch whether the submenu opens.
- Tap the same parent item a second time and watch whether its page opens.
- If the second tap opens the page, the menu is working as designed.
- If the second tap closes the submenu instead, the theme uses tap-to-toggle, and the parent link needs a different path.
- Add the parent page as the first item inside its own submenu, so visitors can reach it with one tap.
- Alternatively, change the parent item to a plain label with a
#link, and put the real page link inside the submenu.
- A parent page that is only reachable by a double tap is effectively hidden from most visitors — the submenu-first-item pattern fixes that.
- Some themes offer a setting for parent tap behaviour, such as “first tap opens submenu” — check the theme options before rebuilding the menu.
- Do not remove parent links entirely without a replacement path, or the parent pages become unreachable from the menu.
- When wordpress menu links not working on mobile means only parent links fail, the two-tap pattern is the explanation, and restructuring the menu is the cure.
Fix 3: Check the Menu Link URLs for Typos and Placeholder Links
A link with a mistyped address, a link to a deleted page, or a placeholder # link does nothing useful when tapped. Desktop testing often misses these, because the mouse hover shows the address and the tester moves on, while phone users tap and get nothing. Checking every link address in the menu editor finds the dead ones quickly.
- In the dashboard, go to Appearance, then Menus, and select the menu shown on mobile.
- Expand each menu item in turn and read its URL or linked page.
- Fix any mistyped address, missing letter, or wrong domain.
- Replace any
#placeholder link with the real page, or convert the item to a plain label if it should not link anywhere. - Remove or relink any item pointing at a deleted page, a draft, or a private page.
- Click Save Menu, clear the cache, and retest every link on a real phone.
- Check custom links especially carefully, because page links update automatically while custom links do not.
- A
#link is meant for parent labels that only open submenus — it should never be used on an item visitors expect to open a page. - Links using the older unsecured web address scheme on a site that now uses the secure scheme can fail or redirect oddly on mobile — update them to the secure scheme.
- After fixing links, test on the phone, not just in the editor, because the editor shows the saved address, not the tapped result.
- One dead link among working links is always a link problem, never a menu problem.
Fix 4: Clear the Mobile Browser Cache and the Site Cache
Phones cache aggressively, and a cached copy of the site’s header, styles, or scripts can keep a fixed menu looking broken for days. The site cache adds a second layer: the server may serve an old mobile menu to every phone. Clearing both — the phone’s browser cache and every site cache layer — is the only way to be sure the phone is testing the current site.
- On the phone, open the browser settings and clear the browsing data, including cached files.
- Alternatively, open the site in a private browsing tab on the phone, which uses no cache.
- In the dashboard, purge the caching plugin’s cache completely.
- Clear the server cache in the hosting panel, and the CDN cache if one is used.
- Wait one minute, then open the site on the phone in a fresh tab.
- Tap-test every menu link, including submenu items.
- If the menu now works, the cache was hiding the fix — keep cache clearing as the first step after every menu change.
- Private browsing on the phone is the fastest clean test, because it skips the cache without deleting saved logins.
- Some caching plugins serve a separate mobile cache — purge it specifically if the plugin offers a mobile cache option.
- If cached pages keep returning after purging, our guide to WordPress cache not clearing covers the deeper cache layers.
- A menu fixed on desktop but still broken on the phone, until the phone cache is cleared, is a cache fault, not a menu fault.
Fix 5: Check the Mobile Menu Toggle Opens the Overlay Correctly
The mobile menu usually hides behind a toggle button — the “hamburger” icon. Tapping it should open an overlay panel with the menu links. If the toggle opens nothing, opens a blank panel, or opens a panel that closes instantly, the links inside can never be tapped. Checking the toggle’s behaviour, and the overlay settings, isolates the panel from the links.
- Open the site on a real phone and tap the menu toggle button.
- Watch whether an overlay panel opens, and whether it stays open.
- If nothing opens, check the theme options or the Navigation block settings for the mobile overlay.
- In the Navigation block, check the overlay setting is set to collapse on mobile, with the overlay enabled.
- If the panel opens and closes instantly, look for a second toggle or a close button overlapping the open button.
- Clear the cache and retest, because a cached script can break the toggle.
- If the toggle still fails, test with the default theme menu in Fix 11 to rule out the theme.
- A toggle that works on some pages but not others points at a page-specific script or a page-builder header on those pages.
- The overlay panel and the menu links are separate parts: a working panel with dead links is a link fault, while a dead toggle is a panel fault.
- On block themes, the overlay settings live in the Navigation block sidebar under display and overlay options.
- Do not add a second mobile menu plugin while the theme menu is broken — two menus fighting over the toggle makes diagnosis harder.
Fix 6: Fix Submenus That Will Not Open on Touch Screens
Submenus built for hover need a tap equivalent, or phone visitors can never reach the submenu items. The fix is to give the parent a tap action: either the theme’s own touch support, a submenu arrow button beside the parent, or a restructured menu that flattens the submenu. The arrow-button pattern is the clearest, because it separates “open the submenu” from “follow the link”.

- Open the menu on a real phone and tap a parent item — note whether the submenu opens, the page opens, or nothing happens.
- Check the theme options for a mobile submenu setting, such as “submenu toggle” or “dropdown on click”.
- Switch the submenu behaviour from hover to click or tap, if the theme offers the choice.
- If the theme has no such setting, check whether the menu plugin offers a submenu arrow or expand button.
- As a structural fix, move the most important submenu items up to the top level of the menu.
- Clear the cache and retest: each submenu should open on tap, and each item inside should follow its link.
- If submenus still fail, test the Navigation block overlay in Fix 14, which handles touch submenus natively.
- Flattening the menu — fewer levels, more top-level items — is the most reliable fix for deep submenu trees on phones.
- A submenu three levels deep is hard to use on any phone, however good the tap handling, so keep mobile menus shallow.
- The arrow button must be large enough to tap comfortably — a tiny arrow beside a link is a usability fault of its own.
- When wordpress menu links not working on mobile means only submenu items fail, the hover-only submenu is the cause.
Fix 7: Remove Custom Code That Blocks Taps on Menu Links
Custom CSS and JavaScript added for styling can accidentally block taps. A CSS rule that sets pointer-events: none on the header, a full-width element with a higher stacking order, or a script that intercepts clicks can all swallow taps before they reach the links. Removing or narrowing custom code, and testing after each removal, finds the offending rule.
- Open Appearance, then Customize, then Additional CSS, and read every rule that mentions the header, menu, or navigation.
- Note any rule using
pointer-events,z-index,position: fixed, oroverflow: hiddenon menu elements. - Copy the custom CSS to a safe note, then remove the menu-related rules temporarily.
- Clear the cache and tap-test the menu on a real phone.
- If the menu works, restore the CSS one rule at a time, testing after each, until the blocking rule is found.
- Rewrite the blocking rule to target only the element it was meant for, or remove it permanently.
- Check custom JavaScript in the same way, especially click handlers attached to the header or menu.
pointer-events: noneis sometimes added to fix a different problem, such as a header blocking page clicks — it trades one fault for another.- A rule that works on desktop can break mobile, because the mobile menu sits in a different container with a different stacking order.
- If styles refuse to update after editing, our guide to WordPress CSS changes not updating covers the cache and minification causes.
- Keep a copy of all custom code before removing it, so the design can be restored once the blocking rule is identified.
Fix 8: Fix a Sticky Header or Overlay Covering the Menu Links
Sticky headers, announcement bars, cookie banners, and chat widgets can cover the open mobile menu, either fully or at its edges. The menu is open underneath, but taps land on the covering element. The covering element may be transparent, or may extend further than it appears. Checking stacking order and spacing, and testing with the sticky elements paused, reveals the cover.
- Open the menu on a real phone and look carefully for any bar, banner, or widget overlapping the menu area.
- Close or dismiss the cookie banner and any popup, then tap-test the menu again.
- Temporarily disable the sticky header in the theme options, and tap-test again.
- If the menu works with the sticky header off, the header’s height or stacking order is the cause.
- Adjust the header settings so the open menu sits above the header, with the menu panel given the higher position.
- Check chat widgets and floating buttons too — a floating button can cover the lowest menu links.
- Restore the sticky header with the corrected settings, clear the cache, and retest.
- A header that sticks on scroll can cover the menu only after scrolling — test the menu both at the top of the page and after scrolling down.
- Sticky header faults often appear after a header builder change, so check the header template if the fault is new.
- Our guide to Elementor sticky header not working covers sticky header faults in Elementor-built headers.
- The menu panel must always sit above sticky elements when open — if the theme cannot do that, the theme needs an update or a replacement.
Fix 9: Test for a Plugin Conflict Affecting the Mobile Menu
Menu plugins, mega-menu plugins, popup plugins, and page builders all touch the mobile menu, and any one of them can break it. Troubleshooting Mode disables plugins for your session only, so you can test the menu safely while visitors see the normal site. Finding the conflicting plugin is a process of elimination, done one plugin at a time.
- Install and activate the free Health Check & Troubleshooting plugin from WordPress.org.
- Go to Tools, then Site Health, then Troubleshooting, and click Enable Troubleshooting Mode.
- On a real phone, sign in to the dashboard in the phone browser so the troubleshooting session applies.
- Open the site on the phone and tap-test the menu with all plugins disabled.
- If the menu works, re-enable plugins one at a time, tap-testing after each, until the culprit is found.
- Keep the culprit disabled, replace it, or check its settings for a mobile menu option that conflicts.
- Click Disable Troubleshooting Mode to restore the normal site.
- Test menu, popup, and optimisation plugins first, because they touch the menu and its scripts directly.
- A plugin updated recently is a prime suspect — check the update history if the fault has a clear start date.
- Troubleshooting Mode on the phone needs the phone browser signed in to the same admin session, so use the phone browser for the whole test.
- Do not test by disabling plugins on the live site directly — visitors would see a broken site during the test.
Fix 10: Stop Optimisation Plugins Delaying the Menu Scripts
Optimisation plugins delay JavaScript until the visitor interacts with the page, to speed up loading scores. The menu script, delayed this way, may not be running when the visitor first taps the menu, so early taps do nothing. Later taps, after the script has loaded, may work — a confusing pattern where the menu “warms up”. Excluding the menu scripts from delay fixes it without losing the speed benefit elsewhere.

- Open the optimisation plugin’s settings and find the JavaScript delay or defer options.
- Look for an exclusion list, sometimes called “excluded scripts” or “scripts to exclude from delay”.
- Add the theme’s menu script and the navigation script to the exclusion list — the plugin’s documentation names the common ones.
- If you cannot identify the script, temporarily switch off JavaScript delay entirely and tap-test the menu.
- If the menu works with delay off, the delay is the cause — restore delay with exclusions, rather than leaving it off.
- Also check the combine and minify options, which can break scripts by merging them badly — pause them while testing.
- Clear all caches, including the optimisation plugin’s cache, and tap-test on a real phone.
- The “works on the second visit” or “works after waiting” pattern is the signature of delayed scripts.
- Excluding scripts is better than disabling optimisation entirely, because the rest of the site keeps its speed benefit.
- If scripts fail to load at all, our guide to WordPress JavaScript not loading covers the wider script faults.
- After changing optimisation settings, always purge the cache — old optimised files otherwise keep serving.
Fix 11: Test the Menu With the Theme Default Mobile Menu
Custom headers, header builders, and menu plugins replace the theme’s own mobile menu with their own version. If that replacement is faulty, the theme’s default menu may work perfectly. Testing with the default menu — by pausing the custom header or switching to a default theme briefly — separates a theme fault from a custom-header fault. Do the test at a quiet time, and restore the custom header promptly.
- Note the current header setup, so you can restore it exactly after the test.
- If a header builder or menu plugin provides the mobile menu, pause it or switch the header back to the theme default.
- Clear the cache and tap-test the menu on a real phone with the default menu active.
- If the default menu works, the custom header or menu plugin is the cause.
- Check the custom header’s mobile settings, especially the menu widget’s mobile behaviour and link settings.
- Alternatively, switch briefly to a default theme such as Twenty Twenty-Five, and tap-test its mobile menu.
- Restore the original theme or header, with the fault identified, and fix or replace the faulty part.
- Switching themes does not delete menus or content — it only changes the appearance during the test.
- A custom header that works on desktop but fails on mobile usually has a mobile-specific setting wrong, such as the menu widget’s responsive behaviour.
- Keep the test short, and do it when traffic is low, because visitors see the changed header during the test.
- When wordpress menu links not working on mobile survives every other fix, the custom header is the remaining suspect, and this test proves it.
Fix 12: Fix Anchor Links That Point Nowhere on Mobile Pages
Anchor links jump to a section of a page, identified by an ID such as #services. If the section is hidden on mobile, renamed, or present only in the desktop layout, the anchor has nowhere to go, and the tap appears to do nothing. The menu link is fine — its destination is missing on the mobile layout. Checking each anchor’s target on a phone finds the broken ones.
- In the menu editor, list every custom link that contains a
#anchor. - Open the target page on a real phone and check whether the anchored section is visible.
- If the section is hidden on mobile, either show it on mobile or change the menu link to the page itself.
- Check the anchor ID matches exactly, including capital letters —
#Servicesand#servicesare different anchors. - If the section comes from a page builder, check its ID setting, which can change when the section is duplicated.
- Save the menu, clear the cache, and tap-test each anchor link on a real phone.
- For anchors to sections on the homepage, test from another page too, because the link must load the homepage first.
- An anchor link to a section on the same page behaves differently from one to a section on another page — test both patterns.
- Sticky headers can cover the anchored section after the jump, making it look as if nothing happened — check the scroll position, not just the first impression.
- Renaming a section in a page builder often changes its ID silently, breaking every anchor that pointed at it.
- When in doubt, link to the page rather than the section — a page link always has somewhere to go.
Fix 13: Check the Responsive Breakpoint and Viewport Settings
The viewport tag tells phones the page width, and the breakpoint tells the theme when to switch menus. A missing viewport tag makes phones render the desktop layout shrunk down, so the mobile menu never appears. A breakpoint set too low leaves tablets and large phones showing a broken desktop menu. Both settings live in the theme, and both are quick to check.

- On a desktop browser, open the site, right-click, and choose View page source.
- Search the source for
viewportand confirm a viewport meta tag is present. - If the viewport tag is missing, check the theme settings or ask the theme developer — every modern theme should include it.
- Check the theme options for a mobile breakpoint or responsive setting, and note its value.
- If the breakpoint is very low, such as 480 pixels, large phones may miss the mobile menu — raise it to a standard value such as 768 or 1024 pixels if the theme allows.
- Clear the cache and test on phones of different sizes, plus a tablet if available.
- If the theme offers no breakpoint setting, the fault needs a theme update or a child-theme adjustment by a developer.
- The viewport tag belongs in the theme header, and a missing one affects the whole site, not just the menu.
- Testing only one phone size hides breakpoint faults — borrow a second phone or use the browser tools to check several widths.
- A site that looks like a shrunken desktop page on a phone, with tiny text, is missing its viewport tag.
- Do not edit theme files directly to add a viewport tag — use a child theme or ask the theme developer, so updates do not wipe the fix.
Fix 14: Rebuild the Mobile Menu With the Navigation Block Overlay
The Navigation block’s overlay is WordPress’s built-in mobile menu: a full-screen panel with touch-friendly links and submenu handling. Rebuilding the mobile menu as a Navigation block, with the overlay set to appear on mobile, replaces a faulty theme or plugin menu with the core behaviour. It is the cleanest rebuild available on block themes, and it removes the whole class of custom-menu faults.
- In the dashboard, go to Appearance, then Editor, and open the Header template part.
- Select the Navigation block, or add one if the header has no navigation.
- In the block settings, set the menu to the correct menu, with the items in the right order.
- Under display settings, set the overlay to appear on mobile, so phones see the menu button and the overlay panel.
- Check the overlay panel settings: large text, clear submenu controls, and a visible close button.
- Click Save, review the changes, and confirm.
- Clear the cache and tap-test every link and submenu on a real phone.
- The overlay settings control whether the menu collapses, at what sizes, and how the panel looks — check all three.
- A Navigation block can display any existing menu, so rebuilding the block does not mean rebuilding the menu items.
- If the theme is a classic theme without the Site Editor, this fix does not apply — use the theme’s own mobile menu settings instead.
- After rebuilding, remove any menu plugin that was providing the old mobile menu, so the two do not fight.
Fix 15: Update the Theme, Plugins and WordPress, Then Retest on Mobile
Outdated software carries known mobile-menu bugs, fixed in later releases. An old theme may predate proper touch handling, an old menu plugin may conflict with the current WordPress version, and an old WordPress core may mishandle the Navigation block. Updating everything, then retesting on a real phone, clears the version-mismatch class of faults. Back up first, and test after each group of updates.
- Take a full backup of the site, including files and the database.
- Go to Dashboard, then Updates, and note what is available.
- Update WordPress core first, if an update is offered, and wait for it to finish.
- Update the active theme next, and recheck the mobile menu settings after the theme update.
- Update plugins in small groups, tap-testing the menu on a real phone after each group.
- Clear all caches, and tap-test the full menu — every link and every submenu — on a real phone.
- If an update breaks the menu further, roll back with the backup, and update that item alone with care.
- Update on a staging copy first if the site is busy — updates can change the header appearance as well as fix bugs.
- A menu that works after updating proves the fault was a fixed bug, and no deeper repair is needed.
- Keep the theme and plugins updated on a regular schedule afterwards, so mobile faults do not return with age.
- After updating, recheck the optimisation exclusions from Fix 10, because updates can reset plugin settings.
What to Avoid
- Do not judge the mobile menu only in desktop browser tools — test on a real phone before declaring it fixed or broken.
- Do not add a second mobile menu plugin on top of a broken theme menu — two menus fighting makes diagnosis harder.
- Do not use
#placeholder links on items visitors expect to open a page — they do nothing when tapped. - Do not install nulled or pirated themes and plugins — they can carry malware and break menu scripts.
- Do not set
pointer-events: noneon the header to fix a different problem — it kills menu taps too. - Do not hide anchored sections on mobile without fixing the menu links that point at them.
- Do not skip the cache clear after a fix — a cached mobile menu hides the repair and wastes the next test.
Frequently Asked Questions
Why is wordpress menu links not working on mobile when the desktop menu works fine?
Because mobile menus work differently from desktop menus. Desktops use hover, while phones use taps, overlay panels, and scripts that must load early. A hover-only submenu, a delayed script, or an overlay covering the links breaks only the mobile experience. Work through Fix 2, Fix 6, Fix 8, and Fix 10: check the tap pattern, fix touch submenus, look for covering layers, and exclude menu scripts from delay.
Why do I have to tap a menu link twice on my phone?
Because the first tap opens the submenu and the second follows the parent link, on themes that use the two-tap pattern. If the parent page matters, add it as the first item inside its own submenu, so one tap reaches it. Fix 2 explains the pattern, and Fix 6 covers themes that handle submenus with a separate arrow button instead.
Why does the menu work on one phone but not on another?
Because phones differ in browser, screen size, cache, and connection speed. A breakpoint fault appears only at certain widths, a cache fault only on phones that visited before the fix, and a delayed-script fault only on slow connections. Test on more than one phone, clear caches, and check the breakpoint with Fix 13 before concluding the site is at fault.
Can an optimisation plugin really break menu links?
Yes. Delaying JavaScript until interaction means the menu script may not be running when the visitor first taps, so early taps do nothing. Combining and minifying scripts can also break the menu script outright. Fix 10 shows how to exclude menu scripts from delay while keeping the speed benefit for the rest of the site.
Should the mobile menu be the same as the desktop menu?
Not necessarily. Mobile menus work best when they are shorter and shallower: fewer items, fewer submenu levels, and the most important pages first. A desktop menu with forty items and three submenu levels is unusable on a phone however good the tap handling. Consider a dedicated mobile menu with the essential links, assigned to the mobile location if the theme offers one.
Will rebuilding the menu with the Navigation block delete my menu items?
No. The Navigation block displays an existing menu, so the items, order, and links carry over. Fix 14 rebuilds the display — the overlay panel and its touch behaviour — not the menu content. The old menu remains in the Menus screen, and switching the block back restores the previous display if needed.
Conclusion
When wordpress menu links not working on mobile locks phone visitors out, start with a real-phone test, then check the tap pattern, the link addresses, and the cache, and only then dig into overlays, scripts, and breakpoints. Most mobile menus are fixed by the first ten fixes, because the fault is touch handling, a covering layer, or a delayed script — not broken links. Finish by tap-testing every link and submenu on a real phone, at the top of the page and after scrolling, because a menu that works under a real finger is the only proof that counts. Keep the mobile menu short, keep software updated, and phone visitors will reach every page first tap, every time.
