PUT SOURCE, PERIOD AND CONTENT CONTEXT BESIDE THE NUMBERS
Website & Content Analytics
Website & Content Analytics brings Google Analytics and Search Console evidence into WordPress through the configured Google Site Kit connection. A site team uses it to check source health, compare completed periods, review page, query and editorial groups and ask supported analytics questions with the report references kept visible.
Connected Sources
Know which evidence is available before interpreting it.
Google reports use the installed and configured Google Site Kit connection with access to the relevant Analytics/Search Console properties.
Source health helps distinguish available data from missing, stale or capped input. A connection problem is not equivalent to a zero-traffic period.
Review property, scope and dates when a result seems unexpected. Keep WordPress content information and Google measurements identified rather than presenting them as one unexplained total.
Website Intelligence. Both editions read Google Analytics and Search Console reports from the installed and connected Site Kit plugin on the site's own server; Visioix does not contact Google itself. The Website Intelligence screen compares 7, 30 and 90-day periods with the previous period and shows search highlights for top queries, pages, countries, devices and channels. A PMI overall assessment lists the Plus, Minus and Interesting points of the period with the evidence behind them. In Pro, Cross Intelligence relates verified website and visitor signals without merging their source identities.
Period Comparisons
Compare completed windows with their context intact.
Use completed equal-period comparisons and readable charts to inspect changes in the supported metrics. Retain the source dates and missing-data information beside the result.
A period difference can suggest where to look next. It does not prove that one edit caused the change, especially when traffic mix, seasonality or measurement conditions also changed.
Choose a meaningful comparison and inspect the relevant pages before requesting an optional explanation.
Growth data health in both editions. The Growth Intelligence screen of the Free edition compares completed, equal-length 7, 30 and 90-day periods ending yesterday, shows source health, accessible charts with exact daily values, sustained traffic-drop alerts, pages with declining search CTR with a direct "Edit page" link, and the largest page, channel and device changes. Pro adds the explanation, action, link and experiment workflows described in Growth Intelligence.
Search Performance
Review the pages and queries behind visibility.
Inspect supported page/query evidence, traffic, engagement, search visibility and CTR within the configured report scope.
Search Console clicks and impressions describe a different source from Analytics activity. Keep their definitions and periods visible when explaining why the results do not match exactly.
Use the available evidence to identify a specific page or query worth reviewing, then connect that finding to its published content.
Editorial Performance
Compare content groups that can be matched meaningfully.
Review author, category, length, age and content-type groups with their matched content evidence. The current workflow uses weighted engagement calculations rather than treating unequal totals as directly comparable.
Check the underlying pages and sample before drawing an editorial conclusion. A category with more published content can have a larger total without having stronger performance per item.
Use this view to choose examples for review and connect the result to a content decision.
Analytics Questions
Ask a supported question and keep the report behind the answer.
Use natural-language questions for supported reports, filters and periods. Returned context retains source, date and report references, with explicit handling for missing data or unsupported requests.
Optional AI explanation can help read the result, but it should not invent a different report to answer a question outside the supported scope.
Growth questions about future-year revenue are rejected rather than turned into an unrelated retrospective report.
Trend Context
Separate observed changes from modeled expectations.
Inspect observed alerts, change points and supported trend comparisons with their sample conditions. These views can show when a recorded pattern deserves attention.
The separate Forecast workspace has its own configured estimation workflow. A modeled projection is not a completed-period observation, and its presence does not authorize unsupported prediction questions in Growth analytics.
Keep the period and method visible when discussing a forecast, and revisit it against later evidence rather than presenting it as a promised outcome.
Pro Forecast & Early Warning. Warnings & Reports > Forecast & Early Warning gives a deterministic next-7-day forecast with a 95% interval, using separate models for visitor metrics and website metrics and completed historical periods only. Low-volume or incomplete datasets are withheld instead of extrapolated, and page or product risk signals appear only for entities present in Site Kit page reports. Forecast Outcome History in Custom Reports compares the forecasts recorded with a saved report snapshot against the later measured result.
A Practical Analytics Review
Confirm source health, choose completed periods, inspect the relevant pages/groups and ask a bounded question. Transfer a reviewed finding to the Action Plan only when the next step can be stated clearly.
Questions About Website Analytics
What does Visioix need to show Google reports?
Google reports use the installed and configured Google Site Kit connection with access to the relevant Analytics and Search Console properties. Review property, scope and dates when a result seems unexpected.
Why are some results unavailable?
The property connection, permissions, period, sample and available data determine what can be reported. Missing inputs are shown instead of silently filled.
Does a comparison prove the effect of a page edit?
No. Before/after observations need context and do not establish causation on their own.
Can I ask the analytics questions about next year's revenue?
No. Growth questions about future-year revenue are rejected rather than turned into an unrelated retrospective report. The separate Forecast workspace has its own configured estimation workflow.
Continue the Review
Reviewed against Visioix Pro 2.0.0 and Free 2.1.0 · Last updated 29 October 2026