Getting started
Everything hangs off a brand: a site you want recommendations for, the Search Console property that reports on it, and its pages.
Add a brand
Brands, then Add a brand. The form asks for:
- Name, and a slug — leave the slug blank and it is derived from the name.
- Landing URLs — the pages to start from, one per line.
- Positioning, Who it is for and Tone of voice — how the brand describes itself.
- Proof points and Banned claims — facts the copy may use, and claims it must never make.
Connect Search Console
Open the brand and press Connect Search Console. You will be asked to sign in with the Google account that owns the property, and to grant read-only access. GrowthOps never gains the ability to change anything on your site.
The Google account you connect does not have to be the one you sign in with — an agency can sign in as itself and connect a client's property.
Until a property is connected there is nothing to report on. Once it is, the brand shows the property it reads, and Reconnect replaces the grant if you ever need to.
Connecting and reconnecting both fetch straight away, before you are returned to the brand. It is the wait of a few seconds, and it is there so the page you land on shows the data the new grant can actually reach — rather than looking unchanged until the next night's run.
A brand is five sections, listed down the left of its page:
- Search Console — the property it reads, and how current the data is.
- Attribution — issue a token so your site can report visits by source. Search Console counts what Google showed and what was clicked; it cannot see where an account came from.
- Answer engines — whether the AI crawlers may read the site.
- Code — connect a source repository, and recommendations arrive as pull requests rather than instructions.
- Settings — the brand's own fields, the ones the form above asked for.
If a brand has stopped reporting, that banner and its Pull now button sit above all five, because the data behind every one of them is the same age.
When a brand stops reporting
Search Console publishes two to three days behind, so a brand whose newest day is not today is normal. More than four days behind is not, and the brand's page says so: This brand has stopped reporting, with the day the data ends. That banner matters because it is not local to one screen — recommendations, verdicts and the weekly mail are all drawn from the same data, and every one of them is that old.
Press Pull now. The page then says what the run did, including when it did nothing:
- Fetched n page rows just now — the nightly job had missed them, and the brand is current again.
- Google returned nothing new — the days you are missing are the ones Google has not published yet. The normal answer on a brand that is already up to date.
- The fetch failed, or a named reason — the grant itself has expired. Reconnect renews it, and because reconnecting fetches too, one round trip both renews the grant and proves it works.
Fetching first is the order to try, not reconnecting: a nightly job that has stopped is not fixed by a fresh grant, and until this said so the honest sequence was guesswork.