Full-site crawler with JS rendering, keyword rank tracking, automated rank alerts, white-label HTML reports, multi-site dashboard, and content gap analysis plus 14 parallel AI audit agents, 25-signal drift monitoring, Google Search Console, GA4, backlink data, and 3-viewport visual analysis. You supply the API key; Vexifa does the work no SaaS credits, no data leaving your machine.
No reviews yetBe the first to leave a review for Vexifa SEO
Maker
📌
Free Windows download with every feature unlocked. No account, no credit card. An optional $19/year PayPal subscription supports continued development.
Report
A local install is a nice move for privacy, but onboarding looks steep for non-devs. A small Docker Compose file with a one-line setup script and a sample config would make it way easier for marketers to actually try this without fighting terminal errors for an hour.
Report
Maker
@sinan1082007 all you really need are API keys to connect to your preferred data provider. You can still crawl and fix issues without any API keys.
Report
Love that the local-first setup means no data leakage, that's a real differentiator. One thing that would make it stickier for me would be a simple diff view between crawls so I can see exactly which pages gained or lost issues week over week instead of digging through two separate reports.
honestly the local-only setup is pretty cool, but one thing i'd love is a built-in way to schedule recurring crawls with diff comparisons between runs, so i can spot exactly which pages regressed or improved without digging through archives myself.
Report
Maker
@ahinonom there is a scheduler built into the app.
Report
Since the whole pitch is keeping data local and skipping SaaS credits, a built-in scheduled export to your own S3 bucket or Postgres instance would fit perfectly, so audits and historical crawl diffs can be archived without anyone babysitting the dashboard.
A local install is a nice move for privacy, but onboarding looks steep for non-devs. A small Docker Compose file with a one-line setup script and a sample config would make it way easier for marketers to actually try this without fighting terminal errors for an hour.
@sinan1082007 all you really need are API keys to connect to your preferred data provider. You can still crawl and fix issues without any API keys.
Love that the local-first setup means no data leakage, that's a real differentiator. One thing that would make it stickier for me would be a simple diff view between crawls so I can see exactly which pages gained or lost issues week over week instead of digging through two separate reports.
@kemalergdeydc3 you can compare crawls in the app.
honestly the local-only setup is pretty cool, but one thing i'd love is a built-in way to schedule recurring crawls with diff comparisons between runs, so i can spot exactly which pages regressed or improved without digging through archives myself.
@ahinonom there is a scheduler built into the app.
Since the whole pitch is keeping data local and skipping SaaS credits, a built-in scheduled export to your own S3 bucket or Postgres instance would fit perfectly, so audits and historical crawl diffs can be archived without anyone babysitting the dashboard.