Crawlable Architecture, Links, and URLs

Architecture Is a Link System

Search discovery follows addresses exposed through standard web mechanisms. A standard link such as <a href="/menu">View the seasonal menu</a> is understandable to browsers, assistive technology, and crawlers.

Buttons perform actions. Links navigate. A JavaScript click handler can still be part of an interface, but it should not replace a real link when the goal is navigation to a page.

<!-- Fragile navigation -->
<div class="menu-link" onclick="goToMenu()">View menu</div>

<!-- Crawlable navigation -->
<a href="/menu">View the seasonal menu</a>

Every important page should have at least one meaningful internal link. A shallow, logical hierarchy helps people and crawlers understand relationships, but there is no magic click-depth number. The question is whether the pathway makes sense.

Crawlable Does Not Mean Overloaded

A page can be technically reachable and still poorly connected. Good architecture gives important pages clear pathways, sensible context, and enough internal signals to explain why they matter.

Think about four qualities:

For Black Swan Bistro, /menu is stronger than /page?id=47 because it is memorable, readable, and likely to survive design changes. A contextual link from a dish page to dietary information is stronger than relying only on a footer sitemap because it appears at the moment the visitor needs it.

URL Design

URL paths should be stable, descriptive, consistently encoded, and free of avoidable duplicate parameters. A useful URL does not need to contain every keyword. It should make the address understandable and durable.

Avoid treating fragments as separate indexable pages. A fragment such as #dietary-options identifies a location or state inside a document. If dietary information is important enough to search for as its own page, give it a real URL and link to it.

Before changing URLs, ask whether the benefit outweighs the migration cost. Renaming an already indexed page creates redirect, sitemap, canonical, analytics, and internal-link work. New projects can choose cleaner URL patterns early. Existing projects should change URLs only when there is a clear user or maintenance benefit.

Link Roles

The Start Learning control is an anchor with a real destination, making the link available for discovery.

View full-size image

Common Architecture Problems

Watch for these patterns during an audit:

• important pages reachable only through search, filters, tabs, or JavaScript-only controls
• "click here" links that do not explain the destination
• duplicate paths for the same content, such as /menu and /menus/current
• navigation that disappears on mobile and removes important links from the DOM
• deep pages with no contextual links back to related pages
• autogenerated tag, search, or filter pages that create many thin URL combinations

Not every page needs to be in the main navigation. The goal is intentional connectedness: key pages are easy to find, supporting pages are linked from relevant context, and utility pages remain available without pretending to be primary content.