Launching today
Connect Google Search Console, Google Analytics, import your Ahrefs or Semrush lists, and crawl your site on 200-point technical SEO Audit. CrawlRaven joins all four and hands back a ranked plan: what to write, what to update, what to fix first.
Congrats on the launch. Pulling GSC, GA4 and the crawl into one place saves a lot of time. How does the prioritization decide what goes on top? is it based on traffic potential, effort, or something else?
CrawlRaven
@shivam_vyasThanks. It's ranked by traffic potential relative to how close the win is. We look at your real impressions, your current position, and the gap between what you get and what you'd get with a small move. So a page sitting at position 11 with high impressions outranks a bigger but more speculative opportunity.
Note: Search Console is live today, GA4 and the crawl audit are coming next.
For GA4 google verification is pending.
looks good, currently i m not using any seo tools like ahref so does it suggest keyword suggestions on which i should write on based on my GSC data or do i have add those keywords from my end and do u have any same report of any website where it shows what key actions or tasks it suggested based on my gsc and keyword data thanks
CrawlRaven
@gamifykaran Thanks. Yes, no other tools needed. It pulls keywords straight from your own Search Console data and shows you the ones you're already appearing for but haven't written a page for yet. Adding your own keyword list is optional.
Don't have a sample report to link right now, but happy to share a few screenshots of what the suggestions look like. There's also a free plan, so you can connect your Search Console and see it on your own data.
pulling GSC, GA4 and the Ahrefs/Semrush export into one ranked action list is the part that's actually useful, most SEO tools just dump the raw data and leave you to reconcile it yourself. does the ranked plan account for pages where GSC and Ahrefs disagree on ranking, or does it just pick one source of truth?
CrawlRaven
@omri_ben_shoham1 Good question. GSC is the source of truth for positions, since it's Google's own impression-weighted data from real searches, while Ahrefs/Semrush positions are spot checks of one location on one day. So when they disagree, we trust GSC.
Your Ahrefs/Semrush export contributes what GSC can't tell you: search volume and difficulty for keywords you don't rank for yet. GSC says where you stand, your keyword list says what's worth chasing, and the ranked list combines both.
Congrats on the launch! For agencies managing multiple client sites, can one account switch between different GSC properties, or does each site need its own separate account?
CrawlRaven
@irahimiam You can add multiple sites on one account. You can also import multiple site by connecting to multiple search console. The current plans allow you to add 3 sites for $49 and 10 sites for $99.
Congrats on the launch! Merging GSC, GA4, and crawler data under one roof to actually rank priorities is a huge time-saver. On the action items part - how does the model balance quick wins (like "low hanging fruit" keywords) Vs heavier technical fixes when picking the top action items?
CrawlRaven
@denitsapenchevavaltchanova Thanks. Right now the list leans toward quick wins, because that's what Search Console shows best. A page stuck at the bottom of page 1, or a keyword you rank for but never gave its own page, rises to the top. Small effort, and your own numbers already prove the upside.
The heavier technical fixes come from the crawl audit, which we're adding next. Once it's in, the plan will rank both together
the 200-point crawl plus GSC/GA4 in one place is the pitch that matters - when a fix from the ranked plan goes live, does the tool re-check and clear that item itself or do you have to manually mark it done and hope it doesn't resurface next crawl?
CrawlRaven
@sabber_ahamedYou hit Resolve, and the detectors do the rest. They re-run on every daily sync. If your fix held, the item stays resolved and drops out of your Attention list. If the problem comes back later, it doesn't quietly reappear as a new finding. It comes back marked Returned, so you can see it regressed and the history stays attached. No guessing whether it's the same issue twice.
Note: the crawl and GA4 are rolling out next, so today this runs on the Search Console side. The same Resolve and Return logic will cover the crawl fixes when they are released.
@rakesh_rry that Returned status instead of a fresh duplicate finding is the detail that matters - most tools would just re-flag it and you'd lose the regression history.
CrawlRaven
@sabber_ahamed Exactly why we built it that way. A regression tells you what a fresh finding can't, the fix worked once, then broke, so the cause is likely different this time. Lose that history and you solve the same problem from scratch.
Glad it landed.
Congrats on the launch. Collapsing GSC, GA4, and a full crawl into one prioritized list is the time-saver here, three separate dashboards never gave anyone a single priority order. Before I'd hook this to a client's Search Console: does the OAuth grant ask for read-only access, or does it need edit/verify scope too, and if a workspace disconnects later, does that revoke the grant on your end or just stop the sync?
CrawlRaven
@vollos We only request the readonly scopes, webmasters.readonly for Search Console, and analytics.readonly for GA4 (asked separately, only if you open the GA4 tab). No verify, edit, or property-management access at all. We literally can't change anything in the client's Search Console, only read the performance data.
On disconnect, the access lives in the client's Google account, so if they revoke it there (or your Workspace admin does), our token stops working immediately and the sync halts. We hold nothing that survives that. If you want your data removed on our side too, account deletion wipes the stored tokens and history.
@rakesh_rry That clears up the scope question nicely, readonly with no verify access covers most of what I would worry about on the Google side. One more before I would point this at a client project: once a token is issued, does the refresh token sit encrypted at rest on your end, or does that just depend on whatever the hosting or DB setup gives you by default?
CrawlRaven
@vollos Yes, we encrypt it ourselves before it hits the database, so it doesn't depend on hosting defaults. The token gets sealed with AES-256-GCM using a key kept separate from the DB. The table only ever holds ciphertext, and tokens never reach our logs.
So a full copy of the database reads nothing without the key, which lives elsewhere.
@rakesh_rry Key held apart from the database with AES-256-GCM is the right shape here, a full database copy on its own would not hand anyone anything usable without it. Thanks for walking through both layers, solid build.