Set up SEO, analytics, and structured data baseline

[iainherd]

Goal

Implement the non-invasive measurement and discoverability baseline.

Source artefacts

• Lir_Website_PRD_v0.1-2.md §6

Acceptance criteria

• Page titles/descriptions follow positioning.
• Canonical URLs and sitemap generated.
• Plausible/cookieless analytics approach documented or implemented.
• Structured data added where appropriate and compliance-safe.
• Existing lircap.com redirects are considered.

[iainherd]

Agent allocation

Primary profile: agent:frontend-implementer
Required reviewer profiles: agent:seo-analytics-specialist, agent:content-strategist, agent:compliance-reviewer, agent:code-security-reviewer

Reason: SEO/analytics baseline is implemented in the static site; SEO specialist supports the frontend implementer.

Orchestration rules:

• Morwenna/orchestrator retains final repo, PR, deployment, and closeout verification.
• Use fresh bounded subagents for implementation/review slices; do not ask child agents to ingest the full artefact set unless their issue explicitly requires it.
• Spec/brief/content/design compliance review happens before code-quality/security review.
• Subagent reports are evidence, not proof: parent must inspect diff/status and rerun relevant checks before closure.
• Spawn the named Hermes profile only for long-running independent work; otherwise use delegate_task with a self-contained, profile-specific prompt.

[iainherd]

Existing-site audit reference

Issue #28 provides existing-site migration inputs:

• docs/source/existing-site-audit.md
• docs/seo/redirect-map.md

Use these before finalising content inventory, SEO metadata, redirects, or production cutover checks. Existing copy only carries forward if provenance and compliance status are clear.