Pebellslearn by building
0%
RoadmapsMatrixCoursesSandboxSign in
Best Practices  ›  Capstone Project

Calls to Action and References

Call to Actions 13 minA page should end with one specific next step matched to the reader's stage, and every claim in it should link to a checkable, preferably primary, source.

Calls to Action and References

Nightjar's quick start ends with "That's it!" Priya now has one monitor and no verified alert email, so when her site goes down, nothing will reach her. The page stopped one step before the step that matters. Meanwhile, a blog post claims that "most outages last over an hour" with no source. A reader asks "says who?" in the comments, and the post loses its credibility.

The rule

End with one clear next step, and back every claim with a source.

A call to action (CTA) tells the reader what to do next. Good ones share four traits:

  • One main action, not a wall of ten links.
  • A specific verb that says what happens: "Verify your alert email", not "Continue".
  • Matched to the reader's stage. After a quick start: the next setup task. At the end of a blog post for people evaluating tools: "Start a free account". On a troubleshooting page: "Still stuck? Contact support and include your monitor ID."
  • Link text that makes sense alone. Screen-reader users often jump from link to link, and "click here" tells them nothing.

References let readers check what you say and go deeper:

  • Every statistic, quotation and surprising claim needs a source.
  • Cite the primary source, the study, official documentation or standard itself, not a blog that summarised it. When explaining HTTP status codes, for example, link the HTTP specification.
  • Add a date to anything time-sensitive, and check old links still work.
  • If you cannot find a source, cut the claim or narrow it to what you can support.
  • Keep "Related pages" short: two or three links that genuinely come next.

The shortcut

Read the page twice. At the end, ask "What now?" At every claim, ask "Says who?" Any page that cannot answer both is unfinished.

Finishing the quick start and the blog postStep 1 of 4
  1. What now?

    The quick start ends at "That's it!", but alerts cannot reach Priya until her email is verified. New ending: "Next: verify your alert email so Nightjar can reach you."

The traps are the vague ending ("Learn more", "Thanks for reading") and the orphan claim that nobody can check.

Drills

Answer fast — trust the rule.

quick drill

Which is the best ending for Nightjar's quick start?

quick drill

Which link text is best?

quick drill

A statistic you want to use appears in a blog post that quotes a research report. What should you cite?

quick drill

You cannot find any source for "most outages last over an hour". What do you do?

quick drill

What is the right call to action on a troubleshooting page, for readers whose problem the fixes did not solve?

Remember

  • End with one clear next step, and back every claim with a source.
  • Shortcut: ask "What now?" at the end and "Says who?" at every claim.
  • Trap: vague endings like "Learn more", and claims nobody can check.

Practice — level up

0/1 solved

Write your answer, then compare it with a rubric and a model answer.

ExplainFinish a page properly

Nightjar's "Add a Slack alert channel" guide stops right after the last setup step. Its introduction also claims: "Slack is where most engineering teams handle incidents." Write a better ending with one call to action, and explain how you would handle the claim and any references.