Showing posts tagged with

Static site

WordPress vs Static Site for Affiliate Sites: 3-Year Total Cost

Static site vs WordPress for affiliate websites covered the architecture comparison — speed, SEO, what each is good at. This article picks up where that left off and answers a different question: over 3 years of running an affiliate review website, how much cash does each platform actually cost? Most "WordPress vs static" articles online compare hosting fees ($5/mo vs $0) and stop there. They miss plugins, security tooling, migration costs. But other articles wildly overinflate by pricing the founder's time at agency rates. This article does only the cash math — what you actually wire-transfer over 3 years. What "total cost" includes (cash only) This article only counts real cash you'll pay. We're not pricing your own time at $50/hr — that's a useful exercise but tends to inflate numbers in ways most indie operators don't actually feel. If you want to factor in your time, multiply hours from each section by your hourly rate. Cash categories on the table:Hosting and CDN Domain (same on both, ~$10-15/yr) Theme / template Plugins / build-time tools Backup and security tooling Headless CMS (static only, optional)This article models all categories for both platforms across 3 typical site sizes. The 3 site sizes I'm comparing To make the math useful, I'll model three realistic affiliate site sizes:Tier Pages Monthly visits Monthly affiliate revenue Editor countSmall 50-200 < 10k $100-500 1 (you)Medium 500-1500 30-100k $1k-5k 2-3Large 3000+ 200k+ $10k+ 5+Numbers are realistic ranges, not best-case. Adjust to your situation. WordPress 3-year cash breakdown Hosting + CDN For affiliate sites at indie scale, you don't need managed WordPress hosting (Kinsta/WP Engine) until you have real traffic. Realistic tiers:Small site (<10k/mo visits): shared hosting (Hostinger, Namecheap, A2) at $3-5/mo → 3yr: $108-180 Medium (30-100k/mo): VPS (Hetzner CX22 ~$5/mo, DigitalOcean $6-12/mo) or Cloudways DO $14/mo → 3yr: $180-500 Large (200k+/mo): dedicated VPS $20-40/mo or managed tier $30-50/mo → 3yr: $700-1,800Cloudflare free tier handles CDN at every size. Plugins (what you actually need to pay for) Most affiliate-site plugin lists you see online over-prescribe paid plugins. Truth at indie scale:SEO: Rank Math (free) is enough; Pro at $59/yr is optional Schema / markup: included in Rank Math free Affiliate links: Pretty Links free version handles cloaking; ThirstyAffiliates Pro is overkill for < 50 affiliate links Image optimizer: Smush free or build-side compression Caching: WP Super Cache (free) or LiteSpeed Cache (free); WP Rocket $59 only if you want one-click setup Backup: UpdraftPlus free or BlogVault $89/yr only at scale Security: Wordfence free plus 2FA is enough at small scale3-year realistic plugin cash:Small site: $0-200 (mostly free tier) Medium: $100-400 (1-2 paid plugins) Large: $300-700 (Rank Math Pro + WP Rocket + maybe BlogVault)ThemeOne-time: $0-60 (Astra Pro $59 lifetime, GeneratePress free, Kadence free, etc.)3-year cost: $0-60 Domain $10-15/yr × 3 = $30-45 (same for both platforms) Security tooling beyond pluginsCloudflare: free for most cases; Cloudflare Pro is $20/mo only for high-traffic sites Small/Medium: $0 (Cloudflare free + plugin baseline is enough) Large: $0-720 (might add Cloudflare Pro or Sucuri at scale)WordPress 3-year cash totalsTier Hosting Plugins Theme Domain Security TotalSmall $108-180 $0-200 $0-60 $30-45 $0 $140-485Medium $180-500 $100-400 $0-60 $30-45 $0 $310-1,005Large $700-1,800 $300-700 $0-60 $30-45 $0-720 $1,030-3,325Static site 3-year cash breakdown Astro / Next.js / Hugo / 11ty etc on Vercel / Netlify / Cloudflare Pages. Hosting + CDNSmall/Medium (up to ~100k/mo): Free on Vercel / Netlify / Cloudflare Pages within free tiers Large (200k+/mo): Vercel Pro $20/mo or Cloudflare Pages still free for static + Workers cheap → 3yr: $0-720This is the headline gap with WordPress. "Plugins" / build-time tools Static replaces plugins with free code or build-time tools:SEO / schema: built into framework or 1 line of meta tag — free Affiliate link tracking: open-source library — free Image optimization: built-in (Astro, Next/Image) — free; Cloudinary $0-89/yr only if you need it Caching: not needed (static = always cached) — free Backup: git — free Email integration: ConvertKit / Mailchimp same cost as WordPress3-year tooling: $0-300 (mostly $0; Cloudinary/Plausible analytics if you choose) Theme / templateFree framework templates everywhere → $0Domain Same as WordPress: $30-45 Headless CMS (only if you need non-developer editors) If you're solo and write in markdown — $0. If you have 2+ non-developer editors:Decap CMS (free, self-hosted): $0 Tina ($29/mo paid): up to $1,044 over 3 years Sanity team plan ($99/mo): up to $3,600 over 3 yearsStatic site 3-year cash totalsTier Hosting Tools Domain CMS TotalSmall (solo) $0 $0-100 $30-45 $0 $30-145Medium (3 editors, markdown) $0 $0-200 $30-45 $0-200 $30-445Large (5+ editors, 200k+ visits) $0-720 $100-300 $30-45 $0-1,044 $130-2,109Side-by-side 3-year cash costSite tier WordPress Static Static savesSmall $140-485 $30-145 ~$100-340Medium $310-1,005 $30-445 ~$280-560Large $1,030-3,325 $130-2,109 ~$900-1,200Static wins on cash at every site size — but the gap is much smaller than internet "WordPress is expensive" arguments suggest. Both are cheap at indie scale. The real cost difference is time, which we deliberately didn't price here. What cash doesn't capture — your time Cash difference is small ($100-1,200 over 3 years). The real cost difference between platforms is time, which we deliberately didn't price. Rough hour estimates:WordPress: 124-264 hours over 3 years (plugin updates, theme upgrades, security incidents, performance debugging) Static: 80-180 hours over 3 years, but front-loaded — most in year 1 for setupIf you bill your time at $50/hr the time gap can be $2,000-4,000 over 3 years — much bigger than the cash gap. If your time has $0 opportunity cost (you'd be browsing Twitter instead), the cash table above is the whole picture. Where WordPress is the right choice anyway Even though static is cheaper on cash, WordPress wins when:Non-technical editors must publish independently — paid headless CMS (Tina/Sanity) pushes static cost up; WordPress's editor experience is just better for non-coders Site relies heavily on user-generated content / forums / e-commerce — WordPress + WooCommerce / BBpress is mature; static equivalents need much more dev work Migration from existing WP site is too expensive — sometimes the cheapest move is staying on WP You ship 5+ specialized affiliate features yearly — each one as static code is more work than installing a plugin You're comfortable with PHP + admin UI but not with build tools / CIWhere static decisively winsSolo founder writing in markdown — static is free everywhere High traffic spikes — static has zero hosting cost variance under spike, WordPress hosting tiers up sharply Affiliate sites that need to be fast — Core Web Vitals correlate with rankings; static wins by default Long-term security peace of mind — no DB, no exec, no plugins = nothing to hackMigration considerations If you're already on one and considering switching, factor migration cost:WP → Static: 40-100 hours work depending on plugin reliance and content volume Static → WP: 20-60 hours (easier; WP is more flexible re: data import)Migration cost is often equal to 6-12 months of TCO savings. Don't migrate just because the math looks cleaner — only when migration savings clearly exceed migration cost over remaining 18-24 months. Decision rule Pick WordPress if:You ship affiliate sites where non-technical editors must publish independently AND You're not skilled with build tools / framework code AND Your sites grow slowly (no big traffic spikes)Pick static if:You're solo or mostly solo AND You write in markdown comfortably OR can set up Tina/Decap AND Speed and Core Web Vitals matter for your SEOFor static-tooling specifics see static website maintenance checklist and small website automation workflows.Further reading:The architecture comparison without cost: static site vs WordPress for affiliate websites Hosting deep-dive: best web hosting for blog and Cloudflare WordPress hosting If you go WordPress: best WordPress hosting Reddit If you go static: Indie developer website stack covers full developer tooling

Static Website Maintenance Checklist for Small Income Sites

A static website needs less maintenance than a dynamic site, but it still needs regular attention. This checklist covers the essential tasks for keeping a small income site stable, secure, and visible in search.Why Static Sites Still Need Maintenance Static sites do not have databases, server-side software, or login systems. That eliminates many security and performance risks. But they still depend on:domain and DNS configuration hosting provider reliability CDN and SSL certificate validity content freshness and accuracy internal and external link healthA quarterly maintenance routine catches small issues before they become traffic problems. Monthly Tasks (15 Minutes) These tasks can be done in a single session each month. Check uptime: log into UptimeRobot or your monitoring tool; confirm no recent downtime. Review analytics: check traffic trend, top pages, bounce rate, and search query changes. Scan for broken links: run a link checker on your domain; fix any broken internal or external links. Verify forms and contact pages: submit a test message to confirm delivery. Confirm SSL certificate is active: visit your site over HTTPS; check expiration date.Quarterly Tasks (1 Hour) Every three months, do a deeper review. Full backup: export or copy all source files and assets to an off-site location. SEO health check: review page titles, meta descriptions, and heading structure for the top 20 pages. Update static dependencies: if your site uses a framework or theme, check for security updates. Review affiliate links: click through each affiliate link; confirm it still works and reaches the correct page. Check page speed: run a Core Web Vitals check; address any regressions.For detailed SEO checks, see the on-page SEO checklist and complete SEO audit guide. Annual Tasks (2-3 Hours) Once per year, do a comprehensive review. Content audit: review every page. Update outdated statistics, prices, screenshots, and examples. Competitor review: check whether newer competitors offer better content or more current information. Domain renewal: verify domain expiration date; renew if needed (set auto-renew if possible). Analytics goals: review conversion tracking; confirm you can still measure what matters. Privacy and terms review: confirm privacy policy, affiliate disclosure, and terms pages match current practice.Common Issues Found During MaintenanceIssue Where it appears How to fixBroken external link External resource links Use a link checker quarterlySlow page Large images or unused CSS Run Lighthouse, optimize assetsStale content Old articles with outdated info Update or archiveMissing SSL Expired certificate Auto-renew with hosting providerDNS propagation Changed hosting, DNS still pointing old Check with dig/whoisAutomation That Reduces Manual Work You can automate several maintenance tasks:Uptime monitoring: UptimeRobot sends email alerts automatically Backup scheduling: most static hosting providers offer automatic backups Link checking: run a monthly script or use a service like Dr. Link Check SSL renewal: Cloudflare and most hosts handle this automaticallySee the small website automation guide for tool recommendations and workflow setup. Maintenance Budget for Small SitesTask Frequency Time Cost (if outsourced)Uptime monitoring Continuous Automated FreeLink checking Monthly 5 min FreeSEO audit Quarterly 30 min Free to $20Content refresh Annual 2-3 hours Self or freelanceBackup verification Monthly 5 min FreeSecurity scan Quarterly 10 min FreeMost small income sites can be maintained for under $50/year and 10-15 hours of your time. FAQ Do static sites need security updates? They need fewer than dynamic sites. If you use a static site generator, update it occasionally. If you use pre-built themes, check for known vulnerabilities. What happens if I skip maintenance? Traffic can decline from broken links and stale content. Security risks are lower than dynamic sites, but DNS, SSL, and hosting issues can still cause downtime. How do I know my backup is working? Test it. Restore the backup to a staging environment or local machine at least once per year. A backup you have not tested is not a backup.

Static Site vs WordPress for an Affiliate Website

Choosing between a static site and WordPress for an affiliate website is not just a technical decision. It affects how quickly you publish, how you manage SEO fields, how easy it is to update pages, how much maintenance you accept, and whether you can grow the site without rebuilding everything. For most beginners, WordPress is easier when the site needs frequent publishing, plugins, forms, affiliate tables, and non-technical editing. A static site can be faster and simpler when you are comfortable editing files, using templates, and keeping the stack lean.Start with the job of the affiliate site Before choosing a platform, define the job of the site. An affiliate website may need to:publish tutorials; compare tools or products; update buying guides; manage affiliate disclosures; add internal links; collect emails; create service or consulting paths; track which pages generate clicks.A platform is good only if it supports that job without creating too much friction. The easiest tool for launching a homepage may not be the best tool for maintaining 100 affiliate pages. When WordPress is the safer beginner choice WordPress is often better when you want an editorial system. You can log in, create posts, edit categories, install SEO plugins, manage media, add forms, and hand editing work to someone else later. WordPress works well for affiliate sites that need:frequent content updates; non-technical editing; plugin-based SEO fields; comparison tables or product blocks; easy media management; comments or forms; a familiar workflow for freelancers.The trade-off is maintenance. You need to manage themes, plugins, backups, security updates, hosting quality, and performance. WordPress can be beginner-friendly, but it is not maintenance-free. If your main challenge is simply getting a useful site online, the Build Websites section is the right starting point before you commit to a platform. When a static site can be better A static site can be a strong choice when speed, simplicity, and control matter more than a visual editor. Static sites can be fast, secure by default, and easy to host cheaply. A static site may fit if:you are comfortable editing Markdown or content files; you want a fast content site with fewer moving parts; you do not need many plugins; you can manage templates or ask someone to set them up; you value performance and portability; you publish in a structured workflow.The weakness is editing convenience. If every small update requires a developer or a Git workflow you do not understand, the site may stop getting updated. Affiliate sites need fresh, accurate content, so the publishing workflow matters as much as performance. Compare by real operating needs Use this table before deciding:Question WordPress may fit Static site may fitWho edits the site? non-technical editors technical owner or structured workflowHow often do pages change? often less often or batch updatesDo you need plugins? yes, many no, keep it simpleIs speed a priority? possible, but needs tuning usually easierDo you need forms and lead capture? plugin-friendly requires services or custom setupWill you outsource editing? easier harder unless workflow is documentedA common mistake is choosing static because it is faster, then failing to update affiliate pages. Another mistake is choosing WordPress because it is familiar, then installing too many plugins and slowing the site down.SEO control is different, not automatically better Both WordPress and static sites can work for SEO. The difference is how you control SEO fields, internal links, schema, speed, and content structure. WordPress gives you plugins and an admin interface. Static sites give you templates and build-time control. Neither platform automatically creates helpful content. For affiliate SEO, focus on:clear page titles; useful descriptions; crawlable content; internal links; comparison criteria; disclosure; updated facts; fast pages; clear next steps.If you are new to SEO, do not choose a platform based only on plugin lists. Choose the platform you can keep accurate and useful. The decision framework A simple decision path:If you need non-technical editing, start with WordPress. If you want maximum simplicity and can handle file-based editing, consider static. If affiliate tables, plugins, and forms matter now, WordPress is easier. If performance, security, and low maintenance matter most, static can be better. If you are unsure, choose the path you can update every week.The last point matters most. An affiliate site that gets updated is usually better than a technically elegant site that nobody maintains. Next step If you are building your first income site, do not start with the platform debate alone. Decide the content model, monetization path, and first 10 pages. Then choose the platform that makes those pages easiest to publish and maintain. For help turning the choice into a launch plan, start with Start Here or the Website Starter Setup service page.