Build. Optimize.
Get found.

Build a new homepage using these inputs:
Current website: [URL]
Design references: [URLS OR SCREENSHOTS]
Business and audience: [WHO WE HELP AND WHERE]
Main visitor action: [CALL / BOOK / REQUEST INFORMATION]
Brand assets: [FILES OR FOLDER]

Read audit/current-urls.csv and audit/site-audit.md first. Use the references for visual inspiration. Keep our identity and use only assets we own or have permission to use. Preserve accurate business information and valuable existing content. Flag missing facts; do not invent testimonials, credentials or results.

Build only the homepage for review, using a maintainable setup suitable for GitHub and Vercel. Make it clear and usable on phones and desktops, with accessible navigation, readable text and prominent calls to action. Show me a preview and explain how to open it. Keep the existing live website unchanged. Wait for homepage approval before building the other pages.

Help me save this website in my own GitHub account and connect the repository to my Vercel account. Guide me through any required sign-in. Keep passwords, API keys and private data out of GitHub.

Run the build, fix errors, commit and push the project, then deploy it to Vercel. Verify the deployed page and give me the preview URL. Keep the temporary site out of search results and document how that protection will be removed for the real launch. Do not change my existing domain or DNS yet. Save the repository link, Vercel project link and preview link in project-notes.md.

Audit the rebuilt website at [PREVIEW URL] against audit/current-urls.csv and the original site at [CURRENT URL]. Check the actual deployed pages as well as the project files. Do not change DNS.

Account for every old URL: retained page, approved redirect or approved removal. Check that redirects reach a relevant working page without loops or unnecessary hops. If a redirect requires the live domain to test, mark it pending and explain how to test it after launch. Check for missing content, broken internal links and missing images.

Review phone and desktop layouts, navigation, keyboard access, text contrast, page speed and image sizes. Check page titles, descriptions, headings, canonical URLs, sitemap, robots.txt, noindex settings and structured data. Verify that production settings will allow the intended public pages to be indexed while keeping previews excluded.

Check phone links, booking links, analytics and forms. Use only clearly labeled test data and ask me before submitting anything that contacts staff or customers. A form is not verified until delivery to its intended destination is confirmed.

Save audit/launch-checklist.md with PASS, FIX or NOT VERIFIED for each check, evidence, and the affected URLs. Separate launch blockers from later improvements. Fix safe code issues, rerun the affected checks, and list manual checks I must complete. Do not report untested items as passed.

The site has passed review and I am ready to plan the launch.
Domain: [DOMAIN]
DNS provider: [PROVIDER OR UNKNOWN]
Vercel project: [PROJECT LINK]

Read audit/launch-checklist.md and identify any unresolved blockers. Inspect the current DNS records and save a copy before proposing changes. Use the exact domain configuration shown in this Vercel project, not generic example values.

Walk me through adding the domain and its www version to Vercel, choosing the primary version, and redirecting the other version. Preserve the existing primary version where practical. Show the specific website DNS records to change and wait for my approval before changing them. Preserve email records, verification records and unrelated subdomains. Explain how to restore the old website records if needed.

After I approve the change, help apply it or guide me through it. Verify DNS, HTTPS, the primary-domain redirect, key pages, old URL redirects, forms and tracking. Confirm public pages are indexable and canonical URLs and the sitemap use the live domain. Help submit the sitemap in Google Search Console. Record anything still pending rather than calling it complete.

Save audit/post-launch.md with the launch date, test results, rollback details and a short follow-up list for checking errors, indexing and traffic over the next few weeks. Keep the old hosting available until the new site is verified.