> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/earn-by-sharing/best-practices.md).

# Best practices

Six rules for sharing links without spending your audience's trust, including saying it is your link.

Short advice for sharing links while keeping your audience's trust.

## What works

1. Share things you would recommend anyway. If you would tell a friend about it for free, it is worth sharing with your link.
2. Tell people it is your link. One line does it: "I earn a commission if you buy through this." Honesty builds trust, and most platforms require it.
3. Give context. Say what the product did for you or who it is for. A link with a story beats a bare link.
4. Put the link at the end. Story first, link last.
5. Skip the spam. One thoughtful recommendation beats ten rushed ones.
6. Check your dashboard. See what people bought, then share more of that.

{% hint style="info" %}
Your audience is the asset. Every recommendation either builds trust or spends it.
{% endhint %}

## Common questions

<details>

<summary>How often should I share?</summary>

When it fits naturally. A product shared with real context once a month beats daily link drops.

</details>

<details>

<summary>Do I have to say I earn a commission?</summary>

Yes. It keeps trust with your audience, and most platforms and regulators require it.

</details>

Pick something you already recommend and start here: [lid.pro](https://lid.pro)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lid.pro/earn-by-sharing/best-practices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.