Weekly Site QA: A 45-Minute Checklist for Small Teams

SEO Slots

Search Intent

The reader wants a repeatable weekly routine for finding site defects without running a full audit.. The article must answer the reader's operational question before any commercial route appears.

Reader Artifact

Reusable checklist, table, or runbook from the article body. This artifact is the reason the article can be saved, cited, or reused by an operator.

Internal Links

• Hub: /resources/small-site-ops-library/
• Related article: /resources/small-site-ops-library/content-inventory-template-small-sites/
• Related article: /resources/small-site-ops-library/broken-link-triage-small-sites/
• Related article: /resources/small-site-ops-library/measurement-sanity-check/
• Related article: /resources/small-site-ops-library/website-publish-checklist/
• Tool/service route: /services/site-operations-review/

Structured Data

Recommended schema: Article, BreadcrumbList. Keep BreadcrumbList aligned with /resources/small-site-ops-library/weekly-site-qa-checklist/. Do not add Product, Offer, Review, Rating, or FAQPage schema for this wave unless a later approved public page visibly supports it.

CTA Route

Primary route: /services/site-operations-review/.

CTA label: Use the related checklist or diagnostic route.

CTA family: diagnostic_sprint.

Use this route only after the article artifact has clarified the next operational step. Public forms, accounts, and payments are intentionally not part of this resource page.

The CTA stays measured and specific, with no public payment or account route on this page.

Measurement

Public-Preflight NG Items

• Fake client proof, fake metrics, fake awards, or guaranteed outcomes.
• Public account, form, payment, repo, domain, or outreach route before checks pass.
• Unapproved cross-brand, unrelated monetization, or off-topic trust route.
• Unsupported claims about SEO, ranking, revenue, or tool behavior.
• Machine-like slug, broken internal link, missing schema plan, or missing measurement slot.slug: "weekly-site-qa-checklist"

primary_query: "weekly website QA checklist"

secondary_queries:

• "small business website QA"
• "weekly website maintenance checklist"
• "website quality assurance checklist"

search_intent: "The reader wants a repeatable weekly routine for finding site defects without running a full audit."

H1: "Weekly Site QA: A 45-Minute Checklist for Small Teams"

H2_outline:

• "What Weekly Site QA Should Catch"
• "The 45-Minute Weekly QA Schedule"
• "Step 1: Start With This Week's Changes"
• "Step 2: Review the Critical Page Set"
• "Step 3: Check Links and CTAs by Impact"
• "Step 4: Verify Forms and Conversion Paths"
• "Step 5: Run a Measurement Sanity Check"
• "Step 6: Assign Decisions, Not Just Notes"
• "Common Failure Modes"
• "Copyable Weekly Site QA Checklist"
• "Natural Next Step"

internal_links:

• "/resources/small-site-ops-library/broken-link-triage-small-sites/"
• "/resources/small-site-ops-library/measurement-sanity-check/"
• "/resources/small-site-ops-library/website-publish-checklist/"
• "/resources/small-site-ops-library/content-inventory-template-small-sites/"

external_reference_policy: "No external references required for draft. If public examples or analytics platform behavior are added, verify against official documentation at publish time."

schema_type_recommended: "Article + FAQPage where visible FAQs are added + BreadcrumbList"

FAQ_candidates:

• "How often should a small team run website QA?"
• "What should be checked first during weekly site QA?"
• "Should every broken link be fixed immediately?"

CTA_route: "/services/site-operations-review/"

measurement_event_name: "small_site_ops_weekly_qa_cta_click"

public_preflight_ng: true

A small website can look fine on Monday and quietly lose trust by Friday. A form stops sending, a pricing page has an old claim, an outbound link breaks, the analytics tag disappears from a new template, or a newly published page has a title that does not match search intent.

Most small teams do not need a complex web operations department. They need a weekly site QA routine that is short enough to survive a busy schedule and structured enough to catch the defects that actually matter.

This guide gives you a 45-minute weekly QA routine for small business sites, service sites, resource blogs, and lightweight product sites. Copy the checklist into a spreadsheet, Notion page, ticket template, or recurring calendar event.

Related same-pack guides: use the broken link triage guide when QA finds link defects, the measurement sanity guide when reports look suspicious, and the publish checklist to prevent the same issues before new pages go live.

## What Weekly Site QA Should Catch

