The 24 Slash Commands: Work Faster Without Leaving Chat

Discovering commands

Type / in any message box to open the command menu, which lists available commands with a short description. Commands are contextual to the tools your workspace has connected, so a workspace without RankAudit connected won't show the audit command.

The core set

The most-used commands create work or pull data without switching tabs: /task creates a RankOps task from the message text, /rank pulls the current position for a keyword, /audit requests a fresh crawl, and /decision logs a permanent note pinned to the channel.

• /task [description] — creates a RankOps task
• /rank [keyword] — pulls current tracked position
• /audit [url] — requests a RankAudit crawl
• /decision [note] — pins a decision record to the channel

Command output

Most commands post a rich card back into the channel confirming what happened and linking to the created object, so the rest of the team can see the outcome without leaving the chat.

Why this matters

In a fast-paced SEO environment, context switching is a significant productivity drain. Manually navigating to different tools to create a task, check a keyword's ranking, or initiate a content audit fragments your workflow. By embedding these actions directly into your communication stream, RankTalk's slash commands drastically reduce the friction of administrative tasks, ensuring that insights gained during discussions are immediately actionable. This eliminates the 'I'll do it later' trap, where crucial follow-ups are often forgotten or delayed, directly impacting project velocity and campaign responsiveness.

Consider a scenario where a client raises an urgent ranking drop for a core keyword during a chat. Instead of leaving RankTalk to open your rank tracker, then another tool to create a task for investigation, a simple `/rank check [keyword]` provides immediate data. Following this, `/task investigate ranking drop [keyword] @analyst` assigns the issue instantly, complete with a link to the current conversation. This integrated approach ensures that critical SEO issues are addressed with minimal latency, preventing minor dips from escalating into significant performance losses, thereby safeguarding client value and team efficiency.

Prioritising Requests: The `/task` Command Workflow

The `/task` command is arguably the most critical for workflow management, but its effectiveness hinges on consistent prioritisation. When creating a task directly from a conversation, immediately consider its impact and urgency. A common pitfall is creating tasks without assigning a clear priority, leading to a backlog of undifferentiated work. Establish a team-wide convention for priority levels (e.g., Critical, High, Medium, Low) and ensure every `/task` command includes this, alongside a due date and assignee. This proactive approach ensures that urgent SEO issues, such as broken redirects or indexation errors, are not lost among routine content updates.

To maintain clarity and prevent task sprawl, leverage the task description field judiciously. Rather than just a title, use this space to summarise the core problem and expected outcome, drawing directly from the preceding chat context. For instance, `/task fix broken canonicals on /category-x-page due:tomorrow priority:high desc:Canonical on product listing page points to itself, should point to /category-x. Affects indexation.` This level of detail, embedded at the point of task creation, prevents subsequent back-and-forth for clarification, saving valuable time and ensuring that team members can act decisively and independently.

• Always include `priority:` and `due:` with `/task`.
• Summarise core problem and desired outcome in the `desc:` field.
• Assign tasks to specific team members using `@username`.
• Link to relevant documentation or previous decisions if applicable.

Do it now

Open any active conversation in RankTalk and practice creating a task, requesting a ranking, and logging a decision using slash commands. Think of a recent SEO insight or action you needed to record; now, do it directly within the chat interface, observing how quickly these actions are processed and acknowledged within the system. This immediate application reinforces the command structure and demonstrates the efficiency gains firsthand, solidifying your muscle memory for a more streamlined workflow moving forward.

• Type `/task optimise blog post about [topic] priority:medium due:friday @content_editor`.
• Enter `/rank check "best [keyword] in [country]"` to see current positions.
• Use `/decision log "Approved new content brief for [client]" type:strategy`.
• Experiment with `/audit request "Technical audit for domain.com" @tech_lead`.

Key takeaways

• ✓Type / to discover which commands are available in your workspace
• ✓Use /task to convert a message into tracked work immediately
• ✓Check the confirmation card's link rather than assuming the command worked

Do it now

Use slash commands, members management and inbox triage to move fast. Take it to the client thread.