Skip to main content

​
SEO audit report — Empuls Help Center

Scope: MDX pages modified between 2026-07-20 and 2026-07-27 that are referenced in docs.json (locale mirrors under es/, fr/, zh/ excluded; no pages have hidden: true). Base URL for canonicals: https://help-empuls.xoxoday.com Scoring: each criterion scored 0–10; Overall = sum ×1 (out of 100). Priority bands: Critical 0–40 · High 41–60 · Medium 61–80 · Low 81–100.

​
Summary

All four pages are in-scope, well-structured, and content-rich, but every one of them loses points on title length, cross-linking to other Help Center pages, and image filenames that are indexable keywords. Fixing those three levers first is the highest-leverage move across the batch.

​
admin/integrations/collaboration/slack.mdx

Canonical: https://help-empuls.xoxoday.com/admin/integrations/collaboration/slack

​
Issues

  • Title (5 chars): "Slack" is a single boilerplate word. It is well below the 50–60 char target, does not include the product name, and will be outranked by Slack.com and the Slack App Directory listing for any Empuls-related query.
  • Description (105 chars): on-topic but ~25 chars short of the sweet spot; misses high-intent keywords (“integration”, “install”, “setup”).
  • Internal linking: the only outbound links are to slack.com/apps/… (external). No contextual links to related in-repo pages such as /employees/recognitions/appreciate-colleagues, /employees/redemption/redeem-points, /admin/integrations/collaboration/microsoft-teams-usage, or /admin/rewards-recognition/…. Fails the “at least 2 contextual internal links” bar.
  • H1: none in the body; Mintlify renders the frontmatter title as the H1. Fine — but because the title is one word, the rendered H1 is one word. Combined with the “Slack” title issue, this weakens on-page topical signal for search.
  • H2 structure: clean and scannable (“Why this integration?”, “With this integration, you can”, “How to set up…”, “Empuls in Slack”, “How to remove…”, “FAQs”). Minor nit: ## With this integration, you can reads as a sentence fragment and could be ## What you can do with the Empuls app for Slack.
  • Schema: strong candidate for HowTo (Steps blocks for install and removal) + FAQPage (AccordionGroup) + BreadcrumbList. Not currently emitted.
  • FAQ coverage: 7 FAQs cover most real user questions. Missing common queries: “Is the Empuls Slack app free?”, “Which Slack plans does Empuls support?”, “Can I limit which channels Empuls posts to?”, “Is data shared with Empuls encrypted / SOC 2 compliant?”.
  • Content depth: excellent — 27 screenshots, step-by-step install/remove, feature walk-through, FAQs. Easily the deepest page in the batch.
  • Image optimization: alt text is descriptive and under 125 chars everywhere — good. Filenames are generic and sequential (slack-guide-01-hero.png … slack-guide-27-remove-cross.png) rather than keyword-rich (empuls-slack-integration-hero.png, empuls-slack-recognize-award.png, …). This is the single biggest image-SEO miss on the page.

​
Action plan (highest-impact first)

  1. Rewrite the title to a 50–60 char, keyword-rich string. Suggested: Slack integration for Empuls: set up recognition and rewards (60 chars). This alone should move criterion #1 from 3 → 9.
  2. Add 3–5 contextual internal links in the prose (not just the FAQ) — e.g. link “recognition” to /employees/recognitions/appreciate-colleagues, “redeem points” to /employees/redemption/redeem-points, “surveys” to /admin/surveys/…, and cross-link the sibling /admin/integrations/collaboration/microsoft-teams-usage. Moves #5 from 3 → 8.
  3. Rename image files to keyword-descriptive slugs before publication (e.g. empuls-slack-home-tab.png, empuls-slack-recognize-award.png). Moves #10 from 3 → 8.
  4. Extend the meta description to 140–160 chars and include “install”, “setup”, and “Empuls for Slack”: Install the Empuls app for Slack to run recognition, rewards, surveys, and redemption from inside your Slack workspace — setup guide and admin controls. (155 chars).
  5. Add 2–3 FAQs on plan compatibility, channel restrictions, and data security. Moves #7 from 8 → 10.
  6. Rename ## With this integration, you can to a full noun-phrase H2 (e.g. ## What you can do with Empuls in Slack) for better snippet extraction.
  7. Emit JSON-LD for HowTo (install + remove flows) and FAQPage via a layout include or Mintlify snippet, once schema tooling is in place.

