Phase 9 · Growth & polish

# ZajLibrary — implementation playbook

You are a **senior implementation assistant** working inside the user’s real development environment (terminal, editor, git repo). You are **not** a documentation writer, tutor, or library editor.

**Mission:** Execute the procedure described below in the user’s real project workspace — create or modify the files and run the commands it specifies. Do not just summarize it.

## Metadata
- title: Phase 9 · Growth & polish
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/
- shelf: Build & Create
- doc_type: implementation playbook
- status: current
- kind: playbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- phase: 9
- est_time: 6–12 hr
- description: The pass that makes the product feel finished — SEO (sitemap, meta, schema, Search Console), onboarding/changelog/feedback/blog, and customer-facing chat + help center. Mostly SHOULD with many alternatives.
- tags: codecanyon, laravel, growth

## Execution rules (binding)
- Follow `## Steps` in order. Do not skip steps or declare the work complete early.
- Respect `:::note[Who does this]`: 👤 **User** steps (browser, downloads, OAuth, moving files) need the human — wait for or instruct them; 🤖 **Agent** steps you run in the shell.
- After every command, compare its output to the `# Expected:` comment or ✅ bullet beneath it. If it differs, **stop, show what you got, and ask how to proceed** — do not guess or rewrite the procedure.
- Honor `:::caution` / `:::note` callouts as hard gates (a step may forbid a command at this stage).
- Do not mark the step done until every `## Checklist` item is genuinely satisfied.
- Scope: implement only what this page describes — no refactors, added features, or later-phase work unless the page says so.
- When reporting progress, cite the `##` / `###` headings you completed or got blocked on.
- Secrets: never put API keys, passwords, or `.env` values in frontend code, commits, or chat logs — use server-side `.env` / config only, and keep `.env` gitignored.

---

# Phase 9 · Growth & polish

The difference between *functional* and *finished*. Three streams — discoverability, engagement, and support — each mostly SHOULD with several alternatives, so pick what fits the product and surface what you skip.

<StageFlow
  title="Phase 9 — three polish streams"
  caption="Gate is qualitative ('app is polished'). Do SEO first (it needs a live URL), then engagement and support layers."
  stages={[
    { label: 'SEO', sub: '9A', tone: 'core' },
    { label: 'Onboarding + blog', sub: '9B' },
    { label: 'Feedback', sub: '9B' },
    { label: 'Chat + help center', sub: '9C', tone: 'good' },
  ]}
/>

:::note[Gate]
**App is polished** — search-discoverable (valid sitemap, meta, schema, Search Console verified), an onboarding/changelog/feedback path exists, and customers have a way to get help (chat + knowledge base).
:::

Reaching that gate usually means picking among several tools per job:

:::tip[Alternatives are choices, not skips]
Most of Phase 9 offers multiple tools per job. Record which you picked (and why) in `_CUSTOMIZATIONS.md` so the decision is traceable later.
:::

## Pages in this phase

<CardGrid>
  <LinkCard title="1 · SEO (9A)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/01-seo/" description="Sitemap + robots, meta + schema + titles, Search Console + PageSpeed — do first, it needs a live URL." />
  <LinkCard title="2 · Engagement (9B)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/02-engagement/" description="Onboarding, changelog, feedback channel, and an optional blog." />
  <LinkCard title="3 · Support (9C)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/03-support/" description="Live chat widget + help center / knowledge base — pick one tool per row." />
</CardGrid>

Start with **[SEO](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/01-seo/)**.

---

> Three streams — SEO, onboarding/changelog/feedback/blog, and chat + help center. Per-tool alternative tables live in the reference set.

# Phase 9 · Growth & polish

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/

The difference between *functional* and *finished*. Three streams — discoverability, engagement, and support — each mostly SHOULD with several alternatives, so pick what fits the product and surface what you skip.

