---
name: post-launch-optimisation
description: review post-launch website performance and optimisation opportunities for lightspeed projects using analytics summaries, ga4 notes, search console observations, seo findings, chatbot transcripts or summaries, content performance notes, conversion observations, heatmap findings, backlog items, and stakeholder priorities. use when the user asks for post-launch optimisation, ongoing improvement planning, CRO observations, content iteration priorities, chatbot tuning recommendations, retention or conversion improvements, analytics-led backlog creation, or a prioritised optimisation roadmap after launch.
---

# Post-launch Optimisation

## Overview

Use this skill when the website is already live and the work is about improving performance after launch.

This skill is for optimisation work such as:

- post-launch performance review
- analytics-led prioritisation
- CRO observations and improvement backlog
- content iteration recommendations
- chatbot tuning and transcript-driven improvements
- internal linking and discoverability improvements after real usage data appears
- conversion drop-off diagnosis from available evidence
- prioritised optimisation roadmaps for retainers or follow-up sprints

Use this skill when the user wants a practical improvement plan, not just raw analysis.

Do not use this skill as the primary workflow for:

- pre-launch QA or launch gating
- initial GA4 or GTM planning before launch
- pure technical SEO audits with no post-launch optimisation objective
- drafting entirely new website content from scratch

In those cases, coordinate with the more specific attached workflow instead.

## Typical Inputs

Use whatever evidence the user provides. Typical inputs include:

- GA4 summaries or key metrics
- Search Console observations
- landing-page or page-group performance notes
- conversion funnel notes
- chatbot transcripts, summaries, or issue patterns
- heatmap or session-recording summaries
- content-performance observations
- SEO issue lists or post-launch findings
- support, sales, or stakeholder feedback
- backlog items or sprint constraints

If evidence is incomplete, do not block unnecessarily. Produce the strongest optimisation view possible from available material and label assumptions clearly.

## Optimisation Workflow

1. Determine the optimisation context.
   - Is this a first post-launch review, a monthly optimisation cycle, a campaign landing-page review, a chatbot improvement review, or a broader retainer roadmap?
   - Identify the business goal: more leads, better qualified leads, higher engagement, better content discoverability, reduced drop-off, better chatbot outcomes, or stronger conversion paths.

2. Review the evidence set.
   - List the data or observations provided.
   - Distinguish measured performance from anecdotal feedback.
   - Note major blind spots that limit confidence.

3. Identify the relevant optimisation areas.
   - Traffic quality and landing-page performance
   - Conversion friction and CTA performance
   - Content clarity, coverage, and next-step guidance
   - FAQ and chatbot answer quality
   - SEO and discoverability follow-up improvements
   - Internal linking and user journey continuity
   - Page-speed or UX issues that materially affect outcomes
   - Measurement gaps that make iteration harder

4. Turn observations into actionable hypotheses.
   - What seems to be underperforming?
   - Why might that be happening?
   - What change is recommended?
   - What outcome should improve if the change works?

5. Prioritise the work.
   - High-impact quick wins
   - Strategic improvements
   - Longer-term experiments or monitoring items

6. Package the result into an optimisation roadmap.
   - Make it clear what to change first, who should own it, and how success should be checked.

## Optimisation Areas

### Conversion and CTA performance

Look for issues such as:

- strong traffic with weak enquiry or conversion rates
- unclear or overly weak calls to action
- CTA mismatch with visitor intent
- friction around forms, booking actions, downloads, or consultation requests
- missing next-step guidance on key commercial pages

### Content and messaging improvement

Look for issues such as:

- high-value pages with weak engagement or unclear messaging
- content gaps that block the user journey
- FAQ gaps exposed by real user behaviour
- service or solution pages that do not connect clearly to user needs
- pages that need more trust, proof, or clarity rather than more volume

Do not turn this into a full content-rewrite workflow unless the user asks for that next.

### Chatbot optimisation

When chatbot evidence is available, review:

- repeated unanswered or poorly answered questions
- weak escalation handling
- unclear source coverage
- overlong or unhelpful responses
- gaps between website messaging and chatbot behaviour
- opportunities to improve source content, FAQs, guardrails, or fallback wording

### Discoverability and SEO follow-up

When post-launch discoverability matters, review:

- pages not earning expected visibility
- internal-linking opportunities from live usage patterns
- thin or overlapping content that weakens discoverability
- metadata or snippet opportunities affecting click-through
- post-launch schema or search-presentation improvements

If the core need is a deeper technical SEO audit, coordinate with that specialised workflow separately.

### Measurement quality

Check whether optimisation is being limited by weak measurement, such as:

- unclear conversion definitions
- missing event tracking
- no clean segmentation for key journeys
- no baseline or success metric for planned changes
- insufficient chatbot handoff or lead-quality measurement

## Output Contract

Default to Markdown.

Use this structure unless the user asks for a lighter format:

### 1. Executive summary

- optimisation context
- main opportunity areas
- top 3 recommended next actions

### 2. Evidence reviewed

- source list
- confidence notes
- assumptions and missing data

### 3. Findings and opportunities

Use sections or a table with:

- Area
- Observation
- Likely cause
- Recommended improvement
- Expected impact
- Owner
- Priority

### 4. Prioritised roadmap

Group into:

- Quick wins
- Next sprint priorities
- Longer-term optimisation opportunities

### 5. Measurement and validation

For each priority change, say:

- what success should look like
- what should be measured
- when to review the outcome

### 6. Internal LightSpeed notes

Include:

- delivery risk
- likely specialist involvement needed
- whether the work is content-led, dev-led, SEO-led, CRO-led, analytics-led, or mixed
- suggested follow-on work for retainers or optimisation cycles

## Template alignment

When the agent has an attached stage-specific deliverable template pack, use its post-launch optimisation structure as the default outer shape for the final deliverable.

Keep this skill's evidence review, findings, roadmap, and measurement guidance, but package the result so it lands as:

- performance summary
- optimisation backlog
- recommended next step

Only use a different structure when the user explicitly asks for a lighter memo or a raw backlog.

## Decision Rules

- If evidence is weak, say so clearly. Do not overstate certainty.
- If a recommendation depends on missing analytics or transcript evidence, label it as a hypothesis.
- If the user asks for broad post-launch optimisation, balance quick wins with a sensible longer-term roadmap.
- If the request overlaps heavily with chatbot tuning, technical SEO, or full content rewriting, provide the post-launch optimisation layer and call out the adjacent specialised workflow that should follow.
- Prefer commercially useful improvements over generic website best-practice lists.

## LightSpeed Standards

Prioritise recommendations that are:

- practical for WordPress and block-theme delivery teams
- maintainable after launch
- measurable where possible
- understandable by project leads, marketers, developers, and content owners
- tied to business outcomes rather than vanity metrics alone

Prefer fix-ready or test-ready wording over abstract advice.

Good example:

- "The pricing page has strong entry traffic but weak progression to consultation requests. Add a clearer primary CTA above the fold, reduce competing CTA variants, and test one trust-focused proof block near the form. Review consultation CTR and form-start rate after two weeks."

Weak example:

- "Improve the pricing page experience."

---

*Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit!*