A link containing a fragment, such as #pricing, that identifies a location or element within a document.
An anchor or fragment link points to a particular part of a resource rather than just its beginning. On an ordinary HTML page, the fragment after the hash sign can match an element’s ID. The browser then takes the reader to that location. A table of contents often uses this technique to jump to sections of a long guide.
The fragment is handled by the browser after it retrieves the resource; it is not sent to the server as part of the request. A link ending in #delivery can therefore identify a delivery section without creating a separate delivery page. This differs from a URL path, which can identify a distinct resource, and from query parameters used in a request.
A jump link still needs a meaningful target. If an editor renames or removes the target ID, the URL may load the page without reaching the intended section. Likewise, a fixed header can obscure the section heading even when the jump technically works. Test the experience rather than assuming that a visible hash proves the navigation is useful.
Takeaway: Use fragment links to help readers navigate substantial pages. Do not mistake an in-page jump for a separately published, indexable page about the section.
Example
A caterer’s event guide has sections for menu choices, setup and dietary requests. Its contents list links to #menu, #setup and #dietary-requests. A customer following the dietary link arrives at the relevant explanation on the same guide, rather than having to scroll through unrelated setup details.
What to check
Check the link directly in a fresh browser tab and on a narrow screen. Keep target IDs stable when editing headings. If a topic needs its own search destination and substantial standalone content, plan an actual page rather than using fragment-only routing.
For more detail, see MDN URI fragments.