Integrations
QueryRev AI integrations Google Search Console, Google Analytics 4 and the site crawler.
QueryRev AI connects to Google Search Console, Google Analytics 4 and your website through its own crawler, QueryRevBot. All three are read-only: nothing in your Google account or on your site is changed. Approved changes reach your site only through your CMS, under your policy, and revenue and CRM sources bring in your orders and deals.
Search and analytics
Each is connected in the onboarding flow, shows its state in the product, and can be reconnected, disconnected or have its stored data deleted by you.
Google Search Console
Clicks, impressions and positions by page, query, country and device. The first connection brings in up to 16 months of history. After that it is refreshed every day, and recent days are read again, because Google revises them.
- Read-only access
- 16 months of history
- Refreshed daily
Google Analytics 4
Organic search sessions, engaged sessions, key events and revenue, by landing page and day. QueryRev reads the organic search channel only and asks for read-only access.
- Read-only access
- Organic search only
- Refreshed daily
Site Crawler: QueryRevBot
QueryRev’s own crawler reads your pages as a search engine does: status, title, headings, canonical, robots directives, structured data and internal links, rendering a page where it needs JavaScript. It obeys robots.txt, crawls the site about once a week and returns to a page when your sitemap says it changed. About the crawler.
- Obeys robots.txt
- Weekly crawl
- Recrawl on change
Read-only means read-only. QueryRev asks Google for the two read-only permissions these products offer and for no write access. The crawler never submits forms, never signs in and never changes anything on a site. What it reads becomes the inventory of managed URLs that plans are measured in.
Execution
Reading is half of the loop. The other half is applying an approved change where your site is managed, under your policy, with the state before and after kept.
Where changes are applied
- WordPressPages and posts of a WordPress site.
- ShopifyFor stores: product, collection and content pages.
- WebflowSites built and hosted on Webflow.
- GitHub Pull RequestsFor Git-based sites: a change arrives as a pull request your team reviews.
Nothing outside your policy
A change is applied only if your policy allows it for that page and that kind of change. Everything else waits for a person.
Before and after, in the Change Ledger
Every material change is written to the Change Ledger with the state before and after, who approved it and how it was applied.
No usable API? A universal layer
For a site whose CMS has no usable API: a one-time install that applies approved page-level changes, such as titles, canonicals and structured data, as pages are served. It needs no CMS credentials, each change can be switched off on its own, and it writes to the ledger like any other path.
No integration? A person applies it
Where QueryRev cannot write to your CMS, an approved change becomes a task with the exact text to apply. The ledger entry and the verification work the same way.
Business data
Analytics tells you what a visit earned on the site. For many businesses the money closes somewhere else: in a store’s order system, with a payment provider, or in a CRM. These sources bring that revenue in, and webhooks, an API and MCP connections send decisions, changes and outcomes to your own tools.
Sources and connections
- ShopifyOrders and their revenue.
- StripePayments and subscriptions.
- HubSpotLeads and deals.
- SalesforceLeads and opportunities.
- Other order and CRM systemsThrough the same source model.
- Webhooks and APITo send decisions, changes and outcomes to your own systems.
- MCPConnections to MCP-compatible tools, where they fit.
- Value MappingFor a business with no revenue source to connect: you set what a lead, a sign-up or a booking is worth.
What they add is organic revenue attribution from recorded orders and deals. Without them, revenue comes from Google Analytics 4 where your property reports it, and every figure that is an estimate is labelled as modeled.
Product names are the trademarks of their owners. QueryRev AI is an independent product: it is not affiliated with, endorsed by or a partner of Google, WordPress, Shopify, Webflow, GitHub, Stripe, HubSpot or Salesforce.
Integrations FAQ
Short answers first. Ask anything else at business@queryrev.com.
Which integrations does QueryRev AI support?
Three kinds. To read, all read-only: Google Search Console, Google Analytics 4 and QueryRev’s own site crawler, QueryRevBot. To apply approved changes: WordPress, Shopify, Webflow and GitHub pull requests, with a universal execution layer for sites without a usable API. To bring in business data: revenue and CRM sources, webhooks, an API and MCP connections.
Does QueryRev change anything in my Google account or on my site?
No. It asks for read-only access to Search Console and Analytics 4 and for no write access, and the crawler only reads pages. Changing a site is a separate capability: it goes through your CMS and works only under your policy and with your approval.
Which CMS can QueryRev apply changes to?
It applies changes to WordPress, Shopify, Webflow, and Git-based sites through GitHub pull requests. Where there is no integration, an approved change becomes a task a person applies, with the same ledger entry and the same verification.
Does QueryRev integrate with Shopify, Stripe, HubSpot or Salesforce?
As revenue and CRM sources, so that revenue is read from recorded orders and deals. Without one connected, revenue comes from Google Analytics 4 where your property reports it.
How do I control QueryRevBot on my site?
With robots.txt. QueryRevBot names itself in its user agent, obeys a Disallow rule written for it and honours a Crawl-delay of up to 10 seconds. The crawler page at queryrev.com/bot shows the exact lines.
Can I disconnect a source and delete its data?
Yes. In the product’s integration settings a source can be reconnected, disconnected, or have its stored data deleted.
Keep exploring