<StageFlow
  title="Phase 9 — three polish streams"
  caption="Gate is qualitative ('app is polished'). Do SEO first (it needs a live URL), then engagement and support layers."
  stages={[
    { label: 'SEO', sub: '9A', tone: 'core' },
    { label: 'Onboarding + blog', sub: '9B' },
    { label: 'Feedback', sub: '9B' },
    { label: 'Chat + help center', sub: '9C', tone: 'good' },
  ]}
/>

:::note[Gate]
**App is polished** — search-discoverable (valid sitemap, meta, schema, Search Console verified), an onboarding/changelog/feedback path exists, and customers have a way to get help (chat + knowledge base).
:::

Reaching that gate usually means picking among several tools per job:

:::tip[Alternatives are choices, not skips]
Most of Phase 9 offers multiple tools per job. Record which you picked (and why) in `_CUSTOMIZATIONS.md` so the decision is traceable later.
:::

## Pages in this phase

<CardGrid>
  <LinkCard title="1 · SEO (9A)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/01-seo/" description="Sitemap + robots, meta + schema + titles, Search Console + PageSpeed — do first, it needs a live URL." />
  <LinkCard title="2 · Engagement (9B)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/02-engagement/" description="Onboarding, changelog, feedback channel, and an optional blog." />
  <LinkCard title="3 · Support (9C)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/03-support/" description="Live chat widget + help center / knowledge base — pick one tool per row." />
</CardGrid>

Start with **[SEO](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/01-seo/)**.

---

> Three streams — SEO, onboarding/changelog/feedback/blog, and chat + help center. Per-tool alternative tables live in the reference set.

The difference between functional and finished. Three streams — discoverability, engagement, and support — each mostly SHOULD with several alternatives, so pick what fits the product and surface what you skip.

Phase 9 — three polish streams

Gate is qualitative ('app is polished'). Do SEO first (it needs a live URL), then engagement and support layers.

Reaching that gate usually means picking among several tools per job:

Pages in this phase

1 · SEO (9A) Sitemap + robots, meta + schema + titles, Search Console + PageSpeed — do first, it needs a live URL.

2 · Engagement (9B) Onboarding, changelog, feedback channel, and an optional blog.

3 · Support (9C) Live chat widget + help center / knowledge base — pick one tool per row.

Start with SEO.

Three streams — SEO, onboarding/changelog/feedback/blog, and chat + help center. Per-tool alternative tables live in the reference set.

# ZajLibrary — implementation playbook

You are a **senior implementation assistant** working inside the user’s real development environment (terminal, editor, git repo). You are **not** a documentation writer, tutor, or library editor.

**Mission:** Execute the procedure described below in the user’s real project workspace — create or modify the files and run the commands it specifies. Do not just summarize it.

## Metadata
- title: Phase 9 · Growth & polish
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/
- shelf: Build & Create
- doc_type: implementation playbook
- status: current
- kind: playbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- phase: 9
- est_time: 6–12 hr
- description: The pass that makes the product feel finished — SEO (sitemap, meta, schema, Search Console), onboarding/changelog/feedback/blog, and customer-facing chat + help center. Mostly SHOULD with many alternatives.
- tags: codecanyon, laravel, growth

## Execution rules (binding)
- Follow `## Steps` in order. Do not skip steps or declare the work complete early.
- Respect `:::note[Who does this]`: 👤 **User** steps (browser, downloads, OAuth, moving files) need the human — wait for or instruct them; 🤖 **Agent** steps you run in the shell.
- After every command, compare its output to the `# Expected:` comment or ✅ bullet beneath it. If it differs, **stop, show what you got, and ask how to proceed** — do not guess or rewrite the procedure.
- Honor `:::caution` / `:::note` callouts as hard gates (a step may forbid a command at this stage).
- Do not mark the step done until every `## Checklist` item is genuinely satisfied.
- Scope: implement only what this page describes — no refactors, added features, or later-phase work unless the page says so.
- When reporting progress, cite the `##` / `###` headings you completed or got blocked on.
- Secrets: never put API keys, passwords, or `.env` values in frontend code, commits, or chat logs — use server-side `.env` / config only, and keep `.env` gitignored.

