Organize Web Resources with SuperCommands Link Collections

A Link collection is useful when a task repeatedly starts with the same destinations. A client review needs the brief, report, board, and shared folder. A research comparison needs the shortlisted sources.

Keep the collection small enough to explain its purpose. A list of every page you opened is a browsing record; a maintained collection should help you do something.

What a Link object contains

SuperCommands can store one URL or an ordered set of URLs as a Link object. The rows can have recognizable display names, and the object itself has the name you search for.

Resource	Example name	Why it belongs
Main working page	Client A review board	Starting point
Supporting document	Campaign brief	Defines the task
Evidence	Weekly report	Supplies the data
Reference	Measurement definitions	Explains ambiguous metrics

Put the starting destination before the references. When the set opens, the order should support the task rather than mirror the accidental order in which you found the pages.

Create the collection

1. Choose Link from the Create menu.
2. Select available tabs or enter a URL manually in the Link editor.
3. Add only the destinations that belong to this collection.
4. Enter an object name, such as client A review links.
5. Reorder, rename, correct, or remove URL rows.
6. Confirm the object is saved and inspect the resulting list.

The supplied current Link-editor inspection establishes available tabs and manual URL input. Older source names do not establish visible history/bookmark selection in that creation path. The save-page-to-existing-Link path normalizes URLs and checks duplicates; do not assume identical handling in every creation route.

If a page is missing, check its type and source before collecting again. Do not assume an omitted internal page indicates that the whole collection failed.

Retrieve it using the route you actually use

Search the object name in the Home Screen or Webpage Search. For frequently used collections, assign a Text Command through Properties.

For example, give client A review links the shortcut clienta. Type c clienta in SuperCommands search. To use the browser address bar, type c, press Space, then enter clienta.

A favorite or a Links widget is useful if you prefer a visible destination. A Text Command is useful when you already know what you want. You do not need to assign every access method to every collection.

Keep the reasoning in a separate Note

The Link rows answer where to go. A Note answers why you are going there and what is unresolved.

For the client review, write “Investigate whether the traffic drop is confined to one campaign.” That is more useful than copying the four page titles into a note.

Display the Note and Links widget in the same Home dashboard layout. They remain separate saved objects even when the dashboard places them together.

Use dynamic links for repeatable searches

Configurable command URL templates can accept query placeholders and insert URL-safe search text. This behavior belongs to the command-template execution path; it should not be assumed for every ordinary saved Link.

For a documentation search, configure a command URL template, test it with a phrase containing spaces, and inspect the resulting URL. A Link remains a saved destination or ordered URL set, rather than a general automation script.

Choose a collection or a browser folder

A browser bookmark folder is enough for stable destinations you browse manually. A Link object is useful for an ordered set you want to launch through SuperCommands search, shortcuts, and widgets.

Do not maintain the same changing set in both places unless you have a reason. Two independently edited copies can drift. Choose where you will make future corrections.

Update moved documents, rename ambiguous rows, and remove temporary links when a project ends. Create a workspace backup before major reorganizations. For choosing between a reusable collection and an exploratory working set, see saving and reopening tab groups.