Skip to content
English
  • There are no suggestions because the search field is empty.

How do I perform Post-Launch QA?

Check a newly launched website for SEO and speed on its live domain, with Claude or by hand.

Post-Launch QA checks a client's website on its live domain after launch, so it is in good shape for search engines (SEO) and speed. It doesn't repeat the pre-launch Content & UX QA. Do it within a week of launch.

Before you start

  • The website is announced in #splash and launch admin is done (with /launch-admin, which needs access to the Creative team's buildouts repository (creative-team-assets), or by hand). Launch admin already sets up the BugHerd Website Live project, points the forms at the live thank-you page, submits the sitemap to Google Search Console and closes the website ticket.
  • Have the live URL, the HubSpot company and ticket, and the client's SEO Analysis sheet open.

Option A: With Claude

Use this when you have Claude. Copy the prompt below into Claude, fill in each source, and send it. Claude's report is your first pass: review it, then make the fixes (see Make the fixes). If Claude isn't available, use Option B.

I need a Post-Launch QA for this website, focused on SEO and speed. Don't change anything on the site or in any tool. Only check and report.

Sources (paste a link or the text after each):
1. Live website URL:
2. Staging link:
3. HubSpot company:
4. HubSpot website ticket:
5. SEO Analysis sheet (old URLs, redirects, meta titles and descriptions):
6. Handoff document (handoff.md):

