Before handing off a website, ensure shared links resolve to the correct public URL. This article explains how to distinguish between development previews and live sites using basic URL anatomy, providing steps to verify link integrity for small business websites.

As a hypothetical case, imagine a first-time site builder preparing a small business service site and keeping a short handoff note with three candidate link labels: “Service overview,” “Contact details,” and “Booking notes.” Each label sits beside a copied address, and the builder must decide which address belongs in the note. One candidate may use a long query showing a preview parameter, another may use a subdomain reserved for drafts, and a third may be the intended public path. The open question is whether every copied address resolves to the public location rather than a preview location, and that choice is not settled by appearance alone.

To make the example concrete, suppose the builder has a page titled “On-site support,” a second titled “Request a quote,” and a third titled “Coverage area.” The handoff note lists each page with one address. For the first two, the addresses end with distinct paths; for the third, the address carries extra characters after a question mark. The builder needs to choose whether to replace only the third address or recheck all three. This example is self-made to explain the problem, not a report of a real handoff, a completed check, or a tested result.

A practical comparison would be to inspect the copied address for a preview-specific host or query value and then open it in a fresh browser window to see which page appears. The builder might also ask a colleague to open the same address without signing in. The unresolved choice is whether the note should include only clean public addresses or also a brief label naming the page title, which can help the recipient confirm the destination.

Understanding URL Anatomy

A URL is the address of a unique resource on the internet, and the browser uses it to retrieve published resources such as HTML pages. The MDN article breaks a URL into parts. The scheme comes first and indicates the protocol the browser must use; for websites this is usually HTTPS or HTTP. The authority follows, separated from the scheme by colon slash slash. It includes the domain, which indicates which web server is being requested, and optionally a port, the technical gate used to access resources on that server. The port is usually omitted when the server uses the standard ports, 80 for HTTP and 443 for HTTPS.1

The path identifies the resource on the web server; in modern use it is mostly an abstraction handled by servers rather than a physical file location. Parameters are key/value pairs preceded by a question mark and separated by an ampersand, and the server can use them to do extra work before returning the resource. The anchor, after a hash, is a bookmark inside the resource: the browser scrolls to that spot in an HTML document, and the fragment identifier is never sent to the server with the request. In an address bar you must provide a full absolute URL, though the protocol and port can often be left out.1

Start with your own short list of candidate links, not the address bar. For a business service site, note the visible page title beside each copied address. If one candidate begins with a host that includes a preview word while another begins with the intended public host, you might set the preview-looking one aside and keep the public one for the handoff note. This is an author demonstration, not a check of any live service.

A further practical action is to read the path and query separately. You can write the page title, then the path, then any extra characters after the question mark. If a candidate carries a string that appears only in your editing session, consider replacing it with the plain page address and comparing the two versions side by side. Your final choice remains yours to make.

Identifying Preview vs Live URLs

Take one link you plan to share and read it in two passes rather than one. First, look at the part before the first slash after the host: a word such as “preview,” “staging,” or “draft” there is your cue to pause. Second, read the path and anything after the question mark. Write each piece on its own line, page title first, then path, then query, so you can compare two candidate addresses side by side.

As a hypothetical check, suppose your handoff note has two addresses for the same “Request a quote” page. One carries a short extra string after the question mark; the other ends cleanly at the page path. You might keep the clean one for sharing and set the longer one aside, noting why in your own list. The choice stays yours; the point is that you can say which characters caused the doubt.

You can also rewrite your own sentence before sending it. If a draft message reads “here is the link we discussed,” consider replacing it with the exact page title and the clean path you selected, so the recipient can match the words on the page. These are author demonstrations, not fixed rules. Keep your recorded questions short and answerable from your own material, and decide which candidate you will share before the handoff.

The anchor element’s href attribute holds the URL the hyperlink points to, and the text inside the link should indicate the link’s destination. For a handoff note, the target itself is in the href value, so check that value rather than relying only on the visible wording.2

The source lists several URL forms as valid href values: absolute URLs starting with a scheme and host, origin-relative URLs, directory-relative URLs, and parent-directory-relative URLs. It does not describe a separate preview host, so you cannot confirm a preview from this source alone; its documented link forms are what you can compare.2

For the three link labels in your handoff note, you can add a one-line check beside each: the page title you expect a visitor to land on. Next to “Coverage area,” for example, write “should open the coverage page, not the editing view.” Then compare that expectation with the address you plan to share, and mark any label whose address seems to lead somewhere else. You might also revise your note from “Link for quote page” to “Quote page for visitors — opens the request form.” Keeping the expected visitor destination in the same line makes a mismatch easier to spot before you share the note.

Take the three candidate links in your handoff note and compare the host part of each address with the host of the page you actually mean to share. You can write the page title, then copy the host, then note whether the host looks like the one you associate with your public site or with a private editing session. Suppose the “Request a quote” entry points at an address whose host contains a preview word while the “Coverage area” entry uses the plain public host. That visible difference is enough to decide which one belongs in the note; you might move the preview host into a separate scratch line and keep only the public address beside the title.

Next, decide what your note says around each link, since a correct address can still be surrounded by misleading text. If your draft reads “preview of the new quote page is ready,” consider replacing it with “quote page, public address.” This is an author’s demonstration, not a report of a real edit. You can then reread the note as a recipient would: each page title should sit next to one address, and any address you cannot match to a public host should be removed rather than left for the recipient to interpret.

Finally, choose how to handle leftovers. You might keep a short private list of preview addresses for your own work and a separate handoff list containing only the public ones. Before you send anything, you can read the handoff list alone and ask whether every address there is one you would be willing to open in front of a client. If not, that entry needs a decision from you, not a note to the recipient.

Final Verification Checklist

Take the shared-link section of your handoff note and give each entry its own final pass before you send it. You can choose to mark each row with two things: the page title a visitor should land on, and the host portion you expect for the public site. If the host in a row still matches the address you use while editing, that row is not ready to sit beside the others. This is a short editing choice, not a new technical step.

You might also decide what happens to a preview address once you remove it. One option is to keep a separate private line, clearly labeled as not for sharing, so the working address is not lost. Your handoff section then holds only rows that pass your own title-and-host comparison. Consider rereading the note once after that separation; a reader should be able to pick any row and know which page it opens without asking you.

Frequently asked questions

Start with your own short list of candidate links, not the address bar. For a business service site, note the visible page title beside each copied address.

A further practical action is to read the path and query separately. You can write the page title, then the path, then any extra characters after the question mark.

What two things can I mark on each entry in the shared-link section of my handoff note during a final pass before sending?

Take the shared-link section of your handoff note and give each entry its own final pass before you send it. You can choose to mark each row with two things: the page title a visitor should land on, and the host portion you expect for the public site.

  1. What is a URL? - Learn web development | MDN . Retrieved 2026-11-09. ↩︎ ↩︎

  2. <a> HTML anchor element - HTML | MDN . Retrieved 2026-11-09. ↩︎ ↩︎