$100 Website Offer

Get your personal website + domain for just $100.

Limited Time Offer!

Claim Your Website Now

A Beginner’s Primer on Disclosing Your Own Stake on a Website

If you run a website, you eventually recommend something: a hosting plan, a theme, a plugin, a payment tool, a course for your visitors. This beginner primer explains how to tell visitors what you gain from those recommendations, where on a page the statement belongs, and how a content management system can help you apply it consistently. Technical background is not needed; a mini-glossary closer to the end explains the vocabulary.

The principle in one paragraph

Visitors read a recommendation differently depending on the relationship behind it. A plugin suggested by someone who built it carries a different meaning from one suggested by an unconnected user. Stating the relationship, briefly and in ordinary words, lets the visitor judge your advice accurately. The statement concerns any interest you hold: a free copy, a payment per signup, a working arrangement, or a share in the business concerned.

Why site owners need a deliberate system

On a single page, mentioning your stake is easy. On a site with hundreds of entries, written by several people over several years, it becomes a maintenance matter. A recommendation from an old post may still sit in a sidebar. An author who joined later may not know your habits. A visitor can land on any page, so each page must stand on its own.

This is why the practice belongs in your publishing process rather than in an afterthought. The same reasoning drives our advice on the core pages a company website needs to have: structure decided early saves repair work later.

Step by step: building the habit into your CMS workflow

  1. Keep a register. Maintain a short internal list of the products, companies and services you link to, with the type of relationship next to each one.
  2. Write a standard sentence per relationship type. One for items you bought, one for items you were given, one for links that earn a payment, one for partners and employers.
  3. Store the sentences as reusable blocks. Most editors let you save a snippet or reusable block; drop the correct one next to the recommendation.
  4. Add an editorial check. Before publishing, the reviewer asks whether any link or product in the draft appears in the register.
  5. Revisit older pages. When you update an article, re-read its recommendations against the register.

Where on the page it belongs

Place the statement near the first recommendation, not only in a site-wide footer. A footer note can supplement this, yet readers rarely scroll to it and many arrive from search straight into the middle of a page. A short sentence above the relevant section, or within the introduction, reaches the person who needs it. On service pages, where you describe what you offer, say who the partners behind a component are, in the same plain voice you use for the rest of the copy. Our piece on service pages that persuade visitors to get in touch describes the tone such pages call for, and this sentence fits comfortably within it.

What the sentence should and should not contain

  • Include: the type of relationship (given, paid, employed, owned) and the party concerned.
  • Include: a word on how it affects you, if it is not obvious, such as “I receive a payment when you sign up”.
  • Avoid: technical or ceremonial phrasing that obscures the meaning.
  • Avoid: burying the sentence within a long paragraph where it cannot be found.

Sponsored content and campaign work

Some site owners publish material that a brand has funded. Platforms exist to arrange this. One such venue is CollabGigs, whose site outlines a marketplace pairing brand-funded promotional campaigns with bloggers, video makers and other independent publishers. If you take such work on, apply the same rule with more prominence: the first lines of the post should state that it came from a paid campaign. The reader should never have to infer it from the writing style or the placement of links.

Mini-glossary

  • Affiliate link: a web address carrying a code that credits you when a visitor completes a purchase or signup.
  • Sponsored post: an article that a company paid for or funded, published on your site.
  • Gifted item: a product or service given to you without charge, whether or not you must write about it.
  • Referral credit: a discount, balance or perk granted to you when someone joins through your recommendation.
  • Reusable block: a saved piece of content in an editor that you can insert wherever needed and update in one place.
  • Register: your internal list of relationships, kept outside the public site.

A worked example of the register and the sentences

Suppose a small agency site recommends three things in one article: a form plugin its team built, a hosting provider whose partner programme pays the agency, and a design course the agency simply bought for staff. The register would list all three with their relationship type. The article would then carry three short sentences: “We built this plugin ourselves”, “We receive a payment if you sign up with this host”, and “We bought this course with our own money and have no other link to it”. The third sentence is worth writing too, since it tells readers that the absence of a tie is also a fact.

Common beginner questions

Does stating a tie lower the value of my recommendation? Generally readers adjust their weighting rather than reject the advice. Clarity tends to make the remainder of the page more credible.

What if the relationship is small? If it could influence how a fair reader would weigh your words, state it. Small ties are the ones most often forgotten.

Do I need a developer? No. A register, a handful of saved snippets and a pre-publication question are enough for most sites.

Summary

The practice has three parts: know your relationships, phrase each one plainly, and place the sentence where readers will see it. A modest amount of structure in your CMS turns that into a routine instead of an act of memory, and it keeps every recommendation on your site accompanied by the information a visitor needs.

Related Posts

Page Cap, Plugin Cap or Palette Cap: Which Site Limit Fits?

A friendly comparison of three self-imposed limits for CMS builds, covering pages, plugins and palettes, with when each one helps and where it hurts.

Read More

Near Misses as a Career Skill for Web Developers

Why handling a caught mistake well is a learnable skill for CMS and web developers, and how to show it in a portfolio or interview.

Read More

Five Website Clean-Up Myths That Keep Your CMS Cluttered

Five comfortable beliefs about website housekeeping, and the simpler habit that replaces them: trim drafts, plugins and media files as you work.

Read More

Website Teardown Checklist: Audit a Finished Business Site First

A practical five-part checklist for taking apart a finished business website, structure, content, navigation and technical clues, before you plan your own CMS build.

Read More

Eight Plain-Word Fixes for Clearer Website Copy and CMS Labels

Menus, buttons, error messages and admin fields often use insider words. Eight practical fixes, each with a before and after, to make your site easier to read.

Read More

Why Web Projects Slip: Diagnosing the Unchosen Trade-Off

Late, over budget and still rough? A diagnosis-first look at web projects that never decided whether speed, cost or quality would give, plus the written fix.

Read More
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x
()
x