Website publishing
Registering More Than One Website
How domains, subdomains, language versions and client sites map to the partner dashboard, what 'own or authorized to operate' means, and how to keep numbers readable.
Many people who run one site end up running several: a main site, a blog, a language version, a kids' section, a client's site. The PlayKovo partner program allows registering websites, and the dashboard shows launches from each registered domain. This post explains how that works with more than one site and how to keep the numbers clear.
What the terms say about registration
Three points from the Partner Terms matter here:
- You may register only websites that you own or are authorized to operate.
- The information you give (name, contact email, website address) must be true, complete and kept up to date.
- Websites are registered automatically. That is not a review, approval or endorsement of your site, and it does not limit PlayKovo's right to act under the terms.
The terms define "Your Site" as each website or app where you place embeds or feed data. So the rules apply to every one of your sites, not just the first. The docs page also says you register the exact domain that shows the iframe, and that the dashboard reads your domain from the referrer of the page containing the iframe. (The documentation also mentions review of domains, while the terms describe automatic registration. For the current behaviour, check the dashboard itself, and ask [email protected] if it differs.)
What counts as a separate site
The dashboard works from the domain it sees. In practice:
| Situation | How to think about it |
|---|---|
example.com and blog.example.com | Different hostnames. Register the one that shows the iframe, and check whether you want both listed. |
example.com and example.org | Different domains. Register each one that shows games. |
example.com and example.com/kids | Same domain. Paths are not separate sites, so use your own analytics to split them. |
| A staging site and a live site | Register only the live site you operate publicly, and keep test pages out of the numbers if you can. |
| A client's website | Only if you are authorized to operate it. See below. |
Working for clients
If you build sites for others, the safe reading of "own or authorized to operate" is that you may register a client's site when the client has agreed and you run it for them. Put it in writing in your contract. You also take on the responsibilities in section 8 for that site, such as having a privacy policy and meeting the laws that apply, so make sure the client understands that the games come with PlayKovo's terms attached. Keep a record of which sites you registered under which account, and how to remove them if the client leaves.
Do not register a site you do not control to see what the dashboard looks like. Section 7 lists doing that among the prohibited actions.
One account or several?
Use one partner account per organization or person responsible for the sites. A single account with several registered sites is easier to manage. Separate accounts make sense when different legal entities run the sites, or when a client should own their own dashboard and contact. Whatever you choose, use a contact address that is read; the terms ask you to keep your details up to date, and PlayKovo may need to reach you about a game or a complaint.
Keeping the numbers readable
- Name your sites clearly in your own notes, and match them to domains in the dashboard.
- Keep the embed unchanged on all sites, with no
referrerpolicyrestriction; see why the referrer matters. - Remember that launches only count when the visitor accepted cookies, and that "players" are browsers, not people. Compare sites with those limits in mind; see why the dashboard shows fewer launches.
- If the same game runs on two sites, expect each to have its own count; do not add them up and call the total unique people.
Language versions and subdomains
If you publish the same games in several languages on different subdomains or domains, consider whether each deserves its own game text. Game descriptions in the feed come in one language per game (the language field), so a translated site needs its own wording for the surrounding page. Keep titles accurate and do not rename games in a way that would hide which game it is.
When a site leaves
If you sell, close or hand over a site, remove the embeds first, or make sure the new owner accepts the terms themselves. The embeds and registration are tied to your account, and the license is non-transferable. The seven-day removal rule in leaving the program applies to the site in question.
Start from the partner page and the catalog documentation.


