Site Runbook

How it works

Enter your site. The server loads your homepage and a few standard files, the way a search engine would, asks Google how it sees your site and builds your runbook.

Three views

Green, amber, red, grey

Green means the scan confirmed it. Amber means it works but could be better. Red means the scan found a problem. Amber and red items have the fix on the line below. Grey means the scan could not check it this time. Scanned items are locked to what the scan found, so fix the problem and scan again. Blank items are yours to tick.

What the scan checks

What it asks Google

Help with each item

Use the information button beside any item to learn what it means, why it matters and what the scan can actually confirm. Links name the tool or guide they open. Manual checks are for things a public scan cannot reliably test.

The phone preview

The screenshot comes from the same Google phone test as the speed scores. A first test can take up to two minutes. A spinner and elapsed time show that it is loading, and we stop waiting after three minutes including any queue. A successful preview is reused for up to 12 hours, so it can appear immediately on a return visit even if a new test fails. Speed scores are reused for ten minutes.

Your progress

Ticks are saved in your browser, one list per site. Each runbook has its own link, like /r/example.com, so you can come back to it.

Safe scanning

The scanner only visits public addresses on ports 80 and 443. It follows at most five redirects, gives up after a few seconds and reads at most 1.5 MB per page. Scans are limited per visitor, and the Google search and speed checks run for at most 10 new sites a day per visitor. Google results are kept for 12 hours, so a new ranking can take that long to show.