> ## Documentation Index
> Fetch the complete documentation index at: https://help-empuls.xoxoday.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Seo audit report 2026 07 13 to 2026 07 20

# SEO Audit Report — Empuls Help Center

**Scope:** Pages changed between 2026-07-13 and 2026-07-20 that are present in `docs.json` and not under a locale subdirectory (`es/`, `fr/`, `zh/`).
**Base URL:** `https://help-empuls.xoxoday.com`
**Criteria:** 10 sub-scores (0–10 each) → Overall /100. Priority: Critical 0–40 · High 41–60 · Medium 61–80 · Low 81–100.

## Summary

| Page                                         | Score | Priority |
| -------------------------------------------- | ----: | -------- |
| `home.mdx`                                   |    61 | Medium   |
| `admin/integrations/collaboration/slack.mdx` |    82 | Low      |
| `demo-library/demo-library.mdx`              |    74 | Medium   |
| `demo-library/compass-overview.mdx`          |    66 | Medium   |
| `demo-library/compass-data-integrations.mdx` |    60 | High     |
| `demo-library/compass-plans-metrics.mdx`     |    62 | Medium   |
| `demo-library/compass-groups-reports.mdx`    |    61 | Medium   |
| `demo-library/compass-admin-walkthrough.mdx` |    71 | Medium   |
| `demo-library/compass-user-walkthrough.mdx`  |    63 | Medium   |

**Sub-score legend:** T1 Title · T2 Description · T3 H1 · T4 H2 · T5 Internal links · T6 Schema · T7 FAQ · T8 Intent · T9 Depth · T10 Images.

***

## `home.mdx` — 61 / 100 · Medium

| T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 |
| -: | -: | -: | -: | -: | -: | -: | -: | -: | --: |
|  4 |  5 |  3 |  4 |  5 |  8 |  5 |  9 |  9 |   9 |

**Issues found**

* **Title too short (21 chars):** `Xoxoday Documentation` is well under the 50–60 char sweet spot and misses high-intent terms (Empuls, Plum, Loyalife, help center, guides).
* **Description under-length (94 chars):** target is 130–160; misses secondary keywords ("admin", "employees", "rewards", "recognition", "surveys").
* **No rendered H1 in Markdown:** the page uses `mode: "custom"` with a styled `<h1>` inside a `<div>`. That element is styled inline (`fontSize: '2.7rem'`) but it *is* an `<h1>` tag — good for SEO. Sub-scoring 3/10 because there is no fallback semantic heading if the inline styles fail, and the `h1` text ("Xoxoday's product suite") does not match the frontmatter `title`.
* **Internal links use hardcoded absolute URLs** (e.g. `href="https://help-empuls.xoxoday.com/admin/programs/awards-core-values"`) instead of root-relative paths. This breaks previews and cross-deployment portability and is the single biggest SEO/UX issue on this page.
* **No `<h2>` markdown headings** — all section titles are inline-styled `<h2>` JSX. They still render as `<h2>` but the audit tools cannot verify hierarchy; scan-ability is fine visually but there is no textual outline for search engines relying on the raw MDX.
* **No images with alt text** were flagged, but the two `<img>` logo tags (`xoxoday.svg`, `xoxoday_white.svg`) share the same alt `Xoxoday` — redundant when both render.
* **Schema:** eligible for `WebSite` + `ItemList` (product cards) and `SiteNavigationElement` (footer). Not currently emitted.
* **FAQ coverage:** none. Common queries ("How do I log in to Empuls?", "What is Xoxoday?", "Difference between Empuls, Plum, and Loyalife?") are not answered on this landing page.

**Action plan (highest impact first)**

