# Set up a site

Add a site and run the first audit. nimo will monitor uptime, store history, and use that context when you ask questions.

Canonical URL: https://heynimo.com/docs/setup
Markdown URL: https://heynimo.com/docs/setup.md

## AI summary

Explains site onboarding, Page Control for important URLs, URL validation, automatic uptime checks, scheduled audits, and the difference between real visitor data and simulated test data.

## Key points

- Use the public production URL visitors use.
- Use Page Control for important URLs when the Pages tab is available.
- Paid plans can use weekly, daily, or manual audit schedules.
- Real visitor data is primary when Chrome has enough traffic for the page.
- Simulated test data is diagnostic and useful when field data is missing.

## Sections

### Add your site

- Sign in and choose Add site. Use the public URL visitors use, including the protocol, for example https://example.com.
- Start the first audit. nimo checks the URL, pulls available Chrome field data, runs a simulated test, and builds the report.
- Read the plain-language verdict first. It answers what is slow, why it matters, and what to do next.
- Add production pages when you want search and real visitor context. Staging pages can still be useful for quick simulated checks.

### Choose the right schedule

- Paid plans can use weekly, daily, or manual audit schedules.
- Use weekly audits when a site changes occasionally.
- Use daily audits when the page is tied to paid traffic, high-value SEO traffic, checkout, lead capture, or client reporting.
- Run a manual audit any time you make a change and want a before-after check.

### Add important pages

- If the Pages tab is available for your site, use Page Control to tell nimo which URLs matter most.
- Add pages such as the homepage, pricing page, signup or checkout path, product pages, comparison pages, high-traffic content, and docs.
- When discovery is enabled, the Pages tab can suggest same-site URLs from sitemap and crawl results.
- Discovered rows stay pending until you confirm and save the page profile.
- Each page can have a type, importance, funnel role, owner, device priority, monitoring schedule, and short notes.
- Use these fields to route alerts and recommendations to the right person without making every URL look equally important.
- Start with public production URLs that affect revenue, signups, search traffic, or support. Private, local, and unsafe targets are rejected by nimo's fetch guardrails.

### Understand the data sources

- Real visitor data is Chrome field data. It shows what real visitors experienced and reflects many visits, not one test run.
- Simulated test data is Lighthouse-style lab data. It helps diagnose why a page is slow, but it is not the same as what real visitors saw.
- Page inspection lets nimo inspect structure, scripts, images, and common performance patterns when answering chat questions.
- Google, Ahrefs, Cloudflare, and MCP connections add traffic, SEO, infrastructure, and workspace context.

### Manage site settings

- Use site settings to change schedules, run manual audits, compare history, manage important pages when Page Control is enabled, connect integrations, and remove sites you no longer want nimo to monitor.
- Keep the first setup simple: add one important page first, then add more money pages or client sites after the recommendations make sense.


## Related docs

- [Quick start](https://heynimo.com/docs) - Start the workflow: find the gap, explain why, fix or hand off, and watch the result.
- [Telegram](https://heynimo.com/docs/telegram) - Connect Telegram and use nimo from chat.
- [MCP for agents](https://heynimo.com/docs/mcp) - Use public docs MCP, or connect an authenticated MCP client to nimo.
- [Audits](https://heynimo.com/docs/audits) - Find the gap with CrUX field data, Lighthouse lab checks, history, and plain-language results.
- [Monitoring and alerts](https://heynimo.com/docs/monitoring) - Watch the result with scheduled audits, competitor watches, incidents, uptime checks, and alerts.