What to check:
- Domain and canonical: the main address is the Digital Marketing URL on the HubSpot company (with or without www). Open these four addresses and give the status code and every redirect step for each: http://domain, http://www.domain, https://domain, https://www.domain. All four must end at the main address with one 301 redirect, and no chains or loops. Then confirm the canonical tag on every page, the sitemap URLs and the share link (og:url) all use the main address, with the same www choice and https.
- Indexing: the live site has no noindex tag, robots.txt allows crawling and links to the sitemap, and the sitemap lists the live pages.
- No leftovers: no BugHerd sidebar on the live site, and no links or images pointing to the staging or workers.dev address.
- Redirects: every old URL in the SEO Analysis sheet that should redirect goes to its target with a single 301.
- Crawl: no broken links or 404s. Every page has its meta title and description from the SEO sheet, one H1, and alt text on its images.
- Schema: the Dentist / LocalBusiness schema is valid and uses the practice's real name, address and phone.
- GTM: the container ID in the page source matches this client's GTM ID in HubSpot, on every page.
- Forms: list every form on the site (Booking, Do You Take My Insurance?, Reputation Management "How Did We Do?"). Each goes to the thank-you page. If the practice has online booking, the booking buttons use its booking link instead of a booking form.
- Typeform quizzes: every quiz in the company's Typeforms property is on its matching service page, in the brand colors.
- Lead emails: if you can open Basin and Typeform, confirm every Basin form and every Typeform quiz notifies the Email for leads on the HubSpot company. If you can't, say so.
- Speed: run Google PageSpeed Insights (https://pagespeed.web.dev) on mobile and desktop for the Home page, one service page and the Location page. Give the four scores (Performance, Accessibility, Best Practices, SEO) and the Core Web Vitals (LCP, CLS, INP) for each.

How to report:
1. A table of every check: Pass, Fail or Couldn't check, the page, and what you saw.
2. The PageSpeed scores in a table, page by page, mobile and desktop.
3. A list of fixes, most important first. For speed, name the cause (for example a 1.8 MB hero image, render-blocking fonts, a third-party widget) and the fix.
If you can't open something, say so. Never guess.

Always do these by hand:

  • In Google Search Console, inspect the Home page URL and click Request indexing. A week or two after launch, check the Pages report for errors.
  • Submit each form once, and check in Basin and Typeform that every form and quiz notifies the Email for leads on the HubSpot company (see Option B, Lead emails).
  • Open the site on your own phone.

Option B: Without Claude

Use this when Claude isn't available. Work through each part below.

SEO checks

  1. Domain and canonical: the main address is the Digital Marketing URL on the HubSpot company. It decides whether the site uses www or not.
    • Paste these four addresses into httpstatus.io: http://domain.com, http://www.domain.com, https://domain.com and https://www.domain.com. All four must end at the main address with one 301 redirect (the main address itself returns 200). Two or more steps is a redirect chain: report it.
    • View the Home page source and search for canonical. It must be the main address, with the same www choice and https. Check one service page the same way.
    • Open /sitemap.xml and confirm its URLs use the main address. Search the page source for og:url: it must match too.
    • If the Digital Marketing URL in HubSpot and the site disagree, ask the Creative Lead which is right before anything is changed.
  2. Indexing: view the Home page source and confirm there is no noindex. Open /robots.txt (it must allow crawling and list the sitemap) and /sitemap.xml (it must list the live pages).
  3. Leftovers: the BugHerd sidebar doesn't show on the live site, and nothing links to the staging or workers.dev address.
  4. Crawl with Screaming Frog: crawl the live site and check for 404s and broken links, missing or duplicate meta titles and descriptions, more than one H1, missing alt text, and canonical tags that don't use the main address. Compare titles and descriptions with the SEO Analysis sheet.
  5. Redirects: in Screaming Frog, switch to List mode, paste the old URLs from the SEO Analysis sheet that should redirect, and confirm each one returns a single 301 to its target.
  6. Schema: test the Home page in Google's Rich Results Test. The Dentist / LocalBusiness schema must be valid, with the practice's real name, address and phone.
  7. GTM: view the page source and search for GTM-. The container ID must match the client's GTM ID in HubSpot.
  8. Forms and leads: submit each form once and confirm it goes to the thank-you page. Check: Do You Take My Insurance?, Reputation Management ("How Did We Do?"), and the Booking form only if the practice has no online booking. With online booking, every Book button must open the practice's booking link.
  9. Lead emails: the practice's Email for leads on the HubSpot company is where every lead must go.
    • Basin: open the client's project (<Practice> - <HubSpot company ID>). Every website form's notification email matches the Email for leads, and your test submissions show up.
    • Typeform: open each of the client's quizzes, then Settings, then Follow-ups. The email notification goes to the Email for leads.
    • If the Email for leads is empty or a form sends somewhere else, ask the Onboarding Lead/Specialist for the right email before changing anything.
  10. Typeform quizzes: every quiz in the company's Typeforms property is on its matching service page and uses the brand colors. See How do I create a Typeform for new or existing clients? for which quizzes a client gets.
  11. Search Console: inspect the Home page URL and request indexing. A week or two later, check the Pages report for errors.

Speed: PageSpeed Insights (Lighthouse)

  1. Go to pagespeed.web.dev and test the Home page, one service page and the Location page, on mobile and desktop.
  2. Write down the four scores (Performance, Accessibility, Best Practices, SEO) for each page.
  3. Targets: 90+ on desktop and 80+ on mobile for Performance, and 90+ for Accessibility, Best Practices and SEO on both.
  4. Mobile is harder: PageSpeed tests it as a mid-range phone on a slow connection, so mobile scores below 80 are common. Treat 80 as the goal, not a blocker. If mobile stays below 80 after the usual fixes, record the score and what's holding it back (often third-party scripts such as tracking tags or review widgets) in the wrap-up note.
  5. Below target, open Diagnostics and Opportunities to see what's slowing the page down.

The usual causes on our sites, and their fixes:

  • Large images: compress them, use WebP or AVIF, and size them for where they show. Give every image a width and height.
  • Hero image loads late (slow LCP): don't lazy-load the hero image. Lazy-load everything below the fold instead.
  • Fonts: load only the weights the site uses, and use font-display: swap.
  • Third-party embeds (review widgets, videos, Typeform, maps, chat): load them only when they come into view, or show a preview image until clicked.
  • Layout shift (CLS): reserve space for images, embeds and banners so the page doesn't jump while loading.

Make the fixes

  • The Creative Lead decides which fixes are worth making, and either makes them or reassigns them.
  • To reassign fixes to the Web Designer, the Creative Lead:
    • Leaves a comment for each fix in the client's BugHerd Website Live project (on the staging link), on the page where it applies.
    • Creates a HubSpot task on the website ticket, assigned to the Web Designer, titled POST LAUNCH Edits - <Practice>, with the BugHerd link and a due date.
  • Fixes are made in the client's repository: commit on development, check the staging link, then merge to main. A push to main updates the live site.
  • After the fixes, run PageSpeed again on the same pages and re-check anything that failed.

Wrap up

  1. Add a note to the HubSpot website ticket and company: the PageSpeed scores before and after (page, mobile, desktop), what was fixed, and anything left on purpose.
  2. Add anything still open to the handoff document, saying who it's for. If the Email for leads or a GTM container is missing, ask the Onboarding Lead/Specialist for it.
  3. Mark your Post-Launch QA task as done in Monday.