UI Elements
Do Links Inside Body Text Get Clicked? A/B Test Idea
An inline link offers a route where the surrounding text introduces the topic. A separate button may stand out more but sit outside the reading context. This comparison changes placement and visual treatment together in one defined implementation; it does not isolate their individual effects.
A/B test scenario. This page is a test plan, not the result of a real experiment.
- UI elements
- Completion of the destination action
Option A vs Option B
Two alternatives; neither is the incumbent.
- Changed
- Options
- Page
- UI elements
- Difference
- changed
Hypothesis
If the route sits inside the paragraph where the text introduces the topic, readers can follow it without leaving the reading context; a separate CTA button below the paragraph stands out more but sits outside that flow. That could leave the button with more clicks and the inline link with higher completion of the destination action.
Test plan
When to run this test
A heatmap where the route is skipped, scroll data where readers finish the paragraph and leave, or route traffic that rarely completes the destination action suggest readers miss the route; that is the moment to compare a button with an inline link. If the inline link works better, readers reach the linked content and complete the action there; if the button works better, its visibility opens the route to more visitors. If the destination page is slow or does not deliver what the link promises, fix it first.
How to measure success
Completion of the destination action
Compare completion of the predefined destination-page action among eligible assigned visitors exposed to each link presentation.
Also track
- Inline-link click-through rateMeasure clicks on the tested inline link.
- Destination-page arrival rateCompare visitors who reach the linked content.
- Action completion after arrivalCompare completion of a predefined action on the destination page over the same follow-up window.
How to set it up
- ImplementationCompare the same CTA below the paragraph with a link placed within the paragraph.
- Link locationChoose one inline position; keep paragraph meaning and wording unchanged.
- VisibilityUse a clear link style without changing surrounding typography.
- ProgressTrack completion at the destination, not just exits from the source page.
- AudienceUse predefined segments; do not define audience based on behavior changed by the test.
What to watch when reading the result
- 1Do not name a winner because the inline-link click-through rate or the destination-page arrival rate is higher. Let completion of the destination action choose between them, and compare action completion after arrival for both options across an equal follow-up window.
- 2This comparison changes placement and visual treatment together, so do not credit the difference to either one. Use a single link in the paragraph and give it descriptive text that says where it goes, not a vague "click here"; otherwise you cannot tell which link or wording did the work. Retest before applying the result beyond the page and paragraph type you tested.
- 3The destination action happens far less often than a click, so a small difference only becomes readable once the test has run long enough to collect it. Enter the expected rate of the destination action and the effect you care about in the sample size calculator up front to get the visitors you need per arm.
Frequently Asked Questions
Does this test isolate placement from visual format?
No. It changes both in one defined implementation. Interpret the combined effect rather than attributing it to either component alone.
Does a higher inline-link click rate mean it won?
No. Track arrival at the destination as an intermediate step. Use completion of the predefined destination-page action as the primary outcome.
How should the link be placed within a paragraph?
Fix one location and preserve the paragraph's meaning and wording. Use a recognizable link style without changing surrounding typography. Avoid vague text such as click here.
More tests in UI Elements
All testsAdding Shortcuts for Frequent Actions: A/B Test Idea
UI elementsSuccessful task completion rate
An experiment example adding shortcuts such as reorder or reload last search. See the control, the shortcut arm, the trade-offs and the tracked KPI.
Auto-Advancing to the Next Step: Flow A/B Test Idea
UI elementsFlow completion rate
A multi-step flow experiment example: manual continue versus auto-advance once a choice is made. See both arms, the control-and-undo notes and the KPI.
Site-Wide Campaign Announcement Bar A/B Test Example
UI elementsCampaign action completion rate
Adding a time-boxed announcement bar across every page, framed as an experiment example with both arms, the banner-blindness risk and the KPI.