What these checklists are for
The guides on this site explain how something works and why a decision goes one way rather than another. A checklist does neither. It assumes the reader already knows the method and simply asks, at the point of action, whether the things that most often go wrong have been dealt with. That is a different job, and it needs a different format: short imperative lines, each one a single check that passes or fails, grouped so that a person can work through them in the order the job actually happens.
The checklists fall into a few broad kinds, and each kind gains lists as the library grows, so the examples in brackets are a sample rather than the full set. Pre-launch QA lists (such as a paid campaign, an email send, a landing page, a text or push message, a paid placement in someone else's channel, or a campaign that asks people to phone or message) catch errors before money or reputation is spent. Publishing lists make sure a page, a post or a release goes live with the things search engines and readers need. Verification lists prove that tracking does what the plan says it does. Setup and audit lists (such as a new analytics property, a new ad account, a technical SEO review or an advertising account) give a repeatable structure to work that is otherwise done from memory and done differently each time. Research and event lists (such as a survey, a round of moderated sessions, a webinar, a stand or a customer day) check that the people taking part, what they agreed to and the follow-up are ready before the first invitation goes out or the first guest arrives. Review lists (such as copy drafted with an AI tool, tracking code, formulas, SQL or structured data an AI tool wrote, and anything that names a competitor) check work before it is published, shared or used in a report. Change lists (such as what an ad platform bids towards, how a reported metric is defined, the scope of an AI assistant already answering customers, a sync between the CRM and another tool, an AI step switched on in an automation, a change to affiliate commission or terms, a holdout, geo or lift test of a channel, a mailing or a flow, and cutting marketing spend mid-period) gate a change to something that is already running. Profile optimisation, migration and handover lists cover jobs that happen rarely enough that nobody remembers all the steps.
Every page follows the same shape. It says when to run the checklist, what to have open before starting, then the checklist itself, then what to do when an item fails, and finally the mistakes people make with the list itself. Items are deliberately terse; the sentence that explains an item lives in the linked guide, where it can be as long as it needs to be. A KPIA metric tied directly to an objective. target, a budget or a benchmark never appears in an item, because a checklist should be true for every campaign, not just the one it was written for.
How to use them (ticks stay in your browser)
Each checklist renders as a grid of tick boxes with a progress bar and a reset button. Tick an item and the page remembers it: the ticks are written to your browser's local storage under a key for that page, so the next time you open the same checklist in the same browser, your progress is still there. Nothing is sent to a server. Nobody else can see your ticks, they do not follow you to another device or browser, and clearing site data or using a private window starts the list from empty. That design is deliberate: the checklists need no account and collect nothing, which is the only honest way to offer a tool like this on a public site.
The trade-off is that the ticks are personal, not shared. If a team needs to show that a check was done, copy the items into the ticket or the brief and record who signed off, and use the page as the reference copy. The items are also rendered as a plain list before any script runs, so a checklist can be printed, read on a slow connection or pasted into a document without losing anything.
Run a checklist twice. Work through it once while building, so each item is dealt with as it comes up, then reset it and run it again at sign-off with the finished campaign, page or container in front of you. The second pass is the one that catches the change somebody made after the first. A compact version of the first few lists also lives on the checklists resource page, which is the quick reference; the pages in this library carry the full item set, the failure advice and the links.
A small agency adopting the launch checklist
A three-person agency takes on a garden-furniture retailer whose previous campaigns had been launched by whoever was free. In the first month, two of four campaigns went live with last year's end date and one sent all traffic to a page that had since been redirected. The agency makes the campaign launch QA checklist part of the hand-over: the builder runs it while building, then the account lead resets it and runs it again before approving the £6,500 budget for the spring push. The second pass catches a missing customer exclusion that would have spent an estimated £900 showing a first-purchase discount to people who had bought in the previous 90 days. The ticks live in the account lead's browser; the sign-off itself is recorded as a comment on the ticket, with the date and the two names.
Which checklist when
Start from the job in front of you, not from the list you remember best. Several jobs call for two checklists in sequence: a campaign launch depends on tracking that has been verified, and an audit often ends by sending you to the migration or setup list. The table routes the common situations to the checklist to run first and the one to reach for next.
| Situation | Run first | Then |
|---|---|---|
| A paid campaign is built and waiting for approval | Campaign launch QA | Tracking verification if any conversion item cannot be ticked |
| A new page or a rewrite is ready to go live | SEO page publishing | Landing page if paid traffic will be sent to it |
| A tag, pixel or conversion action has been added or changed | Tracking verification | GA4 setup if the property itself is new or untidy |
| A new analytics property, or one nobody trusts | GA4 setup | Tracking verification once events are flowing |
| A social profile is being created or has drifted | Social page optimisation | Campaign launch QA if paid social follows |
| Organic traffic has dropped, or the quarterly review is due | Technical SEO audit | Website migration if the platform or URLs are changing |
| You are inheriting a Google Ads account | Google Ads account audit | Tracking verification for the conversion actions it relies on |
| You are inheriting a Meta Ads account | Meta Ads account audit | Tracking verification for the pixel and server events |
| A landing page is about to receive traffic | Landing page | Campaign launch QA for the campaign sending it |
| An email is scheduled and the send button is next | Email campaign QA | Tracking verification if the links carry new parameters |
| A redesign, replatform or domain change is planned | Website migration | Technical SEO audit after launch |
| A business opens a new ad account, or takes one back from a former agency or freelancer | New ad account setup | Tracking verification once tags and conversions are installed |
| A customer survey is written and the first invitation is about to go to the sample | Survey launch | Email campaign QA if the invitation goes by email |
| Interviews, focus groups, usability tests or a diary study are about to start | Research session readiness | A/B test launch if the sessions point to a change worth testing on the live site |
| Registration is about to open for a webinar or online event | Webinar launch | Lead routing QA if registrations reach sales as a new lead source |
| A trade show stand, roundtable or customer day is in its final week | In-person event readiness | Lead routing QA to test the routing for the new lead source |
| An AI assistant is about to answer customers, or its scope, content or model is changing | AI customer service launch | AI-assisted content review for copy that is published rather than conversations |
| A text, WhatsApp, push or in-app message is about to be sent or switched on in a flow | Mobile message send QA | Email automation flow launch for the journey the message sits in |
| A television, radio, print or outdoor flight is about to start | Offline media flight launch, once insertion order sign-off has passed | Campaign launch QA for the digital lines in the same campaign |
| A review request is about to start or change, or an incentive is being attached | Review request launch | Email automation flow launch when the request is a step in an automated journey |
| What a platform bids or optimises towards is about to change | Conversion goal change | Tracking verification for the new event before it carries any bidding |
| A data-led PR story is ready to offer to the first journalist | Digital PR data story | Press release distribution when a release goes out with the story |
| A joint campaign with a partner business is ready for approval on both sides | Co-marketing launch | Campaign launch QA for each side's ads, emails and landing pages |
| A sponsored article, newsletter slot, paid affiliate position or podcast read has been agreed and has not yet run | Sponsored placement launch | Influencer campaign launch where creators post on their own accounts instead |
| Tracking code, a formula, a query or structured data an AI tool wrote is about to be published, shared or used in a report | AI-written code review | GTM container publish for the container version, or tracking verification once the change is live |
| Marketing spend has to fall during a period and the size of the cut is known | Marketing budget cut | Monthly paid media review to agree next month's split once results are closed |
| A campaign whose main response is a phone call or a message conversation is about to go live | Call and message campaign launch | Lead routing QA for enquiries that arrive as forms |
| A holdout, geo or lift test of a channel, a mailing or a flow is designed and has not yet started | Holdout test readiness | A/B test launch instead for tests that split website visitors between page variants |
| A page, search ad, video or battlecard that names a competitor is about to go out | Competitor comparison | SEO page publishing for a versus or alternatives page, or YouTube video publishing for a comparison video |
| Staff are about to be invited to post about the business's work on their own accounts | Employee advocacy launch | Social post publishing for each post from the official accounts |
| A sync or connector between the CRM and another tool is about to be switched on, reconnected or changed | CRM sync change | Lead routing QA where forms create leads, or email automation flow launch for flows that read a changed field |
| An AI step that writes, classifies or acts without a person reading each output is about to be switched on in an automation, or its prompt, model or permissions are changing | AI automation go-live | Email automation flow launch for the flow around it, or AI customer service launch where the AI answers customers |
| A change to affiliate commission, tiers, windows, validation or credit rules has been decided and partners have not yet been told | Affiliate commission change | Marketing budget month-end close for the first close after the change |
| A change to how a reported metric is calculated or what it counts has been decided, from a new formula or attribution rule to a redefined lead or a replaced north star, and no report uses it yet | Metric definition change | Dashboard launch QA for each dashboard that reads the metric, conversion goal change where an ad platform bids on the measure, or lead routing QA where a lead or lifecycle stage is redefined |
The pages beneath this introduction are listed automatically, so a new checklist appears here as soon as it is published. If two rows seem to apply, run the one whose failure would cost more first; a campaign that spends against broken tracking is worse than a campaign that launches a day late.
Checklists for specific launches, handovers and reviews
The lists below cover narrower moments, such as a launch on one platform, a paid placement in someone else's channel, a feed or catalogue going live, a tag container being published, a change to what bidding learns from, a change to how a reported metric is defined, a holdout test, a survey, a research study or an event about to start, a handover between agencies, a budget cut, the monthly review and the month-end closeThe point each month when finance books costs into the period and needs marketing's accruals, coded invoices and cleared orders by its deadline.. Each pairs every check with the guide that explains it, so a box that cannot be ticked leads straight to the fix.
| Area | Checklist | When to run it |
|---|---|---|
| Launching paid media | New Ad Account Setup | When a business opens an ad account on any platform for the first time, or takes an existing account back under its own ownership, before the first campaign is built in it |
| Launching paid media | LinkedIn Ads Launch QA | After a LinkedIn Ads campaign is built in Campaign Manager and before it is set live, and again whenever its lead gen form or audiences change |
| Launching paid media | TikTok Ads Launch QA | After a TikTok campaign is built in Ads Manager and before it goes live, and whenever the pixel, the optimisation event or the Spark Ads codes change |
| Launching paid media | Performance Max Launch | Before a new Performance Max campaign is enabled, or before an existing one is rebuilt into new asset groups or listing groups |
| Launching paid media | DV360 Campaign Launch | After insertion orders and line items are built in Google's demand-side platform and before the flight starts, and when a new deal or creative set is added mid-flight |
| Launching paid media | App Install Campaign Launch | Before an app install campaign goes live on any network, and whenever the app's measurement SDK, attribution partner or store listing changes |
| Launching paid media | Insertion Order Sign-Off | Before a media insertion order or direct buy is signed, once the plan is agreed and the publisher's terms are on the table |
| Launching paid media | Offline Media Flight Launch | In the final days before a television, radio, print or outdoor flight starts, once the plan is signed and the insertion orders are placed, and again before each later burst |
| Launching paid media | Sponsored Placement Launch | After a sponsored article, a newsletter placement, a paid affiliate position or a podcast read has been agreed with a publisher, and before it is published or goes out |
| Launching paid media | Call and Message Campaign Launch | Before a campaign whose main response is a phone call or a message conversation goes live on any platform, and again whenever its hours, numbers or reply flow change |
| Commerce and promotions | Merchant Center Feed Setup | When a store first connects a product feed to Google Merchant Center, and after a replatform, a change of feed tool or a launch in a new country |
| Commerce and promotions | Meta Catalog Setup | When a store first connects a product catalog in Meta Commerce Manager, and before its first catalog ads campaign launches |
| Commerce and promotions | Sale Promotion Readiness | In the weeks before a planned sale or seasonal peak, and again on the day before prices change, with marketing, ecommerce and finance in the room |
| Tracking and data | GTM Container Publish | Every time a Google Tag Manager workspace is about to be published as a new container version, however small the change looks |
| Tracking and data | Consent Banner QA | Before a cookie consent banner or consent management platform goes live, and after any change to its wording, categories, vendors or tag configuration |
| Tracking and data | GA4 Property Handover | When a Google Analytics property changes hands: an agency leaves or arrives, the analyst who built it moves on, or the business is sold or merged |
| Tracking and data | Server-Side Tagging Go-Live | Before traffic moves from browser tags to a server-side Tag Manager container, and before each new server-side client or destination is switched on |
| Tracking and data | Dashboard Launch QA | Before a Looker Studio or other BI dashboard is shared with stakeholders for the first time, and after any change to its data sources or metric definitions |
| Tracking and data | Lead Routing QA | Before a new lead source, form or routing rule goes live, and after any change to CRM fields, territories or lead scoring |
| Tracking and data | Conversion Goal Change | Before changing which conversions an ad platform bids or optimises towards, their values or counting, or the attribution model and windows, once per platform |
| Tracking and data | AI-Written Code Review | Before tracking code, a spreadsheet formula, a calculated field, a query or structured data markup that an AI tool wrote is published, shared or used in a report |
| Tracking and data | CRM Sync Change | Before a sync or connector between the CRM and the marketing platform, a form tool or another system that writes contact records is switched on, reconnected or changed, including a new synced field, a new direction or a new matching rule |
| Tracking and data | Metric Definition Change | Once a change to how a reported marketing metric is defined has been decided and before any report or dashboard uses it: a new formula, filter, source, date rule or attribution rule, a lead, customer or lifecycle stage redefined, or a headline measure such as the north star replaced |
| Email and testing | Email Sending Domain Setup | When a business starts sending from a new domain or subdomain, moves to a new email platform, or adds another service that sends mail as the brand |
| Email and testing | Email Automation Flow Launch | Before an automated email flow such as a welcome series, abandoned cart reminder or nurture sequence is switched on, and after any change to its trigger or branches |
| Email and testing | A/B Test Launch | After a test is designed and built and before it is switched on for real visitors, with the designer, the developer and the analyst all available |
| Email and testing | Holdout Test Readiness | After a holdout, geo or lift test of a channel, a mailing or an automated flow has been designed and before the first day of the test, while the cells can still be redrawn |
| Messaging and customer service | Mobile Message Send QA | Before a marketing text, WhatsApp, push or in-app message is sent to a segment or switched on in a flow, and whenever its wording, audience, template or link changes |
| Messaging and customer service | Review Request Launch | Before a review request starts or changes, whether a post-purchase email, a text, an insert card, an app rating prompt or a request made in person, and before any incentive is attached to it |
| Messaging and customer service | AI Customer Service Launch | Before an AI assistant starts answering customers or an AI tool starts drafting replies for agents, and again before its scope, its content source or its model changes |
| Messaging and customer service | AI Automation Go-Live | Before a workflow step in which an AI model writes, chooses, classifies or acts without a person reading each output is switched on, and again before its prompt, model, vendor, sources or permissions change |
| Publishing and channels | Google Business Profile Setup | When a business location is first listed on Google, when a listing is claimed from a previous owner, or when a new location opens |
| Publishing and channels | App Store Listing | Before an app listing is submitted or updated in the App Store or Google Play, including any release that changes screenshots, text or pricing |
| Publishing and channels | YouTube Video Publishing | Before each YouTube video or Short is published or scheduled, with the final edit, the thumbnail and the text ready to review together |
| Publishing and channels | AI-Assisted Content Review | At the human review step, before any article, ad copy or email drafted with an AI tool is published or sent |
| Publishing and channels | Social Post Publishing | Before an organic social post is published or scheduled on any platform, especially a post that carries an offer, a claim or someone else's content |
| Publishing and channels | Influencer Campaign Launch | After creators are contracted and before their first posts go live, and again before any creator content is reused in paid ads |
| Publishing and channels | Press Release Distribution | Before a press release is sent to journalists or a distribution service and published in the online newsroom |
| Publishing and channels | Digital PR Data Story | Before a data-led story is offered to the first journalist or released under embargo, once the data is analysed and the asset page is built |
| Publishing and channels | Affiliate Programme Launch | Before an affiliate programme opens to partners, on a network or in-house, and when it moves to a new network or tracking platform |
| Publishing and channels | Co-Marketing Launch | Before a joint campaign with a partner business goes live, once the partner and the offer are chosen and both sides' material is ready for approval |
| Publishing and channels | New Market Launch | In the final weeks before marketing goes live in a new country or language, once the market has been chosen and the localised site is built |
| Publishing and channels | Competitor Comparison | Before anything that names a competitor or compares the business with one goes out: a versus or alternatives page, competitor-name search ads, a comparison video or a battlecard buyers may see |
| Publishing and channels | Employee Advocacy Launch | Before staff are first invited to post about the business's work on their own accounts, and before any of their posts is sponsored or an incentive is attached to posting |
| Research and events | Survey Launch | After a customer survey is written and before the first invitation goes to the sample, and again before each new wave of a repeated survey or brand tracker |
| Research and events | Research Session Readiness | In the days before the first session of a moderated study (customer interviews, a focus group, a usability test or the briefing call of a diary study), once recruits are confirmed |
| Research and events | Webinar Launch | Before registration opens for a webinar or online event, and again in the days before the session runs, with the host, the speakers and whoever owns the follow-up |
| Research and events | In-Person Event Readiness | In the final week before a trade show stand, a roundtable or a customer day the business exhibits at or hosts, once the stand or the room is booked |
| Agencies, reviews and money | Agency Onboarding | In the first weeks after a new agency is appointed, before it changes any live account or campaign |
| Agencies, reviews and money | Agency Offboarding | When an agency relationship is ending, from notice to the last day of access, and before the incoming team or agency takes over |
| Agencies, reviews and money | Monthly Paid Media Review | At the monthly paid media review, once the month's spend and conversions are closed, with search, social and programmatic reviewed side by side |
| Agencies, reviews and money | Marketing Budget Month-End Close | In the last days of each month and the first days of the next, when marketing spend is closed and reconciled with finance |
| Agencies, reviews and money | Campaign Wrap-Up | In the days after a campaign or flight ends, before the team moves on to the next brief and before results are presented |
| Agencies, reviews and money | Marketing Budget Cut | When marketing spend has to fall during a period, after the size of the cut is known and before any budget, target or campaign is changed in the accounts |
| Agencies, reviews and money | Affiliate Commission Change | After a change to affiliate commission rates, tiers, bonuses, the window, the validation period or the credit rule has been decided, and before it is announced to partners or entered in the platform |
Checklists and the guides behind them
Each checklist is the compressed form of one or more guides, and the links go both ways. The launch, email and landing-page lists sit on top of the planning guides, where the brief, the calendar and the budgeting method are explained; the checklist asks whether the brief was followed, not how to write one. The tracking and analytics lists sit on top of the measurement guides, which define the tracking plan, the naming and UTMURL tags identifying traffic source. conventions and the data-quality checks that the checklist items refer to in a few words. The technical SEO list is the companion to the technical SEO audit tutorial, which owns the method; the checklist is the thing to have open while following it. Where a checklist needs a document rather than a list, such as a brief to QA against or a plan to verify, the templates library holds the copyable version.
When an item fails, the checklist page says what to do and points to the guide that fixes it. That is the intended loop: the list finds the gap, the guide closes it, and the next run of the list confirms it stayed closed. For analytics work in particular, the GA4Google's event-based analytics platform. setup and tracking verification lists are meant to be run together whenever a property or a container changes hands, because a property that looks configured and a container that looks published can still disagree about which event counts.
