ACCOUNT AND PROJECTS
Account, projects and NeuralFuel
A clear structure prevents client data from mixing and makes recommendations, reports and connections easier to maintain.
How to separate projects
Use one project per site or work unit when you need to separate property, data, content and reporting. For client portfolios, use consistent names and avoid ambiguous abbreviations.
Before connecting a source, confirm that you are in the correct project. The URL and connected Google account define the analysis context.
Preferences and connected accounts
Review user preferences, language and active connections in Settings. If someone stops working on a project, revoke access or tokens from the relevant integration.
Google connections provide data; WordPress and GitHub provide execution surfaces. Keep each one at the minimum required scope.
NeuralFuel
NeuralFuel is the balance used by AI operations and some analyses. Consumption depends on the tool and the amount of data processed.
Before launching a large generation, review the estimated usage and reserve capacity for the revisions or variants you will actually use.
- Balance and limits depend on the plan.
- Failed operations may show why usage occurred.
- If the balance runs out, finish the pending review before starting another generation.
Plans and capacity
Free, Pro and Agency plans differ in sites, Google accounts, NeuralFuel capacity and support. Check Pricing on the website for current terms.
Plan growth by properties, reporting frequency and content volume, not only by number of users.