1. **Convert every in-repo `href` from `https://help-empuls.xoxoday.com/...` to root-relative** (`/admin/programs/awards-core-values`, `/demo-library/demo-library`, `/employees/getting-started/log-in`, `/product-updates/june-2026`). Keep external `help-plum` and `help-loyalife` links absolute.
2. **Rewrite the frontmatter title** to 50–60 chars, e.g. `"Xoxoday Help Center — Empuls, Plum & Loyalife guides"` (52 chars).
3. **Expand the description** to 140–155 chars: `"Documentation, admin guides, employee walkthroughs, and API references for Xoxoday's Empuls, Plum, and Loyalife products — all in one place."` (147).
4. **Add a small text-only "Popular topics" block** below the hero listing 4–6 root-relative links; this feeds internal PageRank to top pages.
5. **De-duplicate logo alt text** — set `alt=""` on the second (theme-swap) logo, or give the dark variant a distinct alt (`Xoxoday logo (dark theme)`).
6. Add a lightweight FAQ block near the footer answering the 3 questions listed above; wraps this page into `FAQPage` schema eligibility.

***

## `admin/integrations/collaboration/slack.mdx` — 82 / 100 · Low

| T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 |
| -: | -: | -: | -: | -: | -: | -: | -: | -: | --: |
|  3 |  8 |  8 |  9 |  7 |  9 |  8 | 10 | 10 |  10 |

**Issues found**

* **Title is a single word: `"Slack"`** (5 chars). This is far below the 50–60 char target and misses high-intent modifiers ("integration", "Empuls", "setup", "install"). Real-world search queries: *"empuls slack integration"*, *"how to install empuls in slack"*, *"empuls slack app setup"*.
* **Description (106 chars):** on-brand but under-length; missing "install", "setup", "app directory", or "bot".
* **No frontmatter-level canonical**; page uses `keywords: ["Slack Integration by Xoxoday"]` which is fine but redundant with title improvements.
* **Internal linking:** the intro links out to `slack.com/apps/...` but does not cross-link to other Empuls integration pages (Microsoft Teams, Google Chat) or to the setup prerequisites page.
* **H2 hierarchy:** logical (5 `##`); one bolded "1./2./3." list could be promoted to `<h3>` for scannability.
* **Images:** all 23 images have descriptive alt text under 125 chars. Filenames (`image1.png`…`image17.png`) are non-descriptive — hurts image search.

**Action plan (highest impact first)**

1. **Rewrite title** to `"Slack integration for Empuls — install & setup guide"` (52 chars).
2. **Expand description** to \~150 chars: `"Install the Empuls app in Slack to run recognition, rewards, surveys, and announcements from your workspace. Step-by-step setup guide."` (137).
3. **Add 2–3 contextual internal links** in the "Why this integration?" intro to `/admin/integrations/collaboration/microsoft-teams` and `/employees/social-intranet/overview` (or nearest equivalents).
4. **Rename image files** on the next content pass — batch `image1.png` → `slack-apps-sidebar.png`, `image7.png` → `add-to-slack-button.png`, etc. Non-blocking for this audit (per instructions, do not modify content).
5. **Promote the bold-numbered list** ("1. Create opportunities for feedback"…) to real `###` subheadings so each capability becomes a jumpable anchor.

***

## `demo-library/demo-library.mdx` — 74 / 100 · Medium

| T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 |
| -: | -: | -: | -: | -: | -: | -: | -: | -: | --: |
|  6 |  6 |  6 |  9 | 10 |  8 |  5 | 10 |  9 |   5 |

**Issues found**

* **Title (18 chars):** `Demo Video Library` is short; misses "Empuls" brand keyword and "walkthroughs / tutorials" long-tail terms.
* **Description (77 chars):** under 130; could include the product surface areas covered ("recognition, rewards, surveys, analytics, admin, integrations").
* **No H1** at Markdown level (relies on frontmatter title rendering).
* **H2 hierarchy is strong** (12 sections — Recognition, Rewards, Redemptions, etc.).
* **Internal links (30+ root-relative)** — excellent internal linking hub.
* **No `alt` text on iframes.** iFrames don't take `alt`, but each `<iframe>` lacks a descriptive `title` attribute in some sections — search engines increasingly index iframe `title`.
* **Images (0):** page is entirely video-driven; no still images. Not penalised heavily but reduces image search surface.
* **FAQ coverage:** none. Common queries ("How do I recognise a peer on Empuls?", "How do I redeem points?") link out but aren't answered on the hub itself.

