Connecting Sources

Open Integrations and choose Connect next to the site. If the site is not listed, add it first under Workspace, then Sites. A Founder or an SEO Manager connects the sources of a site; other roles see them.

1. 1Search Console: connect Google and choose the property of the site.
2. 2GA4: choose the site’s GA4 property, with the same Google account.
3. 3Crawl: check the hosts in scope and confirm you may have the site crawled.
4. 4Business: confirm or correct what QueryRev read about the business.
5. 5Revenue: connect the store the site’s orders come from.

Skip for now leaves a step open. You can come back to it from Integrations at any time, and the other sources keep working meanwhile.

QueryRev reads clicks, impressions and position for every page and query, 16 months back, and refreshes them daily. It never changes a property.

Choose Connect Google. Google asks for read-only access to Search Console and Google Analytics, and you can untick either. QueryRev then lists the properties your Google account can read and selects the best match for the site, a Domain property or a URL-prefix property.

If no property matches, the account cannot read this site yet. Ask the owner of the site to add the account to its Search Console property at any level above unverified, or connect the account that already has it.

GA4 brings organic-search sessions, engaged sessions, key events and GA4-reported revenue per landing page and day, 16 months back. It uses the Google account from the first step, and shows each property’s time zone, currency and key events so you can pick the right one.

GA4-reported revenue is what GA4 attributes. It is labelled as such everywhere and is never counted as Known revenue, which comes from your store.

QueryRevBot, the crawler, fetches every page of the site about once a week, at one page per second over one connection. It reads robots.txt first and obeys it, and it records the fields that matter for search: status, title, description, headings, canonical, structured data and internal links. A page the sitemap says has changed is fetched again within the hour.

Check the hosts in scope: pages on these hosts are crawled, and everything else is recorded as out of scope and never fetched. Then tick that you own the site or are authorised to have it crawled; the confirmation is kept in the audit log with your name and the time. The QueryRevBot page explains how a site owner can slow it down or stop it.

Ten short items describe the business behind the site, such as its business model, brand names, markets, offerings and audiences. QueryRev proposes what your data shows, and you confirm or correct each item. Each item says what waits for it, so anything can be left for later.

Nothing proposed is used in a value figure until a person confirms it, and every suggestion shows how it was obtained: read from your data, proposed by a model, or entered by a person. A value a person entered, such as the value of one lead, is never replaced by a suggestion.

Choose Connect WooCommerce or Connect Shopify. Your store makes a read-only key on its own approval page, and QueryRev never changes your store. The store address must be the site’s own address or a subdomain of it.

A store brings Known revenue, orders and products: the orders your store recorded and the visit that brought each one, and Influenced revenue beside it. Without a store, search figures keep working; money figures wait until one is connected.

The Sources list shows every source of every site, with its account or property, how far its data reaches, and when it last ran and runs next. Open a source for its coverage, its run history and its quality flags.

Quality flags name what Google left out: a day capped at 50,000 rows, rows GA4 withheld or folded into “(other)”, or a sampled report. Every number built on a flagged day carries the flag. Data Check compares what QueryRev stored with Google’s own screens, so you can see the two agree.

Pause stops a source and keeps everything stored; Resume starts it again. Disconnect stops it for good and keeps its history unless you also choose to delete the stored data.

A deletion runs 24 hours after you ask for it, and Undo in the source’s panel keeps everything until then. Deleting a source’s data also deletes every question asked of Nori about the site, with its answer, because the answers quote that data. The audit log and the run history, which hold dates and counts and no search data, are kept.