Reference

Checklists

The trimmed-down forms of every review pattern in this notebook. Each one fits on a single sheet and assumes you already know why each item is there.

Cobalt paper card labelled checklists on a research desk.

These are the working forms. The longer reasoning lives on the pillar pages they come from. If a line in a checklist looks unfamiliar, follow it back to the matching pillar (linked under each list).

Domain history review

  1. TLD and any country signal noted.
  2. At least two archived snapshots from distant points reviewed.
  3. Dominant language in each snapshot recorded.
  4. Topic continuity: continuation, mild gap, or significant gap.
  5. Subdomain footprint: stable, light, or wide.
  6. One-line judgement written.

From domain history.

Domain profile

  1. TLD context (generic / country / restricted).
  2. Continuity of registration over time.
  3. Dominant language and topic.
  4. Subdomain footprint.
  5. Current crawl behaviour on a sample of paths.

From domain profile.

Hosting requirements

  1. Server response under 250 ms on a typical page.
  2. Daily automated backups, 14 days retention, one-click restore.
  3. Modern PHP / Node / Python lines available.
  4. Free SSL with auto-renewal.
  5. Renewal pricing visible before checkout.
  6. Documented support response targets.
  7. Migration path in and out without third-party scripts.

From hosting.

Favicon tag set

  1. favicon.ico served from the site root.
  2. icon-32.png linked with rel="icon".
  3. apple-touch-icon.png at 180x180.
  4. Optional site.webmanifest with 192 and 512 PNGs.
  5. Direct request to /favicon.ico returns 200.
  6. Tab icon and iOS home-screen icon both verified.

From favicons.

Subdomain planning

  1. One-sentence reason the content is not on the main host.
  2. Audience or product surface separation justified.
  3. Plan for DNS, SSL, deploy and analytics on the new host.
  4. Clear path to merge or sunset later if the reason fades.

From subdomains.

Pre-launch hygiene

  1. Canonical host decided and enforced.
  2. Redirects from www and any historical hostnames in place.
  3. Robots and sitemap aligned.
  4. Favicon test pass complete.
  5. Hosting checklist signed off.
  6. One-line history judgement on file.

Where this fits next

For longer-form notes, see guides and resources. For small interactive helpers, see tools.