Content being expanded: tutorial with OAuth flow screenshots, export templates, Zapier / Make / n8n examples publishes at public v1.0 release. Current page provides integrations overview + available export formats.
Google Search Console integration
The most useful integration in the app. Standard OAuth flow, one-time connection per Google account, refresh token encrypted locally.
What data it imports:
- Performance: queries, clicks, impressions, CTR, average position over the last 16 months (GSC API maximum limit).
- Coverage: indexed pages, errors, warnings, excluded.
- Core Web Vitals: real CrUX data for pages with traffic.
- Sitemaps submitted: status, last fetch, errors.
Data refresh: at app start + manually from “Refresh GSC” button. Data stored locally in SQLite database — queryable offline afterwards.
Bing Webmaster Tools integration
Similar to GSC but for Bing. OAuth flow + queries import + indexed pages + crawl errors. Data volume is smaller than GSC (Bing has ~3% global market share, ~5% in EU), but valuable for: 1) cross-validation of GSC data, 2) discovering queries Google doesn’t show (Bing returns queries with under 10 impressions), 3) monitor Bing AI / Copilot citation patterns.
PageSpeed Insights integration
Google PSI v5 API for Lighthouse lab data + CrUX field data. Automatic weekly run on all important pages (top 50 by traffic), trend tracking over the last 12 weeks.
Note: PSI API has rate limits (25,000 queries/day free) — for sites with 10,000+ pages under monitor, we recommend Pagespeed with own API key (Google Cloud Console).
Multi-format report export
5 supported formats, each optimized for a specific use case:
- PDF: for the end client. Personalized branding (client / agency logo in header), executive summary at start, technical details at end. Professional format, ready to send via email.
- Excel (.xlsx): for analysts. Separate sheets per category (Audit issues, Keywords, Backlinks, CWV history). Pre-set formulas for custom calculations.
- Word (.docx): for consultants who edit the report with own comments before client delivery. Editable template, consistent headers, auto-generated table of contents.
- CSV: for import into other tools (Google Sheets, Looker Studio, custom BI). One file per data category.
- JSON: for programmatic automations. Complete structured format, publicly documented schema, importable into any Python / Node / Go script.
Automations via Zapier / Make / n8n
The desktop app doesn’t expose direct REST API (it’s local-first), but supports automatic export on schedule + watch folder triggers. Example workflows:
- Weekly: app exports Excel report automatically Monday morning → Dropbox sync folder → Zapier detects new file → sends email to client.
- On Critical issue: audit detects Critical problem (e.g., accidental noindex on homepage) → app writes alert JSON to a watch folder → n8n trigger → Slack notification to team.
- Monthly: app runs full audit → exports brand PDF → Make picks up PDF → uploads to Google Drive client folder → emails client link.
Concrete tutorials with Zapier / Make / n8n workflows + JSON templates publish at public v1.0 release.
Planned integrations (post-v1.0)
Public roadmap, prioritized by user demand:
- Google Analytics 4 (Q3 2026): import traffic + conversion metrics to correlate with SEO rankings.
- Looker Studio data connector (Q4 2026): direct connector for live dashboards.
- Slack notifications (Q3 2026): native alert without Zapier intermediate.
- Webhooks (Q4 2026): triggers for custom integrations.
- Notion / Coda export (2027): for consultants who keep client docs in those tools.
What we DON’T plan direct integration (and why)
- Ahrefs / SEMrush API: would mean asking for their keys + transmitting data through their platforms. Contradiction with local-first. Use both tools separately if needed.
- WordPress plugin: the desktop app is separate from your site; the plugin would mean intrusive code in WP. Better: export schema markup from app → paste in Yoast / RankMath.
- Browser extension: out-of-scope for desktop app. If significant demand comes, we consider at v2.0.