A solar website with no enquiries usually has a plainer problem than its design: Google is not showing the page, the visitor does not believe it, the enquiry button is awkward on a phone, or an enquiry arrives and nobody picks it up. A redesign fixes only some of these.
Picture a Kolhapur installer who pays a designer ₹60,000 for a new site. It looks sharp on the owner's phone. Two months later the contact form has produced three messages, all from people who already knew the firm, and one sat unread for a week because it went to an email address nobody opens. (An invented example, but a familiar pattern.)
This solar website must haves guide is a checklist you can hand to a web developer, page by page. Each page gets what must be on it and a test you can run on your own phone, plus the claims that need care under Indian advertising rules, an audit table and a copy-paste brief. Search facts come from Google's own documentation, with the date each page shows. Our own practice is labelled as such.
One boundary first. Quickest Solar CRM is not a website builder, so nothing here depends on it. For rankings in depth, see our guides to SEO for solar installers and local SEO for a solar business.
Key takeaway
A solar website gets enquiries when four gates all work. Found: Google can show the right page. Trust: a visitor believes you are real and local. Ask: one tap starts an enquiry on a phone. Landed: every enquiry reaches a named person and is logged with a follow-up date. Test each gate on your own phone before you pay for a redesign.
Why your solar website brings no enquiries: find the leaking gate first
A website can fail at four points, and the evidence for each sits in a different place. Search Console shows whether you are Found. Your own phone shows Trust and Ask. Your enquiry log shows Landed. Spend an hour with these before you brief anyone.
The Search Console terms are Google's own: per the Performance report help page, impressions are "How many times your site appeared in Search results" and click-through rate is "The click count divided by the impression count."
| What you see | What it usually means | Where to check | Gate |
|---|---|---|---|
| Very few impressions for your pages | Google is not showing the site for local searches | Search Console Performance report, Queries and Pages tabs | Found |
| Impressions but few clicks | You appear, but rank low or the title is vague | Same report, per page | Found |
| Visits but few taps on call or WhatsApp | The page does not look real or local, or the buttons hide | Your phone, plus a stranger shown the page for five seconds | Trust, Ask |
| Form started, rarely submitted | Too many fields, or it fails on mobile | Google Analytics 4 events form_start and form_submit | Ask |
| Enquiries arrive, few become surveys | Slow pickup or no owner | Count a month of enquiries by channel against leads actually added | Landed |
The Devices tab gives your own phone-versus-desktop split. Use it instead of the "70% of enquiries come from mobile" line on agency blogs, which we could not trace to an independent source.
Fast tip. Our rule of thumb, not a benchmark: if your key pages get fewer than about 30 visits a month, no form tweak will show. Fix Found first, starting with your Google Business Profile and the route in our Google Maps lead guide.
The Four-Gate Enquiry Path: a way to brief your developer
The Four-Gate Enquiry Path is the audit frame for this guide. A visitor must pass Found, Trust, Ask and Landed in order, and a leak early on wastes the work done later. Every row in the audit table is tagged with its gate.
-
1
Found: can Google show the right page for the right town?
The developer fixes titles, links, speed and markup. You keep your Business Profile and contact details consistent.
-
2
Trust: does a stranger believe you are real, local and legal?
Real installations with kW, town and month, honest vendor wording, and prices and warranty terms that follow the advertising guidelines. You supply the proof.
-
3
Ask: can a person start an enquiry with one tap on a phone?
A call button, a WhatsApp button and a short form, visible without scrolling. The developer builds them to your spec.
-
4
Landed: does the enquiry reach a named person and get logged?
No developer needed. You choose who owns each channel, where entries are recorded and when the first follow-up is due.
Most redesign briefs spend nearly all the money on gates 1 to 3 and ignore gate 4, which you can fix this week, alone, for no fee. The worked example later shows why that order matters.
Gate 1, Found: the technical items to hand your developer
Google can only show pages it can reach, read and understand. Ask your developer for a yes or a reason on each row. Every quote is from Google documentation, dated as the page shows.
| Item | Ask the developer for | What Google says | 30-second test |
|---|---|---|---|
| Same content on mobile and desktop | One responsive site | Mobile-first indexing (10 Dec 2025): Google "uses the mobile version of a site's content" for indexing and ranking. Keep content, alt text and structured data the same. | Open a service page on phone and laptop and compare. |
| Unique titles and descriptions | A different title and description per page, naming service and town | SEO Starter Guide (10 Dec 2025): a good title "is unique to the page, clear and concise". | Read your browser tabs. Two saying "Home" need fixing. |
| Real, descriptive links | Menu and town links as ordinary links, with plain-words text | Link best practices (10 Dec 2025): Google can crawl a link only if it is an "<a> HTML element" with an href. | Long-press each menu item on a phone. It should offer a new tab. |
| Readable images | Photos as image tags with alt text and descriptive file names | Image guidance (2 Mar 2026): alt text is "the most important attribute". CSS background images are not indexed. | Rename IMG_2041.jpg to something that describes the job. |
| Speed on real phones | Good Core Web Vitals on the pages that matter | Core Web Vitals (10 Dec 2025): see the figures below. | Run PageSpeed Insights on mobile. |
| Local business markup | Name, address and phone in LocalBusiness data | LocalBusiness data (8 Sep 2026): name and address are required, telephone is recommended. | Paste the page into the Rich Results Test. |
2.5s
Largest Contentful Paint
Google: "strive to have LCP occur within the first 2.5 seconds". Search Central, updated 10 Dec 2025.
200ms
Interaction to Next Paint
Google: "strive to have an INP of less than 200 milliseconds". Same page.
0.1CLS
Cumulative Layout Shift
Google: "strive to have a CLS score of less than 0.1". Same page.
Two cautions. PageSpeed Insights (updated 21 Oct 2024) shows real-user data over 28 days and, separately, a simulated lab score that "may not capture real-world bottlenecks". A small site often has too few real visits, and the tool then falls back to a whole-site figure or shows none. And nobody can promise page one: Google's Search Essentials (10 Dec 2025) says meeting its requirements does not mean Google will "crawl, index, or serve its content".
Watch out. Business details must agree. Google asks that your Business Profile name reflect your "real-world name" and that your site represent your location (Business Profile guidelines). If you hide your address on the profile as a service-area business, do not print a different one in your markup.
Page-by-page: what each page must carry
A small installer's site needs about nine kinds of page, each with one job. The page choices are our judgement, not a Google rule.
Home page
Say in one line what you do, where and for whom: "Rooftop solar for homes and factories in Nashik and nearby towns" beats "Powering a greener tomorrow". Put one real installation photo near the top with kW, town and month. Put call and WhatsApp buttons where a thumb reaches them.
Service pages
Write one page per service you really sell: home rooftop, factory, housing society, plus extras such as maintenance only if you do them. Each covers who it suits, typical sizes, the steps from survey to commissioning, what the customer provides (last three electricity bills, roof access) and what is included. Our site survey checklist lists what the engineer checks, so the page can promise the same things.
Town pages
A town page earns its place only if it says something true that no other page says. Google's spam policies (28 Aug 2026) define doorway abuse as pages "created to rank for specific, similar search queries" and list pages "targeted at specific regions or cities that funnel users to one page". Fifty pages with the town name swapped is that pattern. Two town pages pass only if they differ in all five ways below.
| Difference | A Nashik page might say | Why a stranger cares |
|---|---|---|
| Power company (DISCOM) and process | Which DISCOM serves the area and what its application needs | Shows you have done the paperwork there |
| A real local project | A rooftop in a named area with kW and month, or "none yet, nearest is in ..." | Proof a neighbour can confirm |
| A local contact | The engineer or rep covering the town, with a number | A person, not a call centre |
| Local questions | Society permission, terrace access, local rules | Answers what they were about to ask |
| Service reality | Survey days, travel time, maintenance cover | Shows you can reach them |
If you cannot fill all five for a town, skip the page. Cover that town with a line on the service page and your Business Profile service area.
Price and subsidy page
People search price before they search you, so give them something checkable: one fully defined example with a date, not a "from" figure (the next section explains why). Say what a quote includes and excludes, such as structure, wiring, net-metering paperwork and GST. Link every subsidy figure to the government source and date it. For the layout, see how to pitch PM Surya Ghar to customers.
Projects page
List real jobs with town, kW, month and year, roof type and one clear photo. A customer's quoted words need their permission.
About and contact pages
Google's helpful content guidance (5 Oct 2026) says it helps when "it's clear who created" the content, and asks about "a site's About page". Name the owner and the registered business, show the office address you are willing to publish and how to reach a human. On the contact page, put one answered phone number, a WhatsApp link, hours and the short form, all matching your Business Profile.
Thank-you page and every page
Send each form submission to its own thank-you page that says what happens next, in words you can keep. It also gives analytics a clean count. Every page needs a sticky call and WhatsApp bar on phones, your name, address and phone in the footer, a privacy link and no pop-up on arrival.
Gate 2, Trust: claims that need care on an Indian solar site
Visitors trust specific, checkable statements, and Indian guidelines already catch several favourite solar phrases. The Central Consumer Protection Authority (CCPA) misleading-advertisement guidelines (notified 9 June 2022) apply to "all advertisements regardless of form, format or medium", so a website is covered. Read each row as a prompt to check, not as legal advice.
| Claim on your site | Where it goes wrong | Safer approach | Source |
|---|---|---|---|
| "MNRE approved installer" | The scheme guidelines speak of vendors "registered on the National Portal", so a vague badge can say more than your registration does. | Write "Registered vendor on the PM Surya Ghar National Portal" only if true, and name your registration route. Copy your name as your portal profile shows it. | Ministry of New and Renewable Energy (MNRE) guidelines for PM-Surya Ghar, file uploaded July 2025, clause 7(a), read 31 Oct 2026 |
| "5 year warranty" or "up to 10 years" | Open-ended periods are the pattern the guidelines name. Modules, inverter and workmanship differ. | State a fixed period for each part, matching your signed agreement word for word. | CCPA 2022 guidelines, para 12(e)(i) |
| "Solar from just ₹X per kW" | "Prices from as low as Rs. Y" is listed as an expression to avoid. | Show one fixed price for a defined system (size, brands, structure, GST) with the date. List extras before the form: late-revealed price elements are "drip pricing" under the dark-pattern guidelines. | Same, para 12(e)(i); dark patterns, item 8 |
| "Free site survey" | A "free" offer must cost nothing beyond the unavoidable cost of responding, and must make "clear the extent of commitment". | Say it is free and obligation-free, how long it takes and what you need. If the fee is adjusted against the order, do not call it free. | Same, para 7 |
| "Eco-friendly", "100% green", "saves 5 tonnes of CO2" | Generic terms like "green" and "eco-friendly" need qualifiers and substantiation, and specific claims need evidence. | State what you mean ("designed to generate about X units a year"), and link your calculation and its emission-factor source. | CCPA greenwashing guidelines (issued 15 Oct 2024), paras 5 and 6 |
| Testimonials | An endorsement must reflect "the genuine, reasonably current opinion" of the person. A gift or discount for it is a connection that may need disclosing. | Use real, permitted, dated quotes. If you gave anything in return, say so beside the quote. | CCPA 2022, paras 13 and 14 |
| "Only 3 slots left" or "subsidy ends tonight" | False urgency is a named dark pattern. | Show a real survey calendar, and quote subsidy dates only from the official source. | CCPA dark-pattern guidelines, 30 Nov 2023, Annexure 1 |
One limit: the dark-pattern guidelines apply to "all platforms, systematically offering goods or services in India", advertisers and sellers. Whether a small installer's site counts is a question for a lawyer, but the habits are cheap to avoid anyway. Also, the MNRE guidelines are amended from time to time, so check the National Portal before copying wording. Our registered vendor guide explains registration.
Review stars need a warning too. Google's review snippet documentation (8 Sep 2026) says pages carrying a business's own reviews in LocalBusiness or other Organization markup "are ineligible for star review feature". Pasting a testimonial widget into your markup will not earn stars. Collect reviews where Google can verify them, on your Business Profile.
Gate 3, Ask: the form, the WhatsApp button and the call button
An enquiry button works when it shows without scrolling on a phone, takes one tap and asks for little. Put call and WhatsApp in a sticky bar, and a short form on the contact page and under each service. The grid is our view, from practice rather than a study.
Strengths
- ✓WhatsApp first: an app the visitor already uses, and a prefilled message shows which page they used
- ✓WhatsApp first: no typing into a long form
- ✓Form first: you get town and monthly bill before the first reply
- ✓Form first: works for visitors without WhatsApp
Weaknesses
- ✗WhatsApp first: details arrive in pieces, in any order
- ✗WhatsApp first: a chat on one person's phone vanishes if that person leaves
- ✗Form first: each extra field costs submissions, and a form can fail silently
- ✗Form first: an unwatched inbox loses leads
We offer both: WhatsApp as the large button, the form underneath. Send the developer this spec.
FORM (contact page and under each service page), five fields at most:
1. Name
2. Mobile number (numeric keyboard on phones)
3. Town or PIN code
4. Home, factory or society
5. Approximate monthly electricity bill (optional)
Purpose line under the button:
"We will use your name and number only to contact you about this
solar enquiry. Privacy notice: [link]. Data questions: [name, number]."
Button text: "Book a site survey". After submit: open /thank-you and send
the entry to [the one inbox or sheet the owner named].
WHATSAPP BUTTON (header, sticky bar, contact page)
https://wa.me/91XXXXXXXXXX?text=Hi%2C%20I%20want%20a%20solar%20site%20survey%20for%20my%20home%20in%20Nashik.%20(From%20your%20website)
Number: country code 91 plus the 10-digit mobile, no plus, zero, bracket
or dash. The text changes per page, so each chat shows its source.
CALL BUTTON: tel:+91XXXXXXXXXX on every page, one number that is answered.
DO NOT: open a pop-up asking for a number on arrival, use a "No, I like
high bills" button, or show a fake "12 people viewing now" counter.
WhatsApp's own click to chat help page (no date shown) gives the format: the number in full international format with zeroes, brackets and dashes left out, and a prefilled message after "?text=" as URL-encoded text.
The consent line. The Press Information Bureau release of 14 November 2025 says the Digital Personal Data Protection (DPDP) Rules provide "an 18-month phased compliance timeline" and require "standalone, clear and simple consent notices" stating the specific purpose, with clear contact details for data queries (PIB). Duties phase in, so you may not be bound on every point yet. A purpose line and named contact cost almost nothing, so add them now. See our DPDP Act entry. This is not legal advice.
Pop-ups and shaming buttons. The dark-pattern guidelines list "constant request to turn on or accept notifications or cookies with no option to say NO" as nagging, and define confirm shaming as phrasing meant "to create a sense of fear or shame or ridicule or guilt".
Count the taps. Switch on GA4 enhanced measurement. It records form starts and submits, and an outbound click on "a link that leads away from the current domain". A WhatsApp button opens another domain, so it should show as one (Google Analytics help, no date). Form details reach reports only with custom dimensions. That page documents no phone-tap event, so ask your developer for a named event for call taps and test all three in Realtime.
Gate 4, Landed: where each enquiry goes in the first hour
An enquiry has landed when a named person has it, it is written on a lead, and a follow-up date exists. Anything less is a message in a pile.
| Channel | Arrives as | Owner and backup | Written down as | Label |
|---|---|---|---|---|
| Website form | An entry in an inbox or sheet | One named person and a backup, checked at fixed times | A lead with name, number, town, bill and the page used | Website form + town |
| WhatsApp button | A chat with page text | Whoever holds the shared business number, not one rep's phone | A lead, source copied from the prefilled text | Website WhatsApp + town |
| Call button | A call, answered or missed | The phone owner, with a missed-call routine | A lead after every call, with a note | Website call |
Use one shared place. A form that mails one person, a chat on another's phone and a missed call on a third make three piles. Pick one business number and one lead list. Our lead routing rules cover who gets which lead.
Write the source down at entry. "Website WhatsApp, Nashik page" beats "Online". A month later you can see which page and channel give surveys, which the lead source attribution guide builds on. One person using both form and WhatsApp creates two entries, so read the duplicate leads guide first.
Set the follow-up date when you create the lead. Choose a first-reply target you can actually keep. After that, the follow-up cadence guide applies, the missed-call guide covers unanswered calls, and the Slot-Lock Ladder keeps a booked slot.
The Three Test Enquiries
Once a quarter, and after any website change, send three test enquiries from a phone the team does not know: one by form, one by WhatsApp, one by call. Note the time of each. A day later check that each reached its owner, sits in your lead list with a source label and follow-up date, and got a reply. Any miss is a defect, and usually faster to fix than a new page.
Which gate to fix first: a worked example
Fixing gate 4 first usually returns the most per rupee and per week. These numbers are illustrative, not benchmarks. Replace each assumption with your own count.
Assume a six-person EPC in Nashik with 800 website visits a month. Today 1.0% of visits become an enquiry. Of those, 75% get written down, 60% of those get a call within a day, and 35% of called enquiries book a survey. Better buttons lift the enquiry rate to 1.8%. A routine fix lifts "written down" to 95% and "called within a day" to 90%.
| Scenario | Enquiries a month | Written down | Called within a day | Surveys booked |
|---|---|---|---|---|
| Today | 8 | 75% | 60% | about 1.3 |
| Fix Landed only (routine, no developer) | 8 | 95% | 90% | about 2.4 |
| Fix Ask only (new buttons and form) | 14 | 75% | 60% | about 2.3 |
| Fix both | 14 | 95% | 90% | about 4.3 |
Illustrative. Illustrative only. On these assumptions the routine fix nearly doubles surveys, about the same as rebuilding the buttons, and it starts today. If your real pickup is already 95%, fix Ask first. Count your own month to find out.
The lesson is the order. A site that doubles enquiries into a leaking inbox adds waste. A routine that catches every enquiry makes later website spend count for more.
The on-page audit table: score your site in an hour
Score one point for each row that passes. Rows run sitewide first, then page by page, each tagged with its gate. Test on a phone, with a stranger's eyes where it says so.
| # | Page | Pass if | How to test | Gate |
|---|---|---|---|---|
| 1 | Sitewide | Same content, photos and alt text on phone and desktop | Compare one service page on both | Found |
| 2 | Sitewide | Own title per page naming service and town, and menu links are real links | Read the tabs, long-press menu items | Found |
| 3 | Sitewide | Mobile PageSpeed real-user data is good, or you know why it is blank | Run it on home and one service page | Found |
| 4 | Sitewide | Name, address and phone identical on site, footer and Business Profile | Compare three places | Found |
| 5 | Home | First screen says what, where and for whom | Show a stranger for five seconds | Trust |
| 6 | Home | Real installation photo with kW, town and month near the top; vendor wording matches your portal profile | Scroll twice, compare with the portal | Trust |
| 7 | Home | Call and WhatsApp buttons show without scrolling | The thumb test | Ask |
| 8 | Services | Each covers who it suits, steps, what the customer provides, what is included | Read one aloud to a rep | Trust |
| 9 | Services | No unsupported "free", "from Rs", "up to X years" or "eco-friendly" | Search the site text for each | Trust |
| 10 | Towns | Each page passes the five-difference test, and none for towns you cannot serve | Put two side by side | Found |
| 11 | Price | One defined price example with date and exclusions; subsidy figures link to the government source, dated | Read it as a buyer, click each link | Trust |
| 12 | Projects | Three or more real jobs with town, kW, month and photo; any quotes real, permitted and dated | Count them, check with each customer | Trust |
| 13 | About | Names the people and registered business, and a way to reach a human | Read it | Trust |
| 14 | Contact | Form has five fields or fewer, a purpose line and a privacy link | Count and read | Ask |
| 15 | Contact | WhatsApp link opens a chat with text naming the page | Tap it on a phone | Ask |
| 16 | Contact | Phone number is tap-to-call and answered in stated hours | Tap and call | Ask |
| 17 | Thank-you | A submit opens its own page saying what happens next | Submit a test | Landed |
| 18 | Routine | All three test enquiries appear in your lead list with source and follow-up date | Run them, check a day later | Landed |
| 19 | Routine | Each channel has a named owner and a backup | Ask who, and who if they are away | Landed |
Reading your score. These bands are our judgement, not data. A score of 16 to 19 means the site is sound and later gains are in content. A score of 10 to 15 means fix the gate with the most failed rows, Landed first if it has any. Below 10, a redesign is premature: do the Landed rows, then the Ask rows, then brief the developer. Paste this brief:
BRIEF FOR THE WEB DEVELOPER
1. Audit rows 1 to 4 and 14 to 17: reply yes, no or "not possible because ..." for each.
2. Pages: home, one per service we sell, projects, about, contact, price and
subsidy guide, thank-you. Town pages only for the attached list.
3. Every page: unique title and description, real links, image alt text,
same content on phone and desktop.
4. Call button, WhatsApp button (page-specific text) and the attached form
spec. Sticky call and WhatsApp bar on phones.
5. Thank-you page with its own address. GA4 events for form submit, WhatsApp
tap and call tap. Show us where to see them.
6. LocalBusiness data with the exact name, address and phone on the sheet.
7. Claims, prices and photos come from us. Add no "free", "guarantee" or
urgency wording we did not supply. Send mobile PageSpeed results.
How Quickest Solar CRM fits
Quickest Solar CRM does not build websites, and this guide does not assume it receives your form entries automatically. It helps with gate 4: once an enquiry has arrived, your team adds it as a lead and works it from there.
- Lead Capture: add each website enquiry as a lead with its town and source, put a label on it such as "Website WhatsApp", and set a follow-up reminder when you create it.
- Bulk import from Excel: if your form has been dropping entries into a sheet, bring the backlog in as one import, then filter by label to see which channel and town give surveys.
- Activity log and team permissions: record the first call on the lead, and give the person who watches the inbox and each rep their own access, with a dashboard and team report for the owner.
You can try this at no cost: the Free plan on pricing gives one user and 10 proposals a month, with no card, which is enough to run the Three Test Enquiries on one lead list.
What to do this week, before you pay anyone
None of this needs a developer until day 4.
- Day 1: run the Three Test Enquiries. Fix any miss before anything else.
- Day 2: score the audit table. All 19 rows, honestly. Circle the gate with the most failures.
- Day 3: fix your claims. Search your site for "free", "from", "guarantee", "eco-friendly", "approved" and any countdown, and rewrite each using the claims table.
- Day 4: send the brief. Attach the form spec and your town list, and ask for yes or no on each row.
- Day 5: set the routine. Name each channel's owner and backup, choose labels, and agree where leads are written. Repeat the test enquiries after the developer's changes go live.
For what to offer visitors and how to sort them, see our lead magnet ideas and lead qualifying guide.
Frequently asked questions
What should a solar installer's website include?
A home page that says what you do and where, one page per service you sell, a projects page with real jobs, an About page that names the people, a contact page with call, WhatsApp and a short form, a price and subsidy guide, and a thank-you page. Add town pages only where you can say something true and different about each town.
Do I need a website if I already have a Google Business Profile?
A profile can bring calls and directions without a site, and it is the better first step if you have neither. A website adds room for services, projects, prices and a proper enquiry path. Google's Business Profile guidelines ask for a phone number or a website that represents your individual business location, so a thin page is a weak substitute.
Should I use a WhatsApp button or a form for solar enquiries?
We suggest both, with WhatsApp as the large button and a short form underneath. A prefilled WhatsApp message shows which page the visitor used, and a form lets you collect town and bill first. Name one owner per channel, because both fail the same way when nobody watches them.
Can I write MNRE approved on my solar website?
Be careful. The MNRE guidelines for PM-Surya Ghar (file uploaded July 2025) say the scheme runs only through vendors registered on the National Portal. If you are registered, say that, name your route and copy your name as the profile shows it. Check the portal for current wording, since guidelines can be amended.
How do I check whether my solar website is fast on mobile?
Run PageSpeed Insights on your home page and one service page, and read the real-user section first. Google asks owners to aim for Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1.
Do I need a privacy line on my solar enquiry form?
Add one. The Press Information Bureau says the DPDP Rules of November 2025 require clear consent notices that state the specific purpose, phased in over 18 months. A purpose line, a privacy link and a named contact for data questions are cheap. This is not legal advice, so ask a lawyer if you hold sensitive documents such as Aadhaar copies.
Should I make a page for every town I serve?
No. Make a page only for towns where you can fill all five differences: the local power company and process, a real local project, a local contact, local questions and service reality. Google's spam policies, updated 28 August 2026, call pages built for similar searches that funnel users to one destination doorway abuse.
How much does a solar website cost in India?
We have no primary source for prices, so we will not quote one. Cost varies with page count and the content you supply. Use this guide to fix the scope, then ask two or three developers for written quotes against the same page list, form spec and brief.
Want to put this into practice?
Quickest Solar CRM gives you everything in this article, proposal automation, lead capture, WhatsApp follow-up, built for Indian solar EPCs.
Start free