What Search Console does
The Search Console connection lets Amanda AI factor organic search data into paid keyword decisions and gives you an in-app view showing both sides of search at once. Three things, working together:
Adding high-value search terms. Queries showing up in Search Console that meet your thresholds get added to your paid campaigns automatically.
Pausing keywords that are already covered by organic. Queries ranking strongly organically can be paused on the paid side, so you stop paying for clicks you’d likely get anyway. Toyota Denmark used this rule to stop bidding on queries where their site already ranked well. Read the case study.
The Holistic Search view. Paid and organic data shown side by side — so the trade-off between the two is visible in one place instead of scattered across two tools.
Adding high-value search terms from Search Console
If a query is generating impressions for you organically but isn’t in your paid account, Amanda AI can pull it in based on rules you set:
Average position thresholds. Minimum and maximum. It lets you target a specific organic visibility band — for example, queries ranking between position 5 and 15: visible enough to confirm relevance, low enough that paid coverage genuinely adds reach.
Minimum impression count over the last 30 days. Filters out long-tail noise so only queries with real volume get added.
Together, these rules turn Search Console into a structured keyword-mining feed. You’re not guessing what’s worth bidding on; you’re letting actual organic search behavior inform the call.
Pausing keywords organic already covers
Two ways to do this, both rules-based, only one active at a time per project:
Strong organic presence. If a query ranks above a position threshold you set and has had at least N impressions in the last 30 days, the paid keyword pauses. Brand keywords can be excluded so brand bidding isn’t accidentally turned off — which matters, because the rule is purely organic-rank based and doesn’t factor in competition.
Non-competitive keywords. Pauses keywords where Google Ads’ own competition metric is low and organic rank meets your threshold. Catches the queries where you’d likely win the click without bidding — either because few advertisers are competing, or because organic is already carrying it. Brand exclusion is available here, too. Worth being precise: “non-competitive” doesn’t mean zero competition (nearly impossible on broad match), it means competition is low enough that paid clicks are likely cheap or unnecessary.
You pick one of the two rules per project. They can’t run in parallel.
The Holistic Search view
An in-app view that shows paid and organic as one system instead of two. The top of the page summarises the total ad cost, the estimated organic value, and the brand keyword cost change. Below that, a scatter plot showing how paid spend and organic clicks have shifted per keyword, and a side-by-side comparison of top keywords by clicks across paid and organic, with movement arrows.
The point is to see the trade-off directly: where paid is doing work, organic isn’t, where organic is carrying paid, and where the two overlap in ways worth re-examining.
Where Google picks up
Search Console needs to be connected to the Google account running the campaigns — a one-time auth step during project setup. After that, Amanda AI reads the data; it doesn’t write back to Search Console.
The thresholds (position bands, impression minimums, brand exclusion toggles, which pause rule is active) are configured per project. They can be changed at any time, and the integration can be turned off entirely if you’d rather not have organic data influencing paid decisions on a specific account.
When Search Console is worth connecting to Amanda AI
A rough heuristic.
Worth turning on when there’s enough organic visibility to generate signal — typically accounts past the early-stage SEO phase, where Search Console is showing meaningful impressions and ranking data across more than just brand terms.
We’d hold off on accounts where organic data is too thin to be representative, where you’re deliberately bidding on terms you also rank for as a category-defense move, or where the SEO team has strong views on which paid keywords should stay live regardless of organic position. In that last case, build the exclusions manually first.
Either way, the rules are configurable, the brand exclusion is there for a reason, and nothing pauses without a threshold being met. L’Oréal used the integration across a portfolio of brands to expand coverage and avoid bidding on queries with strong organic visibility. Read the case study.
