SEO

How We Did SEO for a SaaS Product Selling TradingView Indicators Online

By Rajeev Gupta
Quantzee AI trading indicators for TradingView — 6 AI indicators, full Pine Script source, lifetime access, 24/7 AI assistant

Most SEO case studies on agency blogs are written about local businesses — a clinic, a showroom, a law firm. This one is different. The client is a SaaS product, not a local business, and the product itself is a technical one: a bundle of TradingView indicators sold as a single lifetime purchase. We're writing about this engagement because the problems were different from the ones we usually solve, and because the client is one we can name without breaking confidentiality — Quantzee, which sells six Pine Script indicators (SuperTrend Pro+, AI TrendPulse, AI Adaptive Quant Toolkit, SMC Toolkit Pro, MACD Pro+ and Adaptive AI Oscillation Engine) to retail traders across stocks, crypto, forex and indices.

The Starting Point

When we first audited the site, it scored 52 out of 100 on our internal SEO checklist. That number on its own doesn't tell you much, so here's what was actually missing: inconsistent page titles with no character-length discipline, meta descriptions that were either empty or far too long to display in a SERP snippet, no Open Graph or Twitter Card markup on most pages, and no structured data at all beyond the basics Astro ships by default. For a product site where the entire pitch is "these are real, working indicators, not a black box," the absence of trust signals in the markup was working against the sales copy, not just the search ranking.

A SaaS selling a technical product to a global audience also has a positioning trap that a local business never faces: nothing on the site could read as India-specific or as a signals service that trades for the buyer. Quantzee sells the indicator source code as a one-time purchase, not a subscription, and not advice. Every title, description and piece of schema we touched had to hold that line.

What We Actually Fixed

The first pass was mechanical, across all of the site's pages at the time:

  • Every page title rewritten to 60 characters or under, with the primary keyword placed early rather than buried after a brand suffix.
  • Every meta description rewritten to the 140–160 character band that Google reliably displays in full, instead of truncating mid-sentence.
  • Full Open Graph and Twitter Card blocks added site-wide, so a link shared on X or in a trading Discord renders with the right title, description and preview image instead of a blank card.
  • JSON-LD schema added by page type — Service, FAQPage, AboutPage, ContactPage, Blog, and Product markup with Offers for the indicator pricing, plus BreadcrumbList across the board.
  • Hero images given preload hints and fetchpriority="high", since the largest image on a product landing page is almost always the Largest Contentful Paint element Core Web Vitals scores against.
  • Billing documentation pages set to noindex and filtered out of the sitemap — account and billing pages have no business ranking, and leaving them indexable was diluting crawl budget away from pages that should rank.
  • The sitemap rebuilt with accurate lastmod values per section, and robots.txt updated to disallow the billing paths explicitly.

Once the mechanical layer was fixed, we went back through the existing 20 blog posts the client already had live and found a specific, recurring problem: several of them linked to indicator URLs that had since changed slugs, so a reader clicking through from an old post landed on a 404. We fixed every stale link, and added "Explore Indicators" and "Related Articles" blocks to all 20 posts so a reader arriving from search had somewhere relevant to go next instead of a dead end. That work moved the overall score from 52 to roughly 82–88 out of 100 on our internal scale.

The Part That Isn't Finished the Day You Launch

A technical fix-up gets you a clean site. It does not get you rankings on its own, and Quantzee's case made that obvious fast. A few months after the initial overhaul, we pulled Search Console data and found a specific, fixable gap: a cluster of keywords sitting at positions 8 through 14 — close enough to page one to matter, far enough to get almost zero clicks. Terms like "3commas alternative" were pulling hundreds of impressions and converting almost none of them into clicks, because the pages ranking for them didn't actually answer the question the query implied. The fix wasn't a new page. It was going back into the existing page and adding the H2s and FAQ sections that directly addressed what the searcher was actually asking, rather than the generic product copy that was there before.

We also found something less obvious: Google's own indexing-count API was reporting 0 indexed URLs out of the entire sitemap. Taken at face value, that would have been an emergency. Cross-checked against the URL Inspection API one URL at a time, 25 of 25 sampled pages came back "Submitted and indexed" — the sitemap API's indexed count is a known dead metric that Google deprecated without updating the number it returns. Reporting that 0 to a client as a crisis would have been wrong, and chasing a content fix for a problem that didn't exist would have wasted a sprint.

Building New Pages the Right Way

Part of the ongoing work has been building out dedicated pages comparing Quantzee against named competitor products — the kind of "{brand} review" and "{brand} alternative" pages that retail traders actually search for before buying an indicator. We tested two title formats against each other using the site's own Search Console data over a 90-day window, and "{Brand} Review" pages beat "{Brand} Alternative" pages on click-through rate — 1.49% versus 1.26% — so that became the locked format going forward, with the brand name first, one verifiable number from the competitor's real pricing, and the title always ending in a question. We also caught two of Quantzee's own pages cannibalising the same search term — /pine-script-alternative/ and /pineify-alternative/ were both chasing the same generic query with almost no clicks between them — and resolved it by giving each page a clearly different job: one owns the generic term, the other owns the named-competitor brand query.

None of this touches the underlying products or the AI positioning in the copy — Quantzee is explicit that these are non-repainting, adaptive signal tools sold as source code the buyer can read, not a black-box subscription, and the one-time lifetime pricing model on the site reflects that directly: a single purchase instead of a recurring plan, which is also why none of our SEO copy for the product pages was ever allowed to describe it as a subscription or an annual plan.

The Content Side

SEO for a product like this isn't only technical fixes and schema. Quantzee's own blog is where a lot of the keyword and content strategy actually plays out — indicator explainers, comparison pieces and trading-education posts that target the long-tail questions a retail trader types into Google before they're ready to buy anything. Cross-linking those posts to the right product pages, keeping the FAQ sections aligned to what the Search Console data showed people were actually asking, and making sure AI crawlers like GPTBot, ClaudeBot and PerplexityBot could all reach and read that content without being blocked in robots.txt, was as much a part of the engagement as the meta tag work.

What the Search Console Numbers Look Like Right Now

To keep this case study honest, here is what Google Search Console actually reports for quantzee.com today, pulled directly from the API rather than estimated. These numbers reflect the account's current overall search performance across the full ~16.5-month history Search Console exposes (13 June 2025 to 26 October 2026) compared against the latest fully-completed calendar month, September 2026. They describe where the account stands now, not a claim that every point of the gain below came from any single fix described above — SEO compounds, and a lot of other work (content, backlinks, product changes) happened in that window too.

  • Clicks: September 2026 totalled 778 clicks, versus an average of about 223 clicks per month across the full 16.5-month history — up roughly 249%.
  • Impressions: September 2026 totalled 49,664 impressions, versus an average of about 15,653 impressions per month across the same history — up roughly 217%.
  • Average CTR: 1.57% in September 2026, versus 1.42% averaged across the full history — up roughly 11%.
  • Average position: 9.47 in September 2026, versus 11.0 averaged across the full history — an improvement of about 1.5 positions, roughly 14% better.

Every number above came straight from the Search Console API for the quantzee.com property, with no rounding beyond what's shown. We're publishing it here the same way we'd want a client to see it: as a live account snapshot, not a highlight reel.

What We'd Tell Another SaaS Founder

The single biggest lesson from this engagement is that a technical SEO fix and a content fix solve different problems, and a site can fail at either one independently of the other. Quantzee's technical layer was genuinely broken when we started — no amount of good blog content would have fixed missing schema or a 404'd internal link. But once that layer was clean, the remaining gains came from going back into Search Console data on a regular cadence and fixing the specific pages sitting just short of page one, not from writing more content in general. For a technical product sold to a global, skeptical audience, the trust signals in the markup and the accuracy of every claim in the copy matter as much as the keyword targeting itself.

FAQs

Frequently asked questions

What was wrong with the SaaS site before the SEO work started?
It scored 52 out of 100 on our internal checklist: inconsistent page titles with no length discipline, missing or oversized meta descriptions, no Open Graph or Twitter Card markup on most pages, and no structured data beyond Astro's defaults.
How much did the technical fixes improve the score?
The mechanical fixes alone — title and meta rewrites, full OG/Twitter markup, JSON-LD schema by page type, image preload hints, and sitemap/robots cleanup — moved the score from 52 to roughly 82-88 out of 100.
Does fixing the technical SEO layer guarantee better rankings on its own?
No. A clean technical layer removes the things actively working against you, but the ongoing gains came from a separate, regular pass through Search Console data to find and fix pages sitting just short of page one.
Why did a 0-indexed-URLs report from Google turn out to be wrong?
Google's sitemap-level indexing-count API is a known dead metric that still returns 0 after being deprecated. Checking the same URLs one at a time with the URL Inspection API showed 25 of 25 sampled pages were actually indexed.
"{Brand} Review" or "{Brand} Alternative" — which competitor-page title format performs better?
In this case, testing both formats against 90 days of Search Console data showed "{Brand} Review" titles beat "{Brand} Alternative" titles on click-through rate, 1.49% versus 1.26%, so that became the locked format for future competitor pages.

More from the Nurotech blog

Ready to grow your business?

Fill out the form or call us — let’s find where your next growth comes from.

9659 634 634 [email protected]