Skip to main content

​
Run slash commands

  1. Type a slash / in the chat input to check the supported slash commands.
  2. Select the slash command you want to run.
Kombai will run the workflow and generate a report of the issues found, along with suggestions to resolve them. For the /improve-seo or /improve-accessibility commands, Kombai will also fix the identified issues and generate a final audit report.

​
Supported slash commands

CommandDescription
/audit-seoAudits your project’s SEO and generates a detailed report of all crawlability and indexability issues found, along with suggestions to resolve them.
/audit-accessibilityAudits your project’s accessibility based on WCAG 2.0, 2.1, and 2.2 accessibility standards and generates a report of the issues found, along with suggestions to resolve them.
/improve-seoAudits and identifies crawlability and indexability issues in your codebase, fixes them, and generates a final audit report.
/improve-accessibilityAudits and identifies accessibility issues in your codebase based on WCAG 2.0, 2.1, and 2.2 accessibility standards, fixes them, and generates a final audit report.

​
Audit standards

​
SEO

Kombai performs a comprehensive audit of on-page and technical SEO elements to ensure your project is indexable and ready to rank. Here are the SEO issues that Kombai detects:
  • Crawlable anchors: Validates that anchor tags are accessible and indexable, flagging issues like empty hrefs, javascript:void(0) targets, off-screen positioning, negative tabindex, and more.
  • Canonical URL: Detects invalid canonical URLs, multiple conflicting canonical URLs, root canonical URLs on subpages, and more.
  • Legibility: Audits for visual accessibility, ensuring text meets WCAG contrast standards and maintains legible sizes on mobile viewports.
  • Hreflang tags: Detects malformed language codes and non-absolute links in your international SEO tags.
  • Link text: Identifies generic anchor text (e.g., “click here,” “read more”) to ensure links provide valuable context for search engines.
  • Page indexability: Validates that the page is technically accessible to search bots by auditing HTTP status codes, robots.txt syntax, and exclusion directives (like noindex or X-Robots-Tag), while also ensuring essential meta descriptions are populated.

​
Accessibility

Kombai uses the Axe-core engine to detect accessibility issues. When running /improve-accessibility, Kombai also fixes the identified issues. Here are a few examples of accessibility issues that Kombai detects:
  • ARIA attributes: Validates that elements only use ARIA attributes supported by their specific role (e.g., ensuring a heading doesn’t have a checkbox attribute).
  • Keyboard scrollability: Identifies scrollable containers missing a tabindex attribute, which prevents keyboard-only users from accessing hidden content.
  • Video captions: Verifies that <video> elements include caption tracks, ensuring content is accessible to users with hearing impairments and indexable by search engines.
  • Touch target size: Ensures interactive elements (buttons, links) are large enough and spaced appropriately so mobile users can tap them without accidentally hitting neighboring elements.
  • Image alt text: Detects images missing alt attributes or valid presentation roles, which are critical for accessibility compliance.
For the complete list, please refer to the Axe-core documentation.