Guide
Lovable Navigation Menu in WordPress: How to Fix It
Your Lovable header navigation converts into a WordPress navigation block inside a header template part. You edit it in Appearance → Editor → Patterns → Template Parts → Header, not in the old Settings → Menus screen. Links that pointed at page routes are rewritten to WordPress page links; dropdowns and hamburger menus arrive in their default state, because the JavaScript behind them does not travel. This guide shows where each piece lands and how to repair the parts that need a hand.
Where the menu lives after conversion
In a Lovable project the header is a React component. It sits in src/components, is imported by every page, and its links are React Router or TanStack Start route links. There is no menu table and no admin screen behind it.
WordPress block themes work the same way in spirit. The header is a template part, stored as an HTML file in the theme under /parts/header.html, and every template includes it. The converter reads your Lovable header once and writes that file.
Inside it you get a core/navigation block holding one link per route, plus the site logo and any header button. Because it is a block, you edit it visually in the Site Editor and the change lands on every page at once.
Editing the links
WordPress block themes dropped the old Appearance → Menus screen. Everything happens in the Site Editor. The path is short once you know it.
- To rename a link, click its text and type. The page title stays as it is; only the menu label changes.
- To remove a link, select it and use the three-dot menu → Remove.
- To point a link elsewhere, select it, click the link icon, and paste a URL or search for another page.
- To add a dropdown, select a link and choose Add submenu link from its toolbar.
- Open
Appearance → Editorin the WordPress admin. - Go to Patterns → Template Parts → Header, or click the header on any template preview.
- Click the navigation block. The list of links appears in the toolbar and in the block list view.
- Use the plus button inside the navigation block to add a link, then search for a page by name.
- Drag items in list view (the icon top left) to reorder them, or select one and press the arrow buttons.
- Click Save. The change applies to every template that uses the header part.
What converts and what needs a hand
Header navigation is on the supported list. Link labels, their order, the site logo and header buttons come across, and so do the hover colors, which are written into theme.json with the rest of the palette. Internal links that matched a page route become WordPress page links, so they keep working after you change a slug.
Interactive behaviour is a different story. A hamburger menu in Lovable is React state: a boolean that flips when you tap the icon. That state is custom React code, and custom React state and event handlers are not converted. The same goes for dropdown menus built with shadcn/ui, which arrive in their default state only.
This usually matters less than it sounds. The WordPress navigation block has its own responsive behaviour built in, and its own submenu handling. You are not left without a mobile menu; you are left with WordPress's mobile menu instead of yours.
- Converted: link text, link order, internal page links, logo, header button, hover colors.
- Approximated: dropdowns and mega menus, which land as plain submenus or as the default state of the component.
- Replaced: the mobile hamburger, which becomes the navigation block's own overlay menu.
- Not converted: scroll-triggered sticky headers, animated underlines driven by JavaScript, menus that read logged-in state.
Setting up the mobile menu
Select the navigation block and open the block settings sidebar. Under Display, you choose when the menu collapses into an icon: always, never, or on mobile only. Mobile only matches what most Lovable headers do.
The overlay that opens has its own settings. You can set its background and text color, and choose whether it covers the full screen. Pick colors from the theme palette so they match the tokens the converter wrote into theme.json.
Check the result at a narrow width before you call it done. Open the site in a new tab and drag the browser window narrow, or use your browser's device toolbar. The Site Editor preview has desktop, tablet and mobile buttons too, but a real browser window is the honest test.
Common problems and their fixes
Most navigation complaints after a conversion come from one of a handful of causes. Work through these before you start editing theme files.
If a link 404s, the page slug changed. Open Pages, check the slug, then re-point the link in the Site Editor. If every link 404s, flush the permalinks: visit Settings → Permalinks and press Save without changing anything.
If the header looks right on one page and wrong on another, that page is probably using a different template. Open Appearance → Editor → Templates, open the odd one, and confirm the header template part is at the top.
- Menu shows every page, including ones you hid. The navigation block can be set to show all pages. Select it, open the sidebar, and switch to a manual list of links.
- Logo too large or too small. Select the site logo block and set its width in pixels in the sidebar.
- Links wrap onto two lines. Reduce the font size in the navigation block, or shorten the labels.
- Dropdown opens on click, not hover. That is the block's behaviour. It is also better for touch devices; we suggest keeping it.
- Sticky header missing. Select the header template part in a template, open the sidebar, and set position to Sticky.
If you use the IQDesk converter
Our converter reads the Lovable ZIP or your GitHub repository in the browser and writes the header template part for you, navigation block included. The review screen puts the converted site next to the original inside WordPress Playground, so you can compare the two headers side by side before you download anything.
When something in the header is off, the AI fix agent can look at both. It reads the source project, measures both pages, and edits the theme. Every account includes two free fix attempts, which is often enough for a header. Give it a specific instruction, up to 2,000 characters: name the element and what it should do.
Conversion, review and the theme download are free. See supported features for the full list of what converts, what is approximated and what is left out, so there are no surprises when you open the Site Editor.
Checking the menu before launch
A navigation bar is the one element on every page, so test it on every page. A broken header is a broken site.
Run this pass on a staging copy, with Settings → Reading → "Discourage search engines from indexing this site" checked, then uncheck it when you go live.
- Click every link in the header and confirm it lands on the right page.
- Open the site at mobile width and open and close the overlay menu.
- Check the logo links to the home page and that the home page is the one set under
Settings → Reading → "Your homepage displays". - Confirm the header appears on every template: home, page, single post, 404, search.
- If you have submenus, tab through them with the keyboard and check they open.
- Look at the header in a second browser before you announce the launch.
FAQ
Why is there no Appearance → Menus screen in my WordPress theme?
Block themes do not use the classic menus screen. Navigation is a block stored in the header template part instead. Edit it at Appearance → Editor → Patterns → Template Parts → Header. The classic screen only appears for classic themes.
Does my Lovable hamburger menu still work in WordPress?
Not the original one. The open and close behaviour is custom React state, and that code is not converted. The WordPress navigation block has its own responsive overlay menu, which you turn on in the block settings under Display. For most headers the result looks and behaves much the same.
Do dropdown menus from Lovable convert?
They are approximated. A dropdown built with shadcn/ui arrives in its default state, because the JavaScript that opens it does not travel. You can rebuild it as a native submenu in the navigation block by selecting a link and choosing Add submenu link. The WordPress submenu opens on click rather than hover.
I changed a page slug and a menu link broke. What do I do?
Open Appearance → Editor, select the header template part, click the broken link, and point it at the page again by searching for its name. Page links chosen this way follow future slug changes automatically. If every link on the site returns a 404, go to Settings → Permalinks and press Save once to refresh the rules.
Will editing the header in one place change it everywhere?
Yes, as long as every template includes the same header template part. That is how the converter sets it up. If one page shows a different header, open that template in the Site Editor and check which part sits at the top.