supabase.com
Rescan
No builder fingerprint found
Nothing in the page, the bundle or public DNS names a website builder. That is not proof it was hand-written — Cursor, Claude Code and Copilot leave no trace at all.
100/ 100 finish
Prompt to improve
nothing left to clean up · 0 scored findings · 1357 words in initial HTML
AttributionMarks the builder left behind
clear
DefaultsScaffold settings never changed
clear
FinishProduction basics not yet done
clear
SafetySecrets and data access
clear
Prompt to improve
Open as text
You are working on the codebase behind supabase.com. An external scan of the deployed site found the tells listed below — the specific things that make it read as assembled by a website builder rather than built. Fix them in the order given. Each item names the evidence observed on the live page, so you can confirm the problem before you change anything. Rules for this task: - Do not redesign the site. Change only what each item asks for. - Do not change any URL, route or page title beyond what an item explicitly requires. - If an item does not match what you find in the code, say so and skip it rather than inventing a change. - Work through the list top to bottom and report what you changed for each. ## Scaffold defaults still in place ### 1. Deploy-platform response headers Observed on the live site: x-vercel-id (Vercel) Noted for context only: x-vercel-id (Vercel). Deploy-platform headers say where a site is hosted, not how it was written. ## When you are done Re-run the checks yourself before reporting: fetch the deployed page with curl and confirm the markers above are gone from the HTML, that unknown paths return 404, and that `/robots.txt` and `/sitemap.xml` answer 200. Then summarise anything you deliberately did not change and why.
Findings
Nothing scored against this site.
•
Deploy-platform response headersx-vercel-id (Vercel)
noted