for agencies
Before an agency puts a client's domain on the network, somebody on the team asks these questions. Here are the honest answers, checked against how the matching actually works rather than how we would like it to sound.
There is no cap, in either direction. How much moves in a month tracks your own publishing pace and your token balance, since receiving is funded by giving. A domain that publishes often and keeps giving can move quickly; a quiet domain will see less. That is a description of the mechanics, not a ceiling anyone has to ask us to raise.
The one honest caveat: a domain that suddenly starts producing content at an unnatural rate for what it normally publishes is something our review can flag, and in a serious case it can cost that domain its place in the network. Ordinary publishing, even a genuinely busy month, is not what that is aimed at.
Yes, with one condition. Your home page and the pages describing what you do (service pages) are eligible to receive a link, but only with a branded anchor: the anchor text has to be your business's own name or your domain, for example "Peak Outdoor Supply" or "peakoutdoorsupply.com", never a commercial phrase like "best roofing contractor". Product and catalog pages are never eligible, on either side of a link.
The trade-off is that a home page or a service page only ever receives. It cannot be the page that hosts an outbound citation to somebody else; only your articles do that.
On the giving side, that is entirely your call. Matching runs on relevance, and every suggestion, whether it comes from a new exchange, an Existing Opportunities suggestion, or a content bridge, arrives as a proposal your writer sees before anything happens. Nothing is ever placed for you: the agency is the gatekeeper. If a suggestion happens to point at a competitor, decline it and it dies right there. Declining costs nothing.
Receiving works differently, because it is automatic once another site's writer accepts a suggestion and the link is confirmed live; there is no veto beforehand. What stands in for one is the review every site goes through before it can give or receive at all, so any inbound link came from a site that passed the same gate your domain did. The source is visible on your Links received page the moment a link goes live, and each domain has a receiving switch that turns off new inbound links to it entirely.
The one place we refuse a same-trade pairing outright is local links: a roofer and a landscaper in the same city can be introduced, but two roofers in the same city never are. That structural refusal does not extend to links decided by what an article says; there, relevance decides and your review is the control.
Not before it happens. Receiving is automatic: once the other site accepts a suggestion and the link is live and checked, it shows up on your Links received page with the source domain and URL, the anchor in context, and the DR and UR it had when it was placed. The argument for that shape: every site that could link to you passed the same review your own domain did before it joined, so there is no second gate needed after the fact.
What you can control is whether you receive at all. Each domain has a receiving setting, and turning it off stops new inbound links to that domain completely. It does not touch links that are already live.
You cannot browse an inventory of subscriber sites and pick by DR; that is deliberate. A browsable list would let anyone map who is on the network by submitting drafts and never actually placing a link. What you do see: every suggestion shows the other site's tier band, one of 5 bands from Emerging to Authority, alongside the passage it would cite, before you commit to anything.
The public categories page shows the shape of the taxonomy, not a directory of subscriber sites or an aggregate DR figure for the network. If a category depth or a network-wide DR breakdown would help you evaluate the network before joining, ask; that is not something any screen shows today.
Each row: the date, the source domain and its URL, the anchor in its surrounding sentence, a strength badge for the giving site's tier, and a status. Above the rows: links live, what is new since last month, a links-staying-live meter checked monthly for 6 months, and the client domain's own DR.
The report carries no branding of ours. You can add links you built outside the network by hand, so one link tells the whole story of a client's profile instead of just our slice of it.
Two setups, and both work. Most agencies run the account directly: invite your staff onto it and everyone works from the same suggestions and the same reports, signed in as themselves; only the account owner can touch billing or invite people. Domains and content stay shared across the whole team.
The other setup is the client's own writer using the WordPress plugin on their own site, with an API key scoped to that one domain. A key lifted from one client's install is useless against the rest of an agency's roster. You can mix both: run some domains through the console yourself and hand a scoped key to a client's writer for the rest.
They stay. Releasing or cancelling a domain does not touch links other sites already published pointing at you, or links you already gave that are live on other sites; nothing gets deleted. Every link carries a 6-month guarantee against going dead while it is being monitored, and a released domain's own placements keep being checked for 90 days after release for exactly that reason, so a link does not quietly die the week after you leave with nobody watching.
No. The plugin's interface only loads inside your WordPress admin, while you are signed in and writing or reviewing a post. It does not add a script, a stylesheet, or any markup to the pages your visitors see, and there is nothing on your site's front end for a casual visitor, or a competitor, to notice.
We went one step further, because the people we most want as members are the ones who will check. WordPress normally lists every installed plugin's API namespace on a public endpoint, so anyone probing a site can see what it runs. The current plugin removes itself from that listing and answers outside probes exactly the way a site without the plugin would. From the outside, a subscriber site is indistinguishable from any other WordPress site.
No, and it should not be the only thing you do. These are one component of a natural profile, not all of it. Every anchor comes from the sentence the other site's writer actually wrote about your page, so you get real variety: a business name here, a descriptive phrase there, never a list of exact-match keywords rotated on a schedule. Nothing here replaces directories, PR mentions, or guest posts you place yourself; it is a citation source you add to what you are already doing.
Next: Agencies and teams →