**Action plan (highest impact first)**

1. **Rewrite title** to `"Empuls demo video library — feature walkthroughs"` (48 chars) or `"Empuls product demo videos — step-by-step walkthroughs"` (55).
2. **Expand description** to \~145 chars: `"Watch step-by-step Empuls demo videos on recognition, rewards, surveys, analytics, integrations, and admin — with linked written walkthroughs."` (142).
3. **Add `title` attribute to every `<iframe>`** matching the caption (e.g. `title="Recognise your peers and team members — Empuls demo"`).
4. **Add a short intro paragraph per section** (2 lines) describing what's inside — improves depth and lets search engines snippet the section.
5. **Emit `VideoObject` + `ItemList` schema** in a `Head` block. Video schema is the single largest SERP win for this page.

***

## `demo-library/compass-overview.mdx` — 66 / 100 · Medium

| T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 |
| -: | -: | -: | -: | -: | -: | -: | -: | -: | --: |
|  8 |  7 |  5 |  6 |  2 |  8 |  5 |  9 |  8 |   8 |

**Issues found**

* **Title (53 chars):** in range. Slight cleanup: em-dash + long-tail is fine but "Overview" is generic.
* **Description (108 chars):** just under; could include "no-code", "commission automation", "sales incentives".
* **No H1;** only two `##` (Admin console, Mobile app). Depth OK for an overview.
* **No internal links** — this is the biggest issue. The overview does not link to the deeper Compass walkthroughs (`compass-data-integrations`, `compass-plans-metrics`, `compass-groups-reports`, `compass-admin-walkthrough`, `compass-user-walkthrough`) that exist as siblings in `docs.json`.
* **iframe** has a `title` attribute (good).
* **FAQ coverage:** basic ("What is Compass?" is answered in one paragraph). Common queries ("How does Compass compare to spreadsheets?", "Does Compass integrate with Salesforce/HubSpot?") not addressed.
* **Schema:** eligible for `VideoObject` + `TechArticle`.

**Action plan (highest impact first)**

1. **Add a "Related walkthroughs" section** at the bottom linking to the five sibling Compass pages with descriptive anchors ("Set up user data and integrations", "Create metrics and plans", "Groups, reports & escalations", "Complete admin walkthrough", "End user walkthrough"). Biggest single lift.
2. **Rewrite title** to something less generic, e.g. `"Xoxoday Compass overview — admin & end user tour"` (49 chars).
3. **Expand description** to \~145 chars mentioning "no-code commission automation, sales incentives, and analytics".
4. **Add a short FAQ** at the bottom answering: "What is Xoxoday Compass?", "Who uses Compass?", "Does it integrate with our CRM?".
5. Emit `VideoObject` schema for the embedded YouTube video (`SN2qu5Ujzpc`).

***

## `demo-library/compass-data-integrations.mdx` — 60 / 100 · High

| T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 |
| -: | -: | -: | -: | -: | -: | -: | -: | -: | --: |
|  6 |  8 |  5 |  4 |  2 |  8 |  4 |  9 |  6 |   8 |

**Issues found**

* **Title (39 chars):** short and slightly ambiguous. Missing "Compass" brand and product context. Real search queries: *"compass upload sales data"*, *"compass CRM integration"*, *"compass CSV import"*.
* **Description (123 chars):** near range.
* **Only 1 `## Steps` heading** — the entire body is inside a single `<Steps>` component. This produces a flat, thin heading outline.
* **No internal links to prerequisites or next-step pages.** Should link back to `compass-overview` and forward to `compass-plans-metrics` (the next natural step per the video's own copy: "Building on the connection created for Carol…" — that continuity is invisible to search engines and to users who land here directly).
* **Depth:** 447 words — below the 300 threshold when you exclude the video embed, but reference-style step lists are borderline acceptable. Adding a "Prerequisites" and "Next step" section would push this over.
* **FAQ coverage:** none.

**Action plan (highest impact first)**

1. **Add navigational links:** a "Prerequisites → [Compass overview](/demo-library/compass-overview)" line at the top, and a "Next → [Create metrics and plans](/demo-library/compass-plans-metrics)" line at the bottom. This fixes both internal-link and continuity issues in one shot.
2. **Rewrite title** to `"Compass user data, integrations & connections setup"` (52 chars).
3. **Break the single `<Steps>` block** into 2–3 `##` sections ("Upload user data", "Add integrations", "Create connections") each with its own `<Steps>`. Improves scannability and adds real H2 outline.
4. **Add a short FAQ** answering: "Do I have to upload data via CSV?", "What integrations does Compass support out of the box?".
5. Emit `HowTo` schema for the step list.

***

## `demo-library/compass-plans-metrics.mdx` — 62 / 100 · Medium

| T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 |
| -: | -: | -: | -: | -: | -: | -: | -: | -: | --: |
|  6 |  8 |  5 |  6 |  2 |  9 |  4 |  9 |  6 |   7 |

**Issues found**

* **Title (43 chars):** clear but missing "Compass" brand.
* **Description (114 chars):** under 130.
* **3 `##` sections** — good rhythm (Create a metric, Create a plan, Publish).
* **Zero internal links.** Should reference `compass-data-integrations` (prerequisite) and `compass-groups-reports` or `compass-admin-walkthrough` (next).
* **Depth (533 words):** acceptable for a video-anchored walkthrough.
* **FAQ:** none. Common query: *"What's the difference between an aggregate and a linear metric?"* is *almost* answered inline but not in FAQ form for rich snippets.

**Action plan (highest impact first)**

1. **Add prereq + next-step links** at top and bottom to sibling Compass pages.
2. **Retitle** to `"Create Compass metrics and milestone plans — guide"` (52 chars).
3. **Expand description** to \~145 chars including "milestone plan", "aggregate metric", "rewards".
4. **Add a `## FAQ` section** with 2–3 Q\&As ("Aggregate vs linear metric?", "Can a plan use multiple metrics?"). Enables `FAQPage` schema.
5. Emit `HowTo` schema wrapping the two `<Steps>` blocks.

***

## `demo-library/compass-groups-reports.mdx` — 61 / 100 · Medium

| T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 |
| -: | -: | -: | -: | -: | -: | -: | -: | -: | --: |
|  6 |  8 |  5 |  6 |  2 |  8 |  4 |  9 |  6 |   7 |

**Issues found**

* **Title (31 chars):** clear but generic; missing "Compass".
* **Description (123 chars):** just under range.
* **3 `##` sections** (Groups, Reports, Escalations) — clean.
* **No internal links** to sibling Compass docs.
* **Depth (405 words):** on the thin side.
* **FAQ:** none. Common query: *"How do I escalate a commission issue in Compass?"*, *"Can groups be private?"* are not surfaced.

**Action plan (highest impact first)**

1. **Add cross-links** to `/demo-library/compass-admin-walkthrough` (parent) and `/demo-library/compass-user-walkthrough` (where end users see groups/escalations).
2. **Retitle** to `"Compass groups, reports & escalations walkthrough"` (49 chars).
3. **Expand description** to 145 chars.
4. **Add a `## FAQ` block** answering the two questions above.
5. Consider merging with `compass-admin-walkthrough` sections that already cover the same modules to avoid keyword cannibalisation — or add a `canonical` back to the admin walkthrough.

***

## `demo-library/compass-admin-walkthrough.mdx` — 71 / 100 · Medium

| T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 |
| -: | -: | -: | -: | -: | -: | -: | -: | -: | --: |
|  6 |  9 |  5 |  9 |  2 |  9 |  6 | 10 |  9 |   6 |

**Issues found**

* **Title (42 chars):** OK but "Complete admin walkthrough — all modules" is vague without the "Compass" brand — will lose to duplicate titles across product docs.
* **Description (129 chars):** at the edge of range, well-written.
* **10 `##` sections** — best outline of the batch.
* **Depth (1,512 words):** strong.
* **No H1** at Markdown level.
* **No internal links** to the sibling per-module deep-dives (`compass-data-integrations`, `compass-plans-metrics`, `compass-groups-reports`), even though the sections mirror them exactly. **Big missed opportunity for topical clustering** — each `##` should link to the deeper page.
* **Duplicate content risk** with `compass-groups-reports` and `compass-data-integrations` (same module descriptions in different words).
* **FAQ:** none.

**Action plan (highest impact first)**

1. **Turn each `##` section title into a hub link** — under each section header, add a one-liner: "See the focused walkthrough: [User data, integrations & connections](/demo-library/compass-data-integrations)". This resolves the internal-link gap *and* the duplicate-content risk in one edit.
2. **Retitle** to `"Xoxoday Compass — complete admin walkthrough"` (46 chars) so it's brand-anchored.
3. **Add an anchor ToC** near the top listing all 10 sections as jump links — improves SERP sitelink eligibility.
4. **Add a `## FAQ` section** at the end with 3–4 real questions ("Do I need an admin license?", "How long does setup take?", "Can I preview a plan before publishing?").
5. Emit `HowTo` schema (multi-step) — this page is the strongest candidate for it.

***

## `demo-library/compass-user-walkthrough.mdx` — 63 / 100 · Medium

| T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 |
| -: | -: | -: | -: | -: | -: | -: | -: | -: | --: |
|  6 |  8 |  5 |  5 |  2 |  8 |  4 |  9 |  8 |   8 |

**Issues found**

* **Title (29 chars):** too generic; missing "Compass" brand — will collide with any other product's "end user walkthrough" page.
* **Description (128 chars):** near range.
* **2 `##` sections** (Web app, Mobile app) — under-structured for a 577-word page.
* **No internal links** to `compass-admin-walkthrough` (which references the same UI) or `compass-overview`.
* **Depth (577 words):** OK.
* **FAQ:** none. Common query: *"How do I check my Compass earnings?"*, *"How do I raise an escalation?"* — both covered in the body but not FAQ-formatted.

**Action plan (highest impact first)**

1. **Retitle** to `"Xoxoday Compass end-user walkthrough — web & mobile"` (52 chars).
2. **Add a "Related" block** linking to `compass-overview` and `compass-admin-walkthrough`.
3. **Add `###` sub-sections** inside "Web app" (Dashboard, Leaderboards, Widgets, Earnings, Escalations) so the outline matches the depth.
4. **Add a FAQ block** with 3 questions.
5. Emit `VideoObject` + `HowTo` schema.

***

## Cross-cutting recommendations

1. **Replace hardcoded `https://help-empuls.xoxoday.com/...` links in `home.mdx`** with root-relative paths. Every occurrence of an in-repo link with the full domain is a portability and preview-breakage risk.
2. **Establish a Compass topic cluster:** `compass-overview` acts as the pillar page and cross-links down to five spoke pages; each spoke links back up to `compass-overview` and sideways to its predecessor/successor page. Currently the cluster has **zero** internal edges between siblings — the single biggest content-graph win in this batch.
3. **Standardise Compass titles** to always start with the brand — `"Xoxoday Compass — <topic>"` — to prevent title collisions in SERPs and internal search.
4. **Add short FAQ sections** (3 Q\&As) to each Compass page to unlock `FAQPage` structured data.
5. **Add `VideoObject` schema** for every embedded YouTube / Trupeer video across `demo-library/*` — highest-leverage schema opportunity in the audited set.