Docs

RecordsUp docs: direct answers for website monitoring.

Short practical docs for setting up checks, reading results, rechecking issues, and knowing what to fix next.

Start with one siteRead the docs

Example report

demo-store.example

Example

Checkout page needs one link fix.

The site is online and SSL is healthy. RecordsUp found one confirmed broken link on the checkout page and one alert route that still needs a test.

Website

Up

Homepage loaded in 342 ms

SSL

Valid

62 days remaining

Broken links

1 found

Found on /checkout

Alert route

Needs test

Send a test email

Broken privacy policy link

/checkout → https://demo-store.example/privacy-old

Update the checkout footer link, then recheck this finding.

How the fix moves forward

sample flow
Choose checksUptime + SSL + alerts
Find issueBroken privacy policy link
Fix and recheckReady to verify

How RecordsUp feels

A guided path, not a pile of checks.

Add a site, see the result, fix the source, and verify the known issue from the same place. The preview uses reserved example domains.

Start a guided setupView sample report
Add site

Start with the website people visit.

RecordsUp keeps the first setup focused on the domain, the first checks, and the alert route.

Read result

Checkout page needs one link fix.

The site is online and SSL is healthy. RecordsUp found one confirmed broken link on the checkout page and one alert route that still needs a test.

Fix source

Broken privacy policy link

Update the checkout footer link, then recheck this finding.

Verify

Recheck the known issue.

After the page is updated, run a focused recheck so the report confirms the fix without starting over.

Site setup

demo-store.example

example

Guided setup

4 steps

Website

Added

demo-store.example

Uptime

Ready

Homepage + checkout

SSL

Ready

Certificate expiry

Alerts

Test

Primary email route

First report

needs action
Website checkHomepage loaded in 342 ms
SSL certificateValid for 62 days
DNS readiness8 of 8 locations aligned
Broken privacy policy link/checkout -> https://demo-store.example/privacy-old
01

Add site

demo-store.example

02

Choose checks

Uptime + SSL + alerts

03

Find issue

Broken privacy policy link

04

Fix and recheck

Ready to verify

05

Share status

Status draft ready

Live workflow

A site moves from setup to evidence to action. Every row uses safe example data and points to the next customer decision.

Domaindemo-store.exampleadded
Uptime342 ms responsehealthy
SSL62 days lefthealthy
DNS8/8 alignedready
Domaindemo-store.exampleadded
Uptime342 ms responsehealthy
SSL62 days lefthealthy
DNS8/8 alignedready
Broken link/checkoutneeds action
Source pageCheckout footerfound
Next stepUpdate destinationready
RecheckKnown issue onlyqueued
Broken link/checkoutneeds action
Source pageCheckout footerfound
Next stepUpdate destinationready
RecheckKnown issue onlyqueued

From setup to fix

Add a site, choose the first checks, see what needs attention, verify the fix, and share a clean status view when customers or clients need it.

Safe example report

Use this sample to see how RecordsUp explains a website issue before you connect your own site.

01

Add site

Start with the website customers use.

demo-store.example

02

Choose checks

Keep the first setup focused, then add advanced checks later.

Uptime + SSL + alerts

03

Find issue

RecordsUp shows the issue and where it was found.

Broken privacy policy link

04

Fix and recheck

Recheck the known finding instead of crawling everything again.

Ready to verify

05

Share status

Publish a clear status view only when it helps.

Status draft ready

Best for

01New users setting up the first site.
02Teams interpreting broken-link or paused crawler results.
03Teams preparing a new site, campaign, or store release.

Launch checklist

Get the website monitoring checklist

Get a practical launch checklist and a short setup sequence for your first monitored site.

The first checks to set upBroken-link and SSL reviewA short setup sequence

From result to action

A simple path from first check to verified fix.

Add the site, understand the result, fix the source, and recheck the known problem without losing context.

01

Setup

Start with a website people recognize

Add the site, pick the first checks, and keep advanced settings out of the way until you need them.

demo-store.example
02

Result

See what changed in plain language

RecordsUp separates healthy checks, confirmed issues, and blocked results so the next step is easier to trust.

1 broken link found on /checkout
03

Fix

Use the source page and next action

The report shows where the issue was found, what destination failed, and what your team should update.

Update the checkout footer link
04

Verify

Recheck the known problem

After the fix, recheck the finding or report without forcing a full discovery crawl every time.

Ready to verify

What RecordsUp checks

Clear checks, clear results, clear next action.

Start with the website, run the checks that matter, understand what changed, and verify the fix from the same place.

Example issue

Broken privacy policy link

/checkout -> https://demo-store.example/privacy-old

Update the checkout footer link, then recheck this finding.

Add a site

Start with the domain people recognize.

Choose checks

Enable uptime, SSL, DNS, broken links, and optional workflows.

Read results

Separate confirmed issues from blocked or inconclusive crawler results.

Recheck

Rerun the found issue or report after fixes are made.

What is a broken link?

A broken link is a link that still appears on the monitored website and leads to a destination RecordsUp can confirm is unavailable or wrong.

  • 404 and gone pages
  • Bad hosts and invalid URLs
  • Wrong or failed destinations

What is a blocked result?

A blocked or inconclusive result means RecordsUp could not safely confirm the destination. It is not counted the same as a confirmed broken link.

  • Rate limits
  • Bot protection
  • Timeouts

How rechecks work

A recheck focuses on the issue that was found. Full crawls are still available when you need fresh discovery.

  • Individual issue recheck
  • Report-level recheck of known findings
  • Fresh crawl when needed

Release confidence

Before a launch or major campaign, use recent monitor results to make sure the obvious website risks are covered.

  • Recent uptime and SSL results
  • Important pages checked
  • Known issues clearly noted

Direct answers

What does Check link do?

A link recheck verifies whether the destination is still broken and whether the finding still appears in the current RecordsUp results.

Should a report recheck crawl everything again?

No. Report recheck prioritizes the problems already found. Full crawls are reserved for fresh discovery or wider coverage.

Why can a crawl be paused?

RecordsUp pauses or slows crawls when a site blocks, rate-limits, times out, or reaches the daily safety budget for that origin.

Start now

Monitor one website and see the next action clearly.

Add the first site, run the core checks, and use the results to fix what matters before visitors or clients report it.

Start with one site