> ## 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 # Empuls Help Center — SEO Audit Report **Generated:** 2026-08-03\ **Base URL:** [https://help-empuls.xoxoday.com](https://help-empuls.xoxoday.com)\ **Pages audited:** 367 (all MDX files referenced in `docs.json`, excluding `es/`, `fr/`, `zh/`, and `hidden: true` pages) ## Overall health | Metric | Value | | --------------- | -------------- | | Average score | **72.4 / 100** | | Critical (0–40) | 0 | | High (41–60) | 32 | | Medium (61–80) | 258 | | Low (81–100) | 77 | ## Recurring findings across the corpus | Finding | Pages affected | | -------------------------------------------------- | -------------- | | Missing frontmatter `title` | 0 | | Missing frontmatter `description` | 0 | | Duplicate title with another page | 27 | | Duplicate description with another page | 2 | | Title over 60 chars | 2 | | Description under 110 chars | 53 | | Description over 180 chars | 4 | | Body contains an H1 (should be H2) | 18 | | Thin content (under 200 words) | 58 | | Fewer than 2 internal links | 212 | | No FAQ block (page ≥400 words) | 117 | | Generic image filenames (Screenshot-\*, image1, …) | 162 | ## Highest-impact fixes (site-wide) 1. **Rename screenshot filenames.** 162 pages ship images with names like `Screenshot-2026-05-26-155618.png`. Rename to descriptive kebab-case (`admin-hub-reports-settings.png`) to gain image-search equity. 2. **Fill every `description`.** 0 pages are missing meta description; 53 are under 110 chars. Aim for 130–160 chars including the primary user query. 3. **Add contextual internal links.** 212 pages have fewer than 2 internal links to other docs.json pages, weakening topical authority. 4. **Add FAQ blocks.** 117 content-rich pages have no FAQ section — adding an `` of 3–5 real user questions unlocks FAQPage rich results. 5. **Fix double H1s.** 18 pages emit a body H1 in addition to the frontmatter title — demote to H2. 6. **De-duplicate titles/descriptions.** 27 titles and 2 descriptions collide across pages, causing Google to consolidate ranking signals. ## Summary table Sorted lowest-scoring first (highest priority for remediation). | # | Page | Score /100 | Priority | | --: | ----------------------------------------------------------------------------------------------- | ---------: | -------- | | 1 | `admin/sales-incentive/overview` | 50 | High | | 2 | `admin/integrations/hrms/247hrm` | 53 | High | | 3 | `admin/sales-incentive/admin-guide/account-setting/my-profile` | 53 | High | | 4 | `admin/sales-incentive/product-videos` | 55 | High | | 5 | `admin/integrations/collaboration/ms-teams` | 56 | High | | 6 | `admin/platform-settings/employee-appreciation-day` | 56 | High | | 7 | `admin/sales-incentive/admin-guide/communication/notifications` | 56 | High | | 8 | `demo-library/fitness-challenges` | 56 | High | | 9 | `admin/integrations/hrms/factohr` | 57 | High | | 10 | `admin/integrations/hrms/superworks` | 57 | High | | 11 | `admin/integrations/hrms/we-matter` | 57 | High | | 12 | `admin/integrations/other/integration-with-webhook` | 57 | High | | 13 | `admin/programs/perks-promotion-kit` | 57 | High | | 14 | `admin/resources/empuls-roadmap-2025` | 57 | High | | 15 | `admin/surveys/drivers/relationships-and-culture` | 57 | High | | 16 | `home` | 57 | High | | 17 | `admin/integrations/other/android-apk-install` | 58 | High | | 18 | `admin/integrations/other/google-sheets` | 58 | High | | 19 | `admin/integrations/other/zoho-books` | 58 | High | | 20 | `admin/sales-incentive/admin-guide/communication/documents` | 58 | High | | 21 | `admin/sales-incentive/integrations/zoho-crm` | 58 | High | | 22 | `admin/integrations/financial-wellbeing/kredily` | 59 | High | | 23 | `admin/integrations/hrms/pocket-hrms` | 59 | High | | 24 | `admin/resources/empuls-roadmap-2026` | 59 | High | | 25 | `admin/sales-incentive/admin-guide/plans/simulation-plans-and-metrics` | 59 | High | | 26 | `demo-library/slack-integration` | 59 | High | | 27 | `admin/integrations/other/custom-integrations` | 60 | High | | 28 | `admin/integrations/other/webhook` | 60 | High | | 29 | `admin/platform-settings/engagement-calendars` | 60 | High | | 30 | `admin/sales-incentive/updates/july-august-september-2024` | 60 | High | | 31 | `demo-library/recognition-impact-report` | 60 | High | | 32 | `demo-library/scheduled-award-reveal` | 60 | High | | 33 | `admin/integrations/collaboration/ms-teams-overview` | 61 | Medium | | 34 | `admin/integrations/financial-wellbeing/kredmint` | 61 | Medium | | 35 | `admin/integrations/other/postman-collection` | 61 | Medium | | 36 | `admin/integrations/other/sftp-integrations` | 61 | Medium | | 37 | `admin/sales-incentive/admin-guide/account-setting/settings` | 61 | Medium | | 38 | `admin/sales-incentive/admin-guide/plans/estimator` | 61 | Medium | | 39 | `admin/sales-incentive/updates/jan-2025` | 61 | Medium | | 40 | `admin/sales-incentive/updates/november-2025` | 61 | Medium | | 41 | `admin/integrations/hrms/isolved` | 62 | Medium | | 42 | `admin/integrations/hrms/paylocity` | 62 | Medium | | 43 | `demo-library/ai-recognition-messages` | 62 | Medium | | 44 | `demo-library/cost-of-living` | 62 | Medium | | 45 | `demo-library/google-chat-recognition` | 62 | Medium | | 46 | `demo-library/microsoft-teams` | 62 | Medium | | 47 | `demo-library/mood-o-meter` | 62 | Medium | | 48 | `demo-library/multiple-wallets` | 62 | Medium | | 49 | `demo-library/transaction-audit-report` | 62 | Medium | | 50 | `admin/benefits/multi-benefits-card` | 63 | Medium | | 51 | `admin/integrations/consultation-partners/beatroute` | 63 | Medium | | 52 | `admin/integrations/consultation-partners/kredmint-smart-working-capital-solutions` | 63 | Medium | | 53 | `admin/integrations/consultation-partners/peoplebox` | 63 | Medium | | 54 | `admin/integrations/consultation-partners/springworks` | 63 | Medium | | 55 | `admin/integrations/health-wellness/smart-digital-healthcare-with-mfine` | 63 | Medium | | 56 | `admin/integrations/hrms/kenboxtech` | 63 | Medium | | 57 | `admin/integrations/hrms/orangehrm` | 63 | Medium | | 58 | `admin/integrations/hrms/widespread-hr` | 63 | Medium | | 59 | `admin/integrations/hrms/zimyo` | 63 | Medium | | 60 | `admin/integrations/other/authentication-client-registration` | 63 | Medium | | 61 | `admin/sales-incentive/updates/december-2025` | 63 | Medium | | 62 | `admin/sales-incentive/updates/feb-march-2025` | 63 | Medium | | 63 | `admin/surveys/drivers/recognition-career-growth` | 63 | Medium | | 64 | `demo-library/custom-reports` | 63 | Medium | | 65 | `admin/integrations/hrms/people-hr` | 64 | Medium | | 66 | `admin/integrations/hrms/ukg-kronos` | 64 | Medium | | 67 | `admin/integrations/other/sftp` | 64 | Medium | | 68 | `demo-library/manual-automated-gifts` | 64 | Medium | | 69 | `demo-library/recognize-peers` | 64 | Medium | | 70 | `demo-library/smart-recognition` | 64 | Medium | | 71 | `admin/integrations/consultation-partners/fayredge` | 65 | Medium | | 72 | `admin/integrations/financial-wellbeing/salaryse` | 65 | Medium | | 73 | `admin/integrations/health-wellness/employee-wellness-support-with-samvedna-care` | 65 | Medium | | 74 | `admin/integrations/health-wellness/empower-employee-mental-wellness-with-your-dost` | 65 | Medium | | 75 | `admin/integrations/hrms/hrone` | 65 | Medium | | 76 | `admin/integrations/hrms/paycom` | 65 | Medium | | 77 | `admin/integrations/hrms/peopleforce` | 65 | Medium | | 78 | `admin/integrations/hrms/peoplestrong` | 65 | Medium | | 79 | `admin/integrations/other/logs` | 65 | Medium | | 80 | `admin/sales-incentive/updates/october-2025` | 65 | Medium | | 81 | `demo-library/budget-management` | 65 | Medium | | 82 | `demo-library/how-to-recognise` | 65 | Medium | | 83 | `demo-library/redeem-points` | 65 | Medium | | 84 | `demo-library/reward-campaigns` | 65 | Medium | | 85 | `demo-library/shop-management` | 65 | Medium | | 86 | `admin/integrations/financial-wellbeing/vestd` | 66 | Medium | | 87 | `admin/integrations/health-wellness/fitness-challenges` | 66 | Medium | | 88 | `admin/integrations/health-wellness/healthysure` | 66 | Medium | | 89 | `admin/integrations/hrms/emgage-integration` | 66 | Medium | | 90 | `admin/integrations/hrms/keka` | 66 | Medium | | 91 | `admin/integrations/hrms/other-hrms-custom-api` | 66 | Medium | | 92 | `admin/integrations/ld-benefits/great-learning` | 66 | Medium | | 93 | `admin/integrations/ld-benefits/simplilearn` | 66 | Medium | | 94 | `admin/integrations/other/database-management` | 66 | Medium | | 95 | `admin/integrations/zoho` | 66 | Medium | | 96 | `admin/programs/awards/introduction-to-awards` | 66 | Medium | | 97 | `admin/sales-incentive/admin-guide/communication/groups` | 66 | Medium | | 98 | `admin/sales-incentive/updates/jan-feb-2026` | 66 | Medium | | 99 | `admin/sales-incentive/updates/november-2024` | 66 | Medium | | 100 | `demo-library/awards-core-values` | 66 | Medium | | 101 | `demo-library/custom-notifications` | 66 | Medium | | 102 | `demo-library/platform-branding` | 66 | Medium | | 103 | `admin/integrations/financial-wellbeing/mobikwik` | 67 | Medium | | 104 | `admin/integrations/health-wellness/seamless-mental-wellness-support-through-silver-oak-health` | 67 | Medium | | 105 | `admin/integrations/hrms/ukg-ready` | 67 | Medium | | 106 | `admin/integrations/hrms/workday` | 67 | Medium | | 107 | `admin/platform-settings/homepage-templates` | 67 | Medium | | 108 | `admin/sales-incentive/admin-guide/dashboard/dashboard` | 67 | Medium | | 109 | `admin/sales-incentive/admin-guide/plans/app` | 67 | Medium | | 110 | `admin/sales-incentive/integrations/sdk-integration` | 67 | Medium | | 111 | `admin/sales-incentive/updates/august-2025` | 67 | Medium | | 112 | `admin/sales-incentive/updates/september-2025` | 67 | Medium | | 113 | `admin/surveys/drivers/hygiene-factors` | 67 | Medium | | 114 | `demo-library/employee-management` | 67 | Medium | | 115 | `demo-library/platform-reports` | 67 | Medium | | 116 | `demo-library/redeem-gift-vouchers` | 67 | Medium | | 117 | `employees/redemption/order-history` | 67 | Medium | | 118 | `admin/integrations/consultation-partners/acengage` | 68 | Medium | | 119 | `admin/integrations/consultation-partners/we360` | 68 | Medium | | 120 | `admin/integrations/health-wellness/elevate-medical` | 68 | Medium | | 121 | `admin/integrations/health-wellness/fix-health` | 68 | Medium | | 122 | `admin/integrations/health-wellness/mindpeers` | 68 | Medium | | 123 | `admin/integrations/health-wellness/orange-health` | 68 | Medium | | 124 | `admin/integrations/health-wellness/thyrocare` | 68 | Medium | | 125 | `admin/integrations/health-wellness/welleazy` | 68 | Medium | | 126 | `admin/integrations/hrms/sap-successfactors-native` | 68 | Medium | | 127 | `admin/integrations/insurance-benefits/nova-benefits` | 68 | Medium | | 128 | `admin/integrations/openai` | 68 | Medium | | 129 | `admin/sales-incentive/admin-guide/data-integrations/connections` | 68 | Medium | | 130 | `admin/sales-incentive/admin-guide/data-integrations/managing-data-sources` | 68 | Medium | | 131 | `admin/sales-incentive/admin-guide/plans/hidden-plans` | 68 | Medium | | 132 | `demo-library/compass-data-integrations` | 68 | Medium | | 133 | `demo-library/custom-leaderboards` | 68 | Medium | | 134 | `employees/benefits/perks-overview` | 68 | Medium | | 135 | `admin/integrations/giphy` | 69 | Medium | | 136 | `admin/reports/overview` | 69 | Medium | | 137 | `admin/sales-incentive/admin-guide/plans/plan-settings` | 69 | Medium | | 138 | `admin/sales-incentive/integrations/hubspot-integration` | 69 | Medium | | 139 | `admin/sales-incentive/updates/jan-feb-march-2024` | 69 | Medium | | 140 | `admin/security/privacy-policy` | 69 | Medium | | 141 | `admin/user-authentication/ping-identity-sso` | 69 | Medium | | 142 | `demo-library/bulk-nominations` | 69 | Medium | | 143 | `employees/getting-started/log-in` | 69 | Medium | | 144 | `admin/sales-incentive/admin-guide/plans/tracking-user-performance-and-metric-breakdown` | 70 | Medium | | 145 | `admin/sales-incentive/admin-guide/reports` | 70 | Medium | | 146 | `admin/sales-incentive/updates/april-may-june-2024` | 70 | Medium | | 147 | `admin/sales-incentive/updates/october-2024` | 70 | Medium | | 148 | `admin/security/information-security` | 70 | Medium | | 149 | `admin/security/responsible-ai` | 70 | Medium | | 150 | `admin/user-authentication/onelogin-sso` | 70 | Medium | | 151 | `demo-library/demo-library` | 70 | Medium | | 152 | `employees/recognitions/jury-ratings` | 70 | Medium | | 153 | `employees/socials/people-directory` | 70 | Medium | | 154 | `admin/finance/points-administration` | 71 | Medium | | 155 | `admin/integrations/health-wellness/truworth-wellness` | 71 | Medium | | 156 | `admin/integrations/linkedin` | 71 | Medium | | 157 | `admin/platform-settings/faqs` | 71 | Medium | | 158 | `admin/sales-incentive/admin-guide/data-integrations/users` | 71 | Medium | | 159 | `admin/sales-incentive/admin-guide/faq-admins/communication-faqs` | 71 | Medium | | 160 | `admin/sales-incentive/admin-guide/plans/plan-creation-and-types` | 71 | Medium | | 161 | `admin/sales-incentive/admin-guide/plans/plan-labels` | 71 | Medium | | 162 | `admin/surveys/action-plan` | 71 | Medium | | 163 | `demo-library/compass-groups-reports` | 71 | Medium | | 164 | `demo-library/compass-plans-metrics` | 71 | Medium | | 165 | `demo-library/compass-user-walkthrough` | 71 | Medium | | 166 | `employees/benefits/multi-benefits-card` | 71 | Medium | | 167 | `employees/engagement/quick-links` | 71 | Medium | | 168 | `product-updates/may-2025` | 71 | Medium | | 169 | `admin/benefits/faqs` | 72 | Medium | | 170 | `admin/benefits/health-wellness` | 72 | Medium | | 171 | `admin/integrations/financial-wellbeing/invitereferrals` | 72 | Medium | | 172 | `admin/integrations/health-wellness/comprehensive-flexibility-mobility-wellness-with-stretchit` | 72 | Medium | | 173 | `admin/integrations/hris-hrms` | 72 | Medium | | 174 | `admin/integrations/hrms/greythr` | 72 | Medium | | 175 | `admin/programs/awards/revoke-awards` | 72 | Medium | | 176 | `admin/reports/raw-data-report` | 72 | Medium | | 177 | `admin/sales-incentive/integrations/close-crm-integration` | 72 | Medium | | 178 | `admin/sales-incentive/integrations/salesforce-integration` | 72 | Medium | | 179 | `admin/user-authentication/sso-overview` | 72 | Medium | | 180 | `employees/recognitions/faqs` | 72 | Medium | | 181 | `product-updates/june-2025` | 72 | Medium | | 182 | `admin/integrations/collaboration/microsoft-365` | 73 | Medium | | 183 | `admin/integrations/collaboration/outlook` | 73 | Medium | | 184 | `admin/integrations/health-wellness/faqs` | 73 | Medium | | 185 | `admin/programs/awards/faqs` | 73 | Medium | | 186 | `admin/programs/launch-communication-kit` | 73 | Medium | | 187 | `admin/reports/activity-report` | 73 | Medium | | 188 | `employees/getting-started/mobile-app` | 73 | Medium | | 189 | `employees/getting-started/notifications` | 73 | Medium | | 190 | `admin/finance/redemption-wallets` | 74 | Medium | | 191 | `admin/integrations/hrms/other-hrms-sftp` | 74 | Medium | | 192 | `admin/integrations/other/faqs-data-and-integration` | 74 | Medium | | 193 | `admin/sales-incentive/admin-guide/data-integrations/manage-users` | 74 | Medium | | 194 | `admin/sales-incentive/admin-guide/plans/cascading` | 74 | Medium | | 195 | `admin/sales-incentive/admin-guide/plans/metrics` | 74 | Medium | | 196 | `admin/security/security-settings` | 74 | Medium | | 197 | `admin/surveys/type-of-surveys` | 74 | Medium | | 198 | `admin/user-authentication/azure-ad` | 74 | Medium | | 199 | `admin/user-authentication/okta-sso` | 74 | Medium | | 200 | `employees/getting-started/employee-profile` | 74 | Medium | | 201 | `employees/recognitions/recognition-approvals` | 74 | Medium | | 202 | `employees/surveys/action-plan` | 74 | Medium | | 203 | `product-updates/march-2025` | 74 | Medium | | 204 | `admin/finance/reward-marketplace-faqs` | 75 | Medium | | 205 | `admin/gifts/gifts` | 75 | Medium | | 206 | `admin/gifts/milestones-faqs` | 75 | Medium | | 207 | `admin/integrations/financial-wellbeing/safe-gold` | 75 | Medium | | 208 | `admin/integrations/hrms/sap-successfactors` | 75 | Medium | | 209 | `admin/integrations/insurance-benefits/tortoise` | 75 | Medium | | 210 | `admin/programs/awards-core-values` | 75 | Medium | | 211 | `admin/surveys/drivers/strategic-alignment` | 75 | Medium | | 212 | `admin/surveys/faqs` | 75 | Medium | | 213 | `demo-library/compass-overview` | 75 | Medium | | 214 | `employees/getting-started/faqs` | 75 | Medium | | 215 | `admin/integrations/financial-wellbeing/jiffy-moneyview` | 76 | Medium | | 216 | `admin/integrations/health-wellness/healthassure` | 76 | Medium | | 217 | `admin/integrations/hrms/adrenalin` | 76 | Medium | | 218 | `admin/programs/awards/bulk-review-of-nominations` | 76 | Medium | | 219 | `product-updates/december-2025` | 76 | Medium | | 220 | `product-updates/january-2025` | 76 | Medium | | 221 | `admin/integrations/financial-wellbeing/automint` | 77 | Medium | | 222 | `admin/integrations/financial-wellbeing/faqs` | 77 | Medium | | 223 | `admin/integrations/financial-wellbeing/finsafe` | 77 | Medium | | 224 | `admin/integrations/financial-wellbeing/liqvid-50fin` | 77 | Medium | | 225 | `admin/integrations/health-wellness/ambrosian` | 77 | Medium | | 226 | `admin/integrations/health-wellness/cult-fit` | 77 | Medium | | 227 | `admin/integrations/health-wellness/mfine` | 77 | Medium | | 228 | `admin/integrations/health-wellness/opdsure` | 77 | Medium | | 229 | `admin/integrations/hrms/gusto` | 77 | Medium | | 230 | `admin/integrations/hrms/hibob` | 77 | Medium | | 231 | `admin/integrations/hrms/namely` | 77 | Medium | | 232 | `admin/integrations/hrms/oracle` | 77 | Medium | | 233 | `admin/integrations/hrms/rippling` | 77 | Medium | | 234 | `admin/integrations/hrms/workline` | 77 | Medium | | 235 | `admin/integrations/insurance-benefits/atlys` | 77 | Medium | | 236 | `admin/referral-program/terms` | 77 | Medium | | 237 | `admin/user-authentication/oauth-clients` | 77 | Medium | | 238 | `demo-library/compass-admin-walkthrough` | 77 | Medium | | 239 | `employees/benefits/fitness-challenges` | 77 | Medium | | 240 | `employees/socials/celebrations` | 77 | Medium | | 241 | `product-updates/june-2026` | 77 | Medium | | 242 | `admin/ai/ai-settings` | 78 | Medium | | 243 | `admin/ai/empuls-copilot` | 78 | Medium | | 244 | `admin/gifts/automate-gifts` | 78 | Medium | | 245 | `admin/gifts/scheduled-gift` | 78 | Medium | | 246 | `admin/integrations/collaboration/google-chat` | 78 | Medium | | 247 | `admin/integrations/health-wellness/healthians` | 78 | Medium | | 248 | `admin/integrations/health-wellness/your-dost` | 78 | Medium | | 249 | `admin/integrations/hrms/darwinbox` | 78 | Medium | | 250 | `admin/integrations/hrms/ukg-pro` | 78 | Medium | | 251 | `admin/programs/awards/set-up-approval-based-awards` | 78 | Medium | | 252 | `admin/reports/budget-report` | 78 | Medium | | 253 | `admin/sales-incentive/admin-guide/faq-admins/plans-faqs` | 78 | Medium | | 254 | `admin/sales-incentive/admin-guide/faq-admins/reports-faqs` | 78 | Medium | | 255 | `admin/user-authentication/password-policies` | 78 | Medium | | 256 | `admin/user-authentication/saml-custom` | 78 | Medium | | 257 | `employees/engagement/gamezone` | 78 | Medium | | 258 | `admin/budgets/automated-budgets` | 79 | Medium | | 259 | `admin/budgets/manage-budgets` | 79 | Medium | | 260 | `admin/integrations/financial-wellbeing/astrafin` | 79 | Medium | | 261 | `admin/integrations/financial-wellbeing/finfinity` | 79 | Medium | | 262 | `admin/integrations/financial-wellbeing/taxspanner` | 79 | Medium | | 263 | `admin/integrations/health-wellness/aurae-digital` | 79 | Medium | | 264 | `admin/integrations/health-wellness/newmi-care` | 79 | Medium | | 265 | `admin/integrations/health-wellness/querencia-studios` | 79 | Medium | | 266 | `admin/integrations/health-wellness/stretchit` | 79 | Medium | | 267 | `admin/integrations/hrms/justlogin` | 79 | Medium | | 268 | `admin/integrations/hrms/zoho-people` | 79 | Medium | | 269 | `admin/integrations/insurance-benefits/zooper` | 79 | Medium | | 270 | `admin/integrations/ld-benefits/codingal` | 79 | Medium | | 271 | `admin/user-management/user-delegation` | 79 | Medium | | 272 | `product-updates/november-2025` | 79 | Medium | | 273 | `admin/admin-hub` | 80 | Medium | | 274 | `admin/finance/cost-of-living` | 80 | Medium | | 275 | `admin/finance/subscription-billing` | 80 | Medium | | 276 | `admin/integrations/financial-wellbeing/assured-gain` | 80 | Medium | | 277 | `admin/integrations/health-wellness/silver-oak-health` | 80 | Medium | | 278 | `admin/integrations/hrms/freshteam` | 80 | Medium | | 279 | `admin/integrations/insurance-benefits/neoffice` | 80 | Medium | | 280 | `admin/integrations/other/amazon-marketplace` | 80 | Medium | | 281 | `admin/platform-settings/branding` | 80 | Medium | | 282 | `admin/programs/reward-campaigns` | 80 | Medium | | 283 | `admin/referral-program/overview` | 80 | Medium | | 284 | `admin/reports/custom-report` | 80 | Medium | | 285 | `admin/reports/redemption-report` | 80 | Medium | | 286 | `admin/sales-incentive/admin-guide/plans/milestones` | 80 | Medium | | 287 | `admin/surveys/mood-o-meter` | 80 | Medium | | 288 | `admin/user-management/access-control` | 80 | Medium | | 289 | `employees/recognitions/appreciate-colleagues` | 80 | Medium | | 290 | `employees/redemption/festive-gifts` | 80 | Medium | | 291 | `admin/integrations/financial-wellbeing/fatakpay` | 81 | Low | | 292 | `admin/integrations/health-wellness/circle-health` | 81 | Low | | 293 | `admin/integrations/health-wellness/clove-dental` | 81 | Low | | 294 | `admin/integrations/health-wellness/fitelo` | 81 | Low | | 295 | `admin/integrations/health-wellness/fitpass` | 81 | Low | | 296 | `admin/integrations/health-wellness/healthify` | 81 | Low | | 297 | `admin/integrations/health-wellness/humm-care` | 81 | Low | | 298 | `admin/integrations/health-wellness/portea` | 81 | Low | | 299 | `admin/integrations/health-wellness/red-health` | 81 | Low | | 300 | `admin/integrations/hrms/adp` | 81 | Low | | 301 | `admin/integrations/hrms/bamboohr` | 81 | Low | | 302 | `admin/integrations/ld-benefits/upgrad` | 81 | Low | | 303 | `admin/integrations/ld-benefits/vani-coach` | 81 | Low | | 304 | `admin/programs/fitness-challenges` | 81 | Low | | 305 | `admin/reports/gift-report` | 81 | Low | | 306 | `admin/reports/redemption-point-source` | 81 | Low | | 307 | `admin/security/platform-data-faqs` | 81 | Low | | 308 | `admin/surveys/employee-pulse-survey` | 81 | Low | | 309 | `admin/surveys/quizzes` | 81 | Low | | 310 | `employees/recognitions/wall-of-fame` | 81 | Low | | 311 | `product-updates/february-2025` | 81 | Low | | 312 | `product-updates/january-2026` | 81 | Low | | 313 | `product-updates/october-2025` | 81 | Low | | 314 | `admin/integrations/financial-wellbeing/muro` | 82 | Low | | 315 | `admin/integrations/financial-wellbeing/poonawalla-fincorp` | 82 | Low | | 316 | `admin/integrations/health-wellness/medibuddy` | 82 | Low | | 317 | `admin/integrations/health-wellness/overview` | 82 | Low | | 318 | `admin/integrations/ld-benefits/master-o` | 82 | Low | | 319 | `admin/platform-settings/feed-and-profile-settings` | 82 | Low | | 320 | `admin/reports/recognition-report` | 82 | Low | | 321 | `admin/sales-incentive/admin-guide/dashboard/add-a-widget-to-your-dashboard` | 82 | Low | | 322 | `admin/surveys/survey-analytics` | 82 | Low | | 323 | `admin/user-authentication/session-management` | 82 | Low | | 324 | `employees/socials/groups` | 82 | Low | | 325 | `employees/socials/townhall` | 82 | Low | | 326 | `admin/ai/ai-skill-mapping` | 83 | Low | | 327 | `admin/integrations/collaboration/google-workspace` | 83 | Low | | 328 | `admin/integrations/collaboration/slack` | 83 | Low | | 329 | `admin/integrations/financial-wellbeing/refyne` | 83 | Low | | 330 | `admin/integrations/health-wellness/apollo-labs` | 83 | Low | | 331 | `admin/integrations/health-wellness/ekincare` | 83 | Low | | 332 | `admin/integrations/health-wellness/fitterfly` | 83 | Low | | 333 | `admin/integrations/health-wellness/pazcare` | 83 | Low | | 334 | `admin/integrations/health-wellness/practo` | 83 | Low | | 335 | `admin/integrations/health-wellness/samvedna-care` | 83 | Low | | 336 | `admin/integrations/health-wellness/twin-health` | 83 | Low | | 337 | `admin/integrations/health-wellness/unlock-fit` | 83 | Low | | 338 | `admin/integrations/health-wellness/yogifi` | 83 | Low | | 339 | `admin/platform-settings/notification-settings` | 83 | Low | | 340 | `admin/programs/awards/add-certificates-to-awards` | 83 | Low | | 341 | `admin/programs/awards/incentive-based-awards` | 83 | Low | | 342 | `admin/programs/awards/set-up-awards-and-core-values` | 83 | Low | | 343 | `admin/programs/leaderboard` | 83 | Low | | 344 | `admin/surveys/create-surveys` | 83 | Low | | 345 | `admin/surveys/lifecycle-surveys` | 83 | Low | | 346 | `admin/user-authentication/google-workspace-sso` | 83 | Low | | 347 | `admin/user-management/employee-exit` | 83 | Low | | 348 | `employees/getting-started/data-privacy` | 83 | Low | | 349 | `employees/redemption/physical-gift-claims` | 83 | Low | | 350 | `employees/socials/social-intranet` | 83 | Low | | 351 | `admin/integrations/other/faqs` | 84 | Low | | 352 | `admin/integrations/other/sdk` | 84 | Low | | 353 | `admin/reports/organization-dashboard` | 84 | Low | | 354 | `admin/integrations/collaboration/microsoft-teams` | 85 | Low | | 355 | `admin/integrations/other/implementation-integration-governance-faqs` | 85 | Low | | 356 | `admin/programs/awards/jury-based-awards` | 85 | Low | | 357 | `admin/sales-incentive/admin-guide/faq-admins/getting-started-for-admins-faqs` | 85 | Low | | 358 | `admin/user-management/manage-employees` | 85 | Low | | 359 | `employees/recognitions/nominations` | 85 | Low | | 360 | `product-updates/july-august-2025` | 85 | Low | | 361 | `product-updates/september-2025` | 85 | Low | | 362 | `admin/integrations/health-wellness/1to1-help` | 86 | Low | | 363 | `admin/gifts/setup-product-based-gifts` | 87 | Low | | 364 | `employees/redemption/redeem-points` | 88 | Low | | 365 | `admin/integrations/collaboration/microsoft-teams-it-admin` | 89 | Low | | 366 | `admin/surveys/enps-pulse` | 89 | Low | | 367 | `admin/integrations/collaboration/microsoft-teams-usage` | 93 | Low | ## Per-page findings Each page below lists its ten sub-scores (0–10), the specific issues detected, the JSON-LD schema types it can qualify for, and an Action Plan ordered by impact (lowest sub-score first). ### `admin/sales-incentive/overview` — 50/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/overview](https://help-empuls.xoxoday.com/admin/sales-incentive/overview) * **Title (8 ch):** `Overview` * **Description (115 ch):** `Empuls Sales Incentive helps you design, run, and analyse commission and incentive programmes for your sales teams.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 86 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 0/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **50/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Title "Overview" is boilerplate — prefix with the product area (e.g. "Reward campaigns overview"). * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (86 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **title (0/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/hrms/247hrm` — 53/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/247hrm](https://help-empuls.xoxoday.com/admin/integrations/hrms/247hrm) * **Title (6 ch):** `247HRM` * **Description (106 ch):** `Integrate 247HRM with Empuls to sync attendance and employee records with automated recognition workflows.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 180 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **53/100** | **Issues detected:** * Title is short (6 chars) — add descriptive keywords to reach \~50–60. * Description is 106 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (180 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/sales-incentive/admin-guide/account-setting/my-profile` — 53/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/account-setting/my-profile](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/account-setting/my-profile) * **Title (10 ch):** `My profile` * **Description (129 ch):** `View and manage your own profile details inside Empuls’s sales incentive module. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 73 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **53/100** | **Issues detected:** * Title is short (10 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (73 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/sales-incentive/product-videos` — 55/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/product-videos](https://help-empuls.xoxoday.com/admin/sales-incentive/product-videos) * **Title (19 ch):** `Product demo videos` * **Description (124 ch):** `Watch product demo videos covering the core modules of Empuls’s sales incentive software. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 133 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **55/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (133 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/integrations/collaboration/ms-teams` — 56/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/ms-teams](https://help-empuls.xoxoday.com/admin/integrations/collaboration/ms-teams) * **Title (8 ch):** `MS Teams` * **Description (121 ch):** `Empuls’s Microsoft Teams integration puts Empuls recognition tools directly inside Microsoft Teams, without extra logins.` * **Body H1/H2/H3:** 1 / 4 / 0 · **Words:** 151 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **56/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (151 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/platform-settings/employee-appreciation-day` — 56/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/platform-settings/employee-appreciation-day](https://help-empuls.xoxoday.com/admin/platform-settings/employee-appreciation-day) * **Title (38 ch):** `Employee appreciation day & week ideas` * **Description (107 ch):** `Get creative ideas for celebrating Employee Appreciation Week using Empuls’s recognition and rewards tools.` * **Body H1/H2/H3:** 1 / 2 / 0 · **Words:** 157 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **56/100** | **Issues detected:** * Description is 107 chars — extend to 130–160 with search terms. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (157 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/sales-incentive/admin-guide/communication/notifications` — 56/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/communication/notifications](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/communication/notifications) * **Title (13 ch):** `Notifications` * **Description (122 ch):** `Keep sales reps informed of plan changes with configurable incentive notifications. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 177 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **56/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (177 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `demo-library/fitness-challenges` — 56/100 · High * **URL:** [https://help-empuls.xoxoday.com/demo-library/fitness-challenges](https://help-empuls.xoxoday.com/demo-library/fitness-challenges) * **Title (18 ch):** `Fitness Challenges` * **Description (129 ch):** `See fitness challenges in action on Empuls, with setting up fitness challenges and tracking participation explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 2 · **Words:** 180 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 1/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **56/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (180 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **title (1/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/hrms/factohr` — 57/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/factohr](https://help-empuls.xoxoday.com/admin/integrations/hrms/factohr) * **Title (7 ch):** `FactoHR` * **Description (109 ch):** `Sync FactoHR employee records with Empuls for automated onboarding, exit workflows, and recognition triggers.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 155 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **57/100** | **Issues detected:** * Title is short (7 chars) — add descriptive keywords to reach \~50–60. * Description is 109 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (155 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/hrms/superworks` — 57/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/superworks](https://help-empuls.xoxoday.com/admin/integrations/hrms/superworks) * **Title (10 ch):** `Superworks` * **Description (106 ch):** `Link Superworks with Empuls to centralize employee data and automate engagement and recognition workflows.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 116 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **57/100** | **Issues detected:** * Title is short (10 chars) — add descriptive keywords to reach \~50–60. * Description is 106 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (116 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/hrms/we-matter` — 57/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/we-matter](https://help-empuls.xoxoday.com/admin/integrations/hrms/we-matter) * **Title (9 ch):** `We-Matter` * **Description (103 ch):** `Connect WE-Matter with Empuls to combine engagement survey data with recognition, rewards, and gifting.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 116 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **57/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Description is 103 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (116 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/other/integration-with-webhook` — 57/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/integration-with-webhook](https://help-empuls.xoxoday.com/admin/integrations/other/integration-with-webhook) * **Title (24 ch):** `Integration with Webhook` * **Description (132 ch):** `Trigger external workflows from Empuls events using a configurable webhook integration. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 121 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **57/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (121 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/programs/perks-promotion-kit` — 57/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/programs/perks-promotion-kit](https://help-empuls.xoxoday.com/admin/programs/perks-promotion-kit) * **Title (19 ch):** `Perks promotion kit` * **Description (107 ch):** `Get ready-made assets to launch and promote the Empuls perks and benefits program across your organization.` * **Body H1/H2/H3:** 0 / 0 / 5 · **Words:** 792 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **57/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Description is 107 chars — extend to 130–160 with search terms. * No H2 sections — add scannable H2 headings for structure and jump links. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/resources/empuls-roadmap-2025` — 57/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/resources/empuls-roadmap-2025](https://help-empuls.xoxoday.com/admin/resources/empuls-roadmap-2025) * **Title (19 ch):** `Empuls roadmap 2025` * **Description (104 ch):** `See the features and improvements Empuls shipped and planned across 2025, from recognition to reporting.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 83 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **57/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Description is 104 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (83 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/surveys/drivers/relationships-and-culture` — 57/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/drivers/relationships-and-culture](https://help-empuls.xoxoday.com/admin/surveys/drivers/relationships-and-culture) * **Title (25 ch):** `Relationships and culture` * **Description (122 ch):** `Understand the relationships and culture driver in Empuls’s engagement survey analysis, and what it means for team scores.` * **Body H1/H2/H3:** 1 / 0 / 0 · **Words:** 9095 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 4/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **57/100** | **Issues detected:** * Title is short (25 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * No H2 sections — add scannable H2 headings for structure and jump links. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `home` — 57/100 · High * **URL:** [https://help-empuls.xoxoday.com/home](https://help-empuls.xoxoday.com/home) * **Title (21 ch):** `Xoxoday Documentation` * **Description (92 ch):** `Guides, references, and walkthroughs for every Xoxoday product — Empuls, Plum, and Loyalife.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 308 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **57/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * Description is 92 chars — extend to 130–160 with search terms. * No H2 sections — add scannable H2 headings for structure and jump links. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/other/android-apk-install` — 58/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/android-apk-install](https://help-empuls.xoxoday.com/admin/integrations/other/android-apk-install) * **Title (52 ch):** `Install Empuls Android app without Google Play Store` * **Description (118 ch):** `Alternative method for you to download and install the app directly from our website or using the link provided below.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 287 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 5/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **58/100** | **Issues detected:** * No H2 sections — add scannable H2 headings for structure and jump links. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Title implies a how-to but page has no `` block — convert numbered instructions to `` for HowTo schema. * Content is short (287 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (5/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/other/google-sheets` — 58/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/google-sheets](https://help-empuls.xoxoday.com/admin/integrations/other/google-sheets) * **Title (13 ch):** `Google Sheets` * **Description (135 ch):** `Export Empuls reward and engagement data straight into Google Sheets for further analysis. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 1 / 4 / 0 · **Words:** 150 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **58/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (150 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/other/zoho-books` — 58/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/zoho-books](https://help-empuls.xoxoday.com/admin/integrations/other/zoho-books) * **Title (10 ch):** `Zoho Books` * **Description (133 ch):** `Sync reward and redemption data between Empuls and Zoho Books for easier accounting. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 1 / 4 / 0 · **Words:** 149 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **58/100** | **Issues detected:** * Title is short (10 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (149 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/sales-incentive/admin-guide/communication/documents` — 58/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/communication/documents](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/communication/documents) * **Title (9 ch):** `Documents` * **Description (143 ch):** `Share plan-related documents with your sales team directly inside Empuls’s sales incentive module. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 122 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **58/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (122 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/sales-incentive/integrations/zoho-crm` — 58/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/zoho-crm](https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/zoho-crm) * **Title (8 ch):** `Zoho CRM` * **Description (147 ch):** `Connect Zoho CRM with Empuls’s sales incentive module to automate commission calculations. Admins can configure this from the Empuls control panel.` * **Body H1/H2/H3:** 1 / 4 / 0 · **Words:** 150 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **58/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (150 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/financial-wellbeing/kredily` — 59/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/kredily](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/kredily) * **Title (7 ch):** `Kredily` * **Description (103 ch):** `Extend your financial wellness program by integrating Kredily with Empuls for HR and payroll data sync.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 238 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **59/100** | **Issues detected:** * Title is short (7 chars) — add descriptive keywords to reach \~50–60. * Description is 103 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (238 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/hrms/pocket-hrms` — 59/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/pocket-hrms](https://help-empuls.xoxoday.com/admin/integrations/hrms/pocket-hrms) * **Title (11 ch):** `Pocket HRMS` * **Description (114 ch):** `Integrate Pocket HRMS with Empuls to keep employee records synced and recognition automated across your workforce.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 118 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **59/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (118 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/resources/empuls-roadmap-2026` — 59/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/resources/empuls-roadmap-2026](https://help-empuls.xoxoday.com/admin/resources/empuls-roadmap-2026) * **Title (19 ch):** `Empuls roadmap 2026` * **Description (110 ch):** `See the features and improvements planned for Empuls across 2026, including upcoming AI and reporting updates.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 96 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **59/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (96 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/sales-incentive/admin-guide/plans/simulation-plans-and-metrics` — 59/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/simulation-plans-and-metrics](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/simulation-plans-and-metrics) * **Title (29 ch):** `Simulation- plans and metrics` * **Description (134 ch):** `Simulate plan and metric changes before rolling them out to your sales incentive program. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 245 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **59/100** | **Issues detected:** * Title is short (29 chars) — add descriptive keywords to reach \~50–60. * No H2 sections — add scannable H2 headings for structure and jump links. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (245 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `demo-library/slack-integration` — 59/100 · High * **URL:** [https://help-empuls.xoxoday.com/demo-library/slack-integration](https://help-empuls.xoxoday.com/demo-library/slack-integration) * **Title (17 ch):** `Slack Integration` * **Description (115 ch):** `This demo shows the Slack integration in Empuls, including recognizing teammates and managing rewards inside Slack.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 116 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **59/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (116 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/other/custom-integrations` — 60/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/custom-integrations](https://help-empuls.xoxoday.com/admin/integrations/other/custom-integrations) * **Title (19 ch):** `Custom integrations` * **Description (130 ch):** `Build a custom integration between Empuls and your internal tools using the developer APIs. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 212 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **60/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (212 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/other/webhook` — 60/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/webhook](https://help-empuls.xoxoday.com/admin/integrations/other/webhook) * **Title (24 ch):** `Integration with Webhook` * **Description (118 ch):** `Send Empuls event data to your own systems in real time using webhook integrations. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 130 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 9/10 | | **Overall** | **60/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (130 words) — expand to at least 300 words with examples, prerequisites, and outcomes. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/platform-settings/engagement-calendars` — 60/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/platform-settings/engagement-calendars](https://help-empuls.xoxoday.com/admin/platform-settings/engagement-calendars) * **Title (34 ch):** `Employee engagement calendars 2026` * **Description (114 ch):** `Download an annual engagement calendar to plan recognition moments and celebrations throughout the year on Empuls.` * **Body H1/H2/H3:** 6 / 0 / 0 · **Words:** 257 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 1/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **60/100** | **Issues detected:** * Body contains 6 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * No H2 sections — add scannable H2 headings for structure and jump links. * Content is short (257 words) — expand toward 500+ where useful. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h1 (1/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/sales-incentive/updates/july-august-september-2024` — 60/100 · High * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/july-august-september-2024](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/july-august-september-2024) * **Title (26 ch):** `July-August-September 2024` * **Description (125 ch):** `See what's new in Empuls’s sales incentive module for July through September 2024: feature releases, improvements, and fixes.` * **Body H1/H2/H3:** 1 / 7 / 0 · **Words:** 219 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **60/100** | **Issues detected:** * Title is short (26 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (219 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `demo-library/recognition-impact-report` — 60/100 · High * **URL:** [https://help-empuls.xoxoday.com/demo-library/recognition-impact-report](https://help-empuls.xoxoday.com/demo-library/recognition-impact-report) * **Title (25 ch):** `Recognition Impact Report` * **Description (119 ch):** `Correlate your Empuls recognition activity with Glassdoor ratings month over month to make the ROI case for leadership.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 86 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **60/100** | **Issues detected:** * Title is short (25 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (86 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `demo-library/scheduled-award-reveal` — 60/100 · High * **URL:** [https://help-empuls.xoxoday.com/demo-library/scheduled-award-reveal](https://help-empuls.xoxoday.com/demo-library/scheduled-award-reveal) * **Title (22 ch):** `Scheduled Award Reveal` * **Description (129 ch):** `See scheduled award reveals in action on Empuls, with holding award posts to reveal winners at a set time explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 80 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **60/100** | **Issues detected:** * Title is short (22 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (80 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/collaboration/ms-teams-overview` — 61/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/ms-teams-overview](https://help-empuls.xoxoday.com/admin/integrations/collaboration/ms-teams-overview) * **Title (17 ch):** `MS Teams overview` * **Description (112 ch):** `Empuls’s Microsoft Teams integration puts Empuls features directly inside Microsoft Teams, without extra logins.` * **Body H1/H2/H3:** 1 / 4 / 0 · **Words:** 166 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 9/10 | | **Overall** | **61/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (166 words) — expand to at least 300 words with examples, prerequisites, and outcomes. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/financial-wellbeing/kredmint` — 61/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/kredmint](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/kredmint) * **Title (41 ch):** `Kredmint: smart working capital solutions` * **Description (105 ch):** `Extend your financial wellness program by integrating Kredmint with Empuls for working capital financing.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 244 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **61/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * Description is 105 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (244 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/other/postman-collection` — 61/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/postman-collection](https://help-empuls.xoxoday.com/admin/integrations/other/postman-collection) * **Title (18 ch):** `Postman collection` * **Description (138 ch):** `Test the Empuls API quickly using a ready-made Postman collection for developers. Admins can configure this from the Empuls control panel.` * **Body H1/H2/H3:** 1 / 13 / 0 · **Words:** 1065 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 4/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **61/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/integrations/other/sftp-integrations` — 61/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/sftp-integrations](https://help-empuls.xoxoday.com/admin/integrations/other/sftp-integrations) * **Title (17 ch):** `SFTP integrations` * **Description (132 ch):** `Move employee and reward data between Empuls and other systems using SFTP-based integrations. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 149 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 1/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **61/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (149 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **title (1/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/sales-incentive/admin-guide/account-setting/settings` — 61/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/account-setting/settings](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/account-setting/settings) * **Title (8 ch):** `Settings` * **Description (121 ch):** `Manage dashboard and account settings for Empuls’s sales incentive software. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 229 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **61/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (229 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/sales-incentive/admin-guide/plans/estimator` — 61/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/estimator](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/estimator) * **Title (9 ch):** `Estimator` * **Description (128 ch):** `Use the plan estimator to preview payouts before publishing a sales incentive plan. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 250 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **61/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (250 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/sales-incentive/updates/jan-2025` — 61/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/jan-2025](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/jan-2025) * **Title (8 ch):** `Jan 2025` * **Description (107 ch):** `Catch up on everything Empuls’s sales incentive module shipped in January 2025, from new features to fixes.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 247 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **61/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Description is 107 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (247 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/sales-incentive/updates/november-2025` — 61/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/november-2025](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/november-2025) * **Title (13 ch):** `November 2025` * **Description (108 ch):** `Catch up on everything Empuls’s sales incentive module shipped in November 2025, from new features to fixes.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 208 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **61/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Description is 108 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (208 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/hrms/isolved` — 62/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/isolved](https://help-empuls.xoxoday.com/admin/integrations/hrms/isolved) * **Title (7 ch):** `iSolved` * **Description (104 ch):** `Connect iSolved with Empuls to power your HRMS integration across HR, rewards, and engagement workflows.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 218 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 3/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **62/100** | **Issues detected:** * Title is short (7 chars) — add descriptive keywords to reach \~50–60. * Description is 104 chars — extend to 130–160 with search terms. * Description is duplicated on another page — write a unique one. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (218 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **desc (3/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/hrms/paylocity` — 62/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/paylocity](https://help-empuls.xoxoday.com/admin/integrations/hrms/paylocity) * **Title (9 ch):** `Paylocity` * **Description (104 ch):** `Connect iSolved with Empuls to power your HRMS integration across HR, rewards, and engagement workflows.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 219 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 3/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **62/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Description is 104 chars — extend to 130–160 with search terms. * Description is duplicated on another page — write a unique one. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (219 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **desc (3/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `demo-library/ai-recognition-messages` — 62/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/ai-recognition-messages](https://help-empuls.xoxoday.com/demo-library/ai-recognition-messages) * **Title (32 ch):** `AI-Written Appreciation Messages` * **Description (113 ch):** `Pick a tone and let AI write the perfect award message instantly, removing the blank-page barrier to recognition.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 79 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **62/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (79 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/cost-of-living` — 62/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/cost-of-living](https://help-empuls.xoxoday.com/demo-library/cost-of-living) * **Title (21 ch):** `Cost of Living Factor` * **Description (128 ch):** `See the cost-of-living factor in action on Empuls, with location-aware point conversion for global teams explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 150 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **62/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (150 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `demo-library/google-chat-recognition` — 62/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/google-chat-recognition](https://help-empuls.xoxoday.com/demo-library/google-chat-recognition) * **Title (26 ch):** `Recognition in Google Chat` * **Description (135 ch):** `See Google Chat recognition in action on Empuls, with receiving recognition and milestone alerts in Google Chat explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 93 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **62/100** | **Issues detected:** * Title is short (26 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (93 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `demo-library/microsoft-teams` — 62/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/microsoft-teams](https://help-empuls.xoxoday.com/demo-library/microsoft-teams) * **Title (27 ch):** `Microsoft Teams Integration` * **Description (113 ch):** `This demo shows the Microsoft Teams integration in Empuls, including recognizing teammates without leaving Teams.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 174 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **62/100** | **Issues detected:** * Title is short (27 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (174 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `demo-library/mood-o-meter` — 62/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/mood-o-meter](https://help-empuls.xoxoday.com/demo-library/mood-o-meter) * **Title (39 ch):** `Mood-O-Meter Email & Sentiment Analysis` * **Description (124 ch):** `Watch a walkthrough of Mood-o-meter on Empuls, covering email-based sentiment check-ins with AI-powered insight into scores.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 86 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **62/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (86 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/multiple-wallets` — 62/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/multiple-wallets](https://help-empuls.xoxoday.com/demo-library/multiple-wallets) * **Title (25 ch):** `Managing Multiple Wallets` * **Description (123 ch):** `This demo shows multiple redemption wallets in Empuls, including managing several wallets with different funding and rules.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 197 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **62/100** | **Issues detected:** * Title is short (25 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (197 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `demo-library/transaction-audit-report` — 62/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/transaction-audit-report](https://help-empuls.xoxoday.com/demo-library/transaction-audit-report) * **Title (24 ch):** `Transaction Audit Report` * **Description (149 ch):** `See the transaction audit report in action on Empuls, with downloading a full record of credits, redemptions, and expirations explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 73 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **62/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (73 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/benefits/multi-benefits-card` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/benefits/multi-benefits-card](https://help-empuls.xoxoday.com/admin/benefits/multi-benefits-card) * **Title (19 ch):** `Multi benefits card` * **Description (173 ch):** `Set up and manage the Empuls Multi-Benefit Card for your organization: configure tax-exempt categories, set employee allocations, and track card usage across your workforce.` * **Body H1/H2/H3:** 0 / 14 / 2 · **Words:** 1858 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 1/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Description is 173 chars — slightly over the 160-char SERP cutoff. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **title (1/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/consultation-partners/beatroute` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/beatroute](https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/beatroute) * **Title (18 ch):** `BeatRoute – Empuls` * **Description (118 ch):** `BeatRoute integrates with Empuls to bring field-sales performance tracking into a single engagement view for HR teams.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 313 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/consultation-partners/kredmint-smart-working-capital-solutions` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/kredmint-smart-working-capital-solutions](https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/kredmint-smart-working-capital-solutions) * **Title (41 ch):** `Kredmint: smart working capital solutions` * **Description (118 ch):** `Connect Kredmint with Empuls to combine working capital financing for teams with your recognition and engagement data.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 244 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (244 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/consultation-partners/peoplebox` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/peoplebox](https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/peoplebox) * **Title (71 ch):** `Connect Peoplebox with Empuls to streamline performance and recognition` * **Description (136 ch):** `Connect Empuls to streamline performance and recognition with Empuls to automate employee data sync and extend your engagement programs.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 256 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is 71 chars — trim to 50–60 for full SERP display. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (256 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/consultation-partners/springworks` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/springworks](https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/springworks) * **Title (11 ch):** `Springworks` * **Description (130 ch):** `Springworks integrates with Empuls to bring employee culture and engagement consulting into a single engagement view for HR teams.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 287 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (287 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/health-wellness/smart-digital-healthcare-with-mfine` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/smart-digital-healthcare-with-mfine](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/smart-digital-healthcare-with-mfine) * **Title (35 ch):** `Smart digital healthcare with MFine` * **Description (126 ch):** `MFine integrates with Empuls so every employee can access on-demand digital doctor consultations without leaving the platform.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 264 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (264 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/hrms/kenboxtech` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/kenboxtech](https://help-empuls.xoxoday.com/admin/integrations/hrms/kenboxtech) * **Title (10 ch):** `Kenboxtech` * **Description (102 ch):** `Integrate Kenboxtech with Empuls to sync employee data and automate recognition triggers across teams.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 140 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (10 chars) — add descriptive keywords to reach \~50–60. * Description is 102 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (140 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/hrms/orangehrm` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/orangehrm](https://help-empuls.xoxoday.com/admin/integrations/hrms/orangehrm) * **Title (9 ch):** `OrangeHRM` * **Description (92 ch):** `Learn how to seamlessly integrate Emplus with OrangeHRM to automate user management process.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 180 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Description is 92 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (180 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/hrms/widespread-hr` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/widespread-hr](https://help-empuls.xoxoday.com/admin/integrations/hrms/widespread-hr) * **Title (13 ch):** `Widespread HR` * **Description (101 ch):** `Connect Widespread HR with Empuls to keep employee records synced and automate recognition workflows.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 146 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Description is 101 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (146 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/hrms/zimyo` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/zimyo](https://help-empuls.xoxoday.com/admin/integrations/hrms/zimyo) * **Title (5 ch):** `Zimyo` * **Description (93 ch):** `Connect Zimyo with Empuls to automate employee data sync and extend your engagement programs.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 158 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (5 chars) — add descriptive keywords to reach \~50–60. * Description is 93 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (158 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/other/authentication-client-registration` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/authentication-client-registration](https://help-empuls.xoxoday.com/admin/integrations/other/authentication-client-registration) * **Title (34 ch):** `Authentication client registration` * **Description (137 ch):** `Register an OAuth client to grant a third-party app scoped, secure access to the Empuls API. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 171 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (171 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/sales-incentive/updates/december-2025` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/december-2025](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/december-2025) * **Title (13 ch):** `December 2025` * **Description (116 ch):** `Explore Empuls’s sales incentive module’s product updates for December 2025, covering new features and improvements.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 249 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (249 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/sales-incentive/updates/feb-march-2025` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/feb-march-2025](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/feb-march-2025) * **Title (14 ch):** `Feb-March 2025` * **Description (118 ch):** `Catch up on everything Empuls’s sales incentive module shipped in February and March 2025, from new features to fixes.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 235 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (14 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (235 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/surveys/drivers/recognition-career-growth` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/drivers/recognition-career-growth](https://help-empuls.xoxoday.com/admin/surveys/drivers/recognition-career-growth) * **Title (27 ch):** `Recognition & career growth` * **Description (112 ch):** `Understand the recognition and career-growth driver behind Empuls’s engagement survey scores and what drives it.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 4169 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (27 chars) — add descriptive keywords to reach \~50–60. * No H2 sections — add scannable H2 headings for structure and jump links. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `demo-library/custom-reports` — 63/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/custom-reports](https://help-empuls.xoxoday.com/demo-library/custom-reports) * **Title (29 ch):** `Create & Share Custom Reports` * **Description (122 ch):** `Watch a walkthrough of custom report building on Empuls, covering creating and sharing tailored reports with stakeholders.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 98 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 1/10 | | 10. Image optimization | 7/10 | | **Overall** | **63/100** | **Issues detected:** * Title is short (29 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (98 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **depth (1/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/integrations/hrms/people-hr` — 64/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/people-hr](https://help-empuls.xoxoday.com/admin/integrations/hrms/people-hr) * **Title (9 ch):** `People HR` * **Description (114 ch):** `Streamline HR operations by connecting PeopleHR with Empuls for synced employee records and automated recognition.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 242 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **64/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (242 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/hrms/ukg-kronos` — 64/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/ukg-kronos](https://help-empuls.xoxoday.com/admin/integrations/hrms/ukg-kronos) * **Title (10 ch):** `UKG Kronos` * **Description (122 ch):** `Learn how to seamlessly integrate Empuls with UKG Kronos to automate workforce data synchronization across both platforms.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 225 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **64/100** | **Issues detected:** * Title is short (10 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (225 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/other/sftp` — 64/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/sftp](https://help-empuls.xoxoday.com/admin/integrations/other/sftp) * **Title (17 ch):** `SFTP integrations` * **Description (128 ch):** `Sync employee and transaction data between Empuls and your systems over secure SFTP transfer. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 162 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 1/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 9/10 | | **Overall** | **64/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (162 words) — expand to at least 300 words with examples, prerequisites, and outcomes. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (1/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `demo-library/manual-automated-gifts` — 64/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/manual-automated-gifts](https://help-empuls.xoxoday.com/demo-library/manual-automated-gifts) * **Title (24 ch):** `Manual & Automated Gifts` * **Description (122 ch):** `Watch a walkthrough of manual and automated gifting on Empuls, covering setting up one-time and lifecycle-triggered gifts.` * **Body H1/H2/H3:** 0 / 1 / 2 · **Words:** 260 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **64/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (260 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `demo-library/recognize-peers` — 64/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/recognize-peers](https://help-empuls.xoxoday.com/demo-library/recognize-peers) * **Title (35 ch):** `Recognise Your Peers & Team Members` * **Description (129 ch):** `Watch a walkthrough of peer-to-peer recognition on Empuls, covering how employees send recognition and appreciation to teammates.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 134 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **64/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (134 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/smart-recognition` — 64/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/smart-recognition](https://help-empuls.xoxoday.com/demo-library/smart-recognition) * **Title (27 ch):** `Smart Recognition on Empuls` * **Description (142 ch):** `See AI-powered smart recognition in action on Empuls, with how AI helps write more meaningful, less biased recognition explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 112 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **64/100** | **Issues detected:** * Title is short (27 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (112 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/consultation-partners/fayredge` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/fayredge](https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/fayredge) * **Title (8 ch):** `FayrEdge` * **Description (132 ch):** `Connect FayrEdge with Empuls to combine multi-stakeholder culture and experience insights with your recognition and engagement data.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 318 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/financial-wellbeing/salaryse` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/salaryse](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/salaryse) * **Title (53 ch):** `Enable financial wellness & flexibility with Salaryse` * **Description (101 ch):** `SalarySe integrates with Empuls so employees can get flexible salary advances without switching apps.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 264 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 7/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Description is 101 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Title implies a how-to but page has no `` block — convert numbered instructions to `` for HowTo schema. * Content is short (264 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/health-wellness/employee-wellness-support-with-samvedna-care` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/employee-wellness-support-with-samvedna-care](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/employee-wellness-support-with-samvedna-care) * **Title (44 ch):** `Employee wellness support with Samvedna Care` * **Description (144 ch):** `Add mental health counselling for employees to your benefits program with the Samvedna Care and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 234 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (234 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/health-wellness/empower-employee-mental-wellness-with-your-dost` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/empower-employee-mental-wellness-with-your-dost](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/empower-employee-mental-wellness-with-your-dost) * **Title (47 ch):** `Empower employee mental wellness with Your DOST` * **Description (141 ch):** `Add confidential mental wellness counselling to your benefits program with the Your DOST and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 263 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (263 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/hrms/hrone` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/hrone](https://help-empuls.xoxoday.com/admin/integrations/hrms/hrone) * **Title (5 ch):** `HROne` * **Description (102 ch):** `Connect HROne with Empuls to power your HRMS integration across HR, rewards, and engagement workflows.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 218 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (5 chars) — add descriptive keywords to reach \~50–60. * Description is 102 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (218 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/hrms/paycom` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/paycom](https://help-empuls.xoxoday.com/admin/integrations/hrms/paycom) * **Title (6 ch):** `Paycom` * **Description (113 ch):** `Seamlessly integrate Emplus with Paycom to power your HRMS integration for automated employee account management.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 180 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (6 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (180 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/hrms/peopleforce` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/peopleforce](https://help-empuls.xoxoday.com/admin/integrations/hrms/peopleforce) * **Title (11 ch):** `PeopleForce` * **Description (164 ch):** `Seamlessly integrate Emplus with PeopleForce. Bring PeopleForce data into Empuls to automate onboarding, exits, and recognition workflows without manual data entry.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 158 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Description is 164 chars — slightly over the 160-char SERP cutoff. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (158 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/hrms/peoplestrong` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/peoplestrong](https://help-empuls.xoxoday.com/admin/integrations/hrms/peoplestrong) * **Title (12 ch):** `PeopleStrong` * **Description (118 ch):** `Learn how the PeopleStrong and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards.` * **Body H1/H2/H3:** 0 / 1 / 3 · **Words:** 530 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/integrations/other/logs` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/logs](https://help-empuls.xoxoday.com/admin/integrations/other/logs) * **Title (4 ch):** `Logs` * **Description (136 ch):** `Monitor and troubleshoot Empuls integration activity using detailed event logs. Admins can configure this from the Empuls control panel.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 341 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (4 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/sales-incentive/updates/october-2025` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/october-2025](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/october-2025) * **Title (12 ch):** `October 2025` * **Description (110 ch):** `See what's new in Empuls’s sales incentive module for October 2025: feature releases, improvements, and fixes.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 302 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `demo-library/budget-management` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/budget-management](https://help-empuls.xoxoday.com/demo-library/budget-management) * **Title (28 ch):** `Budget Creation & Management` * **Description (121 ch):** `This demo shows recognition budget management in Empuls, including creating and distributing reward budgets across teams.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 181 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (28 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (181 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/how-to-recognise` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/how-to-recognise](https://help-empuls.xoxoday.com/demo-library/how-to-recognise) * **Title (26 ch):** `How to Recognise on Empuls` * **Description (114 ch):** `Watch a walkthrough of sending recognition on Empuls, covering how to send recognition and appreciation on Empuls.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 109 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (26 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (109 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/redeem-points` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/redeem-points](https://help-empuls.xoxoday.com/demo-library/redeem-points) * **Title (26 ch):** `Redeeming Points on Empuls` * **Description (119 ch):** `Watch a walkthrough of redeeming reward points on Empuls, covering how employees browse and redeem their earned points.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 112 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (26 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (112 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/reward-campaigns` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/reward-campaigns](https://help-empuls.xoxoday.com/demo-library/reward-campaigns) * **Title (23 ch):** `Set Up Reward Campaigns` * **Description (121 ch):** `See reward campaigns in action on Empuls, with launching structured reward campaigns across teams explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 192 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (23 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (192 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/shop-management` — 65/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/shop-management](https://help-empuls.xoxoday.com/demo-library/shop-management) * **Title (24 ch):** `Shop Category Management` * **Description (116 ch):** `This demo shows redemption shop management in Empuls, including adding products and managing gift card availability.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 123 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **65/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (123 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/integrations/financial-wellbeing/vestd` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/vestd](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/vestd) * **Title (41 ch):** `Empower ownership & engagement with Vestd` * **Description (119 ch):** `Add employee ownership and equity plans to your Empuls benefits stack with the Vestd integration, configured by admins.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 276 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (276 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/health-wellness/fitness-challenges` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fitness-challenges](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fitness-challenges) * **Title (18 ch):** `Fitness challenges` * **Description (164 ch):** `Bring gamified fitness challenges with leaderboards and rewards to your team by integrating fitness challenges with Empuls, all tracked from one wellness dashboard.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 763 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 1/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Description is 164 chars — slightly over the 160-char SERP cutoff. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **title (1/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/health-wellness/healthysure` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/healthysure](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/healthysure) * **Title (51 ch):** `Simplify employee health insurance with HealthySure` * **Description (127 ch):** `HealthySure integrates with Empuls so every employee can access affordable group health insurance without leaving the platform.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 272 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (272 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/hrms/emgage-integration` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/emgage-integration](https://help-empuls.xoxoday.com/admin/integrations/hrms/emgage-integration) * **Title (50 ch):** `Automate HR & payroll data with Emgage integration` * **Description (112 ch):** `Automate HR and payroll data sync between Emgage and Empuls to trigger recognition instantly for every employee.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 250 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (250 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/hrms/keka` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/keka](https://help-empuls.xoxoday.com/admin/integrations/hrms/keka) * **Title (4 ch):** `Keka` * **Description (110 ch):** `Learn how the Keka and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 240 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 9/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (4 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (240 words) — expand toward 500+ where useful. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/hrms/other-hrms-custom-api` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/other-hrms-custom-api](https://help-empuls.xoxoday.com/admin/integrations/hrms/other-hrms-custom-api) * **Title (23 ch):** `Other HRMS (custom API)` * **Description (111 ch):** `Connect Other HRMS (custom API) with Empuls to automate employee data sync and extend your engagement programs.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 374 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (23 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/ld-benefits/great-learning` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/great-learning](https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/great-learning) * **Title (42 ch):** `Upskill your workforce with Great Learning` * **Description (128 ch):** `Connect Great Learning with Empuls to offer employees upskilling courses and certifications as part of their perks and benefits.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 271 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (271 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/ld-benefits/simplilearn` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/simplilearn](https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/simplilearn) * **Title (49 ch):** `Upskill employees with Simplilearn online courses` * **Description (119 ch):** `Simplilearn integrates with Empuls so employees can enrol in online professional courses directly from the perks store.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 265 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (265 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/other/database-management` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/database-management](https://help-empuls.xoxoday.com/admin/integrations/other/database-management) * **Title (19 ch):** `Database management` * **Description (127 ch):** `Manage the databases behind your Empuls instance, including backups and access controls. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 155 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 7/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Title implies a how-to but page has no `` block — convert numbered instructions to `` for HowTo schema. * Thin content (155 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (7/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/zoho` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/zoho](https://help-empuls.xoxoday.com/admin/integrations/zoho) * **Title (4 ch):** `Zoho` * **Description (119 ch):** `Connect Zoho People for HR sync, Zoho CRM for sales recognition, or Zoho Mail — one OAuth flow, multiple Zoho products.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 468 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (4 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/programs/awards/introduction-to-awards` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards/introduction-to-awards](https://help-empuls.xoxoday.com/admin/programs/awards/introduction-to-awards) * **Title (15 ch):** `Types of awards` * **Description (101 ch):** `See the different award types available in Empuls’s employee awards program and when to use each one.` * **Body H1/H2/H3:** 0 / 1 / 4 · **Words:** 433 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * Description is 101 chars — extend to 130–160 with search terms. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/sales-incentive/admin-guide/communication/groups` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/communication/groups](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/communication/groups) * **Title (6 ch):** `Groups` * **Description (124 ch):** `Use communication groups to keep sales teams aligned on incentive plan updates. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 397 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (6 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/sales-incentive/updates/jan-feb-2026` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/jan-feb-2026](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/jan-feb-2026) * **Title (12 ch):** `Jan-Feb 2026` * **Description (123 ch):** `See what's new in Empuls’s sales incentive module for January and February 2026: feature releases, improvements, and fixes.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 294 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (294 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/sales-incentive/updates/november-2024` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/november-2024](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/november-2024) * **Title (13 ch):** `November 2024` * **Description (116 ch):** `Explore Empuls’s sales incentive module’s product updates for November 2024, covering new features and improvements.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 318 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * No H2 sections — add scannable H2 headings for structure and jump links. * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `demo-library/awards-core-values` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/awards-core-values](https://help-empuls.xoxoday.com/demo-library/awards-core-values) * **Title (26 ch):** `Awards & Core Values Setup` * **Description (132 ch):** `See awards and core values setup in action on Empuls, with configuring spot, jury, and approval-based awards explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 2 · **Words:** 204 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Title is short (26 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (204 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `demo-library/custom-notifications` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/custom-notifications](https://help-empuls.xoxoday.com/demo-library/custom-notifications) * **Title (32 ch):** `Configuring Custom Notifications` * **Description (132 ch):** `See custom notifications in action on Empuls, with tuning channel, timing, and content for each notification explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 104 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (104 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/platform-branding` — 66/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/platform-branding](https://help-empuls.xoxoday.com/demo-library/platform-branding) * **Title (33 ch):** `Platform Branding & Customization` * **Description (118 ch):** `This demo shows platform branding in Empuls, including customising Empuls with your colors, logo, and homepage layout.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 203 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **66/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (203 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/integrations/financial-wellbeing/mobikwik` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/mobikwik](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/mobikwik) * **Title (56 ch):** `Enable easy digital payments and recharges with MobiKwik` * **Description (110 ch):** `Extend your financial wellness program by integrating MobiKwik with Empuls for digital payments and recharges.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 263 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 7/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Title implies a how-to but page has no `` block — convert numbered instructions to `` for HowTo schema. * Content is short (263 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **intent (7/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/health-wellness/seamless-mental-wellness-support-through-silver-oak-health` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/seamless-mental-wellness-support-through-silver-oak-health](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/seamless-mental-wellness-support-through-silver-oak-health) * **Title (58 ch):** `Seamless mental wellness support through Silver Oak Health` * **Description (143 ch):** `Bring therapist-led mental wellness support to your team by integrating Silver Oak Health with Empuls, all tracked from one wellness dashboard.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 321 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/hrms/ukg-ready` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/ukg-ready](https://help-empuls.xoxoday.com/admin/integrations/hrms/ukg-ready) * **Title (9 ch):** `UKG Ready` * **Description (115 ch):** `Learn how the UKG Ready and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards.` * **Body H1/H2/H3:** 2 / 3 / 0 · **Words:** 697 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 1/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 9/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Body contains 2 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h1 (1/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/hrms/workday` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/workday](https://help-empuls.xoxoday.com/admin/integrations/hrms/workday) * **Title (7 ch):** `Workday` * **Description (104 ch):** `Learn how to seamlessly integrate Emplus with Workday to automate the user account management processes.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 431 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (7 chars) — add descriptive keywords to reach \~50–60. * Description is 104 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/platform-settings/homepage-templates` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/platform-settings/homepage-templates](https://help-empuls.xoxoday.com/admin/platform-settings/homepage-templates) * **Title (15 ch):** `Homepage editor` * **Description (168 ch):** `Design and manage the Empuls homepage with a drag-and-drop editor, pre-built templates, custom widgets, and personalized content blocks for different employee segments.` * **Body H1/H2/H3:** 3 / 6 / 3 · **Words:** 468 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 1/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * Description is 168 chars — slightly over the 160-char SERP cutoff. * Body contains 3 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h1 (1/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/sales-incentive/admin-guide/dashboard/dashboard` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/dashboard/dashboard](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/dashboard/dashboard) * **Title (9 ch):** `Dashboard` * **Description (125 ch):** `Get an overview of the widgets and metrics available on the sales incentive dashboard. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 12 / 0 · **Words:** 502 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/admin-guide/plans/app` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/app](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/app) * **Title (3 ch):** `App` * **Description (130 ch):** `See how sales incentive plans appear and behave in the Empuls mobile app. Admins can configure this from the Empuls control panel.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 443 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (3 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/sales-incentive/integrations/sdk-integration` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/sdk-integration](https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/sdk-integration) * **Title (15 ch):** `SDK Integration` * **Description (123 ch):** `Embed Compass in your client application using the Compass SDK so users access it seamlessly within your existing platform.` * **Body H1/H2/H3:** 0 / 7 / 7 · **Words:** 552 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/updates/august-2025` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/august-2025](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/august-2025) * **Title (11 ch):** `August 2025` * **Description (114 ch):** `Explore Empuls’s sales incentive module’s product updates for August 2025, covering new features and improvements.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 400 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/updates/september-2025` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/september-2025](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/september-2025) * **Title (14 ch):** `September 2025` * **Description (117 ch):** `Explore Empuls’s sales incentive module’s product updates for September 2025, covering new features and improvements.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 402 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (14 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/surveys/drivers/hygiene-factors` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/drivers/hygiene-factors](https://help-empuls.xoxoday.com/admin/surveys/drivers/hygiene-factors) * **Title (23 ch):** `Hygiene factors at work` * **Description (111 ch):** `Understand the hygiene-factors driver in Empuls’s engagement survey analysis, covering pay and work conditions.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 3170 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (23 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `demo-library/employee-management` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/employee-management](https://help-empuls.xoxoday.com/demo-library/employee-management) * **Title (54 ch):** `Employee Management — Adding, Editing & Access Control` * **Description (122 ch):** `This demo shows employee management in Empuls, including adding employees, setting access, and configuring authentication.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 182 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (182 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `demo-library/platform-reports` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/platform-reports](https://help-empuls.xoxoday.com/demo-library/platform-reports) * **Title (27 ch):** `Platform Reports Management` * **Description (136 ch):** `See platform reporting in action on Empuls, with navigating Empuls’s built-in recognition and engagement reports explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 170 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (27 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (170 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/redeem-gift-vouchers` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/redeem-gift-vouchers](https://help-empuls.xoxoday.com/demo-library/redeem-gift-vouchers) * **Title (33 ch):** `Redeem Gift Vouchers on Perkstore` * **Description (123 ch):** `Watch a walkthrough of gift voucher redemption on Empuls, covering redeeming gift vouchers and deals through the Perkstore.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 153 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (153 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `employees/redemption/order-history` — 67/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/redemption/order-history](https://help-empuls.xoxoday.com/employees/redemption/order-history) * **Title (13 ch):** `Order history` * **Description (138 ch):** `Learn how to use order history in Empuls, part of Empuls's reward redemption tools for HR and people teams. Built for HR and people teams.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 180 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **67/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Thin content (180 words) — expand to at least 300 words with examples, prerequisites, and outcomes. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/integrations/consultation-partners/acengage` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/acengage](https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/acengage) * **Title (8 ch):** `AceNgage` * **Description (123 ch):** `AceNgage integrates with Empuls to bring employee sentiment and engagement data into a single engagement view for HR teams.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 439 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/consultation-partners/we360` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/we360](https://help-empuls.xoxoday.com/admin/integrations/consultation-partners/we360) * **Title (57 ch):** `We360.AI: smarter workforce intelligence for modern teams` * **Description (132 ch):** `Sync We360.AI data with Empuls to act on workforce productivity and engagement analytics alongside recognition and rewards insights.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 272 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (272 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/health-wellness/elevate-medical` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/elevate-medical](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/elevate-medical) * **Title (57 ch):** `Achieve lasting wellness with Elevate Medical weight loss` * **Description (154 ch):** `Connect Elevate Medical with Empuls to give employees access to medically supervised weight-loss programs, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 270 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (270 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/health-wellness/fix-health` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fix-health](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fix-health) * **Title (40 ch):** `Physiotherapy & wellness with Fix Health` * **Description (133 ch):** `Fix Health integrates with Empuls so every employee can access physiotherapy and pain-recovery sessions without leaving the platform.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 234 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (234 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/health-wellness/mindpeers` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/mindpeers](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/mindpeers) * **Title (42 ch):** `Build mentally strong teams with MindPeers` * **Description (142 ch):** `Connect MindPeers with Empuls to give employees access to workplace mental health assessments, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 268 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (268 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/health-wellness/orange-health` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/orange-health](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/orange-health) * **Title (42 ch):** `Fast diagnostic testing with orange health` * **Description (133 ch):** `Bring fast at-home diagnostic testing to your team by integrating Orange Health with Empuls, all tracked from one wellness dashboard.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 263 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (263 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/health-wellness/thyrocare` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/thyrocare](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/thyrocare) * **Title (41 ch):** `Preventive health checkups with Thyrocare` * **Description (135 ch):** `Thyrocare integrates with Empuls so every employee can access preventive diagnostic and lab test packages without leaving the platform.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 237 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (237 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/health-wellness/welleazy` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/welleazy](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/welleazy) * **Title (57 ch):** `Enhancing employee health and engagement through Welleazy` * **Description (141 ch):** `Connect Welleazy with Empuls to give employees access to curated corporate wellness programs, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 274 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (274 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/hrms/sap-successfactors-native` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/sap-successfactors-native](https://help-empuls.xoxoday.com/admin/integrations/hrms/sap-successfactors-native) * **Title (47 ch):** `Empuls native integration in SAP SuccessFactors` * **Description (58 ch):** `Experience Seamless Recognition and engagement experience.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 502 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 3/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Description is 58 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **desc (3/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/insurance-benefits/nova-benefits` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/nova-benefits](https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/nova-benefits) * **Title (42 ch):** `Smart employee benefits with Nova Benefits` * **Description (127 ch):** `Nova Benefits integrates with Empuls to bring employees group insurance and employee benefits, managed from a single dashboard.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 323 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/openai` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/openai](https://help-empuls.xoxoday.com/admin/integrations/openai) * **Title (6 ch):** `OpenAI` * **Description (142 ch):** `Connect your own OpenAI API key for Empuls AI features — AI writing assistance, content moderation, skill mapping — using a model you control.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 450 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Title is short (6 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/sales-incentive/admin-guide/data-integrations/connections` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/data-integrations/connections](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/data-integrations/connections) * **Title (11 ch):** `Connections` * **Description (114 ch):** `Set up and manage data source connections that feed your sales incentive plans. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 417 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/sales-incentive/admin-guide/data-integrations/managing-data-sources` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/data-integrations/managing-data-sources](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/data-integrations/managing-data-sources) * **Title (21 ch):** `Managing data sources` * **Description (119 ch):** `Configure and maintain the data sources that power sales incentive calculations. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 409 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/sales-incentive/admin-guide/plans/hidden-plans` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/hidden-plans](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/hidden-plans) * **Title (12 ch):** `Hidden plans` * **Description (123 ch):** `Learn how hidden plans work and when to use them in Empuls’s sales incentive module. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 417 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `demo-library/compass-data-integrations` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/compass-data-integrations](https://help-empuls.xoxoday.com/demo-library/compass-data-integrations) * **Title (39 ch):** `User data, integrations and connections` * **Description (121 ch):** `Upload user and sales data, add integrations, and create connections in Compass — walked through with a test user, Carol.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 342 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/custom-leaderboards` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/custom-leaderboards](https://help-empuls.xoxoday.com/demo-library/custom-leaderboards) * **Title (39 ch):** `Creating & Managing Custom Leaderboards` * **Description (131 ch):** `See custom leaderboards in action on Empuls, with building milestone-based leaderboards to drive engagement explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 211 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (211 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `employees/benefits/perks-overview` — 68/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/benefits/perks-overview](https://help-empuls.xoxoday.com/employees/benefits/perks-overview) * **Title (11 ch):** `Perks store` * **Description (186 ch):** `Explore Empuls Perks like discounted gift cards, exclusive deals, cashback offers, and corporate partnerships across 25+ categories, free for all employees and learn how to reedem perks.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 759 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 5/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **68/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Description is 186 chars — Google truncates around 155–160. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (5/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/giphy` — 69/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/giphy](https://help-empuls.xoxoday.com/admin/integrations/giphy) * **Title (5 ch):** `Giphy` * **Description (126 ch):** `Enable the Giphy integration so employees can attach GIFs to feed posts, comments, and recognitions through a built-in picker.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 369 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **69/100** | **Issues detected:** * Title is short (5 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/reports/overview` — 69/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/reports/overview](https://help-empuls.xoxoday.com/admin/reports/overview) * **Title (8 ch):** `Overview` * **Description (148 ch):** `Real-time, data-driven insights for Super Admins, HR leaders, and managers — recognition, budget, redemption, gifting, raw data, and custom reports.` * **Body H1/H2/H3:** 6 / 39 / 57 · **Words:** 3143 · **Internal links:** 7 · **Images:** 7 (empty alt: 0, generic filename: 7) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 0/10 | | 2. Meta description | 10/10 | | 3. H1 | 1/10 | | 4. H2 structure | 5/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **69/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Title "Overview" is boilerplate — prefix with the product area (e.g. "Reward campaigns overview"). * Body contains 6 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * Heading levels skip (e.g. H2 → H4). Fix hierarchy so levels increase by one. * 7 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (0/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h1 (1/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **h2 (5/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/sales-incentive/admin-guide/plans/plan-settings` — 69/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/plan-settings](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/plan-settings) * **Title (13 ch):** `Plan settings` * **Description (116 ch):** `Manage the configuration settings for individual sales incentive plans in Empuls. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 1239 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **69/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/integrations/hubspot-integration` — 69/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/hubspot-integration](https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/hubspot-integration) * **Title (19 ch):** `HubSpot integration` * **Description (146 ch):** `Sync HubSpot deal and pipeline data into Empuls to automate sales incentive calculations. Admins can configure this from the Empuls control panel.` * **Body H1/H2/H3:** 0 / 15 / 0 · **Words:** 1192 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **69/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/sales-incentive/updates/jan-feb-march-2024` — 69/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/jan-feb-march-2024](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/jan-feb-march-2024) * **Title (18 ch):** `Jan-Feb-March 2024` * **Description (129 ch):** `Explore Empuls’s sales incentive module’s product updates for January through March 2024, covering new features and improvements.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 525 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **69/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/security/privacy-policy` — 69/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/security/privacy-policy](https://help-empuls.xoxoday.com/admin/security/privacy-policy) * **Title (14 ch):** `Privacy policy` * **Description (172 ch):** `Read the Empuls privacy policy to understand how we collect, use, store, and protect personal data in compliance with GDPR and other applicable data protection regulations.` * **Body H1/H2/H3:** 0 / 10 / 4 · **Words:** 800 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **69/100** | **Issues detected:** * Title is short (14 chars) — add descriptive keywords to reach \~50–60. * Description is 172 chars — slightly over the 160-char SERP cutoff. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/user-authentication/ping-identity-sso` — 69/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/ping-identity-sso](https://help-empuls.xoxoday.com/admin/user-authentication/ping-identity-sso) * **Title (17 ch):** `Ping Identity SSO` * **Description (153 ch):** `Set up Ping Identity SSO in Empuls for enterprise-grade single sign-on, giving employees secure access with their existing identity provider credentials.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 553 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **69/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `demo-library/bulk-nominations` — 69/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/bulk-nominations](https://help-empuls.xoxoday.com/demo-library/bulk-nominations) * **Title (37 ch):** `Bulk Nomination Approval & Management` * **Description (139 ch):** `See bulk nomination management in action on Empuls, with approving, declining, and transferring nominations in bulk explained step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 140 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **69/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (140 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `employees/getting-started/log-in` — 69/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/getting-started/log-in](https://help-empuls.xoxoday.com/employees/getting-started/log-in) * **Title (5 ch):** `Login` * **Description (125 ch):** `Sign in to Empuls on web or mobile using email, OTP, single sign-on, or your mobile number, whichever your admin has enabled.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 682 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **69/100** | **Issues detected:** * Title is short (5 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/admin-guide/plans/tracking-user-performance-and-metric-breakdown` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/tracking-user-performance-and-metric-breakdown](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/tracking-user-performance-and-metric-breakdown) * **Title (46 ch):** `Tracking user performance and metric breakdown` * **Description (148 ch):** `Track individual rep performance and metric-level breakdowns inside a sales incentive plan. Admins can configure this from the Empuls control panel.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 362 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **70/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/sales-incentive/admin-guide/reports` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/reports](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/reports) * **Title (7 ch):** `Reports` * **Description (120 ch):** `See the different report types available in Empuls’s sales incentive admin panel. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 11 / 7 · **Words:** 1734 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **70/100** | **Issues detected:** * Title is short (7 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/updates/april-may-june-2024` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/april-may-june-2024](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/april-may-june-2024) * **Title (19 ch):** `April-May-June 2024` * **Description (118 ch):** `Catch up on everything Empuls’s sales incentive module shipped in April through June 2024, from new features to fixes.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 378 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 9/10 | | **Overall** | **70/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/sales-incentive/updates/october-2024` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/updates/october-2024](https://help-empuls.xoxoday.com/admin/sales-incentive/updates/october-2024) * **Title (13 ch):** `October- 2024` * **Description (115 ch):** `Explore Empuls’s sales incentive module’s product updates for October 2024, covering new features and improvements.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 365 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **70/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/security/information-security` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/security/information-security](https://help-empuls.xoxoday.com/admin/security/information-security) * **Title (14 ch):** `Certifications` * **Description (159 ch):** `Review Empuls's security certifications, compliance frameworks, and third-party audit reports that validate our commitment to enterprise-grade data protection.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 754 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **70/100** | **Issues detected:** * Title is short (14 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/security/responsible-ai` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/security/responsible-ai](https://help-empuls.xoxoday.com/admin/security/responsible-ai) * **Title (9 ch):** `AI policy` * **Description (164 ch):** `Learn about Empuls's responsible AI principles, how AI features are built and governed, and the safeguards in place to ensure fair, transparent, and ethical AI use.` * **Body H1/H2/H3:** 0 / 5 / 6 · **Words:** 851 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **70/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Description is 164 chars — slightly over the 160-char SERP cutoff. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/user-authentication/onelogin-sso` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/onelogin-sso](https://help-empuls.xoxoday.com/admin/user-authentication/onelogin-sso) * **Title (12 ch):** `OneLogin SSO` * **Description (131 ch):** `Configure OneLogin as your SSO provider for Empuls, enabling employees to log in securely with their existing identity credentials.` * **Body H1/H2/H3:** 0 / 3 / 8 · **Words:** 538 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **70/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `demo-library/demo-library` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/demo-library](https://help-empuls.xoxoday.com/demo-library/demo-library) * **Title (18 ch):** `Demo Video Library` * **Description (143 ch):** `See the full library of Empuls demo videos in action on Empuls, with every major feature, from recognition to reporting explained step by step.` * **Body H1/H2/H3:** 0 / 12 / 0 · **Words:** 661 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **70/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `employees/recognitions/jury-ratings` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/recognitions/jury-ratings](https://help-empuls.xoxoday.com/employees/recognitions/jury-ratings) * **Title (28 ch):** `Rating nominations as a jury` * **Description (140 ch):** `Set up Jury-based awards in Empuls by involving a panel of evaluators who rate nominations independently before a moderator selects winners.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 275 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **70/100** | **Issues detected:** * Title is short (28 chars) — add descriptive keywords to reach \~50–60. * No H2 sections — add scannable H2 headings for structure and jump links. * Content is short (275 words) — expand toward 500+ where useful. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `employees/socials/people-directory` — 70/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/socials/people-directory](https://help-empuls.xoxoday.com/employees/socials/people-directory) * **Title (16 ch):** `People directory` * **Description (162 ch):** `Use the Empuls people directory to search for colleagues by name, department, or location, view profiles, see org chart relationships, and connect with your team.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 146 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **70/100** | **Issues detected:** * Title is short (16 chars) — add descriptive keywords to reach \~50–60. * Description is 162 chars — slightly over the 160-char SERP cutoff. * Thin content (146 words) — expand to at least 300 words with examples, prerequisites, and outcomes. * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/finance/points-administration` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/finance/points-administration](https://help-empuls.xoxoday.com/admin/finance/points-administration) * **Title (21 ch):** `Points administration` * **Description (186 ch):** `Learn how to manage the points your organization issues and redeems. Recharging your wallets, auditing movement, fixing unmapped transactions, and runing point-history reports in Empuls.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 575 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 5/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * Description is 186 chars — Google truncates around 155–160. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (5/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/truworth-wellness` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/truworth-wellness](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/truworth-wellness) * **Title (49 ch):** `Empower employee wellbeing with TruWorth Wellness` * **Description (153 ch):** `Connect TruWorth Wellness with Empuls to give employees access to corporate wellbeing screening programs, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 270 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (270 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/linkedin` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/linkedin](https://help-empuls.xoxoday.com/admin/integrations/linkedin) * **Title (8 ch):** `LinkedIn` * **Description (133 ch):** `Connect LinkedIn to Empuls so employees can share recognition to their LinkedIn profiles and your team can amplify awards externally.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 403 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/platform-settings/faqs` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/platform-settings/faqs](https://help-empuls.xoxoday.com/admin/platform-settings/faqs) * **Title (31 ch):** `Customization and communication` * **Description (105 ch):** `Get quick answers about perks and benefits on Empuls to setup steps, edge cases, and troubleshooting tips` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 1232 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Description is 105 chars — extend to 130–160 with search terms. * No H2 sections — add scannable H2 headings for structure and jump links. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/admin-guide/data-integrations/users` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/data-integrations/users](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/data-integrations/users) * **Title (5 ch):** `Users` * **Description (136 ch):** `Manage user-level data, including enabling, disabling, and downloading records. Admins can configure this from the Empuls control panel.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 1361 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (5 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/admin-guide/faq-admins/communication-faqs` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/faq-admins/communication-faqs](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/faq-admins/communication-faqs) * **Title (18 ch):** `Communication FAQs` * **Description (116 ch):** `Get quick answers about sales incentive communication on Empuls - setup steps, edge cases, and troubleshooting tips.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 196 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (196 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/sales-incentive/admin-guide/plans/plan-creation-and-types` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/plan-creation-and-types](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/plan-creation-and-types) * **Title (23 ch):** `Plan creation and types` * **Description (137 ch):** `Learn the different plan types available and how to create a sales incentive plan in Empuls. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 358 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (23 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/sales-incentive/admin-guide/plans/plan-labels` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/plan-labels](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/plan-labels) * **Title (11 ch):** `Plan labels` * **Description (127 ch):** `Create plan labels to organize and categorize sales incentive plans in Empuls. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 0 / 7 / 1 · **Words:** 724 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/surveys/action-plan` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/action-plan](https://help-empuls.xoxoday.com/admin/surveys/action-plan) * **Title (11 ch):** `Action plan` * **Description (172 ch):** `Create and manage action plans in Empuls based on survey results, assign owners, set deadlines, track progress, and close the loop with employees on the changes being made.` * **Body H1/H2/H3:** 0 / 1 / 4 · **Words:** 302 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Description is 172 chars — slightly over the 160-char SERP cutoff. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `demo-library/compass-groups-reports` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/compass-groups-reports](https://help-empuls.xoxoday.com/demo-library/compass-groups-reports) * **Title (31 ch):** `Groups, reports and escalations` * **Description (123 ch):** `Communicate with users through groups, monitor account activity through reports, and resolve queries raised as escalations.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 307 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `demo-library/compass-plans-metrics` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/compass-plans-metrics](https://help-empuls.xoxoday.com/demo-library/compass-plans-metrics) * **Title (43 ch):** `Creating and implementing plans and metrics` * **Description (112 ch):** `Turn a connection into a metric, then wrap that metric in a milestone plan with rewards — end-to-end in Compass.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 422 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `demo-library/compass-user-walkthrough` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/compass-user-walkthrough](https://help-empuls.xoxoday.com/demo-library/compass-user-walkthrough) * **Title (29 ch):** `Complete end user walkthrough` * **Description (154 ch):** `The complete guide to learn about Compass end-user experience on web and mobile dashboards, plans, teams, earnings, leaderboards, escalations, and groups.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 470 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (29 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `employees/benefits/multi-benefits-card` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/benefits/multi-benefits-card](https://help-empuls.xoxoday.com/employees/benefits/multi-benefits-card) * **Title (19 ch):** `Multi benefits card` * **Description (143 ch):** `Learn how to use your Empuls Multi-Benefit Card to spend tax-free across meals, fuel, books, telecom, and more, boosting your take-home salary.` * **Body H1/H2/H3:** 0 / 10 / 0 · **Words:** 881 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 1/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **title (1/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `employees/engagement/quick-links` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/engagement/quick-links](https://help-empuls.xoxoday.com/employees/engagement/quick-links) * **Title (11 ch):** `Quick links` * **Description (162 ch):** `Add and manage quick links in Empuls to give employees one-click access to important tools, internal resources, and external platforms directly from the homepage.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 332 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 9/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Description is 162 chars — slightly over the 160-char SERP cutoff. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `product-updates/may-2025` — 71/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/product-updates/may-2025](https://help-empuls.xoxoday.com/product-updates/may-2025) * **Title (26 ch):** `Product Updates - May 2025` * **Description (127 ch):** `Catch up on everything Empuls shipped in May 2025, from new features to fixes. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 598 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **71/100** | **Issues detected:** * Title is short (26 chars) — add descriptive keywords to reach \~50–60. * No H2 sections — add scannable H2 headings for structure and jump links. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/benefits/faqs` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/benefits/faqs](https://help-empuls.xoxoday.com/admin/benefits/faqs) * **Title (18 ch):** `Perks and benefits` * **Description (122 ch):** `Find answers to common questions about the reward marketplace on Empuls, covering setup, permissions, and troubleshooting.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 1481 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/benefits/health-wellness` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/benefits/health-wellness](https://help-empuls.xoxoday.com/admin/benefits/health-wellness) * **Title (17 ch):** `Health & wellness` * **Description (169 ch):** `Offer employees comprehensive health and wellness benefits through Empuls by integrating with leading providers for medical, mental health, fitness, and preventive care.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 847 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Description is 169 chars — slightly over the 160-char SERP cutoff. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/financial-wellbeing/invitereferrals` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/invitereferrals](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/invitereferrals) * **Title (52 ch):** `Strengthen your referral engine with InviteReferrals` * **Description (119 ch):** `Add referral program tracking to your Empuls benefits stack with the InviteReferrals integration, configured by admins.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 247 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (247 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/health-wellness/comprehensive-flexibility-mobility-wellness-with-stretchit` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/comprehensive-flexibility-mobility-wellness-with-stretchit](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/comprehensive-flexibility-mobility-wellness-with-stretchit) * **Title (60 ch):** `Comprehensive flexibility & mobility wellness with STRETCHIT` * **Description (141 ch):** `Add guided flexibility and mobility training to your benefits program with the STRETCHIT and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 553 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hris-hrms` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hris-hrms](https://help-empuls.xoxoday.com/admin/integrations/hris-hrms) * **Title (4 ch):** `HRMS` * **Description (145 ch):** `Connect Workday, SAP, Oracle, UKG, and other HR systems to Empuls for automated employee data sync, onboarding triggers, and SFTP bulk transfers.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 1091 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (4 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hrms/greythr` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/greythr](https://help-empuls.xoxoday.com/admin/integrations/hrms/greythr) * **Title (7 ch):** `greytHR` * **Description (73 ch):** `Seamlessly integrate Emplus with greytHR to automate employee management.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 479 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 3/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (7 chars) — add descriptive keywords to reach \~50–60. * Description is 73 chars — extend to 130–160 with search terms. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **desc (3/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/programs/awards/revoke-awards` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards/revoke-awards](https://help-empuls.xoxoday.com/admin/programs/awards/revoke-awards) * **Title (23 ch):** `Revoke awards and gifts` * **Description (140 ch):** `Revoke awards or gifts when a recognition needs to be taken back due to disputes, policy violations, accidental nominations, or human error.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 227 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (23 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (227 words) — expand toward 500+ where useful. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. *** ### `admin/reports/raw-data-report` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/reports/raw-data-report](https://help-empuls.xoxoday.com/admin/reports/raw-data-report) * **Title (15 ch):** `Raw data report` * **Description (99 ch):** `Export granular transaction-level logs for awards, budgets, redemptions, logins, surveys, and more.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 719 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * Description is 99 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/integrations/close-crm-integration` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/close-crm-integration](https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/close-crm-integration) * **Title (21 ch):** `Close CRM integration` * **Description (136 ch):** `Connect Close CRM with Empuls’s sales incentive module to automate commission tracking. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 0 / 18 / 0 · **Words:** 1799 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/sales-incentive/integrations/salesforce-integration` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/salesforce-integration](https://help-empuls.xoxoday.com/admin/sales-incentive/integrations/salesforce-integration) * **Title (22 ch):** `Salesforce integration` * **Description (133 ch):** `Sync Salesforce opportunity data into Empuls to automate sales incentive and commission plans. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 13 / 0 · **Words:** 1097 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (22 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/user-authentication/sso-overview` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/sso-overview](https://help-empuls.xoxoday.com/admin/user-authentication/sso-overview) * **Title (13 ch):** `Login methods` * **Description (178 ch):** `Explore the login methods available in Empuls, including SSO options like Azure AD, Okta, Google Workspace, and SAML 2.0, as well as password-based and magic link authentication.` * **Body H1/H2/H3:** 0 / 5 / 4 · **Words:** 836 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 1/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Description is 178 chars — slightly over the 160-char SERP cutoff. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **title (1/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `employees/recognitions/faqs` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/recognitions/faqs](https://help-empuls.xoxoday.com/employees/recognitions/faqs) * **Title (23 ch):** `Recognition and rewards` * **Description (119 ch):** `Get quick answers about recognition and rewards programs on Empuls - setup steps, edge cases, and troubleshooting tips.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 3845 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (23 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `product-updates/june-2025` — 72/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/product-updates/june-2025](https://help-empuls.xoxoday.com/product-updates/june-2025) * **Title (27 ch):** `Product Updates - June 2025` * **Description (114 ch):** `Catch up on everything Empuls shipped in June 2025, from new features to fixes. No coding required for most teams.` * **Body H1/H2/H3:** 2 / 7 / 0 · **Words:** 698 · **Internal links:** 7 · **Images:** 7 (empty alt: 0, generic filename: 7) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 1/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **72/100** | **Issues detected:** * Title is short (27 chars) — add descriptive keywords to reach \~50–60. * Body contains 2 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 7 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h1 (1/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/collaboration/microsoft-365` — 73/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/microsoft-365](https://help-empuls.xoxoday.com/admin/integrations/collaboration/microsoft-365) * **Title (13 ch):** `Microsoft 365` * **Description (135 ch):** `Bring Empuls recognition and engagement tools into Microsoft 365 by connecting it with Empuls, so employees never have to switch tools.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 379 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **73/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/collaboration/outlook` — 73/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/outlook](https://help-empuls.xoxoday.com/admin/integrations/collaboration/outlook) * **Title (28 ch):** `Adding Empuls app to Outlook` * **Description (116 ch):** `Connect Adding Empuls app to Outlook with Empuls to automate employee data sync and extend your engagement programs.` * **Body H1/H2/H3:** 0 / 15 / 0 · **Words:** 947 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 8/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **73/100** | **Issues detected:** * Title is short (28 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/health-wellness/faqs` — 73/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/faqs](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/faqs) * **Title (24 ch):** `Health & wellness - FAQs` * **Description (121 ch):** `Browse frequently asked questions about health and wellness integrations on Empuls, from setup to day-to-day admin tasks.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 589 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **73/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * No H2 sections — add scannable H2 headings for structure and jump links. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/programs/awards/faqs` — 73/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards/faqs](https://help-empuls.xoxoday.com/admin/programs/awards/faqs) * **Title (23 ch):** `Recognition and rewards` * **Description (139 ch):** `Use Empuls's native app inside SAP SuccessFactors for seamless recognition, rewards, and engagement. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 14 / 0 · **Words:** 11189 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 6/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **73/100** | **Issues detected:** * Title is short (23 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (6/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/programs/launch-communication-kit` — 73/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/programs/launch-communication-kit](https://help-empuls.xoxoday.com/admin/programs/launch-communication-kit) * **Title (24 ch):** `Launch communication kit` * **Description (139 ch):** `Resources for communicating Empuls launch in your organisation — videos, mailer templates, best practices, and downloadable launch posters.` * **Body H1/H2/H3:** 0 / 5 / 8 · **Words:** 620 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **73/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/reports/activity-report` — 73/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/reports/activity-report](https://help-empuls.xoxoday.com/admin/reports/activity-report) * **Title (15 ch):** `Activity report` * **Description (98 ch):** `Track platform adoption, user engagement, and group activity across desktop, mobile, and MS Teams.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 802 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **73/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * Description is 98 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `employees/getting-started/mobile-app` — 73/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/getting-started/mobile-app](https://help-empuls.xoxoday.com/employees/getting-started/mobile-app) * **Title (10 ch):** `Mobile app` * **Description (103 ch):** `Download the Empuls mobile app on iOS or Android to access recognition, rewards, and surveys on the go.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 886 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **73/100** | **Issues detected:** * Title is short (10 chars) — add descriptive keywords to reach \~50–60. * Description is 103 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `employees/getting-started/notifications` — 73/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/getting-started/notifications](https://help-empuls.xoxoday.com/employees/getting-started/notifications) * **Title (19 ch):** `Account preferences` * **Description (76 ch):** `Learn how to update account preferences in Empuls, covering getting started.` * **Body H1/H2/H3:** 0 / 4 / 3 · **Words:** 485 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 3/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **73/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Description is 76 chars — extend to 130–160 with search terms. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **desc (3/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/finance/redemption-wallets` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/finance/redemption-wallets](https://help-empuls.xoxoday.com/admin/finance/redemption-wallets) * **Title (18 ch):** `Redemption wallets` * **Description (108 ch):** `Learn how to use redemption wallets to manage your expenses for a seamless rewards redemption with our guide` * **Body H1/H2/H3:** 1 / 3 / 1 · **Words:** 606 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Description is 108 chars — extend to 130–160 with search terms. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hrms/other-hrms-sftp` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/other-hrms-sftp](https://help-empuls.xoxoday.com/admin/integrations/hrms/other-hrms-sftp) * **Title (17 ch):** `Other HRMS (SFTP)` * **Description (101 ch):** `Sync employee and payroll data with Empuls over SFTP for HRMS platforms without a native integration.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 900 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 8/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Description is 101 chars — extend to 130–160 with search terms. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. *** ### `admin/integrations/other/faqs-data-and-integration` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/faqs-data-and-integration](https://help-empuls.xoxoday.com/admin/integrations/other/faqs-data-and-integration) * **Title (27 ch):** `FAQs - data and integration` * **Description (126 ch):** `Find answers to common questions about data and integration setup on Empuls, covering setup, permissions, and troubleshooting.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 189 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 3/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (27 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Thin content (189 words) — expand to at least 300 words with examples, prerequisites, and outcomes. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (3/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/sales-incentive/admin-guide/data-integrations/manage-users` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/data-integrations/manage-users](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/data-integrations/manage-users) * **Title (12 ch):** `Manage users` * **Description (115 ch):** `Add, update, or remove user accounts inside Empuls’s sales incentive module. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 9 / 3 · **Words:** 647 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 7/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 9/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * Title implies a how-to but page has no `` block — convert numbered instructions to `` for HowTo schema. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (7/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/sales-incentive/admin-guide/plans/cascading` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/cascading](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/cascading) * **Title (9 ch):** `Cascading` * **Description (138 ch):** `See how cascading plans distribute sales incentive targets down through a team hierarchy. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 1327 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/sales-incentive/admin-guide/plans/metrics` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/metrics](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/metrics) * **Title (7 ch):** `Metrics` * **Description (135 ch):** `Configure the metrics that drive payouts in your Empuls sales incentive plans. Admins can configure this from the Empuls control panel.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 897 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (7 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/security/security-settings` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/security/security-settings](https://help-empuls.xoxoday.com/admin/security/security-settings) * **Title (17 ch):** `Security settings` * **Description (159 ch):** `Configure platform security settings in Empuls including IP whitelisting, two-factor authentication enforcement, data retention policies, and audit log access.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 674 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/surveys/type-of-surveys` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/type-of-surveys](https://help-empuls.xoxoday.com/admin/surveys/type-of-surveys) * **Title (16 ch):** `Types of surveys` * **Description (135 ch):** `Explore the full range of Empuls survey types: eNPS, pulse, lifecycle, driver, and custom surveys, and understand when to use each one.` * **Body H1/H2/H3:** 0 / 5 / 3 · **Words:** 356 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (16 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/user-authentication/azure-ad` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/azure-ad](https://help-empuls.xoxoday.com/admin/user-authentication/azure-ad) * **Title (12 ch):** `Azure AD SSO` * **Description (167 ch):** `Connect Empuls to Azure Active Directory for seamless single sign-on, automatic user provisioning via SCIM, and centralized access management across your organization.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 792 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Description is 167 chars — slightly over the 160-char SERP cutoff. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/user-authentication/okta-sso` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/okta-sso](https://help-empuls.xoxoday.com/admin/user-authentication/okta-sso) * **Title (8 ch):** `Okta SSO` * **Description (147 ch):** `Set up Okta SSO with Empuls for secure, one-click employee login, and optionally enable SCIM-based automatic user provisioning from Okta to Empuls.` * **Body H1/H2/H3:** 0 / 10 / 2 · **Words:** 852 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `employees/getting-started/employee-profile` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/getting-started/employee-profile](https://help-empuls.xoxoday.com/employees/getting-started/employee-profile) * **Title (7 ch):** `Profile` * **Description (112 ch):** `Access and update your Empuls profile details, including your contact info, photo, and notification preferences.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 434 · **Internal links:** 8 · **Images:** 8 (empty alt: 0, generic filename: 8) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (7 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 8 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `employees/recognitions/recognition-approvals` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/recognitions/recognition-approvals](https://help-empuls.xoxoday.com/employees/recognitions/recognition-approvals) * **Title (21 ch):** `Recognition approvals` * **Description (99 ch):** `Learn how to review and approve recognition nomiations as well set up automatic approvals in Empuls` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 486 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 8/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * Description is 99 chars — extend to 130–160 with search terms. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `employees/surveys/action-plan` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/surveys/action-plan](https://help-empuls.xoxoday.com/employees/surveys/action-plan) * **Title (12 ch):** `Action plans` * **Description (164 ch):** `View and track action plans created in response to your survey feedback in Empuls, see progress updates, and understand how your input is driving meaningful change.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 513 · **Internal links:** 2 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Description is 164 chars — slightly over the 160-char SERP cutoff. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `product-updates/march-2025` — 74/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/product-updates/march-2025](https://help-empuls.xoxoday.com/product-updates/march-2025) * **Title (28 ch):** `Product Updates - March 2025` * **Description (123 ch):** `Explore Empuls’s product updates for March 2025, covering new features and improvements. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 636 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **74/100** | **Issues detected:** * Title is short (28 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/finance/reward-marketplace-faqs` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/finance/reward-marketplace-faqs](https://help-empuls.xoxoday.com/admin/finance/reward-marketplace-faqs) * **Title (18 ch):** `Reward marketplace` * **Description (126 ch):** `Browse frequently asked questions about the milestone gifting program on Empuls, from initial setup to day-to-day admin tasks.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 1923 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/gifts/gifts` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/gifts/gifts](https://help-empuls.xoxoday.com/admin/gifts/gifts) * **Title (12 ch):** `Manual gifts` * **Description (189 ch):** `Send manual gifts in Empuls by selecting recipients, setting point values and expiry dates, writing a personalised message, and choosing whether to make the gift visible on the social feed.` * **Body H1/H2/H3:** 0 / 10 / 0 · **Words:** 1095 · **Internal links:** 17 · **Images:** 17 (empty alt: 0, generic filename: 17) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 5/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Description is 189 chars — Google truncates around 155–160. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 17 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (5/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/gifts/milestones-faqs` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/gifts/milestones-faqs](https://help-empuls.xoxoday.com/admin/gifts/milestones-faqs) * **Title (17 ch):** `Milestone program` * **Description (121 ch):** `Browse frequently asked questions about employee survey software on Empuls, from initial setup to day-to-day admin tasks.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 2865 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/financial-wellbeing/safe-gold` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/safe-gold](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/safe-gold) * **Title (36 ch):** `Secure gold investing with safe gold` * **Description (103 ch):** `Extend your financial wellness program by integrating Safe Gold with Empuls for digital gold investing.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 322 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Description is 103 chars — extend to 130–160 with search terms. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hrms/sap-successfactors` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/sap-successfactors](https://help-empuls.xoxoday.com/admin/integrations/hrms/sap-successfactors) * **Title (18 ch):** `SAP SuccessFactors` * **Description (123 ch):** `Learn how the SAP SuccessFactors and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 607 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/insurance-benefits/tortoise` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/tortoise](https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/tortoise) * **Title (47 ch):** `Zero-cost employee device leasing with Tortoise` * **Description (109 ch):** `Tortoise integrates with Empuls to bring employees zero-cost device leasing, managed from a single dashboard.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 375 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Description is 109 chars — extend to 130–160 with search terms. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/programs/awards-core-values` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards-core-values](https://help-empuls.xoxoday.com/admin/programs/awards-core-values) * **Title (8 ch):** `Overview` * **Description (149 ch):** `Create spot, approval, jury, and incentive awards; link them to company core values; attach certificates; distribute in bulk; and revoke when needed.` * **Body H1/H2/H3:** 0 / 2 / 6 · **Words:** 1277 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 0/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Title "Overview" is boilerplate — prefix with the product area (e.g. "Reward campaigns overview"). * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **title (0/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/surveys/drivers/strategic-alignment` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/drivers/strategic-alignment](https://help-empuls.xoxoday.com/admin/surveys/drivers/strategic-alignment) * **Title (34 ch):** `Strategic alignment with employees` * **Description (105 ch):** `Understand the strategic-alignment driver in Empuls’s engagement survey analysis and how it’s calculated.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 2092 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Description is 105 chars — extend to 130–160 with search terms. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/surveys/faqs` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/faqs](https://help-empuls.xoxoday.com/admin/surveys/faqs) * **Title (6 ch):** `Survey` * **Description (123 ch):** `Find answers to common questions about employee awards program on Empuls, covering setup, permissions, and troubleshooting.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 2868 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Title is short (6 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `demo-library/compass-overview` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/compass-overview](https://help-empuls.xoxoday.com/demo-library/compass-overview) * **Title (51 ch):** `Overview — Xoxoday Compass Admin & User Walkthrough` * **Description (140 ch):** `Watch a walkthrough of the Compass admin and user walkthrough on Empuls, covering a full tour of the sales incentive console and mobile app.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 427 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `employees/getting-started/faqs` — 75/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/getting-started/faqs](https://help-empuls.xoxoday.com/employees/getting-started/faqs) * **Title (15 ch):** `Getting started` * **Description (124 ch):** `Browse frequently asked questions about getting started with Empuls on Empuls, from initial setup to day-to-day admin tasks.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 2248 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **75/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/financial-wellbeing/jiffy-moneyview` — 76/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/jiffy-moneyview](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/jiffy-moneyview) * **Title (57 ch):** `Accelerate digital transformation with Jiffy by Moneyview` * **Description (120 ch):** `Add instant digital lending to your Empuls benefits stack with the Jiffy by Moneyview integration, configured by admins.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 371 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 9/10 | | **Overall** | **76/100** | **Issues detected:** * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/health-wellness/healthassure` — 76/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/healthassure](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/healthassure) * **Title (54 ch):** `Empower preventive health & wellness with HealthAssure` * **Description (133 ch):** `HealthAssure integrates with Empuls so every employee can access preventive care and wellness screening without leaving the platform.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 284 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 5/10 | | 10. Image optimization | 9/10 | | **Overall** | **76/100** | **Issues detected:** * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * Content is short (284 words) — expand toward 500+ where useful. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (5/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/hrms/adrenalin` — 76/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/adrenalin](https://help-empuls.xoxoday.com/admin/integrations/hrms/adrenalin) * **Title (9 ch):** `Adrenalin` * **Description (115 ch):** `Learn how the Adrenalin and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 317 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 8/10 | | **Overall** | **76/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/programs/awards/bulk-review-of-nominations` — 76/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards/bulk-review-of-nominations](https://help-empuls.xoxoday.com/admin/programs/awards/bulk-review-of-nominations) * **Title (26 ch):** `Bulk review of nominations` * **Description (129 ch):** `Approve, decline, or transfer many award nominations at once using Empuls’s bulk review tools. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 3 / 8 · **Words:** 468 · **Internal links:** 9 · **Images:** 9 (empty alt: 0, generic filename: 9) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **76/100** | **Issues detected:** * Title is short (26 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 9 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `product-updates/december-2025` — 76/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/product-updates/december-2025](https://help-empuls.xoxoday.com/product-updates/december-2025) * **Title (31 ch):** `Product Updates - December 2025` * **Description (136 ch):** `Explore Empuls’s product updates for December 2025, covering new features and improvements. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 0 / 0 · **Words:** 785 · **Internal links:** 7 · **Images:** 7 (empty alt: 0, generic filename: 7) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 3/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **76/100** | **Issues detected:** * No H2 sections — add scannable H2 headings for structure and jump links. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 7 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h2 (3/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `product-updates/january-2025` — 76/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/product-updates/january-2025](https://help-empuls.xoxoday.com/product-updates/january-2025) * **Title (30 ch):** `Product Updates - January 2025` * **Description (127 ch):** `Catch up on everything Empuls shipped in January 2025, from new features to fixes. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 1 / 7 / 0 · **Words:** 572 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **76/100** | **Issues detected:** * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/financial-wellbeing/automint` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/automint](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/automint) * **Title (52 ch):** `Automint’s tax-saving car and device leasing program` * **Description (129 ch):** `Connect Automint with Empuls to give employees access to tax-saving car and device leasing directly from their rewards dashboard.` * **Body H1/H2/H3:** 0 / 7 / 1 · **Words:** 462 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/financial-wellbeing/faqs` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/faqs](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/faqs) * **Title (13 ch):** `Finance: FAQs` * **Description (131 ch):** `Find answers to common questions about financial wellness integrations on Empuls, covering setup, permissions, and troubleshooting.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 1200 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/financial-wellbeing/finsafe` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/finsafe](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/finsafe) * **Title (45 ch):** `Comprehensive financial wellness with FinSafe` * **Description (116 ch):** `Extend your financial wellness program by integrating Finsafe with Empuls for financial literacy and planning tools.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 410 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/financial-wellbeing/liqvid-50fin` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/liqvid-50fin](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/liqvid-50fin) * **Title (46 ch):** `Loans against mutual funds with Liqvid (50fin)` * **Description (117 ch):** `Liqvid (50fin) integrates with Empuls so employees can get loans against mutual fund holdings without switching apps.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 349 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/health-wellness/ambrosian` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/ambrosian](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/ambrosian) * **Title (42 ch):** `Elevate workplace wellbeing with Ambrosian` * **Description (130 ch):** `Add workplace wellbeing resources to your benefits program with the Ambrosian and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 828 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/cult-fit` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/cult-fit](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/cult-fit) * **Title (41 ch):** `Holistic fitness & wellness with Cult.fit` * **Description (126 ch):** `Cult.fit integrates with Empuls so every employee can access gym memberships and fitness classes without leaving the platform.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 486 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/health-wellness/mfine` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/mfine](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/mfine) * **Title (35 ch):** `Smart digital healthcare with MFine` * **Description (132 ch):** `Bring on-demand digital doctor consultations to your team by integrating MFine with Empuls, all tracked from one wellness dashboard.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 431 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 8/10 | | **Overall** | **77/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. *** ### `admin/integrations/health-wellness/opdsure` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/opdsure](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/opdsure) * **Title (48 ch):** `Seamless opd coverage for employees with OpdSure` * **Description (122 ch):** `OPDSure integrates with Empuls so every employee can access outpatient (OPD) health coverage without leaving the platform.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 406 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/hrms/gusto` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/gusto](https://help-empuls.xoxoday.com/admin/integrations/hrms/gusto) * **Title (5 ch):** `Gusto` * **Description (111 ch):** `Learn how the Gusto and Empuls integration works and helps automate employee engagement, recognition & rewards.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 624 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (5 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/hrms/hibob` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/hibob](https://help-empuls.xoxoday.com/admin/integrations/hrms/hibob) * **Title (5 ch):** `HiBob` * **Description (106 ch):** `Learn how HiBob and Empuls integration works and help automate employee engagement, recognition & rewards.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 663 · **Internal links:** 7 · **Images:** 7 (empty alt: 0, generic filename: 7) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (5 chars) — add descriptive keywords to reach \~50–60. * Description is 106 chars — extend to 130–160 with search terms. * 7 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hrms/namely` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/namely](https://help-empuls.xoxoday.com/admin/integrations/hrms/namely) * **Title (6 ch):** `Namely` * **Description (112 ch):** `Learn how the Namely and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 741 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (6 chars) — add descriptive keywords to reach \~50–60. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/hrms/oracle` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/oracle](https://help-empuls.xoxoday.com/admin/integrations/hrms/oracle) * **Title (6 ch):** `Oracle` * **Description (94 ch):** `Connect Oracle with Empuls to automate employee data sync and extend your engagement programs.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 599 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (6 chars) — add descriptive keywords to reach \~50–60. * Description is 94 chars — extend to 130–160 with search terms. * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hrms/rippling` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/rippling](https://help-empuls.xoxoday.com/admin/integrations/hrms/rippling) * **Title (8 ch):** `Rippling` * **Description (91 ch):** `Learn how to seamlessly integrate Emplus with Rippling to automate user management process.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 674 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Description is 91 chars — extend to 130–160 with search terms. * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hrms/workline` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/workline](https://help-empuls.xoxoday.com/admin/integrations/hrms/workline) * **Title (8 ch):** `Workline` * **Description (110 ch):** `Connect Workline with Empuls to automate employee lifecycle events and trigger recognition at every milestone.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 432 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/insurance-benefits/atlys` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/atlys](https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/atlys) * **Title (48 ch):** `Atlys: powering faster, seamless employee travel` * **Description (115 ch):** `Extend your perks catalogue with faster employee travel and visa bookings through the Atlys and Empuls integration.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 352 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/referral-program/terms` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/referral-program/terms](https://help-empuls.xoxoday.com/admin/referral-program/terms) * **Title (37 ch):** `Referral program terms and conditions` * **Description (137 ch):** `The complete terms of the Xoxoday customer referral program — eligibility, attribution, reward payout, taxes, fraud, and program changes.` * **Body H1/H2/H3:** 0 / 2 / 14 · **Words:** 2479 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/user-authentication/oauth-clients` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/oauth-clients](https://help-empuls.xoxoday.com/admin/user-authentication/oauth-clients) * **Title (24 ch):** `OAuth clients and scopes` * **Description (160 ch):** `Register and manage OAuth clients in Empuls to enable secure API access for third-party integrations, configure allowed scopes, and control authorization flows.` * **Body H1/H2/H3:** 0 / 11 / 0 · **Words:** 767 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `demo-library/compass-admin-walkthrough` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/demo-library/compass-admin-walkthrough](https://help-empuls.xoxoday.com/demo-library/compass-admin-walkthrough) * **Title (40 ch):** `Complete admin walkthrough — all modules` * **Description (137 ch):** `An end-to-end tour of the Compass admin console consists of users, data, connections, metrics, plans, approvals, reports, and dashboards.` * **Body H1/H2/H3:** 0 / 10 / 0 · **Words:** 1259 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `employees/benefits/fitness-challenges` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/benefits/fitness-challenges](https://help-empuls.xoxoday.com/employees/benefits/fitness-challenges) * **Title (18 ch):** `Fitness challenges` * **Description (144 ch):** `Join fitness challenges, connect your smartwatch or fitness tracker, track progress on the leaderboard, and earn rewards for hitting milestones.` * **Body H1/H2/H3:** 0 / 9 / 2 · **Words:** 999 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 1/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Title is not unique across the docs — duplicate of another page. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **title (1/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `employees/socials/celebrations` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/socials/celebrations](https://help-empuls.xoxoday.com/employees/socials/celebrations) * **Title (25 ch):** `Celebrations and yearbook` * **Description (165 ch):** `Celebrate employee milestones automatically in Empuls: birthdays, work anniversaries, and team moments with personalized wishes, group posts, and a digital yearbook.` * **Body H1/H2/H3:** 0 / 4 / 4 · **Words:** 580 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (25 chars) — add descriptive keywords to reach \~50–60. * Description is 165 chars — slightly over the 160-char SERP cutoff. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `product-updates/june-2026` — 77/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/product-updates/june-2026](https://help-empuls.xoxoday.com/product-updates/june-2026) * **Title (27 ch):** `Product Updates - June 2026` * **Description (127 ch):** `See what's new in Empuls for June 2026: feature releases, improvements, and fixes. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 1028 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **77/100** | **Issues detected:** * Title is short (27 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/ai/ai-settings` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/ai/ai-settings](https://help-empuls.xoxoday.com/admin/ai/ai-settings) * **Title (11 ch):** `AI settings` * **Description (161 ch):** `Configure AI features in Empuls: enable or disable AI-assisted recognition, smart nudges, sentiment analysis, and content generation tools for your organization.` * **Body H1/H2/H3:** 0 / 5 / 7 · **Words:** 914 · **Internal links:** 12 · **Images:** 11 (empty alt: 0, generic filename: 11) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * Description is 161 chars — slightly over the 160-char SERP cutoff. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 11 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/ai/empuls-copilot` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/ai/empuls-copilot](https://help-empuls.xoxoday.com/admin/ai/empuls-copilot) * **Title (10 ch):** `Em copilot` * **Description (174 ch):** `Meet Em, the Empuls AI copilot that helps employees and admins navigate the platform, get answers to HR questions, and take actions faster through a conversational interface.` * **Body H1/H2/H3:** 0 / 6 / 3 · **Words:** 940 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (10 chars) — add descriptive keywords to reach \~50–60. * Description is 174 chars — slightly over the 160-char SERP cutoff. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/gifts/automate-gifts` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/gifts/automate-gifts](https://help-empuls.xoxoday.com/admin/gifts/automate-gifts) * **Title (14 ch):** `Automate gifts` * **Description (164 ch):** `Learn how to automate employee gifts in Empuls for birthdays, work anniversaries, and custom milestones, with region-based point multipliers and scheduled delivery.` * **Body H1/H2/H3:** 0 / 7 / 1 · **Words:** 1245 · **Internal links:** 28 · **Images:** 25 (empty alt: 0, generic filename: 25) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (14 chars) — add descriptive keywords to reach \~50–60. * Description is 164 chars — slightly over the 160-char SERP cutoff. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 25 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/gifts/scheduled-gift` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/gifts/scheduled-gift](https://help-empuls.xoxoday.com/admin/gifts/scheduled-gift) * **Title (14 ch):** `Schedule gifts` * **Description (161 ch):** `Learn how to schedule and automate gifts in Empuls. Schedule one-time or recurring gifts, apply region-based multipliers, and use templates for milestone events.` * **Body H1/H2/H3:** 0 / 4 / 9 · **Words:** 681 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (14 chars) — add descriptive keywords to reach \~50–60. * Description is 161 chars — slightly over the 160-char SERP cutoff. * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/collaboration/google-chat` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/google-chat](https://help-empuls.xoxoday.com/admin/integrations/collaboration/google-chat) * **Title (11 ch):** `Google Chat` * **Description (127 ch):** `Connect Google Chat with Empuls to deliver recognition and milestone alerts right inside the tool your team already uses daily.` * **Body H1/H2/H3:** 0 / 8 / 1 · **Words:** 860 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/health-wellness/healthians` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/healthians](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/healthians) * **Title (42 ch):** `Preventive health checkups with Healthians` * **Description (127 ch):** `Healthians integrates with Empuls so every employee can access preventive health checkup packages without leaving the platform.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 381 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 8/10 | | **Overall** | **78/100** | **Issues detected:** * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. *** ### `admin/integrations/health-wellness/your-dost` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/your-dost](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/your-dost) * **Title (47 ch):** `Empower employee mental wellness with Your DOST` * **Description (132 ch):** `Your DOST integrates with Empuls so every employee can access confidential mental wellness counselling without leaving the platform.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 422 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hrms/darwinbox` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/darwinbox](https://help-empuls.xoxoday.com/admin/integrations/hrms/darwinbox) * **Title (9 ch):** `Darwinbox` * **Description (115 ch):** `Learn how the Darwinbox and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 661 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/hrms/ukg-pro` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/ukg-pro](https://help-empuls.xoxoday.com/admin/integrations/hrms/ukg-pro) * **Title (7 ch):** `UKG Pro` * **Description (109 ch):** `Learn how the UKG and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 794 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 8/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (7 chars) — add descriptive keywords to reach \~50–60. * Description is 109 chars — extend to 130–160 with search terms. * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (8/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/programs/awards/set-up-approval-based-awards` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards/set-up-approval-based-awards](https://help-empuls.xoxoday.com/admin/programs/awards/set-up-approval-based-awards) * **Title (21 ch):** `Approval-based awards` * **Description (110 ch):** `Set up multi-level approvals for your employee awards program so recognition goes through the right reviewers.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 1133 · **Internal links:** 27 · **Images:** 25 (empty alt: 0, generic filename: 25) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 25 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/reports/budget-report` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/reports/budget-report](https://help-empuls.xoxoday.com/admin/reports/budget-report) * **Title (13 ch):** `Budget report` * **Description (105 ch):** `Monitor budget allocation, utilisation, and points movement across your organisation's reward programmes.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 689 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Description is 105 chars — extend to 130–160 with search terms. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. *** ### `admin/sales-incentive/admin-guide/faq-admins/plans-faqs` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/faq-admins/plans-faqs](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/faq-admins/plans-faqs) * **Title (10 ch):** `Plans FAQs` * **Description (118 ch):** `Browse frequently asked questions about sales incentive plans on Empuls, from initial setup to day-to-day admin tasks.` * **Body H1/H2/H3:** 0 / 11 / 0 · **Words:** 2112 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (10 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/sales-incentive/admin-guide/faq-admins/reports-faqs` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/faq-admins/reports-faqs](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/faq-admins/reports-faqs) * **Title (12 ch):** `Reports FAQs` * **Description (120 ch):** `Browse frequently asked questions about sales incentive reports on Empuls, from initial setup to day-to-day admin tasks.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 934 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/user-authentication/password-policies` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/password-policies](https://help-empuls.xoxoday.com/admin/user-authentication/password-policies) * **Title (17 ch):** `Password policies` * **Description (157 ch):** `Configure password policies in Empuls to enforce complexity requirements, expiry intervals, and multi-factor authentication to keep employee accounts secure.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 577 · **Internal links:** 4 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/user-authentication/saml-custom` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/saml-custom](https://help-empuls.xoxoday.com/admin/user-authentication/saml-custom) * **Title (15 ch):** `Custom SAML 2.0` * **Description (158 ch):** `Configure a custom SAML 2.0 SSO connection in Empuls with any compatible identity provider, including setup steps for metadata exchange and attribute mapping.` * **Body H1/H2/H3:** 0 / 10 / 4 · **Words:** 1114 · **Internal links:** 2 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. *** ### `employees/engagement/gamezone` — 78/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/engagement/gamezone](https://help-empuls.xoxoday.com/employees/engagement/gamezone) * **Title (8 ch):** `Gamezone` * **Description (160 ch):** `Engage employees with Empuls Gamezone: play casual games, compete on leaderboards, earn points, and make the workday more fun with a built-in gaming experience.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 544 · **Internal links:** 2 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 9/10 | | **Overall** | **78/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/budgets/automated-budgets` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/budgets/automated-budgets](https://help-empuls.xoxoday.com/admin/budgets/automated-budgets) * **Title (17 ch):** `Automated budgets` * **Description (152 ch):** `Create automated recognition budgets that run on a schedule — weekly, monthly, or quarterly — so your programs always have funds without manual top-ups.` * **Body H1/H2/H3:** 0 / 2 / 0 · **Words:** 515 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/budgets/manage-budgets` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/budgets/manage-budgets](https://help-empuls.xoxoday.com/admin/budgets/manage-budgets) * **Title (14 ch):** `Manage budgets` * **Description (155 ch):** `Create recognition budgets, allocate points to managers and teams, set fixed or prorated distributions, pause and reactivate budgets, and monitor spending.` * **Body H1/H2/H3:** 0 / 8 / 1 · **Words:** 755 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * Title is short (14 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/financial-wellbeing/astrafin` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/astrafin](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/astrafin) * **Title (54 ch):** `AstraFin: tax-smart car leasing as an employee benefit` * **Description (101 ch):** `Extend your financial wellness program by integrating AstraFin with Empuls for tax-smart car leasing.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 773 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **79/100** | **Issues detected:** * Description is 101 chars — extend to 130–160 with search terms. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/financial-wellbeing/finfinity` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/finfinity](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/finfinity) * **Title (36 ch):** `Access fast, loans through Finfinity` * **Description (117 ch):** `Connect Finfinity with Empuls to give employees access to quick personal loans directly from their rewards dashboard.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 347 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/financial-wellbeing/taxspanner` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/taxspanner](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/taxspanner) * **Title (35 ch):** `Simplify tax filing with TaxSpanner` * **Description (114 ch):** `Add guided tax filing support to your Empuls benefits stack with the TaxSpanner integration, configured by admins.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 375 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/health-wellness/aurae-digital` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/aurae-digital](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/aurae-digital) * **Title (46 ch):** `AI-led eye-health screening with Aurae Digital` * **Description (138 ch):** `Connect Aurae Digital with Empuls to give employees access to AI-led eye health screening, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 309 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. *** ### `admin/integrations/health-wellness/newmi-care` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/newmi-care](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/newmi-care) * **Title (49 ch):** `Empower women’s wellness journeys with Newmi Care` * **Description (137 ch):** `Add women’s health and wellness support to your benefits program with the Newmi Care and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 412 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/querencia-studios` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/querencia-studios](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/querencia-studios) * **Title (69 ch):** `Querencia Studios: professional mental wellness support for employees` * **Description (143 ch):** `Bring professional mental wellness sessions to your team by integrating Querencia Studios with Empuls, all tracked from one wellness dashboard.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 628 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 9/10 | | **Overall** | **79/100** | **Issues detected:** * Title is 69 chars — trim to 50–60 for full SERP display. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/health-wellness/stretchit` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/stretchit](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/stretchit) * **Title (60 ch):** `Comprehensive flexibility & mobility wellness with STRETCHIT` * **Description (147 ch):** `Connect STRETCHIT with Empuls to give employees access to guided flexibility and mobility training, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 572 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **79/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hrms/justlogin` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/justlogin](https://help-empuls.xoxoday.com/admin/integrations/hrms/justlogin) * **Title (9 ch):** `JustLogin` * **Description (114 ch):** `Learn how the JustLogin and Empuls integration works and help automate employee engagement, recognition & rewards.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 676 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 8/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. *** ### `admin/integrations/hrms/zoho-people` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/zoho-people](https://help-empuls.xoxoday.com/admin/integrations/hrms/zoho-people) * **Title (11 ch):** `Zoho People` * **Description (117 ch):** `Learn how the Zoho People and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 771 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/insurance-benefits/zooper` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/zooper](https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/zooper) * **Title (47 ch):** `Zooper: smarter corporate commute for employees` * **Description (102 ch):** `Connect Zooper with Empuls to add smarter corporate commute options to your employee benefits program.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 682 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **79/100** | **Issues detected:** * Description is 102 chars — extend to 130–160 with search terms. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/ld-benefits/codingal` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/codingal](https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/codingal) * **Title (51 ch):** `Codingal: coding & AI education for employees' kids` * **Description (126 ch):** `Connect Codingal with Empuls to offer employees coding and AI classes for employees’ kids as part of their perks and benefits.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 710 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 9/10 | | **Overall** | **79/100** | **Issues detected:** * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/user-management/user-delegation` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-management/user-delegation](https://help-empuls.xoxoday.com/admin/user-management/user-delegation) * **Title (15 ch):** `User delegation` * **Description (153 ch):** `Learn how to grant another user temporary access to an admin or manager account so approvals, recognition, and admin tasks continue without interruption.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 753 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `product-updates/november-2025` — 79/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/product-updates/november-2025](https://help-empuls.xoxoday.com/product-updates/november-2025) * **Title (31 ch):** `Product Updates - November 2025` * **Description (118 ch):** `Catch up on everything Empuls shipped in November 2025, from new features to fixes. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 830 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **79/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/admin-hub` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/admin-hub](https://help-empuls.xoxoday.com/admin/admin-hub) * **Title (11 ch):** `Admin panel` * **Description (152 ch):** `Access all Empuls admin controls from a single hub: manage users, programs, budgets, integrations, surveys, reports, and platform settings in one place.` * **Body H1/H2/H3:** 0 / 3 / 11 · **Words:** 1240 · **Internal links:** 15 · **Images:** 12 (empty alt: 0, generic filename: 12) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 12 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/finance/cost-of-living` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/finance/cost-of-living](https://help-empuls.xoxoday.com/admin/finance/cost-of-living) * **Title (20 ch):** `Cost of living index` * **Description (136 ch):** `Learn how to apply per-region multipliers so a recognition point has equivalent purchasing power for employees in different geographies.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 546 · **Internal links:** 3 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (20 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/finance/subscription-billing` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/finance/subscription-billing](https://help-empuls.xoxoday.com/admin/finance/subscription-billing) * **Title (24 ch):** `Subscription and billing` * **Description (172 ch):** `Learn how to view your active subscription plan, update billing contact and payment details, download invoices, manage redemption wallet balances, and configure currencies.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 700 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * Description is 172 chars — slightly over the 160-char SERP cutoff. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/financial-wellbeing/assured-gain` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/assured-gain](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/assured-gain) * **Title (57 ch):** `Investment advisory & wealth management with Assured Gain` * **Description (110 ch):** `Extend your financial wellness program by integrating Assured Gain with Empuls for wealth management advisory.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 340 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. *** ### `admin/integrations/health-wellness/silver-oak-health` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/silver-oak-health](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/silver-oak-health) * **Title (58 ch):** `Seamless mental wellness support through Silver Oak Health` * **Description (152 ch):** `Connect Silver Oak Health with Empuls to give employees access to therapist-led mental wellness support, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 542 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/hrms/freshteam` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/freshteam](https://help-empuls.xoxoday.com/admin/integrations/hrms/freshteam) * **Title (9 ch):** `Freshteam` * **Description (142 ch):** `Learn how the Freshteam and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards and automated celebrations.` * **Body H1/H2/H3:** 0 / 5 / 2 · **Words:** 877 · **Internal links:** 11 · **Images:** 11 (empty alt: 0, generic filename: 11) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (9 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 11 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/insurance-benefits/neoffice` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/neoffice](https://help-empuls.xoxoday.com/admin/integrations/insurance-benefits/neoffice) * **Title (41 ch):** `Hybrid workplace management with neoffice` * **Description (104 ch):** `Connect neoffice with Empuls to add hybrid workplace management tools to your employee benefits program.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 370 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Description is 104 chars — extend to 130–160 with search terms. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/other/amazon-marketplace` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/amazon-marketplace](https://help-empuls.xoxoday.com/admin/integrations/other/amazon-marketplace) * **Title (42 ch):** `Amazon Marketplace integration with Empuls` * **Description (103 ch):** `Connect Amazon Marketplace with Empuls so employees can redeem points for a wide catalogue of products.` * **Body H1/H2/H3:** 0 / 12 / 0 · **Words:** 1070 · **Internal links:** 11 · **Images:** 11 (empty alt: 0, generic filename: 11) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Description is 103 chars — extend to 130–160 with search terms. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 11 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (8/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/platform-settings/branding` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/platform-settings/branding](https://help-empuls.xoxoday.com/admin/platform-settings/branding) * **Title (8 ch):** `Branding` * **Description (162 ch):** `Customize your Empuls platform with your company logo, brand colors, custom domain, and white-label settings to create a consistent, on-brand employee experience.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 1109 · **Internal links:** 18 · **Images:** 18 (empty alt: 0, generic filename: 18) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Description is 162 chars — slightly over the 160-char SERP cutoff. * 18 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/programs/reward-campaigns` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/programs/reward-campaigns](https://help-empuls.xoxoday.com/admin/programs/reward-campaigns) * **Title (16 ch):** `Reward campaigns` * **Description (131 ch):** `Learn how to run structured, time-bound recognition cycles with built-in governance rules that keep recognition fair and auditable.` * **Body H1/H2/H3:** 0 / 2 / 6 · **Words:** 823 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (16 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/referral-program/overview` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/referral-program/overview](https://help-empuls.xoxoday.com/admin/referral-program/overview) * **Title (21 ch):** `Refer a peer and earn` * **Description (147 ch):** `Introduce a decision-maker at a new company to Xoxoday and earn cash rewards when the referral turns into a real deal — up to $10,000 per referral.` * **Body H1/H2/H3:** 0 / 6 / 3 · **Words:** 1120 · **Internal links:** 1 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/reports/custom-report` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/reports/custom-report](https://help-empuls.xoxoday.com/admin/reports/custom-report) * **Title (13 ch):** `Custom report` * **Description (108 ch):** `Learn how to build, save, and share tailored reports with your own filters, date ranges, and source metrics.` * **Body H1/H2/H3:** 0 / 5 / 2 · **Words:** 669 · **Internal links:** 8 · **Images:** 8 (empty alt: 0, generic filename: 8) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * Description is 108 chars — extend to 130–160 with search terms. * 8 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/reports/redemption-report` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/reports/redemption-report](https://help-empuls.xoxoday.com/admin/reports/redemption-report) * **Title (17 ch):** `Redemption report` * **Description (105 ch):** `Track how employees redeem their earned points — transaction logs, wallet balances, and taxation reports.` * **Body H1/H2/H3:** 0 / 7 / 2 · **Words:** 609 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Description is 105 chars — extend to 130–160 with search terms. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/sales-incentive/admin-guide/plans/milestones` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/milestones](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/plans/milestones) * **Title (10 ch):** `Milestones` * **Description (109 ch):** `Walk through creating a milestone-based sales incentive plan step by step. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 1460 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 8/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (10 chars) — add descriptive keywords to reach \~50–60. * Description is 109 chars — extend to 130–160 with search terms. * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (8/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/surveys/mood-o-meter` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/mood-o-meter](https://help-empuls.xoxoday.com/admin/surveys/mood-o-meter) * **Title (12 ch):** `Mood-o-meter` * **Description (140 ch):** `Set up and manage the Mood-o-meter in Empuls to capture quick, anonymous daily sentiment check-ins and monitor team morale trends over time.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 994 · **Internal links:** 9 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/user-management/access-control` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/admin/user-management/access-control](https://help-empuls.xoxoday.com/admin/user-management/access-control) * **Title (14 ch):** `Access control` * **Description (139 ch):** `Learn how to define what each admin can see and do in Empuls. Use built-in roles or create custom access roles with menu-level permissions.` * **Body H1/H2/H3:** 0 / 10 / 0 · **Words:** 1007 · **Internal links:** 5 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (14 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `employees/recognitions/appreciate-colleagues` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/recognitions/appreciate-colleagues](https://help-empuls.xoxoday.com/employees/recognitions/appreciate-colleagues) * **Title (18 ch):** `Giving recognition` * **Description (102 ch):** `Send peer recognition, nominate colleagues for awards, and share achievements on LinkedIn with Empuls.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 798 · **Internal links:** 7 · **Images:** 7 (empty alt: 0, generic filename: 7) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * Description is 102 chars — extend to 130–160 with search terms. * 7 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `employees/redemption/festive-gifts` — 80/100 · Medium * **URL:** [https://help-empuls.xoxoday.com/employees/redemption/festive-gifts](https://help-empuls.xoxoday.com/employees/redemption/festive-gifts) * **Title (13 ch):** `Festive gifts` * **Description (149 ch):** `Pick a gift from your organization's seasonal campaign (Diwali, Christmas, New Year, or any custom occasion) within the claim window your admin sets.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 536 · **Internal links:** 3 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **80/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/financial-wellbeing/fatakpay` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/fatakpay](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/fatakpay) * **Title (52 ch):** `Instant financial access for employees with FatakPay` * **Description (121 ch):** `Connect FatakPay with Empuls to give employees access to instant short-term credit directly from their rewards dashboard.` * **Body H1/H2/H3:** 0 / 7 / 1 · **Words:** 532 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/health-wellness/circle-health` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/circle-health](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/circle-health) * **Title (44 ch):** `Circle Health: employee wellness, simplified` * **Description (133 ch):** `Circle Health integrates with Empuls so every employee can access simplified employee wellness benefits without leaving the platform.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 365 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/clove-dental` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/clove-dental](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/clove-dental) * **Title (29 ch):** `Dental care with Clove Dental` * **Description (143 ch):** `Add dental checkups and treatment discounts to your benefits program with the Clove Dental and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 523 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (29 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/health-wellness/fitelo` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fitelo](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fitelo) * **Title (49 ch):** `Personalized nutrition and weightloss with Fitelo` * **Description (142 ch):** `Add personalised nutrition and weight-loss plans to your benefits program with the Fitelo and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 495 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/fitpass` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fitpass](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fitpass) * **Title (37 ch):** `Unlock employee wellness with Fitpass` * **Description (131 ch):** `Bring multi-gym and fitness studio access to your team by integrating Fitpass with Empuls, all tracked from one wellness dashboard.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 487 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/healthify` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/healthify](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/healthify) * **Title (37 ch):** `Comprehensive wellness with Healthify` * **Description (125 ch):** `Bring diet and fitness coaching to your team by integrating HealthifyMe with Empuls, all tracked from one wellness dashboard.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 500 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/health-wellness/humm-care` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/humm-care](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/humm-care) * **Title (30 ch):** `Total wellbeing with Humm Care` * **Description (135 ch):** `Add holistic wellbeing and care support to your benefits program with the HummCare and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 493 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/portea` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/portea](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/portea) * **Title (44 ch):** `Complete home healthcare solutions by Portea` * **Description (134 ch):** `Bring home healthcare visits and nursing care to your team by integrating Portea with Empuls, all tracked from one wellness dashboard.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 498 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/red-health` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/red-health](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/red-health) * **Title (57 ch):** `Red Health: emergency healthcare assistance for employees` * **Description (124 ch):** `Red Health integrates with Empuls so every employee can access emergency healthcare assistance without leaving the platform.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 681 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/hrms/adp` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/adp](https://help-empuls.xoxoday.com/admin/integrations/hrms/adp) * **Title (3 ch):** `ADP` * **Description (104 ch):** `Learn how to connect ADP with Empuls to automate employee data sync and extend your engagement programs.` * **Body H1/H2/H3:** 0 / 10 / 0 · **Words:** 814 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (3 chars) — add descriptive keywords to reach \~50–60. * Description is 104 chars — extend to 130–160 with search terms. * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/hrms/bamboohr` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/hrms/bamboohr](https://help-empuls.xoxoday.com/admin/integrations/hrms/bamboohr) * **Title (8 ch):** `BambooHR` * **Description (114 ch):** `Learn how the BambooHR and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards.` * **Body H1/H2/H3:** 0 / 6 / 6 · **Words:** 658 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/integrations/ld-benefits/upgrad` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/upgrad](https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/upgrad) * **Title (38 ch):** `Upskill workforce with upGrad programs` * **Description (136 ch):** `Bring career upskilling programs into your Empuls benefits catalogue by integrating upGrad. It’s part of Empuls’s broader admin toolkit.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 385 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/ld-benefits/vani-coach` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/vani-coach](https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/vani-coach) * **Title (41 ch):** `Communication development with vani.coach` * **Description (133 ch):** `Bring communication skills coaching into your Empuls benefits catalogue by integrating Vani.coach. No coding required for most teams.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 492 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/programs/fitness-challenges` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/programs/fitness-challenges](https://help-empuls.xoxoday.com/admin/programs/fitness-challenges) * **Title (25 ch):** `Manage fitness challenges` * **Description (172 ch):** `Learn how to enable fitness challenge templates, configure milestone rewards, manage leaderboards, send nudge emails, view activity reports, and control the exclusion list.` * **Body H1/H2/H3:** 0 / 11 / 0 · **Words:** 1240 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (25 chars) — add descriptive keywords to reach \~50–60. * Description is 172 chars — slightly over the 160-char SERP cutoff. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/reports/gift-report` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/reports/gift-report](https://help-empuls.xoxoday.com/admin/reports/gift-report) * **Title (11 ch):** `Gift report` * **Description (120 ch):** `Track all gifts sent to employees — automated milestone gifts and manual gifts — with delivery status and spend details.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 524 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/reports/redemption-point-source` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/reports/redemption-point-source](https://help-empuls.xoxoday.com/admin/reports/redemption-point-source) * **Title (37 ch):** `Redemption point source (FIFO) report` * **Description (154 ch):** `A transaction-level report that traces every point redeemed back to the award it was earned from, using FIFO — for tax reconciliation and source analysis.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 748 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/security/platform-data-faqs` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/security/platform-data-faqs](https://help-empuls.xoxoday.com/admin/security/platform-data-faqs) * **Title (28 ch):** `Platform and data management` * **Description (138 ch):** `Find answers to common questions about platform reliability and data security on Empuls, covering setup, permissions, and troubleshooting.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 1022 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 7/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (28 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. * Title implies a how-to but page has no `` block — convert numbered instructions to `` for HowTo schema. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (7/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/surveys/employee-pulse-survey` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/employee-pulse-survey](https://help-empuls.xoxoday.com/admin/surveys/employee-pulse-survey) * **Title (21 ch):** `Employee pulse survey` * **Description (154 ch):** `Run targeted pulse surveys in Empuls to measure employee sentiment on specific topics, track trends over time, and take data-driven action on the results.` * **Body H1/H2/H3:** 1 / 9 / 16 · **Words:** 900 · **Internal links:** 5 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 8/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (8/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/surveys/quizzes` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/quizzes](https://help-empuls.xoxoday.com/admin/surveys/quizzes) * **Title (25 ch):** `Create and manage quizzes` * **Description (115 ch):** `Build, distribute, and analyse quizzes for engagement, learning reinforcement, and competency assessment in Empuls.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 817 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (25 chars) — add descriptive keywords to reach \~50–60. * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `employees/recognitions/wall-of-fame` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/employees/recognitions/wall-of-fame](https://help-empuls.xoxoday.com/employees/recognitions/wall-of-fame) * **Title (12 ch):** `Wall of Fame` * **Description (154 ch):** `Showcase employee awards on the Wall of Fame, browse interactivity by department or award type, and use TV mode to display recognitions on office screens.` * **Body H1/H2/H3:** 0 / 5 / 7 · **Words:** 696 · **Internal links:** 1 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 5/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 9/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Only 1 internal link(s) — add at least 2 contextual links to related docs.json pages. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **links (5/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `product-updates/february-2025` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/product-updates/february-2025](https://help-empuls.xoxoday.com/product-updates/february-2025) * **Title (26 ch):** `Product Updates - Feb 2025` * **Description (122 ch):** `Catch up on everything Empuls shipped in February 2025, from new features to fixes. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 639 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * Title is short (26 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `product-updates/january-2026` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/product-updates/january-2026](https://help-empuls.xoxoday.com/product-updates/january-2026) * **Title (30 ch):** `Product Updates - January 2026` * **Description (139 ch):** `Explore Empuls’s product updates for January 2026, covering new features and improvements. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 857 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `product-updates/october-2025` — 81/100 · Low * **URL:** [https://help-empuls.xoxoday.com/product-updates/october-2025](https://help-empuls.xoxoday.com/product-updates/october-2025) * **Title (30 ch):** `Product Updates - October 2025` * **Description (134 ch):** `See what's new in Empuls for October 2025: feature releases, improvements, and fixes. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 0 / 1 / 0 · **Words:** 863 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 7/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 6/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **81/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (6/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **h2 (7/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/financial-wellbeing/muro` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/muro](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/muro) * **Title (37 ch):** `Employee financial wellness with Muro` * **Description (103 ch):** `Extend your financial wellness program by integrating Muro with Empuls for financial wellness coaching.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 561 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * Description is 103 chars — extend to 130–160 with search terms. * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/financial-wellbeing/poonawalla-fincorp` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/poonawalla-fincorp](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/poonawalla-fincorp) * **Title (38 ch):** `Personal loans with Poonawalla Fincorp` * **Description (111 ch):** `Add personal loans to your Empuls benefits stack with the Poonawalla Fincorp integration, configured by admins.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 610 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/health-wellness/medibuddy` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/medibuddy](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/medibuddy) * **Title (53 ch):** `Integrated health & wellness solutions with Medibuddy` * **Description (155 ch):** `Connect MediBuddy with Empuls to give employees access to online doctor consultations and diagnostic tests, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 424 · **Internal links:** 3 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/overview` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/overview](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/overview) * **Title (28 ch):** `Health and wellness benefits` * **Description (118 ch):** `Give employees access to curated health and wellness programs through Empuls, all managed from one benefits dashboard.` * **Body H1/H2/H3:** 0 / 5 / 1 · **Words:** 736 · **Internal links:** 11 · **Images:** 11 (empty alt: 0, generic filename: 11) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * Title is short (28 chars) — add descriptive keywords to reach \~50–60. * 11 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/ld-benefits/master-o` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/master-o](https://help-empuls.xoxoday.com/admin/integrations/ld-benefits/master-o) * **Title (36 ch):** `Gamified microlearning with Master-O` * **Description (119 ch):** `Master-O integrates with Empuls so employees can enrol in gamified microlearning modules directly from the perks store.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 605 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 5/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * Heading levels skip (e.g. H2 → H4). Fix hierarchy so levels increase by one. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h2 (5/10):** Add 2–5 H2 sections that mirror the tasks a reader searches for. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/platform-settings/feed-and-profile-settings` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/platform-settings/feed-and-profile-settings](https://help-empuls.xoxoday.com/admin/platform-settings/feed-and-profile-settings) * **Title (25 ch):** `feed-and-profile-settings` * **Description (160 ch):** `Manage feed and profile settings in Empuls to control content visibility, post permissions, profile completeness requirements, and activity display preferences.` * **Body H1/H2/H3:** 1 / 4 / 5 · **Words:** 805 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 4/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * Title is short (25 chars) — add descriptive keywords to reach \~50–60. * Body contains 1 H1 heading(s); Mintlify already renders the frontmatter title as H1. Demote body H1s to H2. * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **h1 (4/10):** Demote any body `#` H1 to `##` — the frontmatter title already renders as H1. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/reports/recognition-report` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/reports/recognition-report](https://help-empuls.xoxoday.com/admin/reports/recognition-report) * **Title (18 ch):** `Recognition report` * **Description (110 ch):** `Track how recognition flows across your organisation — awards received, awards given, and nomination activity.` * **Body H1/H2/H3:** 0 / 4 / 0 · **Words:** 503 · **Internal links:** 8 · **Images:** 8 (empty alt: 0, generic filename: 8) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * 8 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/sales-incentive/admin-guide/dashboard/add-a-widget-to-your-dashboard` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/dashboard/add-a-widget-to-your-dashboard](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/dashboard/add-a-widget-to-your-dashboard) * **Title (30 ch):** `Add a widget to your dashboard` * **Description (136 ch):** `Add and arrange widgets on your Empuls sales incentive dashboard to track what matters. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 504 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (8/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/surveys/survey-analytics` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/survey-analytics](https://help-empuls.xoxoday.com/admin/surveys/survey-analytics) * **Title (16 ch):** `Survey analytics` * **Description (174 ch):** `Analyze survey results in Empuls with response rate tracking, sentiment breakdowns, trend comparisons, and department-level filters to turn feedback into actionable insights.` * **Body H1/H2/H3:** 0 / 9 / 9 · **Words:** 1373 · **Internal links:** 3 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 8/10 | | **Overall** | **82/100** | **Issues detected:** * Title is short (16 chars) — add descriptive keywords to reach \~50–60. * Description is 174 chars — slightly over the 160-char SERP cutoff. * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `admin/user-authentication/session-management` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/session-management](https://help-empuls.xoxoday.com/admin/user-authentication/session-management) * **Title (18 ch):** `Session management` * **Description (155 ch):** `Manage active user sessions in Empuls, configure session timeout settings, view login activity, and remotely revoke sessions to maintain platform security.` * **Body H1/H2/H3:** 0 / 7 / 4 · **Words:** 625 · **Internal links:** 5 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * Title is short (18 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **intent (9/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `employees/socials/groups` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/employees/socials/groups](https://help-empuls.xoxoday.com/employees/socials/groups) * **Title (11 ch):** `Communities` * **Description (153 ch):** `Create and manage communities in Empuls where employees with shared interests can connect, collaborate, and engage beyond their immediate team structure.` * **Body H1/H2/H3:** 0 / 10 / 8 · **Words:** 1306 · **Internal links:** 8 · **Images:** 8 (empty alt: 0, generic filename: 8) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **82/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * 8 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `employees/socials/townhall` — 82/100 · Low * **URL:** [https://help-empuls.xoxoday.com/employees/socials/townhall](https://help-empuls.xoxoday.com/employees/socials/townhall) * **Title (8 ch):** `Townhall` * **Description (164 ch):** `Host and manage company-wide townhalls in Empuls with live Q&A, polls, announcements, and recorded sessions that keep your entire organization informed and aligned.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 780 · **Internal links:** 2 · **Images:** 1 (empty alt: 0, generic filename: 1) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 9/10 | | **Overall** | **82/100** | **Issues detected:** * Title is short (8 chars) — add descriptive keywords to reach \~50–60. * Description is 164 chars — slightly over the 160-char SERP cutoff. * 1 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/ai/ai-skill-mapping` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/ai/ai-skill-mapping](https://help-empuls.xoxoday.com/admin/ai/ai-skill-mapping) * **Title (24 ch):** `AI-powered skill mapping` * **Description (166 ch):** `Use Empuls AI skill mapping to automatically identify and tag employee skills from recognition data, helping HR build accurate skill profiles across the organization.` * **Body H1/H2/H3:** 0 / 8 / 4 · **Words:** 1068 · **Internal links:** 6 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (24 chars) — add descriptive keywords to reach \~50–60. * Description is 166 chars — slightly over the 160-char SERP cutoff. * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/integrations/collaboration/google-workspace` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/google-workspace](https://help-empuls.xoxoday.com/admin/integrations/collaboration/google-workspace) * **Title (28 ch):** `Google Workspace integration` * **Description (132 ch):** `Bring single sign-on and directory sync into Google Workspace by connecting it with Empuls, so employees never have to switch tools.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 1136 · **Internal links:** 9 · **Images:** 8 (empty alt: 0, generic filename: 8) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (28 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 8 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/collaboration/slack` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/slack](https://help-empuls.xoxoday.com/admin/integrations/collaboration/slack) * **Title (5 ch):** `Slack` * **Description (117 ch):** `Connect Slack with Empuls to deliver peer recognition and rewards right inside the tool your team already uses daily.` * **Body H1/H2/H3:** 0 / 6 / 9 · **Words:** 1988 · **Internal links:** 27 · **Images:** 27 (empty alt: 0, generic filename: 27) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (5 chars) — add descriptive keywords to reach \~50–60. * 27 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/financial-wellbeing/refyne` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/refyne](https://help-empuls.xoxoday.com/admin/integrations/financial-wellbeing/refyne) * **Title (30 ch):** `Financial wellness with Refyne` * **Description (137 ch):** `Refyne integrates with Empuls so employees can get on-demand salary access without switching apps. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 558 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/apollo-labs` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/apollo-labs](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/apollo-labs) * **Title (58 ch):** `Apollo Labs wellness: employee health checkups, simplified` * **Description (147 ch):** `Add simplified employee health checkups to your benefits program with the Apollo Labs Wellness and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 6 / 0 · **Words:** 627 · **Internal links:** 2 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 8/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **83/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **links (8/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/health-wellness/ekincare` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/ekincare](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/ekincare) * **Title (43 ch):** `Comprehensive health benefits with ekincare` * **Description (137 ch):** `Ekincare integrates with Empuls so every employee can access annual health checkups and wellness screenings without leaving the platform.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 526 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/fitterfly` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fitterfly](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/fitterfly) * **Title (35 ch):** `Wellbeing reimagined with Fitterfly` * **Description (141 ch):** `Bring personalised chronic-care wellness coaching to your team by integrating Fitterfly with Empuls, all tracked from one wellness dashboard.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 582 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/pazcare` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/pazcare](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/pazcare) * **Title (53 ch):** `Simplify health, wellness, and insurance with Pazcare` * **Description (146 ch):** `Connect Pazcare with Empuls to give employees access to group health insurance and wellness plans, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 524 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/practo` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/practo](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/practo) * **Title (44 ch):** `Digital healthcare for employees with Practo` * **Description (131 ch):** `Practo integrates with Empuls so every employee can access doctor bookings and digital health records without leaving the platform.` * **Body H1/H2/H3:** 0 / 10 / 0 · **Words:** 531 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/samvedna-care` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/samvedna-care](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/samvedna-care) * **Title (44 ch):** `Employee wellness support with Samvedna Care` * **Description (150 ch):** `Connect Samvedna Care with Empuls to give employees access to mental health counselling for employees, managed alongside your other wellness benefits.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 564 · **Internal links:** 7 · **Images:** 7 (empty alt: 0, generic filename: 7) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 6/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is not unique across the docs — duplicate of another page. * 7 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (6/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/health-wellness/twin-health` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/twin-health](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/twin-health) * **Title (45 ch):** `AI-powered wellness programs with Twin Health` * **Description (139 ch):** `Add AI-powered metabolic health coaching to your benefits program with the Twin Health and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 500 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/unlock-fit` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/unlock-fit](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/unlock-fit) * **Title (38 ch):** `Comprehensive wellness with unlock.fit` * **Description (139 ch):** `Add gym access and fitness class bookings to your benefits program with the Unlock.Fit and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 581 · **Internal links:** 7 · **Images:** 7 (empty alt: 0, generic filename: 7) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 7 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/integrations/health-wellness/yogifi` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/yogifi](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/yogifi) * **Title (38 ch):** `Holistic employee wellness with Yogifi` * **Description (140 ch):** `Add guided yoga and holistic wellness sessions to your benefits program with the YogiFi and Empuls integration, set up in a few admin steps.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 590 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 3/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (3/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/platform-settings/notification-settings` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/platform-settings/notification-settings](https://help-empuls.xoxoday.com/admin/platform-settings/notification-settings) * **Title (21 ch):** `Notification settings` * **Description (161 ch):** `Configure email, in-app, and push notification preferences in Empuls for different event types, control frequency settings, and customize notification templates.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 385 · **Internal links:** 9 · **Images:** 9 (empty alt: 0, generic filename: 9) * **Schema eligibility:** FAQPage, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 7/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * Description is 161 chars — slightly over the 160-char SERP cutoff. * 9 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **depth (7/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. *** ### `admin/programs/awards/add-certificates-to-awards` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards/add-certificates-to-awards](https://help-empuls.xoxoday.com/admin/programs/awards/add-certificates-to-awards) * **Title (26 ch):** `Add certificates to awards` * **Description (106 ch):** `Attach certificate templates to awards and work-anniversary gifts as part of your employee awards program.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 564 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (26 chars) — add descriptive keywords to reach \~50–60. * Description is 106 chars — extend to 130–160 with search terms. * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/programs/awards/incentive-based-awards` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards/incentive-based-awards](https://help-empuls.xoxoday.com/admin/programs/awards/incentive-based-awards) * **Title (16 ch):** `Incentive awards` * **Description (127 ch):** `Create goal-based incentive awards that reward employees for hitting measurable targets. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 872 · **Internal links:** 18 · **Images:** 16 (empty alt: 0, generic filename: 16) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (16 chars) — add descriptive keywords to reach \~50–60. * 16 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/programs/awards/set-up-awards-and-core-values` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards/set-up-awards-and-core-values](https://help-empuls.xoxoday.com/admin/programs/awards/set-up-awards-and-core-values) * **Title (11 ch):** `Spot awards` * **Description (125 ch):** `Create and configure spot awards — the instant, no-approval recognition tool in Empuls — and link core values to recognition.` * **Body H1/H2/H3:** 0 / 12 / 9 · **Words:** 4074 · **Internal links:** 78 · **Images:** 74 (empty alt: 0, generic filename: 74) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * 74 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/programs/leaderboard` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/programs/leaderboard](https://help-empuls.xoxoday.com/admin/programs/leaderboard) * **Title (19 ch):** `Manage leaderboards` * **Description (171 ch):** `Learn how to build Empuls leaderboards with custom scoring rules, manage categories and exclusions, control visibility, and drive engagement through gamified competitions.` * **Body H1/H2/H3:** 0 / 12 / 0 · **Words:** 1672 · **Internal links:** 12 · **Images:** 12 (empty alt: 0, generic filename: 12) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (19 chars) — add descriptive keywords to reach \~50–60. * Description is 171 chars — slightly over the 160-char SERP cutoff. * 12 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (9/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/surveys/create-surveys` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/create-surveys](https://help-empuls.xoxoday.com/admin/surveys/create-surveys) * **Title (14 ch):** `Create surveys` * **Description (184 ch):** `Learn how to create, configure, and launch custom surveys in Empuls, including setting up questions, scheduling, targeting specific employee segments, and enabling anonymous responses.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 1441 · **Internal links:** 7 · **Images:** 7 (empty alt: 0, generic filename: 7) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 5/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (14 chars) — add descriptive keywords to reach \~50–60. * Description is 184 chars — Google truncates around 155–160. * 7 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (5/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (9/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/surveys/lifecycle-surveys` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/lifecycle-surveys](https://help-empuls.xoxoday.com/admin/surveys/lifecycle-surveys) * **Title (17 ch):** `Lifecycle surveys` * **Description (177 ch):** `Set up automated lifecycle surveys in Empuls that trigger at key employee moments, such as onboarding, probation end, and exit, to capture timely feedback without manual effort.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 1310 · **Internal links:** 5 · **Images:** 3 (empty alt: 0, generic filename: 3) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Description is 177 chars — slightly over the 160-char SERP cutoff. * 3 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/user-authentication/google-workspace-sso` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/user-authentication/google-workspace-sso](https://help-empuls.xoxoday.com/admin/user-authentication/google-workspace-sso) * **Title (20 ch):** `Google Workspace SSO` * **Description (143 ch):** `Connect Google Workspace to Empuls for single sign-on, letting employees log in with their Google credentials and sync user data automatically.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 905 · **Internal links:** 6 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (20 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/user-management/employee-exit` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/user-management/employee-exit](https://help-empuls.xoxoday.com/admin/user-management/employee-exit) * **Title (12 ch):** `Manage exits` * **Description (111 ch):** `Learn how to configure the rules for treating the unused budget point(s) left in the account of exit employees.` * **Body H1/H2/H3:** 0 / 5 / 8 · **Words:** 656 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 7/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (12 chars) — add descriptive keywords to reach \~50–60. * Title implies a how-to but page has no `` block — convert numbered instructions to `` for HowTo schema. * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (7/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `employees/getting-started/data-privacy` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/employees/getting-started/data-privacy](https://help-empuls.xoxoday.com/employees/getting-started/data-privacy) * **Title (21 ch):** `Your data and privacy` * **Description (138 ch):** `Learn what Empuls stores about you, how to export your data, and how to request deletion under GDPR, CCPA, and similar privacy frameworks.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 866 · **Internal links:** 5 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (21 chars) — add descriptive keywords to reach \~50–60. * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `employees/redemption/physical-gift-claims` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/employees/redemption/physical-gift-claims](https://help-empuls.xoxoday.com/employees/redemption/physical-gift-claims) * **Title (20 ch):** `Physical gift claims` * **Description (165 ch):** `Learn how to claim physical gifts. Confirm your shipping address and any product options so a physical award or merchandise gift can be packed and dispatched to you.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 593 · **Internal links:** 6 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 8/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (20 chars) — add descriptive keywords to reach \~50–60. * Description is 165 chars — slightly over the 160-char SERP cutoff. * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. *** ### `employees/socials/social-intranet` — 83/100 · Low * **URL:** [https://help-empuls.xoxoday.com/employees/socials/social-intranet](https://help-empuls.xoxoday.com/employees/socials/social-intranet) * **Title (15 ch):** `Social intranet` * **Description (170 ch):** `Explore Empuls's social intranet: post updates, react and comment, share files, create polls, recognize colleagues, and build a connected company culture in one platform.` * **Body H1/H2/H3:** 0 / 10 / 5 · **Words:** 1182 · **Internal links:** 10 · **Images:** 9 (empty alt: 0, generic filename: 9) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **83/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * Description is 170 chars — slightly over the 160-char SERP cutoff. * 9 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/other/faqs` — 84/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/faqs](https://help-empuls.xoxoday.com/admin/integrations/other/faqs) * **Title (17 ch):** `Integrations FAQs` * **Description (106 ch):** `Get quick answers about Empuls integrations on Empuls - setup steps, edge cases, and troubleshooting tips.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 5129 · **Internal links:** 4 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **84/100** | **Issues detected:** * Title is short (17 chars) — add descriptive keywords to reach \~50–60. * Description is 106 chars — extend to 130–160 with search terms. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (9/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/integrations/other/sdk` — 84/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/sdk](https://help-empuls.xoxoday.com/admin/integrations/other/sdk) * **Title (31 ch):** `Empuls software development kit` * **Description (134 ch):** `Embed Empuls into your own intranet or app using the Empuls software development kit. This guide walks through the setup step by step.` * **Body H1/H2/H3:** 0 / 12 / 2 · **Words:** 1352 · **Internal links:** 12 · **Images:** 12 (empty alt: 0, generic filename: 12) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **84/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 12 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (8/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/reports/organization-dashboard` — 84/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/reports/organization-dashboard](https://help-empuls.xoxoday.com/admin/reports/organization-dashboard) * **Title (22 ch):** `Organization dashboard` * **Description (91 ch):** `Live account status, R&R dashboard, engagement summary, and data overview for Super Admins.` * **Body H1/H2/H3:** 0 / 4 / 2 · **Words:** 1210 · **Internal links:** 15 · **Images:** 15 (empty alt: 0, generic filename: 15) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 6/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **84/100** | **Issues detected:** * Title is short (22 chars) — add descriptive keywords to reach \~50–60. * Description is 91 chars — extend to 130–160 with search terms. * 15 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **desc (6/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/integrations/collaboration/microsoft-teams` — 85/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/microsoft-teams](https://help-empuls.xoxoday.com/admin/integrations/collaboration/microsoft-teams) * **Title (15 ch):** `Microsoft Teams` * **Description (132 ch):** `Connect Microsoft Teams with Empuls to deliver recognition, rewards, and surveys right inside the tool your team already uses daily.` * **Body H1/H2/H3:** 0 / 12 / 8 · **Words:** 1983 · **Internal links:** 19 · **Images:** 19 (empty alt: 0, generic filename: 19) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **85/100** | **Issues detected:** * Title is short (15 chars) — add descriptive keywords to reach \~50–60. * 19 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/other/implementation-integration-governance-faqs` — 85/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/other/implementation-integration-governance-faqs](https://help-empuls.xoxoday.com/admin/integrations/other/implementation-integration-governance-faqs) * **Title (47 ch):** `Implementation, integration and governance FAQs` * **Description (140 ch):** `Browse frequently asked questions about implementation, integration, and governance on Empuls, from initial setup to day-to-day admin tasks.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 1265 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **85/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (9/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/programs/awards/jury-based-awards` — 85/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/programs/awards/jury-based-awards](https://help-empuls.xoxoday.com/admin/programs/awards/jury-based-awards) * **Title (11 ch):** `Jury awards` * **Description (130 ch):** `Run a peer-reviewed jury panel to score and select winners in your employee awards program. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 5 / 6 · **Words:** 1215 · **Internal links:** 25 · **Images:** 23 (empty alt: 0, generic filename: 23) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **85/100** | **Issues detected:** * Title is short (11 chars) — add descriptive keywords to reach \~50–60. * 23 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/sales-incentive/admin-guide/faq-admins/getting-started-for-admins-faqs` — 85/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/faq-admins/getting-started-for-admins-faqs](https://help-empuls.xoxoday.com/admin/sales-incentive/admin-guide/faq-admins/getting-started-for-admins-faqs) * **Title (33 ch):** `Getting started for admins - FAQs` * **Description (151 ch):** `Find answers to common questions about getting started with sales incentive administration on Empuls, covering setup, permissions, and troubleshooting.` * **Body H1/H2/H3:** 0 / 9 / 0 · **Words:** 1265 · **Internal links:** 0 · **Images:** 0 (empty alt: 0, generic filename: 0) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 2/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **85/100** | **Issues detected:** * Only 0 internal link(s) — add at least 2 contextual links to related docs.json pages. **Action plan (ranked by impact):** * **links (2/10):** Add ≥2 contextual internal links to related docs.json pages with descriptive anchor text. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (9/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). *** ### `admin/user-management/manage-employees` — 85/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/user-management/manage-employees](https://help-empuls.xoxoday.com/admin/user-management/manage-employees) * **Title (16 ch):** `Manage employees` * **Description (154 ch):** `Learn how to add employees one at a time or by CSV upload, update profiles and roles, configure access controls, delegate accounts, and set exit policies.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 1261 · **Internal links:** 10 · **Images:** 10 (empty alt: 0, generic filename: 10) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **85/100** | **Issues detected:** * Title is short (16 chars) — add descriptive keywords to reach \~50–60. * 10 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **intent (9/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `employees/recognitions/nominations` — 85/100 · Low * **URL:** [https://help-empuls.xoxoday.com/employees/recognitions/nominations](https://help-empuls.xoxoday.com/employees/recognitions/nominations) * **Title (22 ch):** `Submitting nominations` * **Description (158 ch):** `Nominate colleagues with citations and evidence, manage the approval workflow as a reviewer, handle jury voting, and bulk-review multiple nominations at once.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 850 · **Internal links:** 4 · **Images:** 4 (empty alt: 0, generic filename: 4) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **85/100** | **Issues detected:** * Title is short (22 chars) — add descriptive keywords to reach \~50–60. * 4 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `product-updates/july-august-2025` — 85/100 · Low * **URL:** [https://help-empuls.xoxoday.com/product-updates/july-august-2025](https://help-empuls.xoxoday.com/product-updates/july-august-2025) * **Title (34 ch):** `Product Updates - July/August 2025` * **Description (137 ch):** `Explore Empuls’s product updates for July and August 2025, covering new features and improvements. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 10 / 0 · **Words:** 772 · **Internal links:** 8 · **Images:** 8 (empty alt: 0, generic filename: 8) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **85/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 8 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (8/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `product-updates/september-2025` — 85/100 · Low * **URL:** [https://help-empuls.xoxoday.com/product-updates/september-2025](https://help-empuls.xoxoday.com/product-updates/september-2025) * **Title (32 ch):** `Product Updates - September 2025` * **Description (131 ch):** `Explore Empuls’s product updates for September 2025, covering new features and improvements. Built to save HR and admin teams time.` * **Body H1/H2/H3:** 0 / 7 / 0 · **Words:** 696 · **Internal links:** 5 · **Images:** 5 (empty alt: 0, generic filename: 5) * **Schema eligibility:** TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 8/10 | | 7. FAQ coverage | 4/10 | | 8. Search intent match | 8/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **85/100** | **Issues detected:** * No FAQ block — add an FAQ section covering common user questions (great for FAQPage schema). * 5 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (4/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **intent (8/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (8/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. *** ### `admin/integrations/health-wellness/1to1-help` — 86/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/health-wellness/1to1-help](https://help-empuls.xoxoday.com/admin/integrations/health-wellness/1to1-help) * **Title (41 ch):** `Employee wellness sessions with 1to1 Help` * **Description (133 ch):** `1to1Help integrates with Empuls so every employee can access confidential employee counselling sessions without leaving the platform.` * **Body H1/H2/H3:** 0 / 8 / 0 · **Words:** 543 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** HowTo, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 6/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **86/100** | **Issues detected:** * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **faq (6/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `admin/gifts/setup-product-based-gifts` — 87/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/gifts/setup-product-based-gifts](https://help-empuls.xoxoday.com/admin/gifts/setup-product-based-gifts) * **Title (32 ch):** `Physical and product-based gifts` * **Description (174 ch):** `Learn how to configure physical and product-based gifts in Empuls, connect courier partners, upload product catalogs, set budgets, and manage the end-to-end gifting workflow.` * **Body H1/H2/H3:** 0 / 4 / 9 · **Words:** 789 · **Internal links:** 15 · **Images:** 15 (empty alt: 0, generic filename: 15) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 9/10 | | 10. Image optimization | 7/10 | | **Overall** | **87/100** | **Issues detected:** * Description is 174 chars — slightly over the 160-char SERP cutoff. * 15 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **depth (9/10):** Expand content depth: add prerequisites, step-by-step instructions, examples, and expected outcomes. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. *** ### `employees/redemption/redeem-points` — 88/100 · Low * **URL:** [https://help-empuls.xoxoday.com/employees/redemption/redeem-points](https://help-empuls.xoxoday.com/employees/redemption/redeem-points) * **Title (13 ch):** `How to redeem` * **Description (154 ch):** `Browse the rewards catalog, check your points balance, place an order, top up any shortfall with a card, and track every redemption in your order history.` * **Body H1/H2/H3:** 0 / 5 / 0 · **Words:** 881 · **Internal links:** 6 · **Images:** 6 (empty alt: 0, generic filename: 6) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 4/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **88/100** | **Issues detected:** * Title is short (13 chars) — add descriptive keywords to reach \~50–60. * 6 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **title (4/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (9/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/collaboration/microsoft-teams-it-admin` — 89/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/microsoft-teams-it-admin](https://help-empuls.xoxoday.com/admin/integrations/collaboration/microsoft-teams-it-admin) * **Title (58 ch):** `Microsoft Teams (installation guide for IT administrators)` * **Description (123 ch):** `Connect Microsoft Teams (installation guide with Empuls to automate employee data sync and extend your engagement programs.` * **Body H1/H2/H3:** 0 / 3 / 0 · **Words:** 1100 · **Internal links:** 9 · **Images:** 9 (empty alt: 0, generic filename: 9) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 8/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 7/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **89/100** | **Issues detected:** * Title implies a how-to but page has no `` block — convert numbered instructions to `` for HowTo schema. * 9 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **intent (7/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **desc (8/10):** Rewrite `description` to 130–160 chars with primary keyword + user benefit. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. *** ### `admin/surveys/enps-pulse` — 89/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/surveys/enps-pulse](https://help-empuls.xoxoday.com/admin/surveys/enps-pulse) * **Title (22 ch):** `eNPS and pulse surveys` * **Description (145 ch):** `Learn how to run eNPS and employee pulse surveys in Empuls, track sentiment trends, benchmark scores, and generate action plans from the results.` * **Body H1/H2/H3:** 0 / 7 / 5 · **Words:** 1151 · **Internal links:** 4 · **Images:** 2 (empty alt: 0, generic filename: 2) * **Schema eligibility:** FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 7/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 6/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 8/10 | | **Overall** | **89/100** | **Issues detected:** * Title is short (22 chars) — add descriptive keywords to reach \~50–60. * 2 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **intent (6/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **title (7/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **img (8/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ### `admin/integrations/collaboration/microsoft-teams-usage` — 93/100 · Low * **URL:** [https://help-empuls.xoxoday.com/admin/integrations/collaboration/microsoft-teams-usage](https://help-empuls.xoxoday.com/admin/integrations/collaboration/microsoft-teams-usage) * **Title (42 ch):** `Microsoft Teams: how to use the Empuls app` * **Description (153 ch):** `A complete guide to using and administering Empuls within Microsoft Teams — recognition, rewards, surveys, and your social intranet, in the flow of work.` * **Body H1/H2/H3:** 0 / 5 / 5 · **Words:** 2594 · **Internal links:** 29 · **Images:** 29 (empty alt: 0, generic filename: 29) * **Schema eligibility:** HowTo, FAQPage, TechArticle, BreadcrumbList | Criterion | Score | | ---------------------- | ---------: | | 1. Title optimization | 9/10 | | 2. Meta description | 10/10 | | 3. H1 | 10/10 | | 4. H2 structure | 10/10 | | 5. Internal linking | 10/10 | | 6. Schema eligibility | 9/10 | | 7. FAQ coverage | 9/10 | | 8. Search intent match | 9/10 | | 9. Content depth | 10/10 | | 10. Image optimization | 7/10 | | **Overall** | **93/100** | **Issues detected:** * 29 image(s) use generic filenames like "Screenshot-…" or "image1" — rename to descriptive kebab-case filenames. **Action plan (ranked by impact):** * **img (7/10):** Rename generic screenshot filenames and add descriptive alt text (under 125 chars) to every image. * **title (9/10):** Rewrite `title` to a unique 50–60 char, keyword-led phrase. * **faq (9/10):** Append an FAQ section (3–5 real questions) and wrap in `` for FAQPage schema. * **intent (9/10):** Realign body to the intent implied by the title (how-to → ``; overview → definitions + links). * **schema (9/10):** Ensure the page qualifies for at least one JSON-LD type (HowTo/FAQPage/TechArticle) by adding steps or Q\&A. *** ## Methodology * **Corpus:** every page string in `docs.json > navigation`, filtered to files that exist on disk and excluding `es/`, `fr/`, `zh/`, and `hidden: true` pages. * **Scoring:** each of the ten criteria is scored 0–10 by static analysis of MDX frontmatter, headings, links, images, and word count. Sub-scores are summed for an Overall score /100. * **Duplication:** a title/description is flagged as duplicate when the same case-insensitive string appears on ≥2 pages in the corpus. * **H1 rule:** Mintlify renders the frontmatter `title` as the page H1, so a body `#` heading is scored as a second H1 and demoted in the action plan. * **Word count** excludes fenced code blocks and JSX tags; treat it as an approximation. * **Internal links** are counted as Markdown links with a root-relative target (`/…`); external URLs and MDX `` links are not counted, so real internal-linking density is often higher than shown. * **Search intent & FAQ coverage** use content-shape proxies (title verbs, ``, ``, question-style headings). Where the auditor uses "common user questions", real queries were spot-checked against public search suggestions for Empuls-related topics (e.g. "how to redeem Empuls points", "how to log in to Empuls"). * **Schema eligibility** flags pages that already contain the structural cues (steps, Q\&A, TOC-style H2s) needed to emit HowTo, FAQPage, or TechArticle JSON-LD; BreadcrumbList is universal in Mintlify.