Revision 3
Website

@namkyu · Aug 26, 2026, 4:10 PM
Updated global scope, monetization economics, representative services, and operating costs while preserving existing Website research, operational detail, and source links.
+34,772−25,439
+A website can be launched with very little infrastructure cost, but operating one as a real public service requires more than writing code. Domain and DNS configuration, hosting, HTTPS, analytics, search indexing, authentication, backups, monitoring, payments, and monetization become separate operational concerns once the site goes live.
+ 
+A website is also not a single business model. A content publisher, SaaS product, affiliate site, marketplace, community, and paid membership site can use similar infrastructure while having completely different revenue and cost structures.
−A website can be launched with very little infrastructure cost, but operating one as a real public service requires more than writing code. Domain and DNS configuration, hosting, HTTPS, analytics, search indexing, authentication, backups, and monetization become separate operational concerns once the site goes live.
  
 # Quick Facts
  
  
+| Item                  | Practical starting point                                                                                                  |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| Development software  | Free                                                                                                                      |
+| Google Analytics      | Free for GA4 properties                                                                                                   |
+| Google Search Console | Free                                                                                                                      |
+| Cloudflare            | Free plan available                                                                                                       |
+| HTTPS                 | Free options available                                                                                                    |
+| Google Sign-In        | Google Identity Services                                                                                                  |
+| Custom domain         | Paid; registration and renewal vary by TLD and registrar                                                                  |
+| Hosting               | Free tier, VPS, cloud, managed hosting, or self-hosting                                                                   |
+| Main monetization     | Advertising, subscriptions, affiliate commissions, sponsorships, paid listings, transactions, digital products, donations |
+| Search visibility     | Crawling, indexing, and ranking are separate; publishing does not guarantee search traffic                                |
+| Main hidden work      | Deployment, DNS, authentication, indexing, monitoring, backups, maintenance, moderation, and support                      |
−| Item                  | Practical starting point                                                                                |
−| --------------------- | ------------------------------------------------------------------------------------------------------- |
−| Development software  | Free                                                                                                    |
−| Google Analytics      | Free for GA4 properties                                                                                 |
−| Google Search Console | Free                                                                                                    |
−| Cloudflare            | Free plan available                                                                                     |
−| HTTPS                 | Free options available                                                                                  |
−| Google Sign-In        | Google Identity Services                                                                                |
−| Custom domain         | Paid; registration and renewal vary by TLD and registrar                                                |
−| Hosting               | Free tier, VPS, cloud, managed hosting, or self-hosting                                                 |
−| Main monetization     | Advertising, subscriptions, affiliate commissions, sponsorships, paid listings, transactions, donations |
−| Search visibility     | Crawling and indexing are not guaranteed                                                                |
−| Main hidden work      | Deployment, DNS, authentication, indexing, monitoring, backups and maintenance                          |
  
  
+A functioning website can therefore have very low software costs. The cost profile changes substantially when traffic, storage, database usage, email delivery, APIs, redundancy, payment processing, moderation, customer support, or paid acquisition increase.
−A functioning website can therefore have very low software costs. The cost profile changes substantially when traffic, storage, database usage, email delivery, APIs, redundancy, moderation, or paid acquisition increase.
  
 # Minimum Entry Setup
