The growth came from one thing: a page for the solar rules, permits and incentives of every country, state, municipality and utility SurgePV sells into. 890 pages on one site in 9 languages.
Every installer SurgePV sells to must clear a local permit, a grid-connection form and a subsidy rule before they can quote a job. Nobody was writing those pages. theStacc wrote them for every market, and the people searching for the rules found SurgePV first.
[Video placeholder. Poster frame, captions and a transcript toggle go here once recorded. No autoplay.]
Our installers in Tshwane don't search for solar software. They search for the municipality's registration form. We had no page for that. Now we rank third for it, and the signups come from the page.
[CEO photo][CEO name]Founder and CEO, SurgePVDraft quote, pending CEO approval
SurgePV makes AI-assisted solar design and proposal software. Installers use it to lay out panels, size inverters and send a quote. By early 2026 it had paying customers on four continents and a website that mostly served people who already knew the name.
In the 7 months to 1 February 2026 the site got 3,290 Google clicks in total. Nine countries sent more than 50 clicks. The blog covered the general solar topics every competitor covered.
The gap was obvious once we looked at what installers type into Google. They search for the rule: "solar registration tshwane", "cea guidelines for solar power plant", "yapı ruhsatı güneş enerjisi". Each of those queries is a person with a job to quote this week. Almost none of them had a good answer.
theStacc started on 2 February 2026. The brief was traffic that turns into installer signups, in the markets SurgePV sells into and the ones it wanted next.
Search Console data, redrawn with the milestones marked. 121 clicks in the first week. 1,212 in the last.
Weekly counts, same 30 weeks. February averaged 5 a week, August 42. The lumps are real: a week with 84 leads in August, 11 the week after the compliance hub went live.
| 2026 | Clicks | Impressions |
|---|---|---|
| February | 496 | 51,180 |
| March | 867 | 113,796 |
| April | 850 | 118,154 |
| May | 1,586 | 267,701 |
| June | 2,553 | 194,969 |
| July | 4,263 | 305,146 |
| August | 4,986 | 404,079 |
Full calendar months. The headline uses the same February and August figures.
March and April look flat. That is the indexing lag: the compliance pages were written and published in March, Google began showing them on 19 April, and clicks followed about four weeks later. Plan on results in months three to five, and compounding after that.
Impressions moved first. They jumped in May, a month before clicks, because new pages start on page two and move up as Google gathers click data. Impressions tell you it is working before the traffic shows.
Google had indexed 4,197 pages of the site by 10 August.
Solar rules are set at four levels, and an installer needs all four to quote a job. The hub mirrors that structure. Each page answers one question for one place: which permit, which form, which tariff, which deadline, with the source document linked.
The pages share one template and one data model, so a new country is a research job. theStacc writes each page from the primary sources (the regulation, the tariff order, the utility's application form). The service includes an editor's check of each page against those sources before it goes live, and SurgePV's team can correct anything from the admin.
Result: 890 URLs, 4,477 clicks in the window at an average position of 10.7, and 0 → 1,850 clicks a month from February to August. These pages keep ranking, because the rule changes once a year and the question gets asked every week.
Clicks and positions for 2 Feb–30 Aug 2026, Search Console. All pages are live on https://www.surgepv.com/solar-compliance/ for you to check.
The hub ranks in places SurgePV had no visitors from in February. Kenya had 0 clicks that month. Below, the top markets, February and August on the same scale.
Monthly Google clicks by country, Search Console. Italy and France, SurgePV's existing European markets, grew more slowly from a higher base.
Clicks in the 7 months before (6 Jul 2025 – 1 Feb 2026) vs the 7-month window.
GA4 counts a demo request as a person who reached the thank-you page. 596 people in the window (2 Feb – 30 Aug 2026), vs 104 in the period before (tracking began 23 Aug 2025). 5.7x. 86 countries, vs 43 before.
Top 10 countries by demo request events (841 events from 596 people; a person can submit more than once). GA4, event Demo_req.
Demo request events by continent, baseline (23 Aug 2025 – 1 Feb 2026) vs the window. 53% of demo requests came from Organic Search.
SurgePV's site runs in nine languages from one codebase. Product pages and most of the blog are shared and translated. Compliance pages are written per market, in that market's language, because a Turkish installer wants the Turkish permit and the Turkish word for it.
Turkish, Portuguese and Arabic launched in March 2026 and were in Google's index within a week. Non-English pages brought 1,103 clicks in the window, about 7% of the total. The growth was mostly English compliance and blog pages read in Asia and Africa. The languages add reach and credibility in each market, and 1,239 non-English URLs now rank.
[Exact URLs for the Italian and German examples to be added; the Turkish link is live.]
Yes. SurgePV is one codebase with shared content and a country layer on top. About 80% of a page is shared across markets; compliance, pricing and contact details are local. Visitors land on the version for their country and language, and Google is told which version belongs to which market.
For a new country, we add its compliance pages and switch it on. There is no second site to maintain.
Each page starts from the primary source: the regulation, the tariff order, the utility's form. The writing follows a short brand document agreed with SurgePV at the start: tone, terms, what we never say, how we handle uncertainty. The service includes an editor's read of each page against its source before it goes live.
The test is the Tshwane page: it ranks #3–4 and gets 444 clicks from installers who would leave in a second if it were wrong.
theStacc went live on 2 February. The first compliance pages appeared in Google on 19 April, week 11. Impressions jumped in May. Clicks crossed 1,000 a week in the second half of June. You see it moving by month three and feel it in leads by month five. The chart above has the weeks.
Both. We report on leads. SurgePV's sales team logs each inbound lead in a weekly tracker: 5 a week in February, 42 a week in August, 660 in the 30 weeks. Lead-to-customer figures are SurgePV's and are not published here.
You keep everything. The site is plain HTML, CSS and JavaScript in a Git repository you own. Any developer can edit it. No plugins, no builder. If you are on WordPress, we move the content and redirects first, so no ranking is lost.
Pages are built the way AI answers quote them: the direct answer in the first paragraph, one question per page, dated and sourced, with structured data for the organization and each guide. We do not track citations yet. GA4 does show 25 demo requests in the window from AI assistants (ChatGPT, Perplexity and similar), up from 0 before. A small number, and a real one.
A one-hour kickoff, the brand rules sign-off, and a short review each month. SurgePV's team spent its time on the product. theStacc did the research, writing, editing, publishing and technical SEO, and reports clicks and leads each month. Pricing is at https://thestacc.com/pricing/.
This is what the hub is for. Kenya went from 0 to 114 clicks a month, Malaysia from 3 to 157, Singapore from 4 to 174. Those were markets SurgePV had next to no visitors from in February. A market's compliance pages can be live within weeks of the decision to enter it, and they collect the people who are about to need you.
I was worried about AI content. Our users are engineers and they would have told us in a second if a page were wrong. The difference is every page links to the regulation it came from. We get corrections from installers now, which means they are reading it.
[CEO photo][CEO name]Founder and CEO, SurgePVDraft quote, pending CEO approval
No. One site, one codebase, a country and language layer on top. Shared pages are translated once; compliance, pricing and contact pages are local. SurgePV runs 9 languages and 184 countries this way.
Brand rules agreed at the start, primary sources on every page, and an editor's check of each page against its source as part of the service. You review what you want to and can edit anything. Read the Tshwane page as an installer would.
Site live in about 5 days. Pages indexed within weeks. SurgePV saw impressions move in month three and clicks and leads in months four and five. Plan on 6 months to judge it.
We report leads, with tracking that shows which page each one came from. SurgePV's inbound went from 5 to 42 a week. We work out cost per lead against your paid channels with you in the first review.
We move the content, keep or redirect every URL, and check Search Console daily for the first month. The new site is plain HTML and CSS in your repository.
Pages are written to be quoted: direct answer first, one question per page, sources and dates, structured data. We report what the analytics show, small or not. For SurgePV, 25 demo requests in the window came from AI assistants, up from 0 before.
Pricing is on https://thestacc.com/pricing/. The minimum term is 3 months, about the time it takes to see the first results. Switching plans later is easy, and onboarding is the same on every plan.
Yes. The compliance and incentive pages for a new market are the first thing we build, so they collect searches before your sales team arrives. SurgePV's Kenya, Malaysia and Singapore numbers came from markets it had next to no visitors from in February.
A 30-minute call. Bring your Search Console if you have one; we'll show you where the gap is and what the first 90 days would cover.