Partner campaign centre

Never start from ‘what should I post?’

Choose a real audience problem, use a useful destination, customize the hooks in your own voice, disclose the relationship and measure the customer outcome once production attribution is live.

12Evergreen campaign packs

1Primary audience problem each

0Required spam quotas

Live factsRequired before publishing

Campaign library

Evergreen starting points for the weekly campaign system.

These are educational starting points, not pre-approved claims about future pricing, promotions or features. Re-check live product facts before publishing.

First website

Audience: First-time business, portfolio, blog or project builders

Hooks:

What do you actually need to put a first website online?
Domain, hosting and DNS are three different things.
Choose the website outcome before choosing a hosting tier.

Tutorial / content path: Build a beginner walkthrough from domain ownership -> hosting fit -> DNS -> HTTPS -> launch checks.

Disclosure / trust note: If you recommend DotMoose inside the walkthrough, clearly state that the link/recommendation can earn you a commission.

Open campaign destination →

Migration readiness

Audience: People unhappy with an existing host or planning a move

Hooks:

Do not move a website until you know these 10 things.
The DNS record people forget during a hosting migration.
How to know whether you can actually move your website safely.

Tutorial / content path: Use the free migration checker, then explain the missing access/backups/DNS/mail items.

Disclosure / trust note: If DotMoose becomes the recommended destination, disclose the affiliate relationship before or with the recommendation.

Open campaign destination →

WordPress launch

Audience: WordPress beginners and creators

Hooks:

A WordPress install is not the whole launch plan.
Five WordPress hosting questions to answer before paying.
What changes when the WordPress site is a store?

Tutorial / content path: Walk through site type, backups, mail, DNS, developer access and post-launch tests.

Disclosure / trust note: Keep the educational checklist useful even if the viewer chooses another host.

Open campaign destination →

Developer deploy

Audience: Developers, side projects, templates and tutorials

Hooks:

You built the app—now where does it run?
How to turn a deployment tutorial into a useful affiliate path.
Do not recommend a server until you know the workload.

Tutorial / content path: Document a genuinely supported deployment path and use the plan finder for fit.

Disclosure / trust note: Affiliate links belong beside the hosting recommendation, not hidden inside commands or dependency instructions.

Open campaign destination →

Student portfolio / project

Audience: Students and early-career developers/designers

Hooks:

Put your portfolio on a domain you control.
A student project can teach you DNS, hosting and deployment at once.
The low-cost side hustle nobody has to buy inventory for.

Tutorial / content path: Teach a real portfolio/project launch; avoid guaranteed-income framing.

Disclosure / trust note: Make any affiliate relationship clear and do not imply school sponsorship.

Open campaign destination →

Agency client handoff

Audience: Web designers, freelancers and agencies

Hooks:

Who should own the client’s domain and hosting account?
The hosting handoff step I put in every website launch.
Stop leaving recurring referral value outside the client workflow.

Tutorial / content path: Explain client-owned account access, launch handoff, DNS inventory and disclosed referral.

Disclosure / trust note: Separate your professional service fee from DotMoose charges and your affiliate relationship.

Open campaign destination →

Domain ownership / WHOIS

Audience: Domain owners, businesses, migration research

Hooks:

How to see where a domain is registered.
Before moving a site, check who controls the domain.
WHOIS changed: here is the useful modern lookup.

Tutorial / content path: Use RDAP to explain registrar, status, dates, nameservers and why no record does not guarantee availability.

Disclosure / trust note: The free lookup is useful without buying; disclose only when you transition into a commercial recommendation.

Open campaign destination →

DNS troubleshooting

Audience: Website owners, developers and IT audiences

Hooks:

Where is your domain actually pointing?
The DNS records to save before changing nameservers.
Website works but email broke? Check DNS first.

Tutorial / content path: Explain A/AAAA/MX/NS/TXT/CNAME/CAA using the free DNS checker.

Disclosure / trust note: Do not manufacture a hosting problem from a normal DNS result just to create a sale.

Open campaign destination →

Canadian small business website

Audience: Canadian businesses and local creators

Hooks:

What should a Canadian business actually look for in website infrastructure?
CAD billing, .CA and hosting location are separate decisions.
A .CA domain is not the same thing as Canadian hosting.

Tutorial / content path: Use specific verified Canadian facts and explain the layers accurately.

Disclosure / trust note: No unsupported residency/sovereignty claim; disclose affiliate relationship when recommending DotMoose.

Open campaign destination →

Local business referral

Audience: IT shops, printers, photographers, consultants and marketers

Hooks:

What to do when a client asks you who should host their website.
You can help with a domain question without becoming a registrar.
A simple website handoff process for local service businesses.

Tutorial / content path: Use free tools and a clean customer handoff. Do not present yourself as DotMoose support.

Disclosure / trust note: Clearly separate the independent partner’s work from DotMoose services.

Open campaign destination →

Newsletter / podcast infrastructure

Audience: Tech, WordPress, business and developer publications

Hooks:

One practical infrastructure question for this week’s audience.
A hosting sponsor read should still teach something useful.
How to test affiliate economics before buying/selling a sponsorship package.

Tutorial / content path: Build one audience-specific segment and one tracked destination per placement.

Disclosure / trust note: Use disclosure appropriate to the episode/newsletter and do not disguise paid/affiliate promotion as independent editorial testing.

Open campaign destination →

Web-design side hustle

Audience: New freelancers and service-side-hustle audiences

Hooks:

A web-design side hustle starts with a client problem, not a logo.
Who should own the domain when you build a client website?
How hosting referrals can sit beside real web-design work.

Tutorial / content path: Teach first-client scope, ownership, launch and maintenance basics without promising client acquisition or income.

Disclosure / trust note: Disclose the hosting referral and keep service pricing separate.

Open campaign destination →

Weekly campaign drop

The system is ready before the email automation is.

Once live attribution and opt-in partner communications exist, one of these evergreen packs—or a real seasonal pack—can be delivered as the optional weekly brief.

Audience + problem

State exactly who the campaign is for and what problem it solves.

Short-form hooks

Give partners several honest openings they can adapt to their own audience.

Useful destination

Prefer a tool, guide or product path that directly matches the content.

UTM

Campaign naming

Use the campaign builder so performance can be grouped once production attribution is available.

Seasonal gate

Seasonal does not mean invented urgency.

January: side-hustle / first-business-site only where the message is useful without an earnings promise.
Portfolio/job-search periods: portfolio and developer-project launches.
Back-to-school: student projects and portfolios.
WordPress refresh/migration periods: real migration and maintenance education.
Black Friday/year-end: only when DotMoose has a genuine approved offer with a real expiry rule.
Any price-bearing creative must be retired or updated when the offer changes.

Build the tracked version

Name the audience, channel and campaign before publishing.

The campaign builder prepares UTM metadata now; live affiliate/deep-link wrapping remains gated until WHMCS attribution is proven.

Open campaign builder