Neer Automation
A nine-page website for a solar and automation business in Pollachi.
I built the website for Neer Automation, a solutions and integration business based in Pollachi. The site explains what the business supplies, installs and supports, and gives visitors direct ways to make an enquiry.
There are nine pages: the home page, seven service pages for solar power, solar pumping, pumps and motors, water and irrigation automation, home automation, power protection and college lab kits, plus a home construction page with a 2D floor-plan and 3D-render showcase.
The implementation uses Next.js App Router, strict TypeScript, Tailwind CSS and Framer Motion. Service data and business details live in shared modules, while reusable heroes, section headers, cards, FAQs and call-to-action bands keep the pages consistent. The blue and orange palette follows the business logo.
Explain the system before asking for an enquiry
Solar systems, pump controllers and power protection need more explanation than a product name and a photograph. The pages combine service copy, equipment options and FAQs with SVG diagrams showing how the parts connect.
The solar page lets visitors switch between on-grid, off-grid and hybrid explanations. Other diagrams show a solar drive feeding a pump, tank-level control, irrigation zones and the different levels of power protection. These are visual explanations of the services, rather than controls for installed equipment.
Give visitors several ways to reach the business
The site includes phone links, WhatsApp links and an enquiry form. The form validates a name and Indian mobile number, sends the enquiry to Formspree, and shows sending, success and error states. If submission fails, the page points visitors to WhatsApp.
GA4 event hooks cover phone, WhatsApp and email clicks, plus successful form submissions. Events include the contact location, and form submissions include the selected service. A small tracked-link component lets server-rendered sections report clicks without making the whole section a Client Component.
Analytics is optional: the loader renders nothing without a configured measurement ID. The code supports event tracking; it does not establish an increase in enquiries.
Keep search metadata tied to the same business details
A shared SEO module builds per-page titles, descriptions, canonical URLs and social metadata. It also builds LocalBusiness and WebSite structured data, service descriptions, breadcrumbs and the home-page FAQ schema from shared business and service data.
The sitemap derives its service routes from the same list used for the solution cards, with the home construction route added explicitly. Production URL handling has a fallback to the business domain, so a missing configuration does not default production canonical links to localhost.
These are implemented search foundations, not a claim about rankings or traffic.
What I’d do differently
- 01I'd keep more of the enquiry configuration in one validated module. Business identity and phone numbers are already shared, but the form endpoint and WhatsApp number are still read directly by individual components.
- 02I'd verify the complete enquiry journey before judging the site by its appearance: invalid input, a failed submission, a successful submission, and the phone and WhatsApp links on mobile. Event hooks alone do not prove that enquiries reach the business.