Choose the Right Action Verb for Your Creator Button

Inspect what happens after the tap

Start by opening the destination as a visitor would. Do not write from memory or from your intention for the resource. A recording may exist, but if the linked page only offers a request form, requesting is the action available there.

Complete this sentence: “After tapping, my audience can immediately…” Describe the meaningful action, rather than merely saying “visit a page.” They might play a recording, watch an excerpt, read notes, download a worksheet or submit a request.

GOV.UK’s button guidance recommends describing the action performed. Applied to a creator-page link styled as a button, that means naming what the destination lets someone do rather than reaching for the most exciting verb.

• Open the exact URL attached to your button, preferably without your creator account signed in.
• Identify whether the destination contains the full resource, a sample, information about it or a way to ask for access.
• Note any required step between arrival and access, such as submitting a form or waiting for your reply.

Choose the verb that fits the available action

Use “Watch the interview” when the destination provides the complete interview ready to play. Use “Preview the interview” when it provides an excerpt. Preview is not a weaker version of watch; it communicates a different scope.

Use “Request a portfolio critique” when someone submits work for your consideration. Use “Book a feedback session” when the destination lets them select and confirm an available session. A request that you must review is not yet a booking.

Choose “Read my process notes” for notes presented on a page and “Download the shot worksheet” for a destination that offers the worksheet file. If the page only explains the worksheet, “Explore the shot worksheet” may fit better, though making the description more specific is preferable where space allows.

When a destination offers several actions, name the one that best describes its main experience. An excerpt followed by an optional request form can justify “Preview the walkthrough.” A page centered on an access form calls for “Request the walkthrough.” Do not select the verb merely because that option exists somewhere on the page.

Keep the resource name recognizable

Separate the action from the resource name. If your post introduces a “shot worksheet,” keep those words on your profile page rather than renaming it a “production toolkit.” You can correct the action without making visitors wonder whether they have found a different resource.

W3C identifies close agreement between link text and the destination title as useful continuity. Carry that principle through the journey: post, profile-page button and destination should refer recognizably to the same thing.

Write the noun first, then test the verb. “Interview” raises the question “Watch or preview?” “Portfolio critique” raises “Request or book?” This keeps the wording anchored in the actual resource instead of an abstract promise such as “Transform your work.”

Repair the whole promise in a worked example

Consider an illustrator preparing a post that says, “Watch my full sketchbook walkthrough through the link in my profile.” The profile-page button reads “Watch the walkthrough,” but its destination contains an excerpt and a form requesting the complete recording.

The mismatch involves the whole journey. The post promises the full walkthrough, the button suggests it is available to watch, and the destination offers only a preview plus a request. A more accurate button helps, but it cannot fulfill the post’s original promise.

There are two clean corrections. If immediate access is intended, link to the full recording and keep “Watch the walkthrough.” If previewing and requesting are intentional, update the post and button together. This preserves the experience without describing it as something else.

• Record the promise: “The full sketchbook walkthrough is available to watch.”
• Record the destination: “An excerpt is playable; the complete recording must be requested.”
• Revise the post to: “Preview my sketchbook walkthrough, then request the full recording.”
• Change the button to: “Preview the walkthrough.”
• Add nearby text: “Watch an excerpt. Request the full recording on the next page.”

Decide when a label change is enough

A label change is enough when the post already describes the experience accurately and the button is the only misleading part. For example, a post inviting people to request a critique can lead to “Request a portfolio critique” instead of “Get your critique,” with no broader rewrite needed.

Change the destination when the promised action is correct but you linked to the wrong place. Change the post when the intended destination cannot deliver what the post offers. Adding small explanatory text below a button should not become a workaround for a contradictory headline.

There is a real space tradeoff: precise wording can be longer. Keep the word that distinguishes a preview from a complete resource or a request from a booking. GOV.UK’s guidance allows extra words when they describe the action more accurately. Remove decorative language before removing that distinction.

Check expectations before publishing

Show someone the button and ask what they expect to find after tapping. Then compare their answer with the destination. Ask about access as well as content: do they expect to watch now, submit a request or receive something later?

Also read the label without the post. W3C explains that assistive technology can present links in a list, making meaningful wording useful outside the surrounding page. Its guidance allows link purpose to come from link text together with programmatically determined context; this check is a practical writing aid, not a requirement that every label explain everything.

Save a compact worksheet for future links: resource name, post promise, destination action, access step, chosen verb and any required post correction. Finish with one question: after tapping, would the visitor find the action your button named?