Partner With Link Emperor

Link Emperor Next Generation Link Building

The Next Generation Link Building system is intended to provide better results to our customers from building fewer but higher quality links. We expect that under this new system, you as a vendor will probably build only 1/3 as many links, but that's ok. We'll adjust payouts so that you are still able to earn under this system.

Rollout Plan

The Next Generation system (V2 Next Gen) will completely replace our existing system for link building. If you are already fulfilling under that system, we recommend that you build an entirely separate system on your side to accommodate V2 Next Gen.

Right now, the system is not live for any customers. Once 4 vendors fully implement V2 Next Gen, we will at that point make the system live and start transitioning customers to V2 Next Gen. The transition period will take from 3-10 weeks, depending on how well vendors handle the volume.

Once the transition period is over, we will terminate the previous vendor system and only offer V2 Next Gen.

To further incentivize switching, we will guarantee a minimum of $3,000 per month in vendor payouts for 3 months to the first 4 vendors to implement this system.

It is very much to your advantage as a vendor to be one of the first 4 to fully implement the new system.

So here's how to do it!

Integrating to our JSON API

Link Emperor uses a JSON based REST API. XML is available, but is deprecated and will not be supported in the future. All new implementations should use JSON, and vendors with current implementations should migrate to JSON.

To authenticate to the API, read this page. A reference guide to the vendor API is also available, and this guide includes the new methods described below. In that guide, "blasts" and "services" refer to the old system (v1) and "domains" and "target_orders" refer to the V2 Next Gen system described in this document.

The rest of this document assumes knowledge of basic REST API implementations and JSON.


Domains replace the old system's notion of Services. You'll no longer submit to us a list of Services.

You will now register the Domains on which you can build links. We will check statistics about the domain and approve or deny the domain based on those statistics.

In general, we're looking for very high quality domains. These should be domain that have some purpose and reason for existing beyond SEO link juice. Meaning it should have real traffic and ideally should rank in the SERPs itself.

Multiple vendors may submit the same domain. If the domain has already been approved for another vendor, it will auto-approve for you or any new vendors submitting that domain.

We track placement stick rates (how long a link stays alive) as well as other metrics for a given domain, and will score it accordingly. Better domains (better scores, longer link stick rates) will get preferential treatment for linkbuilding orders.

It is your best interests to maintain a very high quality domain list where links will stay alive for months, if not indefinitely. This will have a significant impact to the number of orders sent to that domain, which means more money for you, the vendor.

We will not accept IP addresses as domains.

Configuring Domains via the API

The first thing you'll need to do is build a domain management system. This system should be able to create a new domain, or activate/deactivate existing domains. You're free to use whatever technology you want on your side, but make sure that you have the ability to track which domains you've registered with Link Emperor.

To create a new domain, send a POST request to /api/v2/vendors/domains.json with a simple payload containing the domain name you wish to add, as well as whether you would like us to supply an article when ordering link building for this domain:

  "domain_name": "",
  "needs_article": "true"

You will get a payload back with details about the domain from our side. You should save at least the id element of this payload so you know our reference ID for the domain.

If you have an active domain that you no longer wish to get orders for, send a post request to /api/v2/vendors/domains/[id]/deactivate.json where you replace [id] with the ID number of the domain you wish to deactivate.

Similarly, to activate a deactivated domain, send a post request to /api/v2/vendors/domains/[id]/activate.json where you replace [id] with the ID number of the domain you wish to activate.

When building your initial implementation, you should add a handful of domains to use for testing purposes. When this system goes fully live we will grandfather in a number of existing domains.

Target Orders

Rather than Blasts, the V2 Next Gen system generates TargetOrders. A TargetOrder is simply a request to place a link to a specific URL with a specific anchor text on a specific domain. Compared to a Blast, these are much more specific. We are telling you exactly what we want delivered, and we expect that you'll deliver the exact link that was ordered, or if you are unable, we expect you to deactivate the domain using the domain deactivate method described above.

You will have a limited amount of time to fulfill the order. Once a TargetOrder has been submitted, we will validate the placement and mark the order completed or failed.

Each vendor will have a different amount of orders that can be outstanding at any given time. This is based on a variety of different factors, including the quality of the domains you can fulfill orders on, the length of time a link built stays active, and a few others that are TBD.

Whenever you are ready to build a link, simply ask our API for one or more TargetOrders.

You can get a new order with a GET request to /api/v2/vendors/target_orders/next.json with an optional batch size if you want more than one order at a time:

{ "batch_size": 10 }

If no orders are available, or you have too many unfufilled orders, you will get an empty JSON array back from that call.

For development and testing purposes, you should use sample orders, obtained by a GET request to /api/v2/vendors/target_orders/sample.json

For any order you will get a JSON payload back that describes the order. If you requested more than one order, you will get an array of order payloads.

  "id": 123,
  "domain": "",
  "target": "",
  "anchor_text": "sample anchor text",
  "status": "Reserved by VendorName, In Progress",
  "article_title": "Title",
  "article_body": "Body"

If you did not mark the domain as needing an article, we will not supply one.

To fulfill an order, send a POST request to /api/v2/vendors/target_orders/[id].json where [id] is the ID of the order you are fulfilling. The payload for this request is simply the URL to the page the link was built on:

{ "placement_url": "" }

Start Building Your Apps Now

V2 Next Gen will go live once 4 vendors have built support for it within their systems. We are also guaranteeing a minimum of $3,000 per month in vendor payouts for 3 months to the first 4 vendors to implement this system, so don't delay.

Getting Support

Jeremy Noetzelman from our team is leading the vendor integration support for this project. For any questions, please email [email protected] We look forward to getting this rolled out as soon as we can.