No builder fingerprint found

You are working on the codebase behind www.detectvibecode.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.

## Unfinished production basics

### 2. Initial HTML is an empty shell — content only appears after JavaScript runs
Observed on the live site: 62 words of text in the initial HTML response

Server-render the content. The first response carries 62 words of readable text, so crawlers, link unfurlers and agents that do not execute JavaScript see an empty page. Move at least the hero copy, headings and primary navigation into the server-rendered HTML.

### 3. No Open Graph image — links unfurl as a bare grey box
Observed on the live site: no og:image

Add Open Graph and Twitter card tags with a real 1200×630 `og:image`, plus `og:title`, `og:description`, `og:url` and `twitter:card=summary_large_image`. Right now every share of this link renders as an empty grey rectangle, which reads as unfinished more than any design choice does.

### 4. No robots.txt
Observed on the live site: GET /robots.txt → 404

Add a `/robots.txt` that returns 200 and points at the sitemap. Do not block your own data endpoints in it — agents and crawlers that cannot fetch them will render your pages as empty.

## 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