What Mario approved
Mario asked us to open the visitor suggestion form while keeping website reading conditional on his approval. We retain Cloudflare Free and make Cloudflare changes only through the integrated browser. This release opens the form that earlier notes described as closed.
What a visitor can send
The form accepts one public HTTPS website address and a choice about internal pages. It requests no name or email and creates no visitor account, application cookie or browser-storage entry. New eligible addresses enter the existing private review list as pending. Only Mario can approve them. Submitting a proposal does not fetch the site, run the AI or create a crawl job.
A small shared allowance
Public submissions allow twenty accepted attempts per UTC day, one hundred per UTC calendar month and at least one minute between attempts. Duplicate attempts count too. A public request cannot add a row while twenty proposals await review or the collection already has one hundred website records. These conservative application limits use aggregate counters, not IP addresses or visitor identities. They provide basic protection, not a complete defence against deliberate flooding. Search and crawl allowances are unchanged.
Existing decisions stay intact
One hostname has one record. A repeated public proposal cannot change its address, approval, rejection or crawl scope. The public acknowledgement deliberately does not reveal the private status of an existing entry; it explains that only new entries with room in the review list are saved. Full review lists may therefore decline additions. Review decisions stay in the private desk.
What we checked
Local tests exercise invalid addresses, origin and method checks, bounded requests, simultaneous submissions, daily and monthly pauses, period changes and the pending-list cap. They confirm that public proposals cannot promote themselves or change an approved entry. In the live English form, Aik submitted mario-aik.space with internal pages selected. D1 showed pending status, a maximum of ten pages, depth two and zero crawl jobs for it. A rapid repeat was rejected by the shared pause. The lab proposal remains for Mario to review; it was not approved as part of this test.
Follow-up — 15 October 2026: approved, then paused
Mario explicitly approved mario-aik.space for inclusion, with up to ten pages and two link levels. Aik recorded that decision through the authenticated Cloudflare database administration in the integrated browser; Mario’s personal review-desk session was not available to Aik. The existing visitor proposal changed from pending to approved. At verification, it still had zero crawl jobs and zero indexed pages. All eight reading attempts for 15 October had already been used, so the automatic daily limit prevented further reading. We did not reset counters, increase allowances or enable a paid plan. The next daily allowance opens on 16 October at 00:00 UTC (02:00 in Berlin); queued work can then continue within the unchanged limits. A follow-up check is scheduled for 16 October at 05:15 Berlin time. Automatic reading of the lab and its appearance in search have not yet been verified. This is a saved approval and a working budget stop, not a completed end-to-end search test.
Privacy and limitations
The search privacy notice now explains proposal data and retention, aggregate counters and Cloudflare technical processing. There is no email notification or public list of submissions. Mario checks the private review desk. IndexNow remains deferred. No paid plan, analytics or new authentication provider was added.