Frequently Asked Questions

More context

We aim to keep answers concise, but some topics—like depth selection, rate limits, or how to turn trees into briefs—benefit from added nuance. If you have a question that isn’t covered here, head to the Contact page and let us know. We use your feedback to refine both the product and the documentation, and we update this page regularly so the next person gets an even clearer answer.

Choosing the right depth

Depth controls exploration, not quality. A good practice is to run a quick level‑1 pass to map the immediate neighborhood around your seed terms, highlight two or three promising branches, then selectively expand those to level‑2. If your topic is highly fragmented or you see strong intent diversity, expand one branch to level‑3 for additional nuance. This staged approach balances signal with speed and keeps your trees readable, which in turn makes it easier to brief and ship content.

Working with multiple seed keywords

Entering several seeds at once accelerates discovery, but you’ll get the most value by grouping seeds that share the same searcher intent. For example, combine “product photoshoot ideas” with “product photoshoot at home,” but keep “product photography lighting” in a separate batch. This avoids mixing different tasks and helps the tree express a clean theme, which later supports more targeted internal linking and clearer page objectives.

What counts toward the daily limit?

Each run of the Find Suggestions action counts as one attempt, regardless of how many seeds you provide. Stopping early still counts because rate‑limit protections are engaged the moment the expansion begins. If you need higher limits for a campaign or a larger team, open a request on the Contact page and include rough volume expectations. We’ll respond with options such as temporary quota increases, scheduled windows, or a dedicated backend endpoint.

Exporting and organizing results

The JSON export intentionally mirrors the tree you see in the interface. Many teams import that structure into a spreadsheet where each row contains the node keyword, its parent, and its depth. This simple model allows you to sort by branch, filter by level, tag items that become briefs, and track shipping status. If you want a CSV export option in the UI, let us know—your feedback shapes our roadmap.

Privacy and third‑party APIs

We request suggestions from public autocomplete services and, when configured, through your own backend. We do not share your research with ad networks. Logs capture only operational metadata (errors, timing, and counts) so we can diagnose issues and keep the experience fast. For full details, see the Privacy Policy.

Turning trees into action

The fastest path from ideas to outcomes is a repeatable brief template. Summarize searcher intent, list sub‑questions to answer, include examples or comparisons to add substance, link to related pages, and define the conversion you want for the page or video. Ship a small set, measure, and iterate. Over time, the tree becomes not just a map of ideas but an operating system for your content process.