Headless WordPress menus: what to check before launch

Illustrated infographic summarizing: WordPress headless menus need an exposure check before launch

By Greg Nowak. Updated 1 November 2026.

A headless WordPress menu should let editors change navigation without booking a developer. Before launch, you need to prove that visitors see the right links, changes reach the website reliably, and the API publishes only information you intend to share.

A screenshot of a working header proves very little about those things. For a business owner or operations lead, the useful acceptance test is simple: can someone update an important link, confirm it is live, and fix a mistake without guessing which system controls it?

Identify where the navigation actually comes from

Ask the development team to trace the menu from WordPress to the page visitors receive. Include the header, footer, mobile navigation and any separate language menus.

Classic menus use resources for menu locations, menus and menu items. A typical integration resolves a location such as /wp/v2/menu-locations/primary, then fetches its items. WordPress documents the item routes and query options in its menu items reference.

Block navigation has a separate resource at /wp/v2/navigation. Plugins and custom integrations may provide others. Record what the application actually calls, including requests made during a build or on the server; browser developer tools alone may miss those.

Decide which menu data should be public

Public navigation needs public links, but the complete JSON response deserves its own review. Labels, descriptions, CSS classes, URLs and exposed custom fields can reveal material that never appears in the rendered header.

WordPress introduced the rest_menu_read_access filter in version 6.8. It supplies a read-access decision for classic menu locations, menus and menu items. This commonly copied line grants that access broadly:

add_filter( 'rest_menu_read_access', '__return_true' );

Use it only when that scope is intentional. Other authentication and permission checks can still apply; it is not a universal REST API unlock. It also does not govern the separate block-navigation resource.

For narrower access, have the developer implement a reviewed rule in a custom or must-use plugin. A dedicated endpoint returning approved fields may be clearer. Checking only a caller-supplied menus= parameter is insufficient unless omitted parameters, alternative filters and direct item requests are handled too.

Launch decision Evidence to keep Suggested owner
Which navigation is public? Approved routes, menus and complete responses Content owner and developer
Does the menu render correctly? Checks of nesting, order, destinations and mobile behaviour Agency or QA lead
When do edits appear? Measured refresh time and tested purge procedure Operations lead
What happens when fetching fails? Agreed fallback and a tested failure case Developer
Who handles later changes? Named approver and support contact Project owner
Use these checks as acceptance criteria in the launch handover.

Test requests without a WordPress login

Run anonymous requests against a production-like environment, then repeat them on the deployed configuration. Replace the host, location and IDs below. The -q option, placed first, prevents curl from loading its default configuration file; do not add cookies or credentials.

curl -q -i 'https://cms.example.com/wp-json/wp/v2/menu-locations/primary'
curl -q -i 'https://cms.example.com/wp-json/wp/v2/menu-items?menus=MENU_ID&context=view'
curl -q -i 'https://cms.example.com/wp-json/wp/v2/menu-items/ITEM_ID'
curl -q -i 'https://cms.example.com/wp-json/wp/v2/menu-items'
curl -q -i 'https://cms.example.com/wp-json/wp/v2/menus'
curl -q -i 'https://cms.example.com/wp-json/wp/v2/navigation'

Record the status, response headers and body. Try an unapproved location, another menu ID and an item outside the approved menu. Allowed requests should return publishable data; disallowed requests should return no protected content. A successful response from an unexpected route needs investigation even if the website never uses it.

Review the full response, then the rendered menu

Ask the content owner to inspect every returned item for staging domains, placeholder destinations, internal descriptions and campaign links that are not ready for release. A public URL can reveal a planned page even when the destination itself is protected.

WordPress supports _fields to reduce returned fields and processing. Use it for efficiency, but review the response without it: callers can omit the parameter, so it does not enforce privacy.

Check that the integration handles pagination and preserves item order and parent-child relationships. Then test real links, keyboard navigation and the mobile menu. A correct API response can still produce missing children, broken destinations or an unusable submenu.

Prove that an edit reaches visitors

Make a harmless label change, time its appearance on the public website, then revert it. Establish an acceptable delay with the business before launch.

Trace each relevant layer: WordPress hosting cache, CDN, application cache and any static build. If publication depends on a webhook, test that a menu edit triggers the required refresh. Document how to correct an urgent link and who has access to do it.

Also agree what happens when WordPress is unavailable. A last successful menu may keep navigation working, but it needs an understood refresh policy. Test the chosen behaviour on staging so a temporary request failure does not unexpectedly remove the site's main navigation.

Leave a handover someone can use

CORS settings are not an access policy for confidential data. WordPress's REST API guidance explains that public endpoints can be accessed from other sites; direct requests also remain possible. Keep private requests authenticated and reusable credentials on the server.

The handover should contain the route list, approved payload, anonymous test commands, expected refresh time, failure behaviour and named owner. That gives the next team something they can verify after a plugin update or infrastructure change.

If these responsibilities sit across your agency, hosting provider and internal team, talk to Greg about reviewing the launch and handover. A practical review can turn the outstanding questions into clear acceptance criteria before launch.

Related on GrN.dk

Need help with this kind of work?

Discuss your WordPress launch with Greg Get in touch with Greg.

Sources

Latest articles

Before changing an AI workflow, check that it still does the job. Use realistic examples, clear release criteria and a comparison with the version running today.

Sending an invoice does not mean it has arrived. Understand delivery statuses, the system requirements coming in 2027, and how focused AI support can help finance teams handle errors and follow-up.

Before scaling AI content, check the pages you already have. Verify claims, resolve overlapping coverage, and give WordPress reviewers control over publication.

Build a refund approval workflow in n8n and Stripe that shows reviewers the exact action, expires old approvals and tracks refunds through to completion.

A timeout can hide a successful job creation. Use stable operation IDs, destination API rules and a clear recovery process to prevent duplicate work.

Does your ChatGPT subscription cover website translation? Understand API credits, access and a WordPress workflow that turns approved Danish content into translation drafts.

An internal AI can keep quoting a deleted policy. Check document updates, indexed passages and cached answers to find where outdated guidance survives.

Codex drew all ten pages of my Ninjai comic from the script Claude wrote in the first test. What made that handover work, and what it cost.

ChatGPT delivered ten painted comic pages; Claude drew one page in code. A practical look at AI tool selection, creative briefs and approval decisions.

Get missing supporting documents under control with a clearly scoped AI workflow that sorts replies, coordinates reminders and gives the bookkeeper a clear follow-up list.