> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sitepulse.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Sites
> What sites are, their settings, and how per-site overrides interact with team defaults
Sites are the websites your team keeps an eye on. Each site lives in one team and has its own checks, monitoring settings, notes, screenshot, favicon, check history, and reports.
## Sites list
The **Sites** page shows every site in your current team. Search, filter, see how each one is doing at a glance.
Search by name or URL, and use the health filter to narrow down to sites with a particular problem (or sites you haven't checked yet). Sort by name, URL, or pinned status.
## Creating sites
The dashboard requires a URL and site name:
* **Website URL** - the site you want to monitor
* **Site name** - a display name;
* **Notes** - anything you want to remember about the site (client details, goals, and so on)
* **JavaScript rendering** - turn this on for sites built with React, Vue, Next.js, and similar so broken-link checks crawl the fully rendered page; leave it off for server-rendered sites like WordPress, Ghost, or plain HTML
You don't choose which checks run when you create a site - a new site **inherits your [team monitoring settings](/guide/monitoring)** automatically. To turn individual tools on or off or change how often they run for one site, edit it afterward (see [Site-specific overrides](#site-specific-overrides)).
You can't add the same site to a team twice, and your plan sets how many sites you can monitor.
As soon as you add a site, Sitepulse grabs its favicon and screenshot, runs its first checks, and starts monitoring on a regular schedule.
### Bulk import
Multiple sites can be imported at once from a pasted URL list or a `.txt`, `.csv`, or `.xlsx` file (up to 4 MB). Files can include URL and Name columns; without headers, the first column is treated as the URL and the second as the optional name. Duplicate and invalid URLs are reported before any sites are created.
Text import accepts one URL per line. File import accepts a header row with `URL` and optional `Name` columns, or two columns in that order with no header.
## Pinning
Pinned sites jump to the top of the list (newest pins first), appear in the sidebar, and get their own spot on the dashboard. Pin the sites you care about most - production, key clients - so they're always one glance away.
Each pinned site in the sidebar shows a [pulse indicator](#pulse-indicator) so you can spot problems without opening the site.
Pin or unpin a single site from its row, or select several and do it in bulk.
## Bulk actions
Select sites from the table to act on several at once.
| Action | Effect |
| ---------- | -------------------------------------------------------------- |
| **Pin** | Adds selected sites to the dashboard pinned-sites area |
| **Unpin** | Removes selected sites from the pinned-sites area |
| **Delete** | Deletes selected sites and their schedules, checks, and issues |
Bulk deletion asks for confirmation before it runs.
Pulse indicator
The pulse is a small animated dot that summarizes a site's latest Status, SSL, Broken Links, and Performance results in one place. You'll see it next to pinned sites in the sidebar and on each site's detail page.
| Level | Meaning |
| -------------------- | --------------------------------- |
| **Positive** (green) | All four checks are healthy |
| **Warning** (amber) | One to three checks have problems |
| **Critical** (red) | All four checks have problems |
Sitepulse counts a problem when:
* The latest status check reports the site as down
* The latest SSL check reports an invalid certificate
* The latest broken-link check found one or more broken URLs
* The latest performance check breaches your configured thresholds
DNS is not included in the pulse - use the [health filters](#health-states) or site detail view for DNS status.
Hover the pulse on a site detail page to see how many issues were detected.
Health states
You can filter the list by health, based on each site's **most recent** check results:
| Condition | Meaning |
| -------------------- | --------------------------------------------------------------- |
| **Down** | Latest status check reports the site as unavailable |
| **Invalid SSL** | Latest SSL check reports an invalid certificate |
| **DNS issues** | Latest DNS check has a hard failure or expected-record mismatch |
| **Broken links** | Latest broken-link check found one or more broken URLs |
| **Poor performance** | Latest performance check breaches configured thresholds |
| **No check yet** | No result exists yet for that tool |
## Site detail
Open a site to see:
* The site screenshot, favicon, URL, notes, and [pulse indicator](#pulse-indicator)
* Latest Status, SSL, DNS, Performance, and Broken Links indicators
* Uptime stats for today, 30 days, and 90 days
* A response-time chart
* DNS provider and record summaries
* Recent check history
* Buttons to **Run Check**, **Edit**, or **Visit** the site
Use **Run Check** to check a site right now instead of waiting for the next scheduled run. What you can run depends on your plan's tools and how many on-demand checks your team has left this month. Dashboard checks can run outside the automatic cadence, unless the same tool already has a pending on-demand check for that site.
### Check history
Filter past checks by source (**All**, **On-demand**, **Automatic**) and by tool - handy for separating your on-demand troubleshooting from the routine scheduled monitoring.
Open any result to see the full detail. You can delete your own on-demand results (with the right permission); automatic results are kept for as long as your plan allows and can't be deleted by hand.
## Site settings
| Setting | Description |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Name | Display name |
| URL | Monitored URL |
| Notes | Team notes |
| Pin state | Whether pinned |
| JavaScript rendering | For broken-link checks |
| Enabled checks | Which tools run automatically and evaluate issues for this site |
| Request header | Overrides the team header for Status, Broken Links, and Performance checks |
| Check cadence | Overrides team default cadence per tool |
| Problem threshold overrides | Override team [issue rules](/guide/monitoring#issue-settings) |
| Broken-link ignore paths | Paths excluded from broken-link crawls (overrides the [team default](/guide/monitoring#broken-link-thresholds-and-filters)) |
| DNS expected records | Per-site expected DNS records for change detection |
| Performance page URL | Optional page on the same domain used for performance monitoring |
Changing enabled checks or cadence settings updates the site's automatic monitoring schedule.
## Site-specific overrides
Most sites inherit [team monitoring defaults](/guide/monitoring). Use overrides only when one site needs different behavior.
DNS expected records are stored on the site itself. Resetting monitoring overrides does not clear that DNS baseline.
Send a different HTTP header when Status, Broken Links, and Performance checks fetch this site. Both the name and value are required. If you leave them empty, the site inherits the team header. For broken-link crawls, Sitepulse sends the header only to URLs on this site's host and not to external links.
Check one or more tools more or less often than the team default.
Override status, SSL, broken-link, performance, or DNS thresholds for this site only. Status overrides can choose which supported HTTP response codes count as incidents.
Monitor a specific page, such as `https://example.com/pricing`, instead of the site's root URL. The URL must belong to the same domain as the site.
URL path patterns the broken-link crawler skips on this site (for example `/admin`, `/cart`, `/wp-admin/*`). Useful for admin areas or dynamic URL spaces that should not affect incident detection.
Explicit expected DNS records by type and value (for example `A` -> `203.0.113.1`). You can add values by hand or pull them from the latest DNS check. When unset, Sitepulse uses the first DNS check as the baseline for [record change monitoring](/guide/monitoring#dns-record-monitoring).
Enable for JavaScript-heavy sites so broken-link checks see the rendered page. Leave off for server-rendered sites (WordPress, Ghost, plain HTML).
## Deleting a site
Deleting a site removes its automatic schedules, check history, and issues along with the site itself.
Deletion cannot be undone.