Web hosting

How to host a website in India: step-by-step guide for beginners (2027)

6 min read By Cloud Ninza

From "I have a website" to "it is live on my domain with https" in seven steps — for WordPress, plain HTML and apps — with what each step costs in India and the mistakes to avoid.

In short To host a website: 1) choose a hosting plan that runs your kind of site (WordPress, HTML, PHP, Node.js, Python or Java) on servers near your visitors; 2) buy or use your domain name; 3) upload your site or install WordPress; 4) test it on a temporary address; 5) point your domain's A records (@ and www) to the server; 6) let free SSL switch on https; 7) set up backups and email records. On Cloud Ninza the account is created automatically after payment and plans start at ₹1,788 a year.

Before you start: the three things you need

Hosting a website is not difficult once you see the pieces. You need a website (WordPress, an HTML site from a designer or a page builder, or an app in PHP, Node.js, Python or Java), a domain name such as yourbrand.in, and hosting — the server that keeps the site online. Budget about ₹500–₹1,000 a year for a .in or .com domain at any registrar and from ₹1,788 a year for hosting. The steps below take one to two hours for a small site.

Step 1: Choose hosting that runs your kind of site

This is the decision that matters most. Match the plan to what you are hosting:

You haveChooseCloud Ninza plan from
A WordPress site or WooCommerce storeWordPress hosting₹1,788 a year
HTML/CSS/JS files or a React/Vue buildStatic website hosting₹1,788 a year
A PHP or Laravel sitePHP hosting₹1,788 a year
A Node.js, Next.js or NestJS appNode.js hosting₹2,988 a year
A Django, Flask or FastAPI appPython hosting₹2,988 a year
A Spring Boot, JSP or WAR appJava hosting₹3,588 a year
Docker, root access, custom softwareA cloud server₹1,073 a month

Also check that the servers are in India if your visitors are, that SSL is free and automatic, and that backups are off-site. When you pay, Cloud Ninza creates your account automatically and emails you; you can also start on a free cloudninza.in address if your domain is not ready.

Step 2: Get your domain ready

If you already own a domain, find out where its DNS is managed — usually your registrar (GoDaddy, Hostinger, BigRock, Namecheap) or Cloudflare. If you are buying one, choose a short name, prefer .in or .com, and make sure it is registered in your name or your company's, with auto-renew on. The domain and the hosting are separate: you can keep the domain at any registrar and point it to any host.

Step 3: Put your website on the server

How you put the site on the server depends on what you built:

WordPress

Choose a WordPress plan and tick "Install WordPress for me" at checkout (or install it later from the dashboard). Open wp-admin straight from the dashboard with one click — no password screen — then pick a theme, add pages and install plugins. Moving an existing WordPress site? Copy its files and database, or use a migration plugin, to the new account.

Static HTML site

Zip the folder that contains index.html and upload it with Deploy a zip, or use the File manager to upload into public_html. The previous three versions are kept, so you can undo a bad upload in one click.

PHP, Node.js, Python or Java app

Connect your GitHub, GitLab or Bitbucket repository and deploy, or upload with the File manager or SSH. Set environment variables (database URL, secret keys) in App settings, choose the framework preset and runtime version, and press Deploy. Each deploy has a health check and rolls back automatically if the new version fails.

Step 4: Test on a temporary address

Never switch a domain to an untested site. Open your site on its temporary address and check: every menu link, contact and enquiry forms, checkout or payment in test mode, images and fonts, mobile layout, and page speed. Fix problems now, while your old site (if any) is still serving visitors.

Step 5: Point your domain to the hosting

At your DNS provider, set two A records to the server's IP address shown in your dashboard: one for @ (the bare domain) and one for www. Delete any other A or AAAA records for @ and www, or some visitors will still reach the old place. If you use Cloudflare, you can keep the orange cloud on; set SSL to Full (strict). Most changes work within minutes; some networks take a few hours.

Keep your MX records as they are if your email is with Google Workspace, Microsoft 365 or another provider — moving your website does not require moving your email.

Step 6: Switch on HTTPS (free SSL)

As soon as your domain reaches the server, Cloud Ninza requests a free Let's Encrypt certificate for both the domain and www, installs it, forces https and renews it automatically before it expires. You do not need to buy an SSL certificate for a normal website.

Step 7: Backups, email records and the launch checklist

