Publisher Guidelines.

1. Introduction

These Publisher Guidelines explain what we expect from websites that join the Highpay Ads network. All publishers must comply with these rules before and after verification. By monetizing traffic with us, you agree to maintain a safe, usable experience for visitors and advertisers.

2. Eligible websites

We approve sites that offer real content or tools and are operated in good faith on a domain you control.

• You own or have permission to monetize the site.
• The site is publicly reachable over HTTPS where possible.
• Content is original or properly licensed; not a parked or "coming soon" placeholder.
• The site has clear navigation and a legitimate purpose (blog, tool, community, app landing page, etc.).
• Pages must feel like a finished product: readable layout, working links, and enough substance that a visitor would use the site without ads.

3. Own domains only

Highpay Ads only accepts inventory on domains you own or control. Free hosted subdomains and disposable platform URLs are rejected at signup and during review. We want durable sites that advertisers can trust — not temporary blogs on someone else's platform.

• Use a domain registered to you (or your organization), for example example.com or a subdomain of that domain such as blog.example.com or www.example.com.
• Free platform hosts are not allowed, including Blogspot / Blogger, WordPress.com, Tumblr, Medium, Substack, Ghost.io, Hashnode, and similar blogging networks.
• Website-builder and free-host default hosts are not allowed, including Wix, Weebly, Webflow.io, Carrd, Notion.site, Framer, GitHub Pages, GitLab Pages, Netlify.app, Vercel.app, and comparable free tiers.
• Shopify preview or *.myshopify.com hosts, Google Sites, and other shared platform hostnames are not accepted as publisher sites.
• Pointing a free subdomain at our tags or wrapping thin content on a platform URL does not qualify. Connect a custom domain you own and build a proper site before applying.
• During domain verification you must prove ownership by hosting our verification file on that domain. If you cannot do that, the site is not eligible.

4. Prohibited content

We do not approve sites that host or promote the following:

• Illegal content or activities in any jurisdiction we serve.
• Malware, phishing, scams, or deceptive downloads.
• Piracy, hacking, or circumvention of paywalls or DRM.
• Hate speech, violence, or harassment targeting individuals or groups.
• Adult or explicit content without appropriate age gating and legal compliance.
• Drugs, weapons, or other restricted goods where prohibited.

5. User experience

Visitors must be able to use your site without aggressive interference.

• No excessive popups, pop-unders, or chained redirects.
• No auto-redirects that trap users or hijack the back button.
• Layouts must work on common desktop and mobile browsers.
• Ads must not be disguised as system messages or site navigation.
• In-Page Push ads must remain clearly labeled as advertising with a visible close button.

6. Traffic quality

We only accept organic or legitimate marketing traffic.

• No incentivized clicks, paid-to-click schemes, or misleading buttons.
• No bot or artificial impression inflation.
• No misrepresentation of the site topic to attract unrelated clicks.

7. Ad placement

Once approved, ad zones must follow these rules:

• Place ads in visible areas; do not hide or stack ads behind other elements.
• Do not place ads on pages that violate section 4.
• Maximum zones per page as described in your dashboard; do not overload pages with ads.
• Do not modify our ad tag to manipulate impressions or clicks.
• Use at most one In-Page Push zone per page.
• Do not remove, hide, or manipulate the push ad close button.
• Push ad creatives must not mimic operating-system notifications or fake system alerts.

8. Domain verification

Before manual review, you must prove domain ownership by hosting a verification file at your site root. After submission, our team reviews your site against these guidelines. Approval is not guaranteed.

• File name: highpay-ads-verification.txt in the site root.
• The file must contain only the token we provide.
• Review typically completes within 24 hours after a valid file is detected.
• Sites on blocked free-hosting or platform domains cannot complete verification and will be rejected.

9. Rejection and re-submission

If your site is rejected, you will see specific reasons in your Publisher Dashboard. Fix every listed issue, then submit verification again. Repeated violations may lead to permanent removal from the network.

• Read the rejection reasons and this document carefully.
• Improve the site before requesting another review.
• Use "Verify Domain" on the dashboard after the verification file is in place.
• Contact support only if you believe the decision was made in error.