Making The Web Simple, Accessible and Universal

A Web Developer and SEO Expert based in India. The work covers custom websites and web applications, web engineering, technical and on-page SEO, Core Web Vitals, and accessibility improvements. It also spans low-code and no-code platforms, scalable content systems, and open-source integrations, built on WordPress, Webflow, Framer, Webstudio, Ghost, and headless CMS systems. Development and search are handled together rather than sequenced, because when they are split the gaps show up in page architecture, performance, crawlability, and conversion. Academic background: Computer Science, Devi Ahilya Vishwavidyalaya (DAVV), Indore.

Working since

2019

Based in

India

Languages

English, Hindi

Education

Computer Science · DAVV Indore

• 

  Active development 2026

  RawLaw.in - Legal News-First Platform Architecture

  An actively developed legal technology platform connecting editorial publishing, structured legal-help intake, advocate discovery, and operational workflows across independently scalable systems.

  • Platform Architecture
  • Frontend Engineering
  • SEO
  • Accessibility
  • Product UX

  Read case study → View public platform ↗

A brief may need custom code, a content platform, technical SEO, performance work, accessibility remediation, or several of them together.

1. Custom websites and web applications

   Purpose-built websites and applications with maintainable frontend architecture, responsive interfaces, structured content, and reliable API integrations.

2. SEO and search visibility

   Technical and on-page SEO: crawlability, indexation, information architecture, internal linking, and structured data, with content structured for both traditional and AI-assisted search.

3. Performance and accessibility

   Core Web Vitals, PageSpeed improvements, semantic HTML, keyboard access, responsive behavior, and accessibility practices informed by WCAG.

4. CMS, low-code, and no-code platforms

   Professional websites and publishing workflows across WordPress, Webflow, Framer, Webstudio, Ghost, and headless content systems.

5. Open-source systems and integrations

   Self-hosted platforms, reusable frontend foundations, custom plugins, API work, and automation, chosen for what the product actually needs to do.

Common questions about this work →

1. 01

   Understand

   Business goal, audience, search context, technical constraints, and success criteria, agreed before any build decision.

2. 02

   Plan as one system

   Information architecture, content structure, and technical scope shaped so development and search requirements resolve together.

3. 03

   Build with quality defaults

   Semantic HTML, performance budgets, accessibility requirements, and structured data written in during the build, not retrofitted.

4. 04

   Validate end to end

   Responsive behavior, Core Web Vitals, accessibility, analytics, structured data, and critical journeys checked before and after release.

1. UI & Usability Developer

   Zoho Corporation

   Oct 2022 - Present

   Chennai, India

2. UI Developer

   Chapter247 Infotech

   Nov 2020 - Sep 2022

   Indore, India

3. Web Designer

   Alpha Infolab Pvt. Ltd.

   Jul 2019 - Oct 2020

   Indore, India

Technologies change between projects. The constants are clear architecture, maintainable code, accessibility, performance, and discoverability.

• Why hire one person for both web development and SEO?

  Development and SEO influence many of the same decisions, including site structure, performance, accessibility, rendering, internal linking, and crawlability. Keeping both areas aligned from the beginning reduces hand-offs, prevents avoidable SEO issues, and helps create a website that is technically strong and easier to grow.
• How do I know whether I need a custom website, CMS, or web application?

  The right choice depends on what the project needs to achieve. A CMS works well for content-driven websites, custom development is better for specialized functionality and integrations, and a web application is suitable when users need accounts, data, workflows, or interactive features. The goal is to choose the simplest solution that meets current needs without limiting future growth.
• Can an existing website be improved, or does it need to be rebuilt?

  A complete rebuild is often unnecessary. The existing website can first be reviewed for performance, SEO, accessibility, usability, CMS limitations, and technical issues. Improvements can then be made where they provide the most value, with a rebuild recommended only when the current architecture is genuinely holding the website back.
• Can a website redesign or migration hurt SEO?

  Yes, especially when URLs, redirects, content, metadata, internal links, or indexing signals are changed without proper planning. The safer approach is to audit the existing website before migration, preserve important pages and content, map redirects correctly, and validate technical SEO and indexing after launch.
• Can website speed and Core Web Vitals be improved without changing the design?

  In many cases, yes. Performance problems often come from images, fonts, JavaScript, CSS, third-party scripts, caching, or loading behavior rather than the visual design itself. These areas can often be optimized while keeping the existing look and user experience intact.
• When is AI integration or automation actually useful for a business?

  AI and automation are most useful when they solve a clear problem, such as reducing repetitive work, processing information faster, improving customer workflows, connecting systems, or assisting users. The right approach is to identify the business problem first and introduce AI only where it provides practical and measurable value.
• Who owns the website, code, accounts, and data after the project?

  Ownership and access remain clear and transparent. Project code, website accounts, third-party services, credentials, and relevant documentation can be handed over according to the agreed scope, helping avoid unnecessary vendor lock-in and making future maintenance easier.
• How is SEO success measured, and can rankings be guaranteed?

  Specific search rankings cannot be guaranteed because results depend on competition, algorithms, content, authority, and other external factors. Progress is better measured through organic visibility, qualified traffic, indexing health, technical improvements, conversions, and growth against the actual goals of the website.
• Where can your work be reviewed?

  Published work is available through the portfolio. Some professional work cannot be shared publicly because of confidentiality, client agreements, or internal product restrictions. Where possible, case studies focus on the actual problem, responsibilities, technical approach, and constraints rather than screenshots alone.
• Do you provide support after launch?

  Yes. Post-launch support can include bug fixes, performance improvements, SEO monitoring, CMS updates, new features, integrations, accessibility improvements, and ongoing technical maintenance depending on the project. The level of support can be defined based on what the website needs after launch.

Share the goal, the current constraints, and the technical or search problem. A 30-minute call is usually enough to establish whether there is a fit and what the most useful next step is.

30 minutes · No preparation required · No obligation