An app for Google Search Console

What it adds to the same data

Every report carries a comparison period, every filter survives the jump from one report to the next, and every table exports. None of that requires a second query or a second tab.

• Previous period or previous year, without re-running anything
• Stored daily rows, so history outlives the rolling 16-month window
• Branded and non-branded splits, weekday filters and content groups
• Multi-clause filters carried across reports through the URL
• CSV and HTML export from any table

Reports the interface does not have

These are the analyses that used to be an afternoon of pivot tables, each reduced to a page.

• Content decay, and query decay
• Keyword cannibalization
• CTR measured against a curve fitted to your own data
• Striking-distance opportunities with potential clicks
• Rank changes, and new and lost rankings
• Anomaly and change-point detection against your own baseline

A portfolio, not one site

Cross-site summaries put every property in one table, so an agency or an in-house team managing thirty domains sees the one that moved without opening thirty tabs.

How access works

AutoPSEO reads through the read-only Search Console scope. Properties are imported from the account you connect, and nothing is written back unless you deliberately submit a URL or save an annotation.

What still lives in Search Console

Property verification, ownership, inspection quota and the Google-side settings stay where they are. This is a reporting layer, not a replacement for the console.