Multi-site admin
One Filament cockpit. Many domains. Sites & Ads as a first-class nav group.
← Portfolio
Software / SaaS · Growth & Marketing · Pakistan / MENA / Global
Monetization Engine - Multi-Site Google AdSense OS
One stack. Many niches. Publisher-safe Google display revenue with policy-aware AdSense and hybrid Monetag.
Multi-tenant publishing OS for AdSense portfolios: isolated sites, placement policy, ads.txt, tools that earn dwell time, and AI/RSS gates that protect the publisher account.
The story
What this platform is really for
Publishers who want a portfolio of niche sites usually clone WordPress again and again - and gamble the AdSense account with thin content, wrong placements, and hand-copied ads.txt.
Monetization Engine is Zi SoftTech's multi-site publisher OS. Each domain is an isolated content + tools + ads property under one Filament admin. Google AdSense (and hybrid Monetag where policy allows) is first-class: publisher IDs, Auto ads, slots, zones, in-article injection, live ads.txt, and AdsBot-aware robots.
Interactive tools - finance calculators, converters, DNS/IP utilities - earn dwell time. AI Studio and RSS pipelines rewrite and schedule content, but PublisherSafeContent holds thin or clickbait drafts offline so the live inventory stays AdSense-safe.
Demo verticals prove the model: finance hub, converter bench, AI prompt directory, and cloud stack check - four faces, one engine.
Client: Multi-site publisher / Zi SoftTech growth product | Industry: Publisher Monetization & Growth
The challenge
Publishers who want a portfolio of niche sites usually clone WordPress again and again. Themes look the same. AdSense policy gets guessed. Thin RSS and AI drafts go live and risk the whole publisher account. Ads appear on privacy pages. Interstitials fire where Google forbids them. ads.txt and robots.txt are copy-pasted by hand. Scaling to finance, converters, AI directories, and cloud niches means four fragile installs - not one product with a Google-display monetization brain.
The Zi SoftTech answer
Zi SoftTech built Monetization Engine: one Laravel multi-tenant publishing OS where each domain is an isolated content + tools + ads property. Google AdSense (and hybrid Monetag where policy allows) is governed by placement rules, Auto-ads awareness, live ads.txt, AdsBot-aware robots, in-article injection, and AI/RSS gates that keep thin or clickbait inventory out of the live feed - so operators scale niches without cloning the stack or gambling the AdSense account.
Built for
Who buys a multi-site ad monetization OS
Digital publishers running a portfolio of niche AdSense sites
Agencies delivering calculator, converter, and directory properties for clients
Operators who need one admin across finance, utility, AI, and hosting verticals
Zi SoftTech buyers who want a publisher OS - not another blog theme
Teams that treat Google display revenue as product infrastructure, not a plugin afterthought
Regional Zi SoftTech clients across Pakistan, MENA, and global English niches
Inside the product
Publisher stack at a glance
AdSense / hybrid config
Publisher ID, Auto ads, Monetag zones, and network selector per site.
Policy-aware placements
Legal pages stay clean. Interstitials respect AdSense vs Monetag rules.
Tools inventory
Calculators and converters that keep users on-page for display yield.
AI + RSS pipeline
Feeds and daily automation with AdSense-safe draft gates.
Vertical themes
Finance, converters, AI directory, and cloud shells that do not look cloned.
Platform pillars
What the Monetization Engine actually runs
Add image
True multi-site isolation
Every request resolves Host → Site. Posts, tools, ads, themes, and foreign keys stay locked to that tenant. One codebase. Many independent brands.
- Domain, slug, theme, locale, timezone, and branding per site
- BelongsToSite scoping so public queries never leak across hosts
- Cross-site FK guard nulls wrong category / tool / feed links
- Indexable, HTTPS, www, and SEO defaults per property
Add image
Google AdSense-first monetization
Ad networks are first-class: AdSense, Monetag, hybrid, or custom. Publisher ID, Auto ads, slots, zones, and visibility rules live in the Sites & Ads admin - not scattered plugins.
- Per-site AdSense publisher ID (ca-pub) and Auto ads toggle
- Hybrid Monetag site ID + zone map for converter-style inventory
- Ad units with slot / zone / custom HTML and page-type visibility
- Placements: header, in-article, sidebar, footer, sticky, tool top/bottom
Add image
Publisher policy brain
AdSense survival is engineered, not hoped for. Legal pages stay ad-light. Interstitials respect network rules. ads.txt and robots.txt are generated per host with Mediapartners-Google and AdsBot in mind.
- No ads on privacy, terms, cookies, disclaimer pages
- About/contact ad-light when AdSense (including hybrid) is on
- Interstitial blocked on AdSense-only; allowed on Monetag/hybrid
- Live /ads.txt seller line + AdsBot-aware /robots.txt
Add image
In-content ad injection that respects the page
In-article units inject after natural paragraph breaks. Auto-ads awareness hides conflicting chrome. Demo creatives stay ad-blocker-resistant for QA.
- HtmlAdInjector places in_article_1 / in_article_2 after 2nd and 4th paragraphs
- Auto ads mode softens header / footer / sticky on AdSense-only
- Home, posts, pages, and tools visibility per unit
- Sort order and active flags for operator control
Add image
Tools that earn dwell time
Interactive tools are inventory, not decoration. Finance calculators, in-browser converters, DNS/IP/speed utilities, and prompt libraries keep users on-page for display and affiliate yield.
- Mortgage, auto-loan, compound interest, salary, tax calculators
- PDF/image/JSON/Base64 converters in the browser
- DNS checker, IP lookup, speed test with SSRF hygiene
- Programmatic tool landers (city/state) for long-tail SEO
Add image
AI + RSS pipeline with AdSense gates
Content automation is allowed - thin and clickbait are not. Feeds rewrite through AI, daily topics publish on schedule, and PublisherSafeContent holds weak drafts offline.
- Per-site feeds with interval, rewrite, and auto-publish controls
- FetchFeedJob + ProcessFeedItemJob on a recurring pipeline
- Min word count and strip of “click the ad” language
- AI Studio: Write / Improve / Rewrite + daily blog automation
Add image
Vertical themes that do not look like clones
Finance hub, terminal converters, cream AI directory, and ops cloud shells keep each niche visually distinct - same engine, different face.
- Theme shells: tools, converters, directory, cloud, and more
- Per-site colors, branding JSON, and SEO defaults
- JSON-LD, canonicals, and verification meta per host
- Sitemap.xml generated for home, tools, posts, and pages
Add image
One Filament ops cockpit
Sites & Ads, Content, AI Studio, Pipeline, SEO Tools, and System live in one admin. Operators run a portfolio - not a zipper of logins.
- Site resource with dedicated Ads tab
- Ad Unit resource for slots, zones, and visibility
- Posts, pages, categories, tags, tools, tool pages
- Feeds, pipeline logs, redirects, settings, topic queue
Customer journey
From one niche site to a portfolio that earns
01
Spin up a site
Create the tenant: domain, theme, niche branding, locale, and SEO defaults. The host now resolves to its own isolated world.
02
Wire Google display monetization
Pick AdSense, Monetag, hybrid, or custom. Set publisher ID, Auto ads, placements, and units. ads.txt goes live with the seller line.
03
Ship tools + guides
Attach calculators or converters, publish posts and pages, and grow programmatic landers for search inventory.
04
Automate safely
Connect feeds and AI Studio. Thin or clickbait drafts stay offline until they clear AdSense-safe gates.
05
Scale the next vertical
Add finance, converters, AI directory, or cloud niches on the same admin - without cloning WordPress again.
Instead of tool sprawl
What Monetization Engine replaces
N× WordPress + Ad Inserter plugins
becomes
One multi-site engine with policy-aware AdSense / Monetag placements
Manual ads.txt and robots.txt per host
becomes
Generated per-site ads.txt + AdsBot-aware robots
Thin spun RSS live on AdSense
becomes
Pipeline that holds thin/clickbait as draft until publishable
Same theme recolored for “new brands”
becomes
Distinct vertical shells - finance, converters, directory, cloud
Separate tool microsites glued with ads
becomes
Whitelisted tool engine + landers inside each tenant
Agency guessing AdSense policy
becomes
Codified network policy for legal pages, interstitials, and Auto ads
Capability checklist
Full multi-site ad & publishing stack
- Host → Site resolution with true per-tenant data isolation
- Ad networks: Google AdSense, Monetag, hybrid, custom
- Per-site publisher ID, Auto ads, Monetag zones, and analytics scripts
- Ad units with placements: header, in-article, sidebar, footer, sticky, tool top/bottom
- Policy engine: no ads on legal pages, interstitial rules, Auto-ads awareness
- Generated /ads.txt seller line and AdsBot-aware /robots.txt
- In-article HtmlAdInjector after natural paragraph breaks
- Interactive tools whitelist: finance, converters, DNS/IP, speed, prompt library
- Programmatic tool landers for long-tail SEO inventory
- RSS pipeline with AI rewrite, interval controls, and pipeline logs
- AI Studio: Write / Improve / Rewrite, topic queue, daily automation
- PublisherSafeContent gates (min words, strip ad-clickbait language)
- Vertical themes: tools, converters, directory, cloud, and more
- Filament admin: Sites & Ads, Content, AI Studio, Pipeline, SEO Tools
- Per-host sitemap.xml, JSON-LD, canonicals, verification meta
Business outcomes
What changes for the publisher
- One admin replaces a farm of cloned WordPress installs
- AdSense policy is codified - not guessed per site
- Thin AI/RSS drafts never go live by accident
- Each niche keeps a disti