Weekly QA is not a full audit. It is a recurring inspection for preventable issues.

The routine should catch:

- pages that were changed but not reviewed;
- broken links on important pages;
- forms or CTAs that no longer complete;
- analytics gaps that make reports unreliable;
- outdated claims on high-trust pages;
- visible layout problems on common devices;
- internal links that lead readers away from the intended path;
- missing or confusing publish metadata.

It should not try to solve every SEO, design, or conversion question in one sitting. If the checklist tries to do everything, the team will stop running it.

## The 45-Minute Weekly QA Schedule

| Minute | Area | What to check | Output |
|---:|---|---|---|
| 0-5 | Change review | What pages, templates, forms, or tracking items changed this week? | List of pages to inspect |
| 5-15 | Critical pages | Home, service, pricing, contact, top traffic pages | Pass/fail notes |
| 15-25 | Links and CTAs | Primary buttons, nav links, footer links, recent article links | Broken link or wrong-destination list |
| 25-32 | Forms and conversion paths | Contact forms, booking links, newsletter signup, checkout/contact route | Completion evidence |
| 32-38 | Measurement | Pageview, click, form, and conversion events appear where expected | Measurement confidence note |
| 38-43 | Content freshness | Claims, dates, offers, staff info, screenshots, policy text | Update tasks |
| 43-45 | Decision | Assign severity and owner | Issue log updated |

If you only have 20 minutes, check critical pages, CTAs, and forms. If you have more than 45 minutes, spend the extra time repairing issues rather than expanding the checklist.

## Step 1: Start With This Week's Changes

Before browsing the site, ask what changed.

Small-site QA fails when the reviewer starts from the homepage every week and ignores the actual change history. A small update to a landing page, plugin, header component, form embed, or tracking script is more likely to create defects than a page that has been stable for months.

Use this quick change intake:

| Question | Example answer | QA implication |
|---|---|---|
| What pages were published or edited? | New service page, updated case study | Review content, metadata, links |
| What templates or components changed? | Header button changed | Check multiple page types |
| What forms or embeds changed? | New scheduling widget | Submit a test or verify destination |
| What tracking changed? | New click event name | Check analytics/debug output |
| What external dependencies changed? | New payment link, new partner URL | Check outbound path |

If nobody knows what changed, that is a process issue. Add a simple "changed pages this week" field to your publish workflow.

## Step 2: Review the Critical Page Set

Every small site should maintain a critical page set. These are the pages where defects hurt trust, leads, sales, or operational clarity.

Common critical pages:

- homepage;
- primary service or product page;
- pricing or plans page;
- contact page;
- booking or quote request page;
- top organic landing page;
- top paid campaign landing page;
- legal or policy page if linked in conversion paths;
- any page recently sent to prospects, partners, or press.

For each page, check:

- Does the page load without obvious visual breakage?
- Does the title match the page content?
- Is the primary CTA visible and still relevant?
- Are claims current and supportable?
- Are internal links useful and intentional?
- Does the mobile view remain usable?
- Is there any placeholder, duplicate block, or staging text?

### Critical Page Review Template

Page:

URL:

Last changed:

Reviewer:

Device/browser:

Pass:

• Main content matches page intent:
• Primary CTA works:
• Internal links are relevant:
• Mobile view acceptable:
• No outdated claims:
• Measurement present:

Issues:

1.

2.

Decision: PASS / REPAIR / ESCALATE

Owner:

Due date:

## Step 3: Check Links and CTAs by Impact

Do not treat every broken link with the same urgency. A broken footer social link is not the same as a broken "Request a Quote" button.

Use this severity table:

| Severity | Example | Response |
|---|---|---|
| P0 | Contact form button goes to a 404; payment link fails; quote route unreachable | Fix immediately or roll back |
| P1 | Primary CTA destination is wrong; top landing page links to obsolete offer | Fix same day |
| P2 | Article internal link broken; resource link points to moved page | Fix in next cleanup block |
| P3 | Low-traffic archive link broken; non-critical external citation moved | Queue for weekly/monthly cleanup |

Checklist:

- Test primary CTA on homepage.
- Test primary CTA on each critical page.
- Click the contact or booking route.
- Check nav items.
- Check footer links that affect trust.
- Check links in newly published or recently edited pages.
- Check 404 report or crawl output if available.

You do not need to click every link manually every week. Combine manual testing for critical paths with a lightweight crawler or CMS link report when available.

