Module 1: Foundation & Stack Selection

Why WordPress hurts new affiliate sites in 2026

Let me be direct: I'm not saying WordPress is bad. It powers a third of the internet and there are successful affiliate sites built on it. But for someone starting a new affiliate site today, it's the wrong choice for four specific reasons.

1. Core Web Vitals are a ranking signal and WordPress fails them by default

Google officially uses Core Web Vitals — Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP) — as a ranking factor. A default WordPress install with a popular theme, WooCommerce disabled, and basic plugins scores around 40–55 on mobile in Google PageSpeed Insights. A static HTML page served from Cloudflare Pages or Vercel typically scores 92–99.

The gap isn't trivial. For a new domain with no authority, every ranking advantage matters. You can't compensate for slow pages with good content alone — Google's own documentation confirms site speed affects crawl budget.

2. Plugin debt compounds over time

A new WordPress affiliate site needs at minimum: SEO plugin (Yoast or RankMath), caching plugin, security plugin, CDN plugin, image optimization plugin, spam protection, and sometimes a page builder. That's 6–8 plugins before you've written a word. Each one adds maintenance overhead, introduces security vulnerabilities, and creates compatibility issues on updates. I spend zero time on plugin maintenance on this site.

3. Hosting costs at scale are real

Decent managed WordPress hosting (WP Engine, Kinsta, Flywheel) starts at $25–$35/month. That's $300–$420/year on hosting alone before you've earned anything. If you're running a new site building toward its first $500/month in affiliate revenue, paying $420/year in hosting is a 7% overhead tax that a free Vercel deployment doesn't carry.

4. The Google "blog site" classification problem

Affiliate SEO practitioners have documented that Google now appears to classify sites into rough categories: "proper businesses" vs. "content blogs." Business-classified sites have significantly better ability to rank for commercial queries post-HCU. A WordPress blog with affiliate links in posts reads unmistakably as "content blog" in every structural signal. A site with a clear service architecture, schema-marked business entities, and clean technical signals reads more ambiguously — which is advantageous.

The three stack options for 2026

I've narrowed it to three realistic options for affiliate sites. Each has a different skill ceiling and different trade-offs.

This site — alternativeentrepreneur.com — runs on static HTML deployed to Cloudflare Pages. Every page you're reading is a hand-coded HTML file. When Google crawls it, it gets clean semantic HTML with schema markup and no JavaScript overhead on initial load. This is why the site regularly scores 95+ on mobile PageSpeed despite having no paid SEO tools applied to the hosting layer.

