To check whether a Mac shortcut encodes selected search text, inspect the value that reaches its final URL: add a Quick Look action after the shortcut builds the URL, run it with a test phrase containing spaces and reserved characters, and check whether those characters appear as percent escapes. A successful run alone does not prove the search text was encoded correctly; the visible URL gives you a way to inspect what the shortcut actually assembled. Apple documents Quick Look for previewing content passed between shortcut actions, and its Mac guide describes URL-based workflows that require text to be URL-encoded. (Testing your actions in Shortcuts on Mac; Use another app’s URL scheme in Shortcuts on Mac)

Identify the text and the URL you need to inspect

A search shortcut commonly takes a selected phrase, places it into a search URL, and opens that URL. The part to check is the query value containing the phrase—not just whether the final URL begins with a web address. For example, if the search URL has the shape https://example.com/search?q=..., inspect the value after q=. The example domain is illustrative; use the actual search service and parameter your shortcut is built for.

Look through the shortcut actions from top to bottom. Find where the selected text enters the workflow, where the URL or search query is assembled, and the action that opens the URL. Apple’s Shortcuts guide explains that connected actions pass their output forward, and that a Quick Look action can preview the content moving between actions. (Action connections in Shortcuts on Mac; Testing your actions in Shortcuts on Mac)

Make selected text available to a Mac shortcut

If you are checking an existing shortcut, confirm it is configured to receive selected text. In Shortcuts, open the shortcut, open its Details, and enable Use as Quick Action or Show in Share Sheet. Apple says this adds an input action at the beginning of the workflow. Then select a phrase in an app and invoke the shortcut from the app’s share options or available Quick Actions. The exact menu depends on the app and how the shortcut is enabled. (Run a shortcut while working on your Mac)

A shortcut launched from the Dock does not receive content from the current app, according to Apple. If you launch it that way, it may run without the selection you intend to test. Check the shortcut’s input action and run it from a supported source app with text selected. (Run a shortcut while working on your Mac; Limit the input for a shortcut when run from another app on Mac)

Preview the completed URL before it opens

In the shortcut editor, insert Quick Look between the action that creates the final URL and the action that opens it. Run the shortcut with a harmless test phrase such as red & blue sky. Quick Look should show the output of the preceding action. This lets you inspect the constructed URL before the open action receives it; it does not itself validate that the search provider accepts the URL or interprets the query as intended. Apple recommends Quick Look as a way to identify what content flows between shortcut actions. (Testing your actions in Shortcuts on Mac)

Read the query value in the preview. In a typical percent-encoded query component, a space may appear as %20, and an ampersand that belongs to the search phrase may appear as %26. If the ampersand remains a literal & inside the value, a URL parser may treat it as the start of another parameter. This is a diagnostic example, not a guarantee about every search service’s query format. Apple’s own Shortcuts URL-scheme examples use %20 for spaces and explicitly describe supplied text as URL-encoded. (Run a shortcut using a URL scheme on Mac)

Check which action performs the encoding

Search actions in the editor for URL Encode and inspect whether it receives the selected-text variable before that value is inserted into the query. The action’s documented purpose is to encode or decode text for use in a URL by adding or removing percent escapes. (URL Encode) Apple also documents constructing URLs with the URL action and opening them with Open URLs or Open X-Callback URL, but its guide warns that URL schemes can require encoded text and may be difficult to debug. (Use another app’s URL scheme in Shortcuts on Mac)

The useful check is the action’s position and the preview, not simply the presence of an action with “URL” in its name. Confirm the selected text flows into the encoding step, and that the encoded result—not the original selection—is what gets inserted as the query value. Then confirm the Quick Look preview shows the expected escapes. Avoid encoding an already encoded value a second time: percent signs may themselves become encoded, changing %20 into %2520. That pattern in the preview is a clue to inspect the workflow for repeated encoding.

Interpret the result and its limits

If the preview shows escaped spaces and reserved characters inside the query value, that is evidence the assembled URL contains encoded text. If it shows raw spaces, the selected text may not have passed through an encoder, the wrong variable may have been inserted, or you may be previewing an earlier action’s output. If the phrase is missing, check the shortcut’s input and variable connections before changing its URL structure.

A preview can show the URL string the shortcut assembled; it cannot establish how a particular search service will process the query, whether the URL opens successfully, or whether the service applies its own rules. For a final functional check, remove or move the diagnostic Quick Look action and use the shortcut with a non-sensitive sample phrase. Apple documents the Mac controls for receiving content and opening URLs, but does not promise identical query behavior across search services. (Run a shortcut while working on your Mac; Use another app’s URL scheme in Shortcuts on Mac)

Sources