Sitearc

A weekly and monthly website upkeep routine

Two routines with the signals each one reads, filled in for one site over a month. The stop rule ends a cycle.

Answers
Run upkeep on a fixed cycle so nothing depends on remembering.
Included routine
A filled month of the weekly and monthly routines
Written for
Solo developers and site owners

Why a fixed cycle beats good intentions

Work that depends on noticing happens when something is already wrong. Work that runs on a date happens before you would have noticed.

Weekly, twenty minutes

1. read new feedback and form responses
2. triage each into reply, queue, or ignore with a reason
3. read the newest search data, pages first, queries second
4. open the queue and check it is still ordered by what matters
5. ship nothing today unless it was approved yesterday

Monthly, one hour

1. refresh the site and read the findings
2. compare this month's pages to last month's, by page
3. close the changes that shipped, and note the verdict
4. pick one theme for next month from the queries that appeared
5. write the owner or client update, in one page
6. confirm the backup exists, and its date

A filled month

Brightwater Dental, one site, one person, September 2026.

week 1  responses 3, comments 2, queued 1, replied 2, dismissed 1
week 2  responses 1, comments 0, queued 0, read only
week 3  responses 2, comments 1, queued 1 (alt text), shipped 1
week 4  responses 2, comments 0, queued 0, monthly pass

monthly pass
- refresh ran on the 14th, 7 findings, 2 queued
- pages compared: /pricing gained 3 queries, /about lost 1
- verdict closed: the title rewrite, inconclusive, comparison set noted
- theme for October: cost questions on the treatment pages
- update written on the 2nd, one page
- backup dated the 1st, 12 days old

The stop rule

The routine ends when the list is empty. If the list is never empty, the scope is wrong, not the routine.

Acceptance: the routine is running when

  • each week has a recorded outcome, including weeks with nothing
  • one verdict is closed each month, or explicitly deferred
  • one theme is chosen for the next month
  • the backup date is written down
  • the update was sent before its deadline

Troubleshooting

Symptom Likely cause What to do
The weekly read becomes daily The queue is too long Cap the queue, and defer
Verdicts pile up Windows are not being closed Reserve the monthly pass for them
The same finding returns It was dismissed without a reason Record the reason
The month is skipped No date was booked Book the pass, and keep it to an hour
The update repeats itself Nothing changed Say so, and propose one test

Limits

A weekly read is not a weekly change. Most weeks decide to change nothing.

Measurement windows are longer than a week, so never read a verdict from data collected over seven days.

Where this came from