Documentation
Match requests
How reaching out works
You introduce yourself to a member: a few lines on who you are and why their site caught your eye. If you already know exactly what you want, you can add the details too (your page, the type of collaboration, the page on their site, the anchor), but you do not have to. They accept or they decline. If they accept, a conversation opens with your original message already in it, and you take it from there. If they decline, you are told, with a short note if they chose to add one.
You cannot send a second request to somebody who already has one waiting from you, and you cannot send one to somebody you are already talking to.
Requests count against your allowance, replies do not
Your plan gives you a number of monthly requests, and the allowance resets on the first of the month.
A request is used when you send, not when they accept. This is deliberate. Charging on acceptance would make a request free to fire off and would fill everybody's inbox with copy-paste, which is the failure mode we watched happen elsewhere. Using the request up front means you send fewer and mean them.
Receiving and accepting always costs nothing.
If a request is declined, it stays used. If nobody answers at all, the request expires after fourteen days, we email you, and it comes back to you.
Each card shows when the member was last active: today, this week, this month, or not recently. Never the exact time. You can also show only members active in the last 30 days.
If you receive a request, we remind you by email after three days, and again four days before it expires. At most one email a day.
A request that would be refused, because the member is unavailable or has set requirements you do not meet, is stopped before it counts.
Once it is accepted
A conversation opens containing the message you sent. If you added details, they are carried over as a starting point, but they are not yet an agreement. If you did not, you agree on everything in the chat.
In the conversation you can also send images, such as a screenshot of a page or proof that a link is live: up to 4 per message, JPEG, PNG or WebP, 5 MB each. Only the two of you can see them. A request itself is text only.
Agreeing is a separate, explicit step, and it is covered in Collaborations.
Requirements members can set
Members can decide who is allowed to contact them. The simplest is to accept requests only from verified profiles. Beyond that, a member on premium can set a minimum Authority Score, a minimum traffic figure, a matching niche, a particular traffic country, or a minimum share of traffic from that country.
When those requirements involve sites, they all have to be met by one single site you own, not spread across several.
If you do not meet them you are told, without the specific numbers. Members set their own bar and do not have to publish it.
Being unavailable
There is a switch on your profile that marks you as unavailable. While it is off, nobody can send you a request. Use it when you are busy rather than letting requests pile up unanswered, which costs the sender one of their monthly requests and gets them nothing.
What you cannot do
A request cannot be taken back once sent. There is no undo, and it does not come back to your allowance. It comes back only if the request expires unanswered after fourteen days. Write it before you send it.