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

## Placeholder and filler copy

### 1. Generic launch-copy vocabulary
Observed on the live site: "seamless" ×4 · "seamlessly" ×1 · "elevate" ×2

Rewrite the marketing copy in concrete terms. It currently leans on filler that says nothing specific ("seamless" ×4, "seamlessly" ×1, "elevate" ×2). Replace each claim with what the product actually does, a number, or a named use case. Do not substitute different superlatives.

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