> For the complete documentation index, see [llms.txt](https://wiki.playgama.com/playgama/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.playgama.com/playgama/guides/deploy-a-game-on-your-own-domain/deploy-with-playgama-wrap.md).

# Deploy with Playgama Wrap

## What Wrap gives you

Playgama Wrap turns your HTML5 game into a website of its own. You fill in the game's content once in the developer console; Playgama generates the site, hosts it on a global CDN, and serves it on your domain.

Everything below works out of the box, with nothing to integrate:

* **Monetization** — Playgama Ads, with high eCPM, is enabled from day one.
* **Ready-made UX** — sign-in, in-game purchases, a PWA version and sharing.
* **SEO** — meta tags, structured data and share previews are generated from the content you fill in, and the form gives you everything you need to tune how the site ranks in search engines.
* **Player analytics** — player behaviour on your own domain, in your developer cabinet.

Wrap is free. The game must meet the Playgama [game requirements](/playgama/game-requirements.md).

{% hint style="info" %}
**Early access** — Wrap is rolling out to all developers through autumn 2026.
{% endhint %}

## Before you start

1. **The game integrates the Bridge SDK.** See [Getting started](/playgama/bridge-sdk/getting-started.md).
2. **The game is uploaded to Playgama** and has at least one successful build in your developer cabinet — the site runs that build.
3. **Wrap is available for the game.** Wrap is being opened up to every developer — if you do not see it on your game yet, it has not reached your account yet.
4. **You own a domain** (or are ready to buy one). It can be a root domain such as `coolgame.com` or a third-level one such as `play.example.com`. You can fill in the site and check it without a domain, but the site becomes publicly reachable and indexable by search engines only on a domain of your own.

## How it works

```
 I. Integrate the bridge   →   II. Upload the game   →   III. Configure & publish
    (Playgama Bridge SDK)          (developer cabinet)      (Standalone site + domain)
```

Stages I and II are the regular Playgama flow. Everything below is stage III.

## Step 1. Start the setup

Go to [developer.playgama.com](https://developer.playgama.com/) and open your game. Among the platforms of the game there is a new one — **Standalone site**. Press **Setup** next to it.

This opens the content form and creates the website draft, pre-filled from your game card in the cabinet. Everything you edit from now on lives in the draft — the published site does not change until you publish a new version.

## Step 2. Fill in the content

The form is split into sections. Required fields are what the site cannot be built without; the recommended ones are what makes the site rank and convert, so treat them as part of the job rather than as optional extras.

### Content

| Field             | What to write                                              | Requirements                                          |
| ----------------- | ---------------------------------------------------------- | ----------------------------------------------------- |
| **Game Title**    | The main title of the game, shown as the site heading.     | Required                                              |
| **About Game**    | The core game loop and target audience. HTML is supported. | Required                                              |
| **How to Play**   | How the game is played on desktop and on mobile.           | Required                                              |
| **Game Features** | Levels, skins, bosses, game modes — one item per line.     | Recommended, at least 3                               |
| **FAQ**           | Question/answer pairs with tips about the game.            | Recommended, at least 3 pairs with both fields filled |

### Meta and SEO

| Field                                | What to write                                                | Requirements                             |
| ------------------------------------ | ------------------------------------------------------------ | ---------------------------------------- |
| **HTML Title**                       | Browser tab title of the site.                               | Required, best kept under 65 characters  |
| **HTML Description**                 | Short SEO description of the game.                           | Required, best kept under 160 characters |
| **Genres**                           | List of genres; the first one is the main genre.             | Recommended, at least 1                  |
| **Links to game on other platforms** | Pages where the game is already published (stores, portals). | —                                        |

{% hint style="warning" %}
Both meta fields have to be filled in, but their length is not a hard limit — a longer title or description does not block publishing. It is still worth staying under 65 and 160 characters: beyond that, search engines cut the text off in their results.
{% endhint %}

### About Developer

| Field                                        | What to write                            |
| -------------------------------------------- | ---------------------------------------- |
| **Developer Name (nickname) or Studio Name** | Shown as the game author on the website. |
| **Developer website**                        | Link to your studio or personal page.    |

### Game images

The cover, icon and share preview of the generated website.

| Image                            | Used for                                                           | Requirements                                  |
| -------------------------------- | ------------------------------------------------------------------ | --------------------------------------------- |
| **Horizontal game cover** (hero) | The main image on the site.                                        | Minimum width 1280 px, aspect ratio 16:9      |
| **Game icon**                    | The game icon in the interface, the site favicon and the PWA icon. | Minimum 512×512 px, aspect ratio 1:1 (strict) |
| **Open Graph Share Image**       | The snippet in messengers and social networks.                     | Minimum width 1280 px                         |
| **Gameplay Screenshots**         | The screenshot gallery on the site.                                | At least 3, minimum width 1280 px each        |

Click the upload area or drag & drop the file. The console validates the size and the aspect ratio right after the upload and shows an error if the image is too small or has the wrong proportions.

Give every screenshot a short caption describing what is actually happening on it — the captions are part of the page text and help the site rank in image and web search.

## Step 3. Publish and check the site

Press **Validate and publish**. If all required fields are filled in, the site starts building; otherwise the form points at what is missing.

Building takes a while. When it is done, the site is available on a technical hostname of the form `<game>.wrap.playgama.com`. That address is **closed to search engines**, so it is a safe place to look at the result — it exists for checking, not for traffic.

Open it and go through the site: texts, images, the game itself, how it looks on a phone. Anything you want to change goes back into the form — see [Step 5](#step-5-update-the-site-later).

## Step 4. Connect your domain

The technical hostname is not indexed, so a domain of your own is what turns the build into a real site. Domains are managed in the **Domains** section of the same page. Press **Add domain**, enter the hostname, and pick how the domain is connected. After adding it, the console shows the exact DNS records to create — copy them from there, they are generated per domain.

### CNAME (subdomain)

For a subdomain such as `play.example.com`. In your DNS panel, create the record shown in the console:

```
Type: CNAME
Name: play.example.com
Value: <target shown in the console>
TTL: Auto
```

That single record is all that is needed — the CNAME points the traffic at Playgama, and the certificate is issued automatically. Nothing else about the domain changes, so this is the right option when the domain also runs your mail or other sites.

### Root domain delegation

For a root (apex) domain such as `coolgame.com`, which cannot hold a CNAME. Here the DNS zone of the domain moves to Playgama: the console assigns **two nameservers**, you set both of them at your domain registrar, and from that moment the zone is served by Playgama's infrastructure.

{% hint style="warning" %}
Delegation takes over the whole domain: the DNS records it has today stop working once the new nameservers take effect. Delegate a domain that is dedicated to the game. If the domain also carries your mail, your studio site or other subdomains, connect the game on a subdomain over CNAME instead — that leaves the rest of the domain untouched.
{% endhint %}

Before switching the nameservers:

* **If DNSSEC is enabled, remove its DS record** at the registrar first, otherwise the delegation will not complete.
* Mind the **delegation deadline** shown next to the domain. If it expires, remove the domain and add it again to restart the process.

The `www` hostname is created for you and permanently redirects to the root domain.

### Domain statuses

| Status                  | What is happening                                                    |
| ----------------------- | -------------------------------------------------------------------- |
| **Waiting for DNS**     | The records are not visible yet. Add them and press **Check again**. |
| **Pending nameservers** | Delegation is set but the registrar has not propagated it yet.       |
| **Issuing certificate** | DNS is fine; the HTTPS certificate is being issued.                  |
| **Active**              | The domain serves the site over HTTPS.                               |

DNS changes usually take 15–30 minutes to propagate, but a registrar may need up to 24 hours. Use **Check again** to re-run the check rather than removing and re-adding the domain.

When the domain is ready, press **Enable domain** to start serving the site on it.

## Step 5. Update the site later

The published site keeps running the whole time you work on changes. Press **Edit**, change whatever you need in the form, and press **Validate and publish** again — the new version replaces the live one once it is built. There is no moderation step in between.

## Troubleshooting

* **There is no Standalone site platform on the game page** — Wrap has not reached your account yet; it is rolling out to all developers.
* **Validate and publish does not start the build** — a required field is empty. The form points at the fields that are still missing.
* **The technical hostname does not show up in search** — it is not supposed to: it is closed to indexing. Connect your own domain.
* **The domain stays in "Waiting for DNS"** — the records do not match what the console shows. Compare them character by character, then press **Check again**. For a delegated root domain, verify both nameservers are set at the registrar and DNSSEC is off.