## Step 4: Verify Forms and Conversion Paths

Forms fail in boring ways: notification emails stop, hidden fields change, captcha blocks real users, confirmation pages are removed, or the embedded tool changes behavior.

Weekly QA should record evidence, not just "looks fine."

Form QA checklist:

- The form loads.
- Required fields are clear.
- Error messages appear when expected.
- A valid submission can be completed in the test environment or approved live test path.
- Confirmation message or thank-you page appears.
- Notification reaches the expected inbox or CRM.
- Analytics event appears if the site uses conversion tracking.
- The route does not expose private test data.

If live test submissions are not allowed, document the allowed verification method. For example, "submit to staging form," "use vendor test mode," or "verify recent real submissions with operations owner."

## Step 5: Run a Measurement Sanity Check

Weekly QA should not become a deep analytics audit, but it should catch obvious measurement failures.

Check:

- Pageviews are still arriving for the site.
- Top landing pages are plausible.
- Newly published pages appear in reports after enough time has passed.
- Key click or form events have not dropped to zero unexpectedly.
- Campaign URLs use expected parameters.
- Internal traffic filtering or consent settings have not hidden all data.

Measurement sanity table:

| Signal | Healthy pattern | Warning sign | Action |
|---|---|---|---|
| Pageviews | Similar to recent baseline | Sudden zero or unexplained spike | Check tag and reporting filters |
| Contact events | Low but present if traffic exists | Zero after form/template change | Test form event |
| CTA clicks | Plausible relative to page traffic | Clicks exceed pageviews or vanish | Check duplicate/missing trigger |
| New pages | Appear after normal delay | No traffic despite internal links | Check tag/template/indexing |
| Campaign URLs | Expected source/medium | Mixed or missing parameters | Fix link builder template |

## Step 6: Assign Decisions, Not Just Notes

A QA routine is only useful if it produces decisions.

Use three decision labels:

- `PASS`: no action needed.
- `REPAIR`: issue found and assigned.
- `ESCALATE`: issue affects revenue, legal trust, measurement integrity, or launch readiness.

Avoid vague notes such as "check later" or "maybe broken." Each issue should have an owner and next action.

### Weekly QA Issue Log Template

| Date | Page/path | Issue | Severity | Evidence | Owner | Due | Status |
|---|---|---|---|---|---|---|---|
| YYYY-MM-DD | /contact/ | Submit button loads wrong URL | P0 | Screenshot + tested on Chrome mobile | Name | YYYY-MM-DD | Open |
| YYYY-MM-DD | /blog/example/ | External source link returns 404 | P2 | Link checker result | Name | YYYY-MM-DD | Queued |

## Common Failure Modes

### The Checklist Is Too Long

If the weekly checklist takes two hours, it will not run weekly. Split deep work into monthly audits and keep weekly QA focused on critical paths.

### The Reviewer Only Looks at Desktop

Many small-site defects appear on mobile first: sticky headers cover buttons, form fields overflow, or hero images push CTAs too far down.

### The Team Checks Pages but Not Evidence

"Looks okay" is weaker than "form submitted, confirmation displayed, notification received." Record the evidence level.

### Every Issue Becomes Urgent

If every broken link is a fire, real fires become invisible. Use severity labels.

## Copyable Weekly Site QA Checklist

Weekly Site QA

Date:

Reviewer:

Change source checked:

Change intake

[ ] List pages changed this week

[ ] List templates/components changed this week

[ ] List forms/embeds/tracking changed this week

Critical pages

[ ] Homepage reviewed

[ ] Primary service/product page reviewed

[ ] Contact/booking page reviewed

[ ] Top landing page reviewed

[ ] Recently changed page reviewed

Links and CTAs

[ ] Homepage primary CTA tested

[ ] Critical page CTAs tested

[ ] Navigation links sampled

[ ] Footer trust links sampled

[ ] Recently published page links checked

Forms and paths

[ ] Contact/lead route verified

[ ] Confirmation behavior verified

[ ] Notification/CRM route verified when applicable

Measurement

[ ] Pageviews present

[ ] Key event trend plausible

[ ] New/changed pages measurable

[ ] Campaign link parameters plausible

Decision

[ ] Issues assigned severity

[ ] Owners assigned

[ ] P0/P1 items escalated

[ ] Log updated

Decision: PASS / REPAIR / ESCALATE