When building a service-oriented website, users often struggle to find deep-level links during the preview phase. This article focuses on using the built-in preview tools to reproduce and check hard-to-find service links specifically in the mobile view, helping you confirm navigation paths without leaving the editor.
Locating Deep Service Links in Mobile Preview
This is a hypothetical situation, not a recommendation list. A site editor preparing a mobile-preview review has a small working folder: a navigation draft, a spreadsheet of parts-and-service categories, and a short inventory of page titles copied from the content system, some with their full hierarchy path still attached.
Her immediate problem is that a service page sits several levels down, and in the phone-width preview the path to it collapses. She writes down three name candidates before touching layout: "Parts & Service," "Service & Repair," and "Support: Parts, Service & Repair." The third is long, so she checks whether the middle level still reads when the top label is trimmed to "Support." She keeps the third as a working title and notes the tradeoff in the margin: clearer for scanning, heavier in the collapsed row, so the second level needs its own label rather than repeating "service" three times.
For the deeper link itself, she drafts a plain index row rather than a menu tree: a bold line "Service & Repair," then indented entries "Parts ordering," "Repair request," and "Warranty." Under "Parts ordering" she places a second indent with "Replacement parts list" and "Order status." This lets a narrow preview show the hierarchy through indentation instead of nested taps. Her two sample records show how she sorts the inventory: "Repair request — path: Support > Service & Repair > Repair request; owner column: intake" and "Replacement parts list — path: Support > Parts ordering > Replacement parts list; owner column: catalog." The owner column is her own labelling of which content group would maintain each entry, not a claim about who currently receives requests.
She also keeps a small link ledger so that any reproduced path stays fixed in the demo. One line reads: "Repair request link — destination: the repair request page under the support section; channel: in-site preview only." Another reads: "Parts list link — destination: the catalog subpage; channel: in-site preview only." She does not paste full addresses into the draft; if a colleague needs the route, she writes it as protocol, host, path, and query in separate cells of the ledger so the columns stay readable.
Before the review she picks one tradeoff to illustrate to herself: she drops "Warranty" from the indented list and moves it beside "Repair request" on the same line, because warranty questions usually begin at repair. The reason is space, not evidence about reader behaviour, and she marks the change as provisional. She keeps the three title candidates and two sample records together in one sheet so the mobile preview can be compared against the same source lines, and she notes that the trimmed label must be rechecked for length at the narrowest width she plans to show.
Using the Preview Entry to Access Site Views
The cited official guide identifies Preview as one of three entries at the top of the site, alongside Edit and Manage. It states that Preview lets you view the website effect and that it cannot modify content, making it view-only. To reach it, the guide directs users to the Preview entry in the top navigation bar.1
From Preview, the guide lists available operations: opening in a new window for a larger view, opening the published live website, viewing the sandbox runtime environment, obtaining a shareable preview link through Share address, accessing site-related settings, and refreshing preview content. The guide notes that Share address shows "Copied" after clicking, and that the link can be sent to colleagues or clients for feedback without waiting for formal release.1
The guide's mobile check covers text size, image distortion or overflow, button size and tappability, whether the navigation menu can expand normally, and whether content is blocked. It adds that mobile checks are a must because most visitors access via phone and mobile issues are often not obvious in desktop preview.1
For the mobile-preview review, you can start with the title list itself rather than the navigation draft. Take each copied page title that still carries its full hierarchy path and mark whether the path survives a narrow screen. A title such as “Service & Repair > Parts ordering > Request a part” can be rewritten in the preview as a bold “Service & Repair” line with “Parts ordering” indented beneath it, and the long path becomes a secondary detail you keep in the title list for reference.
You might then compare two candidate labels for the same destination, since the preview is where wording and path length compete. One label could read “Repair request — start here,” while a shorter alternative reads “Repair request.” Note which one still tells a reader where they are without the full breadcrumb visible, and record your choice beside the original title entry. This is a demonstration of a comparison, not a finished decision; you can keep either label and leave the other as a note.
For the deeper service page, consider drafting a plain index row in the same way: a bold line for the section, then indented entries for the pages beneath it. Keep each entry paired with its destination in your working folder so that the reproduced path does not drift between drafts. If a title in your inventory appears under two different parents, write both paths side by side and choose one for the preview, noting the other as an alternative.
Before the review, you can set one tradeoff to examine: whether to show a parent label when only one child is listed. Write the two versions in your folder, mark which reads more clearly at phone width, and bring that pair to the review as your example rather than as a rule for the site.
Checking Navigation Paths for Specific Services
You can also check the navigation paths themselves, not just the labels. Take the service page that sits several levels down and write its full path as one line in your folder: “Home > Services > Repair > Parts ordering.” Then write the shorter path the phone-width preview actually shows. Laying the two lines side by side makes the collapsed steps visible, and you can decide which intermediate level still earns its place on a small screen.
For each service entry in your spreadsheet, consider adding a column you fill in yourself: the path you intend readers to travel. A sample row might read: service name “Parts ordering,” intended path “Repair > Parts,” visible depth in preview “1,” note “parent label hidden.” Filling a few rows this way shows which services depend on a parent label to make sense and which stand alone. If one row reads “visible depth 0,” that is your cue to choose whether to promote it or accept that it appears only after a tap.
You might compare two versions of the same path for one destination. Version A keeps the parent “Repair” visible and nests “Parts ordering” beneath it. Version B drops the parent and shows “Parts ordering” as a direct entry. Write both in the folder, note the word each adds to the row, and mark which one you would show first on a narrow screen. The point is not to settle it now but to arrive at the review with a stated preference and a reason you can say aloud.
When a path passes through a section with only one child, decide in advance whether the parent label stays. Draft the version with the parent, then the version without, and note what a reader loses in each. If the parent word carries meaning the child does not, keep it; if it only repeats the child, you can consider removing it for the preview.
Before the review, you can also trace one path end to end in the draft, from the first entry a reader sees to the service page, and mark each step where the trail depends on scrolling or a tap. Writing those marks next to the path line gives you a short record of where the route is fragile, and you can choose which fragile step to raise first when the group discusses the mobile view.
Verifying Link Visibility on Small Screens
In the mobile preview, use Linkraft 's top navigation bar to open Preview, then select Open in new window so you can inspect the small-screen layout in a separate tab; within that preview you may also use Refresh to reload the content. To manually confirm the link is visible, work through the Mobile Check items in the preview checklist: verify text size, image distortion, button size and tappability, whether the navigation menu expands normally, and that no content is blocked.1
Utilizing Share Address for External Review
In Preview, the share address option is one of the operations available from the preview top navigation bar. The cited official guide states that clicking it provides a shareable preview link and shows "Copied" after clicking. It also describes sending that link to colleagues or clients for feedback, so they can review without waiting for formal release. According to the same guide, this suits projects requiring multi-party confirmation.1
The share address sits among other preview operations rather than in Edit or Manage. The guide separates these entries: Preview is for viewing the website effect and cannot modify content. It lists the share address alongside open in new window, open website, sandbox, settings, and refresh. Before relying on the link for external review, the guide recommends a checklist covering content, function, and mobile checks.1
For the external review, you can start with the short inventory of copied page titles, because each one already carries the hierarchy it was copied from. Take the title with its full path still attached and reduce it to the two pieces a reviewer needs: the destination name and the route a reader would travel. A sample row in your own notes might read: destination, “Repair request”; copied path, “Home > Service & Repair > Repair request”; route for the review, “Service & Repair > Repair request.” You can fill in that last value yourself rather than copying the whole stored path, since the review only needs the steps a reader actually sees. Two other rows could read: destination, “Parts ordering”; route, “Service & Repair > Parts ordering”; destination, “Warranty”; route, “Service & Repair > Warranty.” Filling the route column yourself shows where the copied path and your drafted route disagree.
You might then look at the share address as a separate item in the same note, not as a substitute for the route. For the repair request page, you can record the protocol, host, and the deeper path in words, then ask a reviewer to follow that address on their own device. If the review packet already links an entry through a share address, keep the route column as it is; if it does not, you can add a line under the row that names the protocol and host and the path that ends at the repair request page. This gives the reviewer a way to reach the page without rebuilding your draft navigation, and it keeps the route and the address as two visible records.
Before sending the packet, you can decide which of these two records leads the review. If the point is whether reviewers can find the page through the draft navigation, put the route first and the share address last. If the point is whether one deep page is reachable at all, put the share address first and let the route serve as context. Either choice is yours, and noting which one you chose helps you read the reviewers’ replies against the right question.
Confirming Functional Behavior Before Publishing
According to the cited official guide, saving in the visual editor only saves to the design draft; visitors see the online version, and the two are different. The guide states that after saving edits, the top of the site prompts that the app has changes and asks you to click update to publish the latest content; only then do visitors see the modifications.1
The guide also lists checks to perform before publishing: all placeholder copy and sample images are replaced, contact information is accurate, and there are no typos; navbar links jump normally, forms submit normally, buttons respond correctly, and images load. For mobile, it recommends confirming text size, undistorted images, large enough buttons, a navigation menu that expands, and no blocked content, noting mobile checks are a must.1
Before you publish anything, you can set the draft beside the path record and read them as two versions of the same journey. Take the repair request page you traced through the mobile preview and write its intended route as a single line, then walk that line against the draft: does each step in the record appear as a visible choice in the draft, in the same order? Where a step in the record has no matching entry in the draft, mark it rather than fixing it on the spot.
You might then test whether the reproduced link still leads where the ledger says it should. In your link ledger, the repair request line names a destination; in the separated mobile view, open that entry and note whether it arrives at the page the ledger names, or at a parent, a redirect, or nothing. This is a check you are preparing to perform, not an observation to assert as done.
For the two candidate labels compared earlier, consider what each one does to the path length. Write the full path under each label, count the visible steps, and note any step where the label and the destination no longer agree. The version where the label drops a needed qualifier will show a gap in the path line; the longer label may add a step without adding clarity.
If you send the draft for review, you can attach the route line and the ledger destination as a short comparison note, so reviewers see both the intended path and the recorded landing point. That keeps the review focused on whether the two agree, which is your decision to make before publishing.
Frequently asked questions
How could I record the full path of a service page several levels down in my folder?
You can also check the navigation paths themselves, not just the labels. Take the service page that sits several levels down and write its full path as one line in your folder: “Home > Services > Repair > Parts ordering.”
If I draft an index row for a deeper service page, how should I keep each entry paired with its destination?
For the deeper service page, consider drafting a plain index row in the same way: a bold line for the section, then indented entries for the pages beneath it. Keep each entry paired with its destination in your working folder so that the reproduced path does not drift between drafts.
When a path passes through a section with only one child, how should I compare the versions of that path?
When a path passes through a section with only one child, decide in advance whether the parent label stays. Draft the version with the parent, then the version without, and note what a reader loses in each.