Option A: Static HTML (this site's stack)

The approach: you write HTML files, push to a Git repository (GitHub, GitLab, or Bitbucket), and Cloudflare Pages or Vercel automatically deploys them. No server to manage. No database to secure. No CMS to update.

The actual file structure

Here's the directory layout this site uses:

your-site/
├── index.html              (homepage)
├── css/
│   └── styles.css
├── images/
├── affiliate-marketing/
│   ├── index.html          (pillar hub page)
│   └── beginners-guide/
│       └── index.html      (cluster article)
├── robots.txt
└── sitemap.xml

Every slug is a folder containing an index.html. This means /affiliate-marketing/beginners-guide/ resolves cleanly without any server-side routing. It's the simplest possible SEO-friendly URL structure.

Using AI to generate pages fast

This is where static HTML becomes extremely powerful with AI tools. Instead of using a page builder, you prompt Claude or GPT-4o:

"Generate a complete HTML page for an affiliate article about [topic]. Use this existing page as a template for structure and CSS classes: [paste your existing page HTML]. The content should cover: [outline]. Include schema markup of type BlogPosting."

In practice, I can produce a complete, correctly structured, schema-marked HTML article page in about 5–10 minutes with this workflow. A WordPress editor would take the same time, but with worse output (no schema markup by default, theme CSS overhead, etc.).

Option B: Next.js for developer-built sites

If you're comfortable with JavaScript and React, Next.js with static site generation (SSG) is the better option at scale. The key feature is getStaticProps and dynamic routes — you can define a template and generate hundreds of pages from a JSON or CSV data source automatically at build time.

For example, a comparison site with 500 software products would loop over a products array and generate /reviews/[product-name]/ for each. I cover this fully in Module 6: Programmatic SEO.

Deployment is still Vercel — Next.js was created by Vercel and the integration is seamless. The free tier handles significant traffic before you'd need to pay anything.

Next.js vs static HTML: the right question

The question isn't "which is better" — it's "which do I have the skills to build and maintain?" A poorly executed Next.js site is worse than a clean static HTML site. If you don't know React, don't start with Next.js. Build in HTML first, learn the SEO principles, then migrate later if scale requires it.

Option C: No-code (Webflow / Framer)

Webflow has a legitimate CMS, clean semantic HTML output, and good SEO defaults. If you have no coding background and don't want to use AI tools to generate code, Webflow is a genuine option. The $14/month basic hosting tier gives you a custom domain and reasonable performance.

The limitation is cost at scale and the ceiling on technical SEO control. You can't easily implement custom schema types, modify the HTML structure for specific pages, or add dynamic functionality. For a simpler affiliate site in a low-competition niche, these limitations often don't matter in practice.

Free hosting with Vercel and Cloudflare Pages

Both platforms offer genuinely free tiers that will handle any affiliate site's traffic until it's earning significant revenue.

Vercel free tier

• Unlimited deployments from Git
• 100GB bandwidth per month (more than enough for new sites)
• Custom domains with free SSL
• Edge network — fast globally
• Works natively with Next.js and any static HTML output

Setup: create a free account at vercel.com → import your GitHub repository → add your custom domain. Done. Every push to your main branch triggers a new deployment automatically.

Cloudflare Pages free tier

• Unlimited requests (no bandwidth cap)
• Unlimited sites
• Custom domains with free SSL
• 500 builds per month
• Access to Cloudflare's global edge network

Cloudflare Pages is what this site uses. The unlimited request count is the key advantage — with Vercel, traffic spikes can theoretically push you toward usage limits (though in practice a new affiliate site won't get there). With Cloudflare Pages, there's no bandwidth anxiety at any traffic level on the free tier.

Domain setup and Cloudflare DNS

Your domain setup affects site speed and security. I recommend:

1. Register at Namecheap or Cloudflare Registrar. Namecheap has transparent pricing with no renewal surprises. Cloudflare Registrar sells at cost (no markup) — check both for your specific TLD.
2. Move DNS to Cloudflare immediately. Even if you don't host on Cloudflare Pages, using Cloudflare's nameservers gets you their global DNS resolution, free DDoS protection, and analytics proxying. Point your domain's nameservers to the two Cloudflare NS records they give you.
3. Enable "Proxied" (orange cloud) for your A/CNAME records. This routes traffic through Cloudflare's edge rather than directly to your hosting server, which adds the performance and protection layer.
4. Set SSL/TLS to "Full (strict)" in Cloudflare's dashboard. This enforces HTTPS end to end with no redirect issues.

One non-obvious tip: in Cloudflare's Speed settings, enable "Auto Minify" for HTML, CSS, and JavaScript, and turn on "Brotli" compression. These are free one-click improvements that reduce your page load size by 20–30% with no code changes.

How to choose: the decision framework

Use this simple decision tree:

Your situation	Recommended stack
You can read/write basic HTML and CSS	Static HTML + Cloudflare Pages
You know JavaScript / React	Next.js + Vercel
You want to build programmatic pages at scale	Next.js + Vercel
No coding background, want visual editing	Webflow + custom domain
Existing WordPress site with good traffic	Stay on WordPress — don't migrate
New site, developer background, want max control	Static HTML or Next.js based on scale needs

A practical note: if you're uncertain, start with static HTML. You can always migrate the content strategy to a different stack later. The keyword research, content architecture, and SEO principles in the rest of this course apply equally to all three options.

Module 1 action steps

1. Decide which stack you're using (HTML, Next.js, or Webflow)
2. Create a free Cloudflare account and Vercel account
3. Register a domain (or set one aside to test with)
4. Move the domain to Cloudflare nameservers
5. Create a GitHub repository for your project
6. Deploy a single index.html "Hello World" page to confirm the pipeline works

Don't overthink step 6. A single HTML file that says "Hello World" deployed to your custom domain proves everything in the stack works end to end. You'll replace it in Module 3.