---

# Phase 9 · Growth & polish

The difference between *functional* and *finished*. Three streams — discoverability, engagement, and support — each mostly SHOULD with several alternatives, so pick what fits the product and surface what you skip.

<StageFlow
  title="Phase 9 — three polish streams"
  caption="Gate is qualitative ('app is polished'). Do SEO first (it needs a live URL), then engagement and support layers."
  stages={[
    { label: 'SEO', sub: '9A', tone: 'core' },
    { label: 'Onboarding + blog', sub: '9B' },
    { label: 'Feedback', sub: '9B' },
    { label: 'Chat + help center', sub: '9C', tone: 'good' },
  ]}
/>

:::note[Gate]
**App is polished** — search-discoverable (valid sitemap, meta, schema, Search Console verified), an onboarding/changelog/feedback path exists, and customers have a way to get help (chat + knowledge base).
:::

Reaching that gate usually means picking among several tools per job:

:::tip[Alternatives are choices, not skips]
Most of Phase 9 offers multiple tools per job. Record which you picked (and why) in `_CUSTOMIZATIONS.md` so the decision is traceable later.
:::

## Pages in this phase

<CardGrid>
  <LinkCard title="1 · SEO (9A)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/01-seo/" description="Sitemap + robots, meta + schema + titles, Search Console + PageSpeed — do first, it needs a live URL." />
  <LinkCard title="2 · Engagement (9B)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/02-engagement/" description="Onboarding, changelog, feedback channel, and an optional blog." />
  <LinkCard title="3 · Support (9C)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/03-support/" description="Live chat widget + help center / knowledge base — pick one tool per row." />
</CardGrid>

Start with **[SEO](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/01-seo/)**.

---

> Three streams — SEO, onboarding/changelog/feedback/blog, and chat + help center. Per-tool alternative tables live in the reference set.

# Phase 9 · Growth & polish

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/

The difference between *functional* and *finished*. Three streams — discoverability, engagement, and support — each mostly SHOULD with several alternatives, so pick what fits the product and surface what you skip.

<StageFlow
  title="Phase 9 — three polish streams"
  caption="Gate is qualitative ('app is polished'). Do SEO first (it needs a live URL), then engagement and support layers."
  stages={[
    { label: 'SEO', sub: '9A', tone: 'core' },
    { label: 'Onboarding + blog', sub: '9B' },
    { label: 'Feedback', sub: '9B' },
    { label: 'Chat + help center', sub: '9C', tone: 'good' },
  ]}
/>

:::note[Gate]
**App is polished** — search-discoverable (valid sitemap, meta, schema, Search Console verified), an onboarding/changelog/feedback path exists, and customers have a way to get help (chat + knowledge base).
:::

Reaching that gate usually means picking among several tools per job:

:::tip[Alternatives are choices, not skips]
Most of Phase 9 offers multiple tools per job. Record which you picked (and why) in `_CUSTOMIZATIONS.md` so the decision is traceable later.
:::

## Pages in this phase

<CardGrid>
  <LinkCard title="1 · SEO (9A)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/01-seo/" description="Sitemap + robots, meta + schema + titles, Search Console + PageSpeed — do first, it needs a live URL." />
  <LinkCard title="2 · Engagement (9B)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/02-engagement/" description="Onboarding, changelog, feedback channel, and an optional blog." />
  <LinkCard title="3 · Support (9C)" href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/03-support/" description="Live chat widget + help center / knowledge base — pick one tool per row." />
</CardGrid>

Start with **[SEO](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/09-growth-polish/01-seo/)**.

---

> Three streams — SEO, onboarding/changelog/feedback/blog, and chat + help center. Per-tool alternative tables live in the reference set.