Full SEO-Ready Website Creation with AI

Install and configure every tool you need — VS Code, Node.js, GitHub Desktop, and Claude Code — before writing a single prompt.

• Install VS Code — code.visualstudio.com/download
• VS Code Overview — explore the editor layout, terminal, and extensions panel
• Install Node.js via nvm — nodejs.org/en/download (use nvm install 24)
• Compare Claude Code vs GitHub Copilot — understand when to use each
• Subscribe to GitHub Copilot (optional alternative to Claude Code)
• Install GitHub Desktop — visual Git client for commits, branches, and PRs
• Create a GitHub Repository for your project
• Open the repo folder in VS Code
• Install Claude Code and set up Claude API access
• Your first Claude Code chat — ask it to create a README.md file

Learn the full Git workflow — commit, push, branch, pull request, and merge — so you never lose a working version of your site.

• Stage and commit your first changes (git add + git commit)
• Push to GitHub (git push)
• Create a new branch (git checkout -b branch-name)
• Open a Pull Request on GitHub
• Merge the PR into main

Understand how to direct an AI using a PRD and CLAUDE.md, learn Markdown basics, and run the starter prompt to generate your build checklist.

• Understand what agentic coding means vs traditional coding
• Learn Markdown basics — headings, lists, code blocks, bold/italic
• Download course resources: PRD, CLAUDE.md, and starter prompts
• Read the PRD (what to build) and CLAUDE.md (how to behave)
• Place CLAUDE.md in your project root
• Run the starter prompt — Claude reads the PRD and outputs a build checklist

Go phase by phase — scaffold, layout, core pages, blog system — using AI-generated prompts, reviewing each output before moving on.

• Prompting fundamentals — dos and don'ts of a perfect prompt in vibe coding
• GitHub Copilot: place PRD + .github/copilot-instructions.md in project root
• Create prompts.md for detailed prompts for each phase - using AI
• Phase 1: Ask AI for a focused prompt, run it, review output, test locally
• Phase 2: Core layout and styling — navbar, footer, dark mode, global CSS
• Phase 3: Core pages — homepage, about, contact
• Phase 4: Blog system — Archive and single posts, each post as a .tsx file
• Final test — full site running locally with at least 4 blog posts

Add metadata, Open Graph tags, sitemap, and robots.txt — then write SEO rules into CLAUDE.md so every future page is automatically optimised.

• Add metadata — title tag and meta description for each page
• Add Open Graph tags — how pages look when shared on social media
• Generate sitemap.xml — auto-updated map of all pages
• Create robots.txt — tells crawlers what to index and what to skip
• Write SEO rules into CLAUDE.md — title format, meta description, alt text
• Same SEO rules into .github/copilot-instructions.md for GitHub Copilot users
• Test: ask the AI to create a new page and verify it follows the SEO rules

Before you run the production build, you do a full review of the site locally.

• Do a full review of all pages in browser using npx serve out
• Check all internal links work correctly
• Check dark and light mode on every page
• Check responsive layout at mobile screen size
• Verify all 4 blog posts render correctly
• Verify SEO meta tags using browser DevTools or a meta tag checker
• Confirm robots.txt and sitemap.xml are present in the out/ folder
• Run final clean build — rm -rf .next/ then npm run build
• Verify the /out folder was generated without errors

Your /out folder is ready — now buy hosting, claim your free domain with Hostinger, and log in to hPanel.

• Use link vkapoor.co/hostinger to get the best deal
• Use code VASHISHTHA10 for an extra 10% off
• Discount applies only on 12, 24, or 48 month plans — not monthly
• Choose a Hostinger plan — Shared Hosting recommended for beginners
• Complete purchase and access hPanel
• Claim your free domain from hPanel after checkout

Two ways to deploy — simple File Manager upload for beginners, or one-command rsync over SSH for automation.

• Simple method: upload the out/ folder to public_html/ via Hostinger File Manager
• Generate .htaccess file in public/ folder — use a Hindi prompt to Claude for generation
• Ensure .htaccess is included in the build output
• Alternate (rsync): generate SSH key on local machine (ssh-keygen)
• Alternate (rsync): add public key to Hostinger SSH access
• Alternate (rsync): test SSH connection with SSH command
• Alternate (rsync): build the rsync command with server IP, port, and public_html path
• Alternate (rsync): run the rsync command and verify files in /public_html

Register your live site with Google Search Console and Bing Webmaster Tools, submit the sitemap, and check that pages are being indexed.

• Add site to Google Search Console — verify ownership via HTML tag or DNS record
• Add site to Bing Webmaster Tools — import from GSC or verify separately
• Submit the sitemap.xml URL to both platforms
• Check the coverage report — confirm pages are being discovered without errors
• Understand indexing timeline — pages typically appear in search within days to weeks