Before you announce the site, run through this list:

  • Backups: confirm off-site backups are running — on Cloud Ninza they are encrypted, kept for 30 days and restorable by you from Dashboard → Backups.
  • Email records: if the site sends email (contact forms, WooCommerce orders), add SPF, DKIM and DMARC records so mail is not marked as spam. Check them with our free SPF, DKIM and DMARC checker.
  • Security: strong passwords, two-step verification on your hosting account, WordPress and plugins updated.
  • Search: submit your sitemap in Google Search Console and Bing Webmaster Tools.
  • Analytics: add Google Analytics or another tool to see visitors.

Common mistakes when hosting a website for the first time

These are the problems we see most often in support:

  • Choosing a plan that does not run your stack (for example, a PHP-only plan for a Node.js app).
  • Leaving an old A or AAAA record in DNS, so half the visitors see the old site.
  • Switching the domain before testing on a temporary address.
  • Using Cloudflare's 'Flexible' SSL mode, which causes redirect loops — use Full (strict).
  • Keeping the only backup on the same server as the site.
  • Buying on a first-year offer without checking the renewal price.

After launch: the first 30 days

Going live is the start, not the finish. In the first week, open the site every day from a phone on mobile data and from a laptop, submit your own contact form, and place a test order if you sell online — real visitors find the broken link you missed. Look at the error log in the dashboard once a day; a PHP warning or an app exception repeated on every page is the first sign of a problem.

In the first month, add the site to Google Search Console and Bing Webmaster Tools and submit your sitemap, so new pages are found quickly. Check that a backup restore works by restoring one file to a folder — a backup you have never restored is a hope, not a plan. Finally, write down where everything is: the registrar login, the hosting account, the DNS provider and who to call. When something breaks a year from now, that one page saves hours.

Key takeaways

The short version, for anyone skimming:

  • Hosting a website = the right plan for your stack + your domain + uploading the site + DNS + SSL.
  • Test on a temporary address before you point the domain.
  • Set A records for @ and www to the server; leave MX records alone unless you move email too.
  • Free automatic SSL and off-site backups should be included, not extras.
  • Cloud Ninza creates your account automatically after payment; plans start at ₹1,788 a year.
Host it with us

Web Hosting from ₹1,788/year

Web hosting on cloud servers in India for PHP, WordPress, Node.js, Python and Java sites, from ₹149 a month billed yearly. Backups twice a day (12 AM and 12 PM), last 30 days kept — restore any date yourself from your dashboard, or make your own backup any time · Spam protection: hourly and daily email sending limits per project, and automatic pausing of spam-like sending, keep your domain and our mail servers trusted · Websites or apps, storage and RAM as listed on your plan.

Ready when you are

Hosting from ₹149 a month on servers in India

WordPress, static HTML, PHP, Node.js, Python and Java plans with free SSL and your choice of version. Create your account, pick a plan and pay by UPI, card or netbanking; your hosting is created automatically and you get your login by email, usually within minutes.

Questions

Questions on this topic

How do I host my website for the first time?

Choose a hosting plan for your kind of site, upload or install the site, test it on the temporary address, point your domain's A records to the server and let free SSL switch on https.

How much does it cost to host a website in India?

A domain costs about ₹500–₹1,000 a year and hosting from ₹1,788 a year on Cloud Ninza. A WordPress site is ₹1,788 a year.

Can I host a website without a domain?

Yes, temporarily. Any Cloud Ninza plan can use a free cloudninza.in address, so you can build and share the site before your domain is ready.

How long does it take for a website to go live?

The hosting account is created automatically after payment. DNS changes usually work within minutes and occasionally take a few hours.

Can I host a website on my own computer?

Technically yes, but it must stay on all the time with a fixed IP and good security. Hosting is cheaper and far more reliable.

How do I upload my website files to hosting?

Use the File manager in the dashboard, Deploy a zip for static sites, Git deploys for apps, or SFTP/SSH with your key.

What DNS records do I need?

Two A records — @ and www — pointing to your server's IP address. Add MX, SPF, DKIM and DMARC only for email.

Do I need to buy an SSL certificate?

No. Free Let's Encrypt SSL is issued and renewed automatically for your domain and www.

Can I host a React or Next.js website?

Yes. A React or Vue build runs on static website hosting; a Next.js app with a server runs on Node.js hosting.

Can I host more than one website?

Yes — larger plans include more websites or apps, and you can upgrade at any time from the dashboard.

What if my website stops working after moving?

Check that DNS points only to the new server, that the database settings are right, and look at the error log in the dashboard. Our support team can help.