Stop Guessing Whether an SEO Change Helped—Put the Change Next to the Search Evidence
Aegisify SEO 2.9.4 Evidence Reporting correlates recorded SEO events with Google Search Console snapshots for a specific WordPress URL, giving teams a before/after view of clicks, an annotated daily timeline, and query changes around the period when metadata, schema, redirects, links, or supported fixes changed.
EventsGSCClicksQueries
Resolve a URL, Find the Change, Compare the Search Window
The Evidence tab is page-centric. It is designed to answer “what changed on this URL, and what did Search Console report around that time?”
Click a stage to expand
01SelectURL or page
02SnapshotGSC history
03Compare14d vs 14d
04AnnotateSEO events
05Querylive GSC diff
06Interpretbest-effort
Bring WordPress Change History and Search Console Into the Same View
Aegisify stores SEO events and GSC snapshots for different purposes; Evidence Reporting joins them around a specific page.
URL Resolution
Administrators can paste a same-site URL or choose from recently modified published content. URL resolution anchors the report to one WordPress object so unrelated site-wide changes do not dominate the view.
Daily Snapshot Series
The page reads up to 28 stored snapshot days for the selected content item. These values come from Aegisify’s GSC snapshot system; when no evidence exists, the page should be read as incomplete rather than filled with estimates.
Recent SEO Events
Aegisify loads recent post-scoped events and groups them by date. The timeline can label schema, links, redirect, fix, and metadata activity so an administrator can identify the day a controlled change entered production.
Evidence, Not Universal Analytics
This view does not replace GA4, server logs, crawl data, conversions, or experimentation platforms. Its job is narrower: correlate Aegisify SEO actions with Google-reported search performance for one WordPress URL.
Compare Recent Clicks With the Immediately Previous Window
The current card uses the available snapshot dates to build a simple 14-day-versus-previous-14-day comparison.
Clicks — Last 14 Days
Aegisify sums clicks across the most recent 14 snapshot dates available for the page, rather than extrapolating missing days.
Clicks — Previous 14 Days
The prior period is the preceding block of up to 14 available snapshot dates, providing a near-term baseline for directional comparison.
Absolute + Percentage Change
The card shows click difference and percentage change when the previous period contains traffic. A zero prior period is not turned into a fake percentage comparison.
See Daily Search Evidence With the SEO Event Markers Beside It
The timeline makes a historical review easier: when did the metric move, and what did Aegisify record on or near that date?
Each daily snapshot row displays the date, clicks, a relative bar, and any recognized SEO-event markers associated with that day. Current labels include Schema, Links, Redirect, Fix, and Meta events. The underlying event type remains available so the administrator can distinguish a schema approval from a meta update rather than treating every marker as the same intervention.
If the report finds a recorded schema approval and clicks in the latest 14-day block exceed the previous block, it can show a “Why it moved” prompt suggesting that the administrator review queries to see which terms changed. The text is intentionally framed as an investigation cue rather than a causal claim.
Use Query Deltas to Explain Which Search Demand Actually Moved
When the GSC property is configured, the page can compare query evidence for the selected URL across current and previous 14-day windows.
Page-Level GSC Queries
Aegisify requests a bounded list of queries for the selected page in each comparison period. The result is cached for roughly ten minutes to avoid repeating the same remote request every time the admin view reloads.
Combine Current + Previous Terms
Queries reported in either period are merged into a shared set. For each term Aegisify calculates click delta, impression delta, current clicks, and previous clicks.
Largest Click Gains First
The current comparison sorts by click delta and limits the display to the leading changes. This helps teams move from a page-level increase to the specific search terms that contributed to the movement.
Review Schema/Metadata in Context
If a schema event exists and some queries gained clicks, Aegisify can surface a best-effort note. Administrators should still inspect query intent, CTR, impressions, position, seasonality, and competing page changes before drawing conclusions.
Refresh Evidence Manually When You Need a Checkpoint
The manual runner exists for operational use; normal collection belongs on the scheduled snapshot workflow.
Optimization Should End With Measurement, Not With “Saved Successfully”
Aegisify’s broader SEO model is detect → change → record → measure → keep or revise.
Issues & Fixes can log a metadata, schema, redirect, or internal-link change. Search Stats can expose page/query performance. Evidence Reporting connects those two worlds for one URL. That makes SEO work more defensible for agencies, ecommerce teams, and internal operators who need to explain what was changed and what Google reported afterward.
Record the Change and Return With Search Evidence
Use Aegisify SEO to connect controlled WordPress actions with GSC snapshots and query movement instead of losing optimization history across separate tools.
Common Questions About SEO Evidence Reporting
Does Evidence Reporting prove that an SEO change caused a ranking increase?
No. It correlates recorded events with Search Console data and can highlight timing relationships. Causal attribution requires broader analysis and, where possible, controlled testing.
Where do the performance numbers come from?
The page uses Aegisify’s stored Google Search Console snapshot data and, when configured, page-level GSC query fetches for the comparison windows.
Can I load evidence by URL?
Yes. A same-site URL can be resolved to a WordPress post/page object, or an administrator can choose from recently modified published content.
Does the manual Snapshot Runner backfill all history?
No. The current manual runner is a bounded best-effort recent pull. Scheduled daily collection is the normal evidence-building path.
How can Aegisify AI help?
Ask about Aegisify or WordPress: errors, plugins, security, SEO, compatibility, troubleshooting, comparisons, or launch a free website scan.