What is a White Page?

A White Page is a static placeholder website that is shown instead of the main content when checked by moderation on advertising platforms or for certain categories of traffic (whitelist). A White Page should look like a regular harmless website (blog, store, corporate site, etc.).

---

1. Requirements for White Page

1.1 Archive Format

A White Page is uploaded as a ZIP archive with the following requirements:

• Maximum archive size: 10 MB

• At the root of the archive there must be a file index.html

• The archive may contain nested folders with resources (CSS, JS, images, fonts, etc.)

Correct ZIP structure:

my-whitepage.zip
├── index.html          ← must be at the root
├── css/
│   └── style.css
├── js/
│   └── main.js
└── images/
    ├── logo.png
    └── banner.jpg

Incorrect structure (index.html inside a subfolder):

my-whitepage.zip
└── my-site/            ← ✗ cannot be nested in a folder
    ├── index.html
    └── css/
        └── style.css

1.2 Fully Static Content

A White Page must be a fully static site:

• ✅ HTML, CSS, JavaScript, images, fonts

• ✅ Inline styles and inline scripts

• ❌ Server-side scripts (PHP, Python, Node.js, etc.)

• ❌ Dynamic API requests to external servers (may cause blocking)

• ❌ Linking to external resources from suspicious domains

1.3 Only Relative URLs

This is the most important rule. All links to resources (CSS, JS, images, fonts) within the White Page must be relative.

✅Correct — relative paths:

<link rel="stylesheet" href="css/style.css">
<script src="js/main.js"></script>
<img src="images/logo.png" alt="Logo">

/* In CSS files, relative paths too */
background-image: url('../images/bg.jpg');

@font-face {
  src: url('../fonts/roboto.woff2');
}

❌Incorrect — absolute paths:

<!-- ✗ Absolute path -->
<link rel="stylesheet" href="/css/style.css">
<script src="/js/main.js"></script>
<img src="/images/logo.png" alt="Logo">

<!-- ✗ Full URL to your own files -->
<link rel="stylesheet" href="https://my-server.com/css/style.css">

Why? Relative paths work correctly on any campaign domain where the White Page is published.

1.4 Allowed External Resources

Linking to popular external libraries via CDN is allowed:

<!-- ✅ Google Fonts -->
<link href="https://fonts.googleapis.com/css2?family=Roboto&display=swap" rel="stylesheet">

<!-- ✅ Bootstrap, jQuery, and other popular CDNs -->
<link href="https://cdn.jsdelivr.net/npm/[email protected]/dist/css/bootstrap.min.css" rel="stylesheet">

---

2. Creating a White Page

1. Go to the PWA → White Pages section

2. Click the "Add" button

3. Fill in the fields:

   • Name — a clear name (e.g., "Cooking Blog")

   • Active — activity status

   • ZIP archive — upload the prepared ZIP archive

4. Click "Save"

After saving, the archive will be automatically unpacked and uploaded to the CDN. The status will change to Ready after successful processing.

---

3. Editing HTML

You can edit the content of index.html directly in the browser:

1. In the White Pages table, click ⋮ (action menu) next to the desired entry

2. Select "Edit HTML"

3. An editor with two panels will open:

   • On the left — code editor with syntax highlighting

   • On the right — live preview of the page

4. Make changes to the HTML

5. Click "Save" to save

Keyboard Shortcuts in the Editor

---

4. Viewing on CDN

To view the published White Page:

1. Click ⋮ → "Open CDN"

2. The page will open in a new tab

---

5. Using in Campaigns

When creating or editing a campaign in the Tracker → Campaigns section:

1. In the White Page field, select the desired page from the dropdown list

2. The list displays:

   • White Pages of your team

   • System White Pages (marked as "System") — available to all teams

---

6. White Page Statuses

After upload, the status updates automatically — wait for Ready (or Error), there is no need to refresh the page. If the status is Error, click it to see the reason.

---

7. Common Errors

Page displays without styles/images

Reason: Absolute paths are used instead of relative ones. Solution: Replace all /css/..., /js/..., /images/... with css/..., js/..., images/... (without leading /).

Error uploading archive

Reason: The file index.html is not at the root of the archive. Solution: Ensure that when creating the ZIP, the file index.html is at the top level, not inside a subfolder.

Status "Error" after upload

When the status is Error, click it to see the reason. Then rebuild the archive following the rules in section 1 (size up to 10 MB, index.html at the root, relative paths). If the error persists, contact support.