Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Decisions first
Query Search Console and Plausible Stats API v2 for the same reporting window, preserve each raw request, aggregate each source to canonical page before joining, and compare Google visibility with Plausible visitors, visits, views, bounce, duration, and goals. Use custom properties only for approved low-cardinality context. Never join an aggregate Search Console query to a visitor, session, or goal conversion.
- Plausible visitors, visits, and pageviews are distinct metrics; select the one that matches the question.
- Imported-data inclusion and API warnings can change results; preserve response metadata and show the caveat.
- Plausible is not currently a native SearchHandled connector.
Keep search exposure and onsite behavior separate
Build adjacent evidence panels first; create the page bridge only after the two source reports are independently correct.
Search Console supplies Google impressions, clicks, CTR, and position for aggregate query-page combinations. Plausible supplies visitors, visits, pageviews, bounce rate, visit duration, sources, entry pages, and configured goals. Their identifiers, collection points, privacy design, and processing rules differ.
Use the bridge to answer decisions such as which high-impression pages need a better search promise, which organic landing pages produce a qualified goal, and where instrumentation changed. Do not expect totals to reconcile exactly or treat a click-to-visit ratio as a universal quality score.
| Evidence | Source | Safe interpretation |
|---|---|---|
| Impressions and clicks | Search Console | Google search visibility |
| Visitors and visits | Plausible | Onsite audience and sessions by its definitions |
| Goal conversions | Plausible | Configured event completion |
| Revenue or qualified lead | Business system | Outcome under a disclosed join |
Query Stats API v2 reproducibly
Save the endpoint payload, site, date range, metrics, dimensions, filters, timezone assumptions, response metadata, and transformation version.
Plausible's Stats API v2 uses a POST query with Bearer authentication and has a default request limit documented by the provider. It is a Business-plan feature. Cache governed extracts, group only by dimensions needed for the decision, and keep the key server-side.
Read response metadata and warnings. Plausible documents cases where imported data may be omitted for some dimension and filter combinations, and its metric documentation notes small variation can occur under counting heuristics. Those are report notes, not reasons to silently massage totals.
Aggregate, normalize, then join
Map raw page paths to an effective-dated canonical ID and aggregate each source independently before combining the results.
Preserve host, path, redirect, locale, trailing-slash, and relevant query-parameter rules. Keep the raw values available. Plausible entry pages and Search Console canonical page attribution can legitimately describe different URL forms during a migration.
Never join query-level Search Console rows directly to a page-level Plausible table and then sum analytics metrics; every page metric will repeat for each query. Instead present a query panel, a page-level search aggregate, a page-level Plausible aggregate, and a source-labelled decision layer.
- Raw page value
- Canonical-page ID
- Effective date
- Redirect evidence
- Independent source aggregate
- Coverage flag
Use goals and custom properties sparingly
A Plausible goal or custom property is trustworthy only when its definition, firing rule, privacy review, and change history are attached to the report.
Define qualified outcomes such as accepted signup, demo request, or purchase confirmation rather than generic button clicks. Test refreshes, retries, duplicate submissions, and SPA navigation. If custom properties are used, choose low-cardinality context that supports a real decision and does not contain personal or sensitive data.
Publish the percentage of target pages covered by Plausible, goal-definition changes, imported-data state, blockers or consent effects, and excluded URLs. The honest unknown bucket makes optimization safer than a falsely complete attribution table.
Continue the workflow
Reconcile ten canonical landing pages over one 28-day window, including API metadata, imports, redirects, goal definitions, and every excluded page.
- Fathom and Search Console: compare another privacy-focused analytics bridge
- Matomo and Search Console: compare first-party and aggregate source boundaries
- Search Console vs analytics: understand source collection differences
Questions teams ask
- Can Plausible and Search Console be combined?
Yes at canonical page and reporting-window level, after each source is aggregated independently. Keep definitions and totals source-labelled.
- Can Plausible tell which Google query converted?
Not as a reliable person- or visit-level join from Search Console. Use aggregate query-page visibility beside page-level Plausible goals.
- Does SearchHandled connect directly to Plausible?
No native Plausible connector is currently claimed. The workflow here uses Plausible's Stats API and Search Console data.
Primary sources
The SearchHandled Editorial Team prefers first-party documentation and names the limits of each source. Links were checked on the access date.
- Plausible Analytics: Stats API v2Accessed August 29, 2026 · The Stats API is a paid Business feature and has its own rate limits.
- Plausible Analytics: Metrics definitionsAccessed August 29, 2026 · Plausible notes that some aggregate results may vary slightly because of counting heuristics.
- Plausible Analytics: Custom propertiesAccessed August 29, 2026
- Google Search Console Help: Performance report: clicks, impressions, CTR, and positionAccessed August 29, 2026 · Defines Search Console metrics; it does not create a user-level analytics join.
- Google Search Central: Creating helpful, reliable, people-first contentAccessed August 29, 2026 · Quality guidance, not a guarantee that a page will rank.
