A button that changes the screen is not necessarily a discoverable page link. Public navigation should expose useful URLs through anchor elements with href values.
Inspect the menu element
Use browser developer tools on a navigation item. Check whether it becomes an anchor with a real URL or only has an onclick handler. A framework Link component may produce a proper anchor; verify the generated HTML rather than deciding based on the component name.
<!-- A discoverable destination -->
<a href="/services">Our services</a>
<!-- A click handler alone does not expose a URL -->
<button onclick="openServices()">Our services</button>Check the initial response separately
A link may exist in the browser DOM after rendering while being absent from View Page Source. If your important navigation relies on JavaScript, include it in server-delivered HTML where practical. Keep descriptive labels so both people and automated readers can understand the destination.
Verify with the right tools
SiteReadyFor.SI’s HTML discovery reads homepage anchors when a sitemap yields no URLs. Its script fallback is limited and does not simulate opening a menu. After adding crawlable navigation, run discovery again and compare the URLs found. Use your browser to test keyboard access and actual menu interactions separately.