The query that found the page, and what the page went on to earn.
Search Console ends at the click. Your analytics starts after it. Joining them at the URL turns a ranking report into a commercial one: which queries bring people who convert, which bring people who read one paragraph and leave, and which pages are worth defending.
In short: Reveliqo reads query, impression, click and average position data per URL from Search Console and relates it through the content graph to the pages, conversions and revenue that followed the click.
What it is
Google Search Console is Google's own report on how a verified site appears in search: the queries it showed for, impressions, clicks, average position and the URL that ranked, plus indexing and coverage state.
What this lets you ask
- “Which queries bring buyers, and which bring a single page and an exit?”
- “This page gained position and lost revenue — what changed on it?”
- “Which pages earn impressions we never convert, and what were those people searching for?”
What Reveliqo receives
- Query, impressions, clicks and average position, by URL, by day, by country and device
- Page-level index coverage, and the canonical URL Google selected
- Search appearance types, so a rich result and a plain blue link are not counted as the same thing
- Daily history backfilled to the limit of Search Console's retention when the property is first connected
How it is connected
- Sign in with Google and grant read access to the verified property
- Match the property to a Reveliqo site — a domain property and a URL-prefix property cover different sets of pages, and the difference is shown before you confirm
- Confirm the URL normalisation rules, so /page, /page/ and /page?ref= join to one row instead of three
- Connect your content platform if you want a query to resolve below the URL, to the headline or claim on the page that earned it
How you verify it
- Clicks per page for a closed day sit within Search Console's own rounding of the same figure
- Organic landing pages in Reveliqo carry a query list once two days of data have been pulled
- The join rate is stated openly: how many organic visits matched a Search Console URL, and how many did not
Limits worth knowing
- Search Console anonymises rare queries and rounds its counts. Its totals and Reveliqo's visit counts will not tie exactly, and neither figure is wrong.
- The join is made at the URL, not at the person. A query is related to a page's outcomes; it is not traced to an individual visitor's purchase.
- Data arrives a day or two behind and is restated afterwards, so the most recent days are marked provisional.
Connect a site today. Read tomorrow's brief instead of building it.
Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.
Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo