Purpose of this guide
This guide helps you direct questions and feedback to the right area when working with Search Atlas. Module ownership can change as products evolve, so use the module name and workflow details when requesting assistance.
Module responsibility overview
When raising a question or issue, identify which of the following Search Atlas modules it belongs to, then include that module name along with the full context of your request:
- OTTO (Automated SEO): Questions about reviewing, approving, or monitoring automated on-page and technical optimization recommendations generated by OTTO.
- Content Genius (Content workflows): Questions about article generation, AI-assisted writing, content planning, and bulk content tasks within Content Genius.
- On-Page Audit: Questions about page-level analysis, topical terms, questions, audit reports, and content score tracking.
- Rank Tracker: Questions about keyword performance, visibility trends, rank movement, and report sharing.
- Site Auditor (Technical SEO and site health): Questions about crawling, technical findings, indexing checks, and website performance insights.
- Projects and account settings: Questions about project setup, website connections, user access, permissions, and account configuration.
How to route a question clearly
- Identify the specific module from the list above that best matches your question.
- Note the project name, the page or keyword involved, the action you were attempting, and the result you expected versus what actually happened.
- Include all of that context when submitting your request — for example: "I attempted an OTTO automated SEO action in Project A and the recommendation did not apply as expected."
- If you are unsure which module applies, describe the workflow you were using and the outcome, and the support team will route it appropriately.
Product ownership and escalation
Search Atlas does not maintain a fixed public list of individual owners for every module. Internal ownership may change, and a feature can involve multiple teams, such as product, engineering, SEO, or customer education. The most reliable route is to identify the affected module, gather the full context (project name, exact action taken, expected vs. actual result), and submit that detail through the platform support channel so it can be routed to the correct team without back-and-forth.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.