No builder fingerprint found

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

## Exposed credentials and data access

### 1. A Google browser API key is present
Observed on the live site: AIzaSyAytC…

Noted, not scored: a Google API key of the `AIza…` form is in the page. Maps and Places browser keys are meant to ship — airbnb.com serves one too. Confirm it is restricted by HTTP referrer and to the specific APIs it needs in the Google Cloud console; that restriction, not secrecy, is what protects it.

## Placeholder and filler copy

### 2. Navigation links that go nowhere
Observed on the live site: 8 links with href="#"

Fix the dead navigation: 8 links with href="#". Either point each one at a real route or remove it. A nav bar where half the items do nothing is the fastest way a visitor concludes nothing behind the landing page is real.

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