We have published several Core Web Vitals monitoring templates on GitHub — checklists, playbooks, budgets, alert policies, and client-facing artefacts. The core-web-vitals-checklists repository is an index of those repos for agency technical leads, freelancers, and in-house performance teams who want fork-friendly process material without hunting across our org.
// How the index works
Start at the index README on GitHub, or use the listing on this site for the same links grouped by purpose. Under Monitoring SOP (Standard Operating Procedure) you will find a lightweight checklist you can run as GitHub Issues, or a full agency playbook template for runbooks, clients, and ops in one repo. Under Templates and checklists each repository maps to an Apogee Watcher article — performance budgets, Slack alert policy, client report outline, monthly review, onboarding audit, ROI calculator, and review meeting agenda.
Pick the repo that matches how you already work: copy a checklist into your wiki, fork the playbook as your ops home, or adopt a single template when you are solving one operational gap. The canonical write-up for the monitoring SOP (Standard Operating Procedure) is Core Web Vitals Monitoring Checklist for Agencies on the Watcher blog.
// What to do next
Fork or use the template on the repository you need, then wire it into your existing stack — issues, Notion, Confluence, or a dedicated ops repo. These artefacts define who checks what, when, and how you escalate; they do not replace scheduled lab and field data. When you are ready to automate tests, budgets, alerts, and history across a portfolio, Apogee Watcher builds on the same monitoring mindset. Laravel teams can also run scheduled PageSpeed Insights checks with our PageSpeed Watcher package.
// Links
- Index repository: Apogee-Information-Systems / core-web-vitals-checklists
- Repository listing: Core Web Vitals Checklists on Apogee GitHub Pages
- Monitoring SOP (Standard Operating Procedure) article: Core Web Vitals Monitoring Checklist for Agencies