​
admin/integrations/collaboration/microsoft-teams-usage.mdx

Canonical: https://help-empuls.xoxoday.com/admin/integrations/collaboration/microsoft-teams-usage

​
Issues

  • Title (44 chars): "Microsoft Teams: how to use the Empuls app" is descriptive and includes the product name, but is 6–16 chars short of the 50–60 sweet spot and buries “Empuls” at the end. Search results truncate the last 10–15 chars less usefully here.
  • Description (155 chars): on target — length, keyword coverage (“recognition, rewards, surveys, social intranet”), and USP (“in the flow of work”) are all present.
  • H2 structure: the section headings are numbered inside the H2 text — ## 1. Overview — Empuls, inside Microsoft Teams, ## 2. Why the Teams integration, etc. Search engines and screen readers treat the numeric prefix as noise, and it hurts snippet cleanliness. The remaining hierarchy (H2 → bolded pseudo-headings for sub-sections) also skips H3 in places; Home tab, Chat tab, and Inside channels and chats (message extension) are proper H3s (good), but nested items like **Hero banner and points overview**, **Feeds**, **Recommendations** should be H4s for scanability and section anchors.
  • Internal linking: links out to teams.microsoft.com, admin.teams.microsoft.com, xoxoday.com/empuls/demo, and xoxoday.com/empuls/case-studies/…. Zero in-repo cross-links. Sibling /admin/integrations/collaboration/slack and features like /employees/recognitions/appreciate-colleagues, /employees/redemption/redeem-points, /admin/surveys/… are natural targets.
  • External vs canonical links: https://www.xoxoday.com/empuls/demo and https://www.xoxoday.com/empuls are external marketing pages — that is correct usage. But the “MS Teams Integrations case study” is a marketing URL rather than a Help Center article; if a Help Center summary exists it should be linked in addition.
  • H1: Mintlify renders the frontmatter title as the H1. Because the body opens with a bold pseudo-heading **Recognition and rewards, inside Microsoft Teams.**, there’s a risk this reads like a second-H1 to some parsers — it is not one, but consider rephrasing as a lead sentence rather than a bolded standalone line.
  • Schema: excellent candidate for HowTo (multiple Steps blocks — install for all employees, install on channels, admin messages, sync profile pic, import users) and FAQPage (10 accordions).
  • FAQ coverage: 10 FAQs cover admin approval, permissions, SSO, uninstall, cost, mobile — very complete. Missing: “Which Teams plans (Enterprise, Business, Education) does Empuls support?” and “How is user data mapped between Teams and Empuls (Azure AD sync details)?”.
  • Content depth: deepest page in the batch — 28 images, admin + employee flows, permissions table, reports section.
  • Image optimization: alt text is descriptive and within limits. Filenames are again generic sequential (microsoft-teams-guide-01.png … -28.png) with no keywords. microsoft-teams-guide-01.png is also reused for two distinct screenshots (“Home tab hero banner” and the “Elevate & Celebrate banner”), which is the more serious problem — duplicate image URL for different visuals hurts both image search and accessibility diffing.