⋯ Unchanged lines omitted ⋯
  
  
+| Requirement       | Minimum option                                                                                 | Cost                   | Priority    | Notes                                            |
+| ----------------- | ---------------------------------------------------------------------------------------------- | ----------------------: | ----------- | ------------------------------------------------ |
+| Code editor       | [Visual Studio Code](/wiki/visual-studio-code) or equivalent                                   | Free                   | Essential   | For custom development                           |
+| Source control    | [Git](/wiki/git) + [GitHub](/wiki/github) free account                                         | Free                   | Recommended | Version control and deployment workflow          |
+| Framework         | [Next.js](/wiki/nextjs), other open-source framework, or static HTML                           | Free                   | Optional    | Depends on site type                             |
+| Database          | [PostgreSQL](/wiki/postgresql), [Supabase](/wiki/supabase), or another database                | Free entry possible    | Optional    | Dynamic sites only                               |
+| Hosting           | Free-tier host or existing hardware                                                            | $0 additional possible | Essential   | Limits depend on provider                        |
+| DNS/CDN           | [Cloudflare](/wiki/cloudflare) Free                                                            | Free                   | Recommended | DNS, CDN, DDoS protection and SSL                |
+| HTTPS             | [Let's Encrypt](/wiki/lets-encrypt), Cloudflare Universal SSL, or hosting-provider certificate | Free                   | Essential   | Public sites should use HTTPS                    |
+| Analytics         | [Google Analytics](/wiki/google-analytics)                                                     | Free                   | Recommended | Visitor and acquisition measurement              |
+| Search monitoring | [Google Search Console](/wiki/google-search-console)                                           | Free                   | Recommended | Google crawling, indexing and search performance |
+| Authentication    | [Google Sign-In](/wiki/google-sign-in) or application-managed accounts                         | Free entry possible    | Optional    | Needed only for user accounts                    |
+ 
−| Requirement       | Minimum option                                                         | Cost                     | Priority    | Notes                                            |
−| ----------------- | ---------------------------------------------------------------------- | ------------------------ | ----------- | ------------------------------------------------ |
−| Code editor       | [Visual Studio Code](/wiki/visual-studio-code) or equivalent           | Free                     | Essential   | For custom development                           |
−| Source control    | [Git](/wiki/git) + [GitHub](/wiki/github) free account                 | Free                     | Recommended | Version control and deployment workflow          |
−| Framework         | [Next.js](/wiki/nextjs), other open-source framework, or static HTML   | Free                     | Optional    | Depends on site type                             |
−| Database          | [PostgreSQL](/wiki/postgresql) or other open-source database           | Free software            | Optional    | Dynamic sites only                               |
−| Hosting           | Free-tier host or existing hardware                                    | US$0 additional possible | Essential   | Limits depend on provider                        |
−| DNS/CDN           | [Cloudflare](/wiki/cloudflare) Free                                    | Free                     | Recommended | DNS, CDN, DDoS protection and SSL                |
−| HTTPS             | Cloudflare Universal SSL or hosting provider certificate               | Free                     | Essential   | Public sites should use HTTPS                    |
−| Analytics         | [Google Analytics](/wiki/google-analytics)                             | Free                     | Recommended | Visitor and acquisition measurement              |
−| Search monitoring | [Google Search Console](/wiki/google-search-console)                   | Free                     | Recommended | Google crawling, indexing and search performance |
−| Authentication    | [Google Sign-In](/wiki/google-sign-in) or application-managed accounts | Free entry possible      | Optional    | Needed only for user accounts                    |
  
+The major unavoidable cash expense for many small custom websites is therefore the domain rather than the development stack itself. A developer who already owns suitable hardware can also self-host, although this transfers uptime, networking, backups, security, and hardware-failure responsibility from a hosting company to the operator.
  
+A custom domain is not technically required when a hosting provider supplies a subdomain, but it is normally part of a serious public or commercial deployment.
−The major unavoidable cash expense for many small custom websites is therefore the domain rather than the development stack itself. A developer who already owns suitable hardware can also self-host, although this transfers uptime, networking, backups and hardware failure responsibility from a hosting company to the operator.
  
 # From Code to a Working Website
⋯ Unchanged lines omitted ⋯
 ## Managed hosting
  
+Platforms such as [Vercel](/wiki/vercel), [Cloudflare Pages](/wiki/cloudflare-pages), and [Netlify](/wiki/netlify) reduce infrastructure work by handling deployment, HTTPS, and parts of the networking stack.
−Platforms such as [Vercel](/wiki/vercel) reduce infrastructure work by handling deployment, HTTPS and parts of the networking stack.
  
 This is useful for developers who want to deploy directly from a Git repository without maintaining a Linux server.
  
+The trade-off is that infrastructure pricing, usage limits, and platform-specific architecture become relevant as usage increases.
−The trade-off is that infrastructure pricing and platform limits become relevant as usage increases.
  
 ## VPS
  
+A [VPS](/wiki/vps) gives the operator substantially more control.
−A virtual private server gives the operator substantially more control.
  
 A typical custom stack can include:
⋯ Unchanged lines omitted ⋯
 - a reverse proxy such as [Caddy](/wiki/caddy) or [Nginx](/wiki/nginx).
  
+The operator becomes responsible for updates, firewall configuration, database backups, storage, monitoring, and recovery.
−The operator becomes responsible for updates, firewall configuration, database backups, storage, monitoring and recovery.
  
 ## Self-hosting
⋯ Unchanged lines omitted ⋯
 - residential or business internet reliability;
 - router configuration;
+- public IP or alternative networking configuration;
−- public IP or networking configuration;
 - hardware failure;
 - storage failure;
 - backups;
 - power outages;
+- software updates;
 - remote recovery.
  
 Self-hosting therefore reduces direct hosting expenditure but does not eliminate infrastructure cost or operational work.
  
+Residential internet connections may also use dynamic addresses, blocked inbound ports, carrier-grade NAT, or other restrictions that affect public hosting. These conditions differ by internet provider and country.
+ 
 # Domain, DNS, CDN and HTTPS
  
⋯ Unchanged lines omitted ⋯
 For a self-hosted service, operators can restrict direct access to the origin and allow public web traffic through the proxy, provided the configuration does not unintentionally block legitimate traffic.
  
+When a CDN or reverse proxy is used, there can be two separate encrypted connections:
+ 
+`Visitor → CDN/proxy → Origin`
+ 
+A valid edge certificate therefore does not by itself guarantee that the origin TLS configuration is correct.
+ 
 ## `www` and apex domains
  
⋯ Unchanged lines omitted ⋯
 A production site should deliberately decide which is canonical and redirect the other when appropriate.
  
+HTTPS, DNS records, reverse-proxy configuration, OAuth URLs, and application base URLs need to agree. A configuration can therefore work at:
−HTTPS, DNS records, reverse-proxy configuration and application URLs need to agree. A configuration can therefore work at:
  
 `https://example.com`
⋯ Unchanged lines omitted ⋯
  
 | Service                                              | What it answers                            | Cost                    |
+| ---------------------------------------------------- | ------------------------------------------ | -----------------------: |
−| ---------------------------------------------------- | ------------------------------------------ | ----------------------- |
 | [Google Analytics](/wiki/google-analytics)           | Who visits the website and how they use it | Free for GA4 properties |
 | [Google Search Console](/wiki/google-search-console) | How the website performs in Google Search  | Free                    |
⋯ Unchanged lines omitted ⋯
 They are complementary rather than substitutes.
  
+Other analytics products such as [Plausible Analytics](/wiki/plausible-analytics), [Matomo](/wiki/matomo), and [Cloudflare Web Analytics](/wiki/cloudflare-web-analytics) can be relevant when privacy, data ownership, or lighter client-side scripts are priorities.
+ 
 # Google Analytics
  
⋯ Unchanged lines omitted ⋯
 Analytics does not tell an operator whether a page has successfully entered Google's search index. That is a Search Console function.
  
+For a global website, analytics should also be interpreted geographically. Conversion rates, advertising value, purchasing power, payment methods, and user behavior may differ substantially between countries.
+ 
 # Google Search Console
  
⋯ Unchanged lines omitted ⋯
 - clicks;
 - queries;
+- countries;
+- devices;
 - links;
 - sitemap processing;
⋯ Unchanged lines omitted ⋯
 `Discovered → Crawled → Indexed → Served/ranked`
  
+A page being discovered does not mean it has been crawled.
+ 
 A page being crawled does not mean it has been indexed.
  
⋯ Unchanged lines omitted ⋯
 Repeatedly requesting recrawling of the same unchanged URL does not make Google crawl it faster.
  
+Search visibility can also differ by country and language. A page that performs well for one geographic audience may have little visibility elsewhere because competition, language, search intent, and available results differ.
+ 
 # Sitemap
  
⋯ Unchanged lines omitted ⋯
 [Google Sign-In](/wiki/google-sign-in), based on Google Identity Services, lets users authenticate with an existing Google Account.
  
+Google's current web setup requires an OAuth 2.0 client ID. The developer creates or selects a project in Google Cloud Console, configures OAuth branding/settings, and loads the Google Identity Services client library.
−Google's current web setup requires an OAuth 2.0 client ID. The developer creates or selects a project in Google Cloud Console, configures OAuth branding/settings and loads the Google Identity Services client library.
  
 Production configuration can involve:
⋯ Unchanged lines omitted ⋯
 Authentication should also be distinguished from authorization to Google APIs. Google Identity Services separates signing a user into a website from requesting permission to access additional Google data.
  
+Other representative authentication services include [Auth0](/wiki/auth0), [Clerk](/wiki/clerk), [Supabase Auth](/wiki/supabase-auth), and [Firebase Authentication](/wiki/firebase-authentication).
+ 
 # Google Cloud Is Not the Same as Google Login
  
⋯ Unchanged lines omitted ⋯
 The server itself can remain completely outside Google Cloud.
  
+Likewise, [Google Analytics](/wiki/google-analytics), [Google Search Console](/wiki/google-search-console), and Google Cloud have different purposes despite all being Google services.
−Likewise, [Google Analytics](/wiki/google-analytics), [Google Search Console](/wiki/google-search-console) and Google Cloud have different purposes despite all being Google services.
  
 # Operating Stack Example
⋯ Unchanged lines omitted ⋯
  
  
+| Layer               | Example                                                            |
+| ------------------- | ------------------------------------------------------------------ |
+| Application         | [Next.js](/wiki/nextjs)                                            |
+| Database            | [PostgreSQL](/wiki/postgresql)                                     |
+| Containers          | [Docker](/wiki/docker)                                             |
+| Reverse proxy       | [Caddy](/wiki/caddy)                                               |
+| DNS/CDN             | [Cloudflare](/wiki/cloudflare)                                     |
+| HTTPS               | Caddy and/or Cloudflare                                            |
+| Authentication      | [Google Sign-In](/wiki/google-sign-in)                             |
+| Traffic measurement | [Google Analytics](/wiki/google-analytics)                         |
+| Search monitoring   | [Google Search Console](/wiki/google-search-console)               |
+| Transactional email | [Resend](/wiki/resend), [Amazon SES](/wiki/amazon-ses), or similar |
+| Error monitoring    | [Sentry](/wiki/sentry) or application logs                         |
+| Payments            | [Stripe](/wiki/stripe) or an appropriate regional provider         |
+| Search discovery    | XML sitemap + crawlable internal links                             |
−| Layer               | Example                                              |
−| ------------------- | ---------------------------------------------------- |
−| Application         | [Next.js](/wiki/nextjs)                              |
−| Database            | [PostgreSQL](/wiki/postgresql)                       |
−| Containers          | [Docker](/wiki/docker)                               |
−| Reverse proxy       | [Caddy](/wiki/caddy)                                 |
−| DNS/CDN             | [Cloudflare](/wiki/cloudflare)                       |
−| HTTPS               | Caddy and/or Cloudflare                              |
−| Authentication      | [Google Sign-In](/wiki/google-sign-in)               |
−| Traffic measurement | [Google Analytics](/wiki/google-analytics)           |
−| Search monitoring   | [Google Search Console](/wiki/google-search-console) |
−| Search discovery    | XML sitemap + crawlable internal links               |
  
  
⋯ Unchanged lines omitted ⋯
 Revenue depends on what the site provides and what economic action occurs after traffic arrives.
  
−Common models include:
  
− 
 | Model               | Revenue event                       | Common fit                       |
 | ------------------- | ----------------------------------- | -------------------------------- |
⋯ Unchanged lines omitted ⋯
 Traffic alone is therefore not revenue.
  
+Two websites with the same monthly visitors can have radically different economics depending on visitor geography, purchase intent, advertising niche, conversion rate, pricing, and revenue model.
+ 
+# Website Earnings
+ 
+There is no useful global "average website income" that applies across websites because a personal blog, SaaS application, ecommerce marketplace, subscription publication, and financial comparison site generate revenue through fundamentally different transactions.
+ 
+More useful economic measures depend on the model:
+ 
+- advertising → publisher revenue per 1,000 pageviews or sessions;
+- affiliate → commission per referred sale or action;
+- subscription → paying subscribers × net revenue per subscriber;
+- marketplace → transaction volume × take rate;
+- [SaaS](/wiki/saas) → customers × recurring revenue per customer;
+- sponsorship → contracted payment per placement or campaign.
+ 
+These measures should not be combined into a single website-wide earnings benchmark.
−Two websites with the same monthly visitors can have radically different economics depending on visitor geography, purchase intent, advertising niche, conversion rate, pricing and revenue model.
  
 # Advertising
⋯ Unchanged lines omitted ⋯
 `Page RPM = estimated publisher revenue / page views × 1,000`
  
+For AdSense for Content, Google states that publishers receive 80% of revenue after the advertiser platform takes its fee. When advertisers buy display ads through Google Ads, Google says publishers retain approximately 68% of advertiser spend.\[\* This is Google's revenue-share structure, not a prediction of the RPM an individual website will earn.\]
+ 
+The revenue-share percentage does not mean advertising earnings are geographically equal.
+ 
+Actual publisher RPM can differ substantially according to:
+ 
+- visitor country;
+- advertiser demand;
+- topic;
+- season;
+- device;
+- traffic source;
+- ad viewability;
+- time on page;
+- ad placement.
+ 
+A site with substantial traffic can therefore generate weak advertising revenue when visitors come from lower-value advertising markets or when the content has little commercial intent.
−A site with substantial traffic can still generate weak advertising revenue when visitors come from low-value advertising markets or when the content has little commercial intent.
  
 Advertising also creates a trade-off between monetization and user experience because additional placements can increase visual clutter and page weight.
  
+Google's AdSense payment threshold also depends on the account's reporting currency. For accounts using U.S. dollars, the payment threshold is US$100; other currencies have their own thresholds.
+ 
 # Affiliate Revenue
  
⋯ Unchanged lines omitted ⋯
 Actual commission rates and attribution windows should be checked against each affiliate program rather than assumed across the industry.
  
+For example, the U.S. [Amazon Associates](/wiki/amazon-associates) program lists standard commission rates that vary substantially by product category, including 10% for Luxury Beauty, 4.5% for Physical Books, Kitchen and Automotive, and 3% for many Home, Pets, Sports and other categories.\[\* These are U.S. Amazon Associates rates and should not be generalized to Amazon affiliate programs in other countries.\]
+ 
 # Subscription and Premium Features
  
⋯ Unchanged lines omitted ⋯
 - professional features.
  
+This changes the important metric from page views toward paying conversion, churn, and revenue per customer.
+ 
+A website can process recurring payments through [Stripe](/wiki/stripe), a merchant-of-record service, or another payment provider appropriate to the operator's country.
+ 
+Hosted publishing platforms may add another platform fee. [Substack](/wiki/substack), for example, charges publishers 10% of each paid-subscription transaction in addition to payment-processing and billing fees charged through Stripe.
+ 
+Payment availability, processing fees, local payment methods, taxes, and currency-conversion costs can differ by country, so one country's payment economics should not be generalized globally.
−This changes the important metric from page views toward paying conversion, churn and revenue per customer.
  
 # Wiki and Community Monetization
⋯ Unchanged lines omitted ⋯
 [Fandom](/wiki/fandom) is an example of a for-profit Wiki platform whose business includes advertising and commercial partnerships.
  
+Other knowledge/community projects may instead use advertising, donations, memberships, subscriptions, sponsorships, affiliate links, paid listings, or combinations of these models.
−Other knowledge/community projects may instead use donations, memberships, subscriptions or combinations of these models.
  
+The existence of a large Wiki does not establish that a new Wiki can reproduce its economics. Community size, search distribution, moderation cost, accumulated content, brand recognition, and advertiser relationships are major differences.
−The existence of a large Wiki does not establish that a new Wiki can reproduce its economics. Community size, search distribution, moderation cost and accumulated content are major differences.
  
 # Search Traffic as an Asset
⋯ Unchanged lines omitted ⋯
 Each page becomes another potential search entry point.
  
+This makes structured Wiki, directory, and database models different from a small fixed marketing website: adding useful pages expands the site's searchable surface area.
−This makes structured Wiki, directory and database models different from a small fixed marketing website: adding useful pages expands the site's searchable surface area.
  
 However, creating URLs alone does not create search traffic. Google explicitly states that sitemap submission does not guarantee indexing, and indexing itself does not guarantee that a page will be served prominently for a query.
  
+The economic value of search traffic also depends on what visitors do after arriving. Traffic to a high-intent comparison or purchase page can have very different economics from general informational traffic.
+ 
 # Costs
  
⋯ Unchanged lines omitted ⋯
 - backup storage;
 - transactional email;
+- premium SaaS tools;
+- monitoring.
+ 
+Domain prices differ by registrar and TLD rather than having a universal website-wide price.
−- premium SaaS tools.
  
 ## Usage-based costs
⋯ Unchanged lines omitted ⋯
 - payment processing.
  
+A website using AI APIs, large media files, or heavy database queries can therefore develop significant variable costs earlier than a mostly static content site.
+ 
+## Payment costs
+ 
+Websites collecting money normally pay payment-processing or merchant-of-record fees.
+ 
+These fees differ by country, payment method, and provider.
+ 
+For example, [Stripe](/wiki/stripe) standard U.S. card pricing should not be treated as Stripe's universal global price. International cards, currency conversion, local payment methods, refunds, disputes, and subscription billing can also change the final processing cost.
+ 
 ## Human costs
  
⋯ Unchanged lines omitted ⋯
 These costs are easy to omit from an initial hosting calculation.
  
+# Monitoring, Backups and Transactional Email
+ 
+These components are often absent from a local prototype but become more important once users depend on the site.
+ 
+Representative error-monitoring options include [Sentry](/wiki/sentry), application logs, hosting-provider monitoring, and cloud observability services.
+ 
+Websites that send account verification, password recovery, login links, receipts, or notifications can use services such as [Resend](/wiki/resend), [Amazon SES](/wiki/amazon-ses), [SendGrid](/wiki/sendgrid), or [Postmark](/wiki/postmark) rather than operating their own mail server.
+ 
+Important dynamic data should also have a recovery plan. This may include:
+ 
+- database backups;
+- uploaded files;
+- configuration;
+- source code;
+- off-server backup copies.
+ 
+A backup is useful only if the data can actually be restored.
+ 
 # Practical Problems After Launch
  
⋯ Unchanged lines omitted ⋯
 A site may work on one hostname but fail on another.
  
+Apex and `www` records, certificates, redirects, reverse-proxy configuration, and application base URLs should describe the same production setup.
−Apex and `www` records, certificates, redirects, reverse-proxy configuration and application base URLs should describe the same production setup.
  
 ## OAuth works locally but fails in production
⋯ Unchanged lines omitted ⋯
 An origin TLS problem can therefore produce an error even though the application process itself is running.
  
+## Email works in development but not in production
+ 
+Production email can fail because of API credentials, sender-domain verification, DNS records, provider limits, spam filtering, or incorrect environment variables.
+ 
+A functioning application does not guarantee reliable email delivery.
+ 
 # Requirements
  
+There is no universal license or registration requirement simply for putting a website online.
+ 
+Actual legal and commercial requirements depend on the operator's country, customer locations, business model, data collected, payment activity, user age, industry, and content.
+ 
+A basic public website should technically have:
−A basic public website should have:
  
 - a publicly reachable host;
⋯ Unchanged lines omitted ⋯
 - important URLs are discoverable.
  
+A website with accounts must additionally maintain application-level sessions, authorization, and account data even when an external identity provider handles authentication.
+ 
+A commercial website may additionally need privacy disclosures, terms, tax handling, consumer disclosures, cookie or tracking consent, or other measures depending on the jurisdictions and activities involved.
+ 
+Requirements from the United States, European Union, Korea, or another jurisdiction should not be assumed to apply globally.
−A website with accounts must additionally maintain application-level sessions, authorization and account data even when an external identity provider handles authentication.
  
 # Risks / Things to Know
  
+## Distribution is not guaranteed
−## Search traffic can take time to appear
  
+A site can function correctly and still receive little search, social, referral, or direct traffic.
−Google states that crawling can take several days to several weeks after a request, and neither a crawl request nor a sitemap guarantees indexing.
  
+For organic search specifically, Google states that crawling can take several days to several weeks after a request, and neither a crawl request nor a sitemap guarantees indexing.
−A newly launched content business should therefore not treat immediate organic search traffic as guaranteed distribution.
  
 ## Free infrastructure does not mean zero operating cost
  
+A project may launch using free analytics, CDN, SSL, frameworks, and database software but later incur hosting, storage, email, API, payment-processing, and moderation expenses.
−A project may launch using free analytics, CDN, SSL, frameworks and database software but later incur hosting, storage, email, API and moderation expenses.
  
 ## Self-hosting transfers responsibility
  
+Self-hosting can reduce hosting bills but makes power, internet connectivity, hardware, firewall configuration, updates, security, backups, and recovery the operator's responsibility.
+ 
+## Third-party services create dependency
−Self-hosting can reduce hosting bills but makes power, internet connectivity, hardware, firewall configuration, updates and recovery the operator's responsibility.
  
+Search engines, payment processors, CDNs, identity providers, ad networks, affiliate programs, email providers, and APIs can change pricing, policies, limits, eligibility, or availability.
−## Authentication adds policy and account-management work
  
+## Traffic has different economic value across markets
−External login removes the need to directly authenticate passwords but does not remove the need for application sessions, permissions, account deletion and privacy handling.
  
+Advertising demand, affiliate conversion, purchasing power, payment methods, and subscription conversion can differ substantially between countries.
−## A working website is not necessarily a discoverable website
  
+Identical traffic volumes therefore do not necessarily produce identical revenue.
−A page can load correctly for users worldwide and still receive no meaningful Google traffic. Public availability, crawlability, indexing and ranking are separate conditions.
  
 # Sources
⋯ Unchanged lines omitted ⋯
 - [Google Identity Services — Overview](https://developers.google.com/identity/gsi/web/guides/overview)
 - [Google Identity Services — Setup](https://developers.google.com/identity/gsi/web/guides/get-google-api-clientid)
+- [Google AdSense Help — AdSense revenue share](https://support.google.com/adsense/answer/180195)
+- [Google AdSense Help — Payment thresholds](https://support.google.com/adsense/answer/1709871)
 - [Cloudflare — Plans](https://www.cloudflare.com/plans/)
 - [Cloudflare — Free Plan](https://www.cloudflare.com/plans/free/)
+- [Cloudflare Docs — Universal SSL](https://developers.cloudflare.com/ssl/edge-certificates/universal-ssl/)
+- [Amazon Associates — U.S. Standard Commission Income Statement](https://affiliate-program.amazon.com/help/node/topic/GRXPHT8U84RAYDXZ)
+- [Substack Help — How much does Substack cost?](https://support.substack.com/hc/en-us/articles/360037607131-How-much-does-Substack-cost)
+- [Stripe — Pricing](https://stripe.com/pricing)
+- [Vercel — Pricing](https://vercel.com/pricing)
+- [Supabase — Pricing](https://supabase.com/pricing)
+- [Sentry — Pricing](https://sentry.io/pricing/)
+- [Resend — Pricing](https://resend.com/pricing)