Freelance web developer in Mumbai.
SEO-first builds.

What do you actually build?

Six kinds of build. Marketing sites and storefronts that rank, migrations that do not break rankings, and the schema layer most Mumbai sites are missing.

• Marketing sites

  Brand sites, landing pages, and content sites built on Astro or modern WordPress. SEO-first architecture, schema baked in, sub-1s load on a Mumbai 4G connection. It should keep paying off for years instead of needing a replatform in eighteen months.

• WordPress development

  Custom themes, block-based editing, headless WordPress with a static front-end where it makes sense. No page-builder bloat. The CMS your editorial team actually wants to use.

• Shopify storefronts

  Hydrogen and Liquid storefronts for D2C brands. Performance-tuned, SEO-clean, integrated with the rest of your stack: Klaviyo, GA4, Meta CAPI, structured data. Built to rank as well as to sell.

• Migrations

  Replatform from WordPress to Astro, Webflow to Shopify, custom to headless. Pre-migration audit, redirect map, content equivalence audit, post-launch monitoring. Most agencies lose rankings during migrations; the audit and redirect map are there so you don't.

• Schema & SEO integration

  Every build ships with Person, LocalBusiness, FAQ, Article, Breadcrumb, Product schema where applicable. Core Web Vitals are a constraint from day one. This site is the reference build.

• Maintenance & retainers

  Monthly retainer for content updates, performance monitoring, schema validation, security patches, and the small builds (landing pages, microsites) that come up between bigger projects.

Which stack will you use?

I pick the tool for the job.

• Astro

  Default for marketing sites where SEO and speed are the priority. This site runs on Astro.

• WordPress

  When editorial workflow matters more than build complexity. Custom themes, no page-builder dependence.

• Shopify

  For D2C brands. Liquid for most stores, Hydrogen for performance-critical builds.

• Webflow

  For brand sites where the design team owns ongoing changes. Limited to brochure-style scope.

• Tailwind

  Default CSS layer across stacks. Design tokens, dark mode, motion handled at the token level.

• Headless CMS

  Sanity or Contentful when a separate editorial CMS is needed in front of a static or app stack.

How does it work?

1. 1

   Scope call

   Forty-five minutes. I ask about the brand, traffic profile, what you are migrating from or building first, and what good looks like. No deck. You get a straight answer on stack and timeline.

2. 2

   Fixed-scope proposal

   Within five working days: a written proposal with phases, milestones, deliverables, and a fixed fee. No T&M surprise budgets. If the scope shifts mid-build, we agree the change in writing.

3. 3

   Build sprints

   Two-week sprints. Weekly review with the founder or marketing lead. Staging URL from day three. You watch the build take shape instead of waiting for one big reveal.

4. 4

   Launch & handoff

   Pre-launch checklist, redirect testing, Lighthouse audit, schema validation. Post-launch monitoring for two weeks. Documentation handed off so your team can ship pages without me.

What have you built recently?

Three recent builds. Full case studies live on the work page.

• Technoserve · Astro rebuild

  From WordPress to Astro · PageSpeed 32 to 98, organic +71%

  Replatform from a heavy WordPress theme to a clean Astro build. Schema layer added across all twenty-eight templates. Organic traffic up 71% in the six months after launch with no content changes.

• Cottonstays · Shopify storefront

  Custom Shopify build with full structured data layer

  Hand-coded Liquid theme replacing a paid template. Product, Article, Review, Breadcrumb, FAQ, LocalBusiness schema across the catalog. AOV improved noticeably after launch, partly from richer SERPs and partly from a faster checkout.

• iCharms · WordPress to Astro

  Brand site rebuilt around a tight content engine

  Migration from a brittle WordPress install to Astro. Editorial moved to a headless CMS the founder runs herself. Site stayed up through three platform updates without intervention, a first in five years.