> 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/sell-on-lid/your-product-page.md).
# Your product page
What buyers see on your product page, what you can change, and the three lines that sell.
Every product gets a public page at a link that starts with `lid.pro/p/`, followed by the product's own address. It is where buyers land and where checkout starts.
## What buyers see
* Your title and description
* Your product image
* The price
* A **Buy now** button. Visitors who are not signed in see **Sign in to buy**.
* Any free preview files you added
* A box that says the product can be shared, with your commission per referred sale, and a **Promote and earn** button so anyone can share your product and earn the commission you set
## What you can change
* Title, description and price
* Product image and gallery
* Delivery files, free previews or access link
* The commission you share
* Whether the product is listed in Explore or only reachable by its link
Edit any of these from **My store** in your dashboard. Changes go live right away. A new price applies to the next sales; past purchases stay as they were.
## Three things that sell
1. Say what it is in one sentence.
2. Say who it is for.
3. Say what they walk away with.
## FAQ
Do sharers need my permission?
They join on their own. Anyone can generate a share link from your page and earn the commission you already set, on sales they bring.
Ready to put a page up? Start at [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/sell-on-lid/your-product-page.md?ask=&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.