Architecture

Presentation Layer

The RankAssurance website is a presentation layer only. All scoring mathematics, ranking models, competitor intelligence, historical outcome data, evidence chains, and report generation exist server-side behind authenticated internal APIs and are never transmitted to the browser. A third party could imitate the visual design, but reproducing the RankAssurance product without its proprietary backend data, models, calibration history, and evidence infrastructure is practically infeasible.

What the Browser Receives

The browser receives finished values only — rendered scores, bands, and labels. No RankAssurance scoring formula, weight, threshold, or band boundary — for the Scan Score or the Rank DNA analysis — is present in any page or script this site serves. This is checkable: read the page source and the scripts it loads.

Two illustrative calculators — the Opportunity estimate and the First-Page Ranking figures — compute in the browser from openly published inputs (third-party click-through-rate curves and disclosed constants, labeled as such on those pages). They carry no part of the proprietary scoring.

Where the Rank DNA report is interactive — the what-if projection — the browser sends the input positions to an authenticated server endpoint and displays the finished values the server returns. The computation is not in the browser; this is visible in the network panel, where the request carries positions and the response carries finished scores.

The Server-Side Boundary

Computation runs server-side, behind authenticated internal APIs under /internal/engine/v1/. Those endpoints exist and refuse: a request without a valid session is answered with a 401; a request with a session but without a valid internal signature is answered with a 403. They return no engine data. You can probe them.

The systems behind that boundary include, by category:

• Scoring engine — computes every score, band, and pillar from measured inputs.
• Evidence ledger — the record each finding is derived from and checked against.
• Verification passes — the integrity and consistency checks a report clears before it renders.
• Historical outcome store — prior scans and their outcomes, held for calibration.
• Market cohort graph — how a site's competitive set is resolved for a query.

Reproduction

A third party could copy what the browser can see — the layout, the typography, the wording. Reproducing the product is a different matter: the scores, comparisons, and reports are produced by the server-side systems above, from data and calibration the browser never receives. What ships to the browser is the finished presentation, not the machinery that produced it.

Use of This Site

Scraping, automated bulk extraction, replication, and derivative reproduction of this site, its reports, and its methodology — including the Scan Score and the Rank DNA analysis — are prohibited under the Terms of Service.