Link to a section or text: test where it takes readers

Define where you want the reader to arrive

You want to send the opening hours in a long guide, rather than make someone search the entire document. Before copying an address, identify the page and the heading or phrase the reader needs. The consulted questions show real difficulties combining a section link with text highlighting and understanding why a mechanism works on some pages but not others. This guide separates two outcomes: opening the correct document and reaching the intended point within it. Keep both criteria in your test. If the link opens the guide but does not scroll to the timetable, you have confirmed only the first. Do not present that partial result as a fully tested deep link.

Distinguish an identifier from a text search

MDN explains that a fragment begins with# and is interpreted by the client after retrieving the resource; it is not sent as part of the server request. In HTML it may reference an element's id. In the first fictional address, schedule would need to match the section's actual identifier. The visible heading does not necessarily have the same value. Prefer copying a link supplied by the page's contents list or heading, where available, and check where it leads. Do not invent the identifier simply by removing spaces from the title. If you control the website, ask for a stable identifier that survives reorganizing the guide so existing shared references remain useful.

Treat highlighting as assistance rather than a guarantee

The second address illustrates a text fragment using#:~:text= and an English phrase. The domain is fictional; replace the page and phrase with real values. Strings require appropriate encoding: the space appears as%20. Prefer generating the link with a browser function, where available, and inspecting what it copied instead of building a complicated directive manually. MDN explains that supporting browsers look for matches and can highlight them. Without a match or browser support, the directive is ignored. Content can change, and a repeated phrase may point to a passage other than the intended one. Therefore do not promise permanent highlighting or an identical result for every recipient.

https://example.invalid/guide/#schedule
https://example.invalid/guide/#:~:text=Opening%20hours

Check the page separately from navigation within it

Use WikiURL's checker for a public address without secrets or personal information and record the HTTP response and final URL. That result helps inspect the page or its redirects; it does not certify that a browser will scroll to a paragraph. Fragment processing happens on the client, and a200 response does not establish that an identifier exists or that the text matches. Then open the complete address in the intended browser and observe where it lands. If the information requires private access, test with authorized permissions and avoid sending it to external services. Linking to a section does not grant permission or bypass a sign-in requirement. Keep those checks separate.

Test the address the other person receives

Paste the link into the same kind of message or document you plan to distribute and reopen it from that version. An embedded browser, a redirect or a message transformation may require another check; do not identify the failed layer without reproducing the case. If a WikiURL short address is needed, create it from the complete approved destination and test the exact result, including arrival at the section. Do not assume shortening creates an anchor or adds highlighting support. Activation conditions matter too: MDN describes text fragments as invoked on user-initiated navigations and in the main frame. A test inside an embedded frame is not universal evidence of ordinary navigation behavior.

Use two boxes in your test log: correct page and correct section. If the first passes and the second fails, keep the original link and the link received in the message and compare them before making changes. Record whether both retain the same complete fragment. This log does not automatically diagnose the cause. It avoids confusing a transformed address with failed scrolling and gives the maintainer a concrete case to reproduce.

Provide an alternative that remains useful

Accompany the link with the guide's title and section name, such as Opening hours, so readers can find it if scrolling or highlighting fails. Avoid private information in the fragment: being absent from the HTTP request does not make it secret when the address is shared. Keep the approved URL, phrase or identifier, date and real-channel test result together. When updating the content, recheck links that depend on its wording. A useful result is a reference opening the correct document and helping locate the information, with a readable alternative if the navigation convenience fails. WikiURL helps with the address; verifying arrival at the passage still requires observing the browser itself.