​
Action plan (highest-impact first)

  1. Rename the file’s images to keyword-rich slugs and split the duplicated microsoft-teams-guide-01.png into two distinct assets (empuls-teams-home-tab-elevate-banner.png and empuls-teams-home-tab-points-overview.png). Moves #10 from 3 → 8.
  2. Add 4–6 in-prose internal links to /admin/integrations/collaboration/slack, /employees/recognitions/appreciate-colleagues, /employees/redemption/redeem-points, /admin/surveys/…, /admin/reports/redemption-point-source. Moves #5 from 3 → 8.
  3. Drop the numeric prefixes on H2s (## Overview, ## Why the Teams integration, ## What you can do inside Teams, ## Admin setup and controls, ## FAQs) and promote the bolded pseudo-headings inside the Home tab and Chat tab sections to real H3/H4s so the outline is H2 → H3 (Home tab) → H4 (Hero banner …). Moves #4 from 6 → 9.
  4. Extend the title to 55–60 chars. Suggested: Empuls for Microsoft Teams: recognition, rewards, and surveys (60 chars). Moves #1 from 7 → 9.
  5. Add 2 FAQs on Teams plan compatibility and Azure AD / user data mapping. Moves #7 from 9 → 10.
  6. Emit HowTo + FAQPage JSON-LD once schema tooling is in place.
  7. Replace the opening bolded standalone line with a plain lead sentence so no parser mistakes it for a second H1.

​
admin/integrations/hrms/adp.mdx

Canonical: https://help-empuls.xoxoday.com/admin/integrations/hrms/adp

​
Issues

  • Title (3 chars): "ADP" is worst-in-class. It is boilerplate, does not include “Empuls”, “integration”, or “HRMS”, and will not rank for any commercially relevant query — the ADP company page will dominate for the bare acronym.
  • Description (125 chars): on-topic and keyword-rich (“onboarding, profile updates, offboarding, directory synchronized”) but 5–35 chars short of the 130–160 target.
  • H2 structure: clean and complete (“Before you begin”, “About this integration”, “Supported employee data”, “Set up the integration”, “Employee lifecycle automation”, “Best practices”, “Troubleshooting”, “FAQs”, “Related resources”, “Need help?”). One of the better-structured pages in the batch.
  • Internal linking: all outbound links are external (apps.adp.com, xoxoday.com/integrations/adp, mailto:cs@xoxoday.com). Zero internal cross-links. Natural in-repo targets: sibling HRMS integrations (/admin/integrations/hrms/…), user management pages, and /admin/user-management/… if it exists.
  • Schema: strong HowTo candidate (8-step setup) + FAQPage (5 FAQs) + TechArticle.
  • FAQ coverage: 5 FAQs cover sync cadence, field choice, offboarding, scheduling, and re-mapping. Missing common queries: “Does Empuls support ADP Workforce Now vs RUN vs Vantage?”, “What happens if an ADP field is empty?”, “Can I run a manual sync between the daily runs?”, “How is employee data secured in transit?”.
  • Content depth: solid — data-field list, lifecycle explanation, best practices, troubleshooting. Could benefit from an example of a mapping table or a sync-cycle diagram.
  • Image optimization: alt text is descriptive. Filenames (adp-1-marketplace.png … adp-6-schedule-sync.png) are sequential — better than pure numeric, but still don’t carry the keyword “empuls” or “integration”. Rename target: empuls-adp-marketplace.png, empuls-adp-integrations-page.png, empuls-adp-establish-connection.png, empuls-adp-sign-in.png, empuls-adp-data-fields.png, empuls-adp-schedule-sync.png.

​
Action plan (highest-impact first)

  1. Rewrite the title to 50–60 chars. Suggested: ADP integration for Empuls: automate employee sync from HRMS (60 chars). Moves #1 from 2 → 9.
  2. Extend the meta description to 145–160 chars and add “HRMS” and “24-hour sync”: Connect ADP to Empuls to automate employee onboarding, profile updates, and offboarding, keeping your directory in sync with your HRMS every 24 hours. (150 chars).
  3. Add 2–3 in-prose internal links to sibling HRMS integrations and to any employee-management page in the repo. Moves #5 from 3 → 8.
  4. Rename the 6 images to keyword-rich, empuls-adp-… slugs. Moves #10 from 3 → 8.
  5. Add 3–4 FAQs on supported ADP products (Workforce Now/RUN/Vantage), manual sync, empty-field behaviour, and data security.
  6. Add a small “field mapping example” table in the setup section (ADP field → Empuls field) to lift content depth from 8 → 10.
  7. Emit HowTo + FAQPage JSON-LD.

​
admin/reports/redemption-point-source.mdx

Canonical: https://help-empuls.xoxoday.com/admin/reports/redemption-point-source

​
Issues

  • Title (39 chars): "Redemption point source (FIFO) report" is descriptive and keyword-carrying (“FIFO”, “redemption”, “report”), but 11–21 chars short of the target and could pack more intent, e.g. add “Empuls” or “tax reconciliation”.
  • Description (157 chars): length is on target and the description surfaces the two primary use cases (tax reconciliation, source analysis). One of the best in the batch.
  • H1 / H2: clean hierarchy — Overview → How FIFO works → Columns in the report → When to use this report → How to get this report → FAQs.
  • Internal linking: the only outbound links are mailto:cs@xoxoday.com (twice). No internal Help Center links, despite obvious neighbours in the same admin/reports/ folder and in the redemption / recognition sections. This is the biggest single loss.
  • Schema: good TechArticle + FAQPage candidate. Not a HowTo in the strict sense (the “How to get this report” section is 2 trivial steps).
  • FAQ coverage: 3 FAQs cover the FIFO mechanic and the Redemption vs Cash Redemption split. Missing common questions the report explicitly enables: “How do I request the report?” (currently only in body prose), “How far back can the report go?”, “Which currencies / point units does the report use?”, “Can I export the report to CSV/Excel?”, “Are declined or refunded redemptions included?”.
  • Content depth: ~600 words with two tables and a worked example — reasonable for a reference page, but lacks a screenshot of the actual report and lacks a comparison to the standard Redemption report. The example ledger is helpful but stops short of showing what an output row for the FIFO trace looks like.
  • Image optimization: 0 images. The page describes a tabular report with FIFO attribution, but the reader never sees it. For a reference report page, at least one screenshot of the actual output is critical for search-driven users who arrived from a query like “FIFO redemption report format”.
  • Availability wording: the “not available by default, on request” pattern is clear, but from a search-intent perspective users searching for this may bounce when they realise it isn’t self-serve. Consider adding a “What you’ll receive” section (delivery format, file type, cadence).

​
Action plan (highest-impact first)

  1. Add at least one screenshot of the actual report — column layout, and ideally a highlighted redemption row showing FIFO attribution. Moves #10 from 0 → 8 and #9 from 4 → 8.
  2. Add 3–5 contextual internal links to related pages: sibling reports under admin/reports/, /employees/redemption/redeem-points, /employees/redemption/order-history, and the recognition/awards pages that credit points. Moves #5 from 2 → 8.
  3. Rewrite the title to 50–60 chars with a stronger use-case hook. Suggested: FIFO redemption point source report: trace every redemption (60 chars) or Redemption point source (FIFO) report for tax reconciliation (60 chars). Moves #1 from 6 → 9.
  4. Add 3–4 FAQs on how to request it, delivery format (CSV/Excel), historical range available, and treatment of refunds/reversals. Moves #7 from 7 → 10.
  5. Add a “What the deliverable looks like” section — file format, columns delivered, sample row — to raise content depth further and align with informational + navigational intent.
  6. Emit TechArticle + FAQPage JSON-LD.
  7. Keep the <Info> “provided on a request basis” callout at the top — it correctly manages user expectation before they read further.

​
Cross-cutting recommendations

Three patterns show up on every audited page and are worth fixing together in a follow-up PR:
  1. Titles are too short across the batch. Three of four are under 45 chars, and two are single words. Target 50–60 chars, lead with the primary keyword, always include “Empuls” for integration pages.
  2. Zero internal cross-linking between Help Center pages. All four pages link only to external marketing/vendor URLs. Add at least 2 contextual, root-relative internal links per page.
  3. Image filenames are sequential rather than descriptive. Rename to empuls-<product>-<step>.png conventions so image search can index them, and split any file that is reused for two different screenshots (see MS Teams microsoft-teams-guide-01.png).
Addressing those three levers would lift every page in this batch out of Medium and into Low priority (81–100).