For Admins
Site Growth Tracking (Admin)
Admin β Site Growth pays engineers for growing their assigned website on four metrics: each tracked website is assigned to one engineer, who submits the month's total clicks from Google Search Console + Bing Webmaster Tools (Pay Per Click rule, default βΉ1 per extra click), the site's total verified signed-up users where the per-site signups toggle is on (Pay Per Verified Signup rule, βΉ1 per extra user), and β where the social toggle is on β YouTube + Instagram + Facebook numbers: the month's views (Social Views rule, βΉ100 per 10,000 combined views, paid directly β a month's views are already the increase) and each account's total followers (Pay Per New Follower rule, βΉ1 per follower gained). All rules are tunable at Point Rules like any category. It's a sibling of the Ads Manager β same spirit (self-reported numbers, salary-linked, month-locked), much simpler machinery.
Setting it up
- Track a website β pick a registered root domain (the list is the siteowners catalog; β marks already-tracked ones) and the responsible engineer (pre-filled from the site-ownership email match where there is one). One owner per website β reassigning is an edit, not a second row.
- Give the engineer console access β they need to see the property in Google Search Console (and ideally Bing Webmaster Tools; until then they enter 0 for Bing). For signups they need visibility of the site's verified-user count (admin panel or database report).
- Toggle "signups" and "social" per site β signups on for sites with user registration; social on for sites with YouTube/Instagram/Facebook accounts (the Sitemanagers section knows each domain's handles).
- That's it. The engineer submits monthly from their Site Growth page; the growth lands on their salary automatically as "Search clicks growth (+N clicks)", "Verified signups growth (+N users)", "Social views bonus (N views)" and "Social followers growth (+N followers)".
How the math works
- For the cumulative metrics (clicks, signups, followers): growth = this month's value β the previous recorded month's, clamped at zero (drops never pay negative, and after a drop the recovered amount pays again β the comparison is always to the last recorded month, not the all-time peak). The first recorded month is the baseline and pays nothing.
- Social views pay directly β βΉ per 10,000 combined views that month, no baseline β because platforms report views per period and a month's views already are the increase in total views.
- Multiple sites per engineer: per-site values (each clamped where applicable), summed, Γ the rule value. The four metrics are independent salary items β each has its own history and line.
Integrity β what to watch
The numbers are self-reported, and the one profitable lie on cumulative metrics is a low first month (an understated baseline makes every later month look like growth). For signups, insist on verified accounts only β raw registrations are trivially inflatable by bots. Views are the most spot-check-worthy metric: they pay directly each month with no self-consistent series to audit, so ask for an insights screenshot when a number jumps. So:
- Eyeball the baselines. When a site's first entry lands, open Search Console yourself and sanity-check it. One honest baseline protects every later month.
- The per-site history table shows every month's Google/Bing split and delta β spikes and conveniently-timed dips stand out.
- Locking does the rest: once you lock a salary month, the engineer can no longer edit that month's entry (the pay is frozen and the next month's baseline must not bend). Your own edits here bypass that freeze β they're the data-correction channel, so use them knowingly.
- A site with recorded months can never be deleted β deactivate it instead (history must survive; inactive sites stop paying).
Month-end order
Same as ads: engineers submit last month's clicks early in the new month β you spot-check β lock the salary month. After the lock, entries for that month are immutable to engineers.