If your goal is income from content, the site itself should stay out of the way: fast pages, a low monthly bill, and a publishing flow you will actually keep. A static Astro site on a CDN is a boring stack on purpose.

This is a first-hosting guide, not a framework tour. For the content calendar that sits on top of it, see the 90-day niche blog plan.

Why Astro for money sites

Search and ads both punish slow, bloated pages. Astro’s default is HTML with almost no JavaScript unless you opt in.

• Core Web Vitals are easier to keep in the green without a performance project
• Markdown (or MDX) scales as a folder of guides, not a CMS you have to babysit
• Affiliate links and a simple analytics snippet do not require a plugin bazaar

You can earn on WordPress. You will also spend more time on updates, caching plugins, and theme breakage. If the product is articles, static output is usually the cheaper path.

A deploy path that stays boring

You do not need a custom server on day one.

1. Keep the site in a git repository you control
2. Connect that repo to a host that builds on every push (Vercel is a natural fit for Astro)
3. Set the public site URL in the host’s settings so sitemaps and canonicals match the real domain
4. Attach the custom domain and wait for HTTPS
5. Submit sitemap.xml in Google Search Console

Vercel’s free tier is enough for an early content site. Paid plans matter later (team, spend on bandwidth), not before you have pages worth ranking.

When shared hosting still makes sense

Astro-on-Vercel is not the only honest answer.

Use a shared host if you are running WordPress, PHP apps, or a staging box that is not a static build. Beginner searches still land on Hostinger for that job. Do not put a static Astro site there just because the landing page is cheap — you will fight the platform instead of publishing.

DNS without the 3 a.m. cutover

Buy the domain wherever you like. Point DNS through Cloudflare so you can change nameservers once, then swap A/CNAME records while you move hosts.

• Keep TTL short (five minutes to an hour) until the cutover looks clean in a private window
• Add the apex and www the way your host documents — mixed leftovers are the usual “why is it still the old site?” bug
• Turn on the proxy only after you understand whether the host needs grey-cloud (DNS only) during verification

SEO checklist that matters in the first month

• One H1 and one job per URL
• Unique title and meta description that match the query
• Internal links between related guides (this page should not be an island)
• Compress images; do not let a huge hero shift the layout
• Working sitemap.xml and robots.txt
• A privacy page and an affiliate disclosure before you chase traffic or ads

Monetization readiness

Before you buy traffic or apply for display ads:

• Disclose affiliate links on pages that use them
• Analytics you will actually open (pageviews and outbound clicks)
• A topical cluster, not five unrelated posts — freelancing and digital products is a cleaner start than “random tools I like”

Ten useful URLs in one niche beat fifty thin ones. If you also sell client services from the same brand, keep AI billing honest so the content site and the freelance practice share the same trust standard.

Bottom line

Treat the site like a product: ship, measure, improve. Fancy themes do not pay. Search intent and pages a reader can use today do.