Docs
Sources and signals
Rank tracking
Daily positions for the keywords you track, broken out by location and device, and grouped the way you think about your site rather than alphabetically.
The useful output is momentum rather than a number. A page that moved from 14 to 11 this week is a different situation from a page that has sat at 11 for a year, and only one of them is worth your morning. Onça flags the pages sitting on the edge of page one, where a small edit moves the most traffic.
Google Search Console
Onça reads your Search Console data continuously and turns it into candidates instead of charts. This is the feed that most often produces the cheapest wins, because it shows you demand you have already earned and are not converting.
The clearest example is a page with high impressions and low click-through. The ranking already exists and the traffic does not, which usually means the title and description are the problem rather than the content. That is a fifteen minute fix with a measurable result, and it is exactly the kind of thing that never makes it onto a to-do list.
Google Business Profile
Posts, review prompts, hours, and services. Onça watches for the things that quietly go stale: holiday hours nobody updated, a service you now offer that is not listed, a run of recent reviews with no response.
Local work lands in the same queue as everything else rather than in a separate tab you check on Fridays, which is the main reason local upkeep slips in the first place.
Your content
Your published pages, read against the queries you actually rank for. That comparison is what surfaces gaps: subjects your audience searches for that your site covers thinly or not at all, and pages that have drifted out of date relative to what people now ask.
When a gap is worth filling, Blog Studio turns it into a brief and a first draft.
How the feeds combine
No single feed is authoritative. A ranking drop is more interesting when Search Console shows impressions holding steady, because that points at a click problem rather than a visibility problem. A content gap matters more when the queries behind it are ones you already rank adjacently for.
Reading the feeds together is the whole reason they live in one place. What comes out the other side is the opportunity queue.