The Rental Plug · Operations

Command Centre

Visitor numbers
Cloudflare
Web Analytics — visits, pageviews per car URL, referrers, devices, countries. Edge-injected, no cookies, no banner.
Enquiry attribution
WhatsApp refs
Every enquiry arrives stamped Ref: CAR-<ID> or Ref: PAGE-<NAME>. Log them below to build the per-car picture.
Traffic security
CF Edge
HTTPS forced, TLS 1.2 minimum, Bot Fight Mode, browser integrity check, security headers, CSP report-only.
Redeploy
One drag
Export from Claude Design → drag folder onto the Pages project → live in ~30s.
01

Enquiry log — which cars are earning

saved in this browser · CSV export

When a WhatsApp enquiry lands, its message ends with a Ref code. Log it here (10 seconds) and this page becomes the demand ledger — which cars pull enquiries, which pages convert, what changed month to month. Data lives in this browser via localStorage; export CSV for a backup or a spreadsheet.

DateCar / pageViaNote
No enquiries logged yet. First one arrives, stamp it in.
LeaderboardDemandCount
Leaderboard builds itself as you log.
Read it against pageviews. Web Analytics gives views per Car.dc.html?car=<id>. A car with high views and few enquiries has a pricing or photo problem. A car with few views and steady enquiries deserves a homepage slot.
02

Where every number lives

bookmark this section
QuestionWhere
How many people visited today / this week?Web Analytics → Visits
Which cars get looked at most?Web Analytics → Page views → paths containing Car.dc?car=
Where do visitors come from?Web Analytics → Referrers (Instagram, Google, direct…)
Which car produced this enquiry?The Ref: code inside the WhatsApp message itself
How many enquiries per car all-time?This page, section 01 — search WhatsApp for CAR- to backfill
Is the site being attacked / scraped?Security → Analytics — blocked bot traffic
Is the site fast?Web Analytics → Core Web Vitals (real visitor timings)
03

Security posture

as configured · 22 Aug 2026
LayerStateWhat it does
HTTPS forcedONEvery http:// request 301s to https:// at the edge
Minimum TLS 1.2ONRefuses obsolete, breakable TLS 1.0/1.1 connections
TLS 1.3ONFastest, most secure handshake for modern browsers
Bot Fight ModeONChallenges scrapers and junk bots before they reach the site
Browser Integrity CheckONBlocks requests with forged/abusive headers
Security headersONnosniff, frame-ancestors, referrer policy, permissions policy via _headers
CSPReport-onlyLogs would-be violations without breaking inline styles/scripts. Revisit after a clean week.
HSTSDEFERREDDeliberate. Turn on in SSL/TLS → Edge Certificates only after days of clean HTTPS — it is a one-way door for the max-age.
DDoS protectionONCloudflare's always-on network-layer protection, free tier included
Origin exposureNONEStatic files on Cloudflare's own network — there is no origin server to attack, no database to breach, no forms to inject
Accounts are the soft target now, not the site. The domain (Porkbun) and the hosting (Cloudflare) fall to whoever controls their login emails. 2FA on both accounts matters more than any header above.