Decide what the visitor should reach and whether that destination is already published. Prefer labels such as View hosting plans or Request a quote over vague text that makes sense only beside an image. If several buttons appear together, distinguish the main action without hiding the alternatives.

1. Insert a Buttons block in the intended section, then add a Button inside it.
2. Enter the label and use the link control to select an existing page or enter the complete destination URL.
3. For an anchor destination, use the correct page address and hash. For a normal internal page, avoid accidentally copying a private preview link.
4. Adjust the supported style, alignment and spacing. Select the outer Buttons block when changing the arrangement of several buttons, and the individual Button when changing its text or destination.
5. Save and preview the page before publishing the change.

Open the published page while signed out and follow the button. Confirm the correct protocol, domain and destination, including any query parameters that are genuinely required. Check that a mobile visitor can read and activate the button comfortably and that a keyboard user can see focus.

Use a new tab only when there is a clear reason, and make that behaviour understandable. Opening every internal page in a new tab can make navigation confusing.

For a page that introduces NabWP, configure the individual Button inside the Buttons block. These values create a clear route to the product information; they do not submit a hosting order or activate a trial.

Save the page, open its public address while signed out and use the button. Confirm that it reaches the current NabWP product page. Then use the keyboard to focus the button and check that the focus indicator is visible. On a phone, check that the complete label remains readable and the button does not overlap nearby text.

Expected result: the label accurately describes the destination, and the same link works in the published page as in the editor.

Check whether it has a saved link and whether another positioned element covers it. A link to an unpublished page can work for an administrator but fail for the public. If the destination redirects unexpectedly, inspect that page's redirects separately rather than repeatedly recreating the button. For payment or account actions, use the intended application URL and avoid placing sensitive credentials or private tokens in the link.

• Creating jump links with HTML anchors in WordPress
• Creating reusable calls to action with patterns
• Previewing mobile layouts before publishing
• Adding downloadable documents with the File block

• WordPress: Buttons Block
• WordPress: WordPress Block Editor