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.
No reviews yetBe the first to leave a review for CrawlRaven
Congrats on the launch! Using real GSC impressions and position gaps to surface quick wins is super smart. How far down in rankings (e.g., positions 11–20 vs. 20+) does the algorithm look to identify those high-potential pages?
@hannesh Thanks. It looks at positions 4 through 20, so the bottom of page 1 and the top of page 2 both count. The closer you already rank, the higher it lands on your list, since a jump from 6 to 2 wins more clicks than a climb from 18. We skip anything past 20, since those need real content work. And we want at least 50 impressions so the term is one people actually search.
Where would you draw the line? Some folks want to reach past 20 for niche terms that still convert. Others want the list tight around fast wins. Which fits how you work?
Report
@rakesh_rry I think 4–20 as the default is spot on for fast wins! That said, having a toggle or filter to occasionally scan positions 20–30 (maybe with a higher impression threshold) for high-intent niche terms would be a great power-user feature down the road.
@hannesh Exactly right, and the impression threshold is what makes it work. Positions 20 to 30 get noisy, so you'd want a demand floor before surfacing them, or it's just a longer list. Filed as a power-user filter. Thanks for thinking it through with us. Maybe we can try min max filters for it.
@hannesh Also wanted to share that we just updated the app. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. You can see the algorithm in action and see if it matches your expectations.
Congrats on the launch! The cannibalization detection caught my eye. I'd pay for that alone if it works well, because everyone knows two of your own pages end up competing for the same keyword, and nobody checks it regularly since it means exporting everything and cross-referencing by hand.
One question, what happens when the keyword list itself is stale? Does the tool flag keywords that stopped mattering, or does it take the list as given?
@roguetink Thanks. Cannibalization was one of the original itches, my cofounder's agency was doing exactly that export-and-cross-reference routine you describe.
On stale keywords, the list isn't taken as given. Every keyword is matched against your live Search Console data, which refreshes daily, so one that stopped mattering shows its real current numbers. And you can mark any keyword as ignored, it drops out of your working list without being deleted, so the list stays clean.
An automatic "this keyword is dead" flag isn't there yet, but it's a really good idea. Would love to hear what it finds on your site this week.
Report
the ranked what-to-fix-first output is the actual value here. every seo tool hands you 200 issues and lets you drown in them, the hard part was never finding problems, it was knowing which three actually move rankings this month. good angle joining gsc and the crawl to decide that instead of just showing it
@alex_watson2110 Also wanted to share that we just updated the app. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. let me know if the suggestions match what you already suspected.
Report
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?
@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.
Report
@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.
@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.
@sabber_ahamed Also wanted to share that we just updated the app. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. let me know if the suggestions match what you already suspected.
Report
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?
@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.
Report
@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?
@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.
Report
@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.
@vollos Also wanted to share that we just updated the app. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. let me know if you could find interesting opportunities for your client website.
Report
@aditi_chaturvedi Appreciate the update, and letting people try Opportunities and Target Keywords before paying is a good call. Thanks again for walking through the OAuth scope and token encryption earlier, solid answers both times.
Report
How often does it re-analyze new findings once I've worked on first few??
@axebarma It discovers new keyword opportunities based on the content published, what keywords it already rank for and what can potentially rank for more. The analysis becomes even richer if you add your target keyword list with data from tools like Ahref. With time, you get more data and hence new opportunities are identified. Let me know if this answers your question.
@axebarma GSC data syncs from Google automatically every day, so findings update on their own as your changes take effect. No need to re-run anything. Just note Google reports search data with about a 2 day delay, so give fixes a couple of days to show up.
@axebarma We just updated the app so that you can experience more of CrawlRaven on Free plan. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. Would love to know your feedback
Report
The "what to do next" framing is the right one. GSC will tell you a page is "Discovered, currently not crawled" and then leave you guessing whether that's a technical problem or a site-quality problem. Does the ranked plan distinguish between genuinely technical fixes and pages that just need stronger internal links or better content? That distinction is where I've burned the most hours on my own site.
@podcast_ai The four detectors, striking distance, cannibalization, CTR gap, decay, all run on pages that already have search data. "Discovered, currently not crawled" has none yet, so none of them touch it. Right now we deep-link to Google's own URL Inspection view for that page instead of making the call ourselves.
You're right it's the harder problem. A robots block is a config fix. A page Google crawled, judged thin, and skipped indexing is a content problem. Telling them apart takes more than GSC's status field: internal links to the page, content length, how it compares to pages that did get indexed.
@podcast_ai We share precisely this in the opportunities section. It shows weather you need better content or stronger links. We just made the Opportunities and Target Keywords visible for free plans as well. You can see what CrawlRaven would surface for your site without paying first. let me know if the suggestions meet your expectations.
Congrats on the launch! Using real GSC impressions and position gaps to surface quick wins is super smart. How far down in rankings (e.g., positions 11–20 vs. 20+) does the algorithm look to identify those high-potential pages?
@hannesh Thanks. It looks at positions 4 through 20, so the bottom of page 1 and the top of page 2 both count. The closer you already rank, the higher it lands on your list, since a jump from 6 to 2 wins more clicks than a climb from 18. We skip anything past 20, since those need real content work. And we want at least 50 impressions so the term is one people actually search.
Where would you draw the line? Some folks want to reach past 20 for niche terms that still convert. Others want the list tight around fast wins. Which fits how you work?
@hannesh Exactly right, and the impression threshold is what makes it work. Positions 20 to 30 get noisy, so you'd want a demand floor before surfacing them, or it's just a longer list. Filed as a power-user filter. Thanks for thinking it through with us. Maybe we can try min max filters for it.
@hannesh Also wanted to share that we just updated the app. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. You can see the algorithm in action and see if it matches your expectations.
Congrats on the launch! The cannibalization detection caught my eye. I'd pay for that alone if it works well, because everyone knows two of your own pages end up competing for the same keyword, and nobody checks it regularly since it means exporting everything and cross-referencing by hand.
One question, what happens when the keyword list itself is stale? Does the tool flag keywords that stopped mattering, or does it take the list as given?
Upvoted, will try it on our site this week.
@roguetink You will be able to see ranks, positions and pages for any given keyword. It recommend how to target keywords and in what priority
@roguetink Thanks. Cannibalization was one of the original itches, my cofounder's agency was doing exactly that export-and-cross-reference routine you describe.
On stale keywords, the list isn't taken as given. Every keyword is matched against your live Search Console data, which refreshes daily, so one that stopped mattering shows its real current numbers. And you can mark any keyword as ignored, it drops out of your working list without being deleted, so the list stays clean.
An automatic "this keyword is dead" flag isn't there yet, but it's a really good idea. Would love to hear what it finds on your site this week.
the ranked what-to-fix-first output is the actual value here. every seo tool hands you 200 issues and lets you drown in them, the hard part was never finding problems, it was knowing which three actually move rankings this month. good angle joining gsc and the crawl to decide that instead of just showing it
@alex_watson2110 Thanks Alex!
@alex_watson2110 Also wanted to share that we just updated the app. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. let me know if the suggestions match what you already suspected.
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?
@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.
@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.
@sabber_ahamed Also wanted to share that we just updated the app. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. let me know if the suggestions match what you already suspected.
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?
@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?
@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.
@vollos Also wanted to share that we just updated the app. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. let me know if you could find interesting opportunities for your client website.
@aditi_chaturvedi Appreciate the update, and letting people try Opportunities and Target Keywords before paying is a good call. Thanks again for walking through the OAuth scope and token encryption earlier, solid answers both times.
How often does it re-analyze new findings once I've worked on first few??
@axebarma It discovers new keyword opportunities based on the content published, what keywords it already rank for and what can potentially rank for more. The analysis becomes even richer if you add your target keyword list with data from tools like Ahref. With time, you get more data and hence new opportunities are identified. Let me know if this answers your question.
@axebarma GSC data syncs from Google automatically every day, so findings update on their own as your changes take effect. No need to re-run anything. Just note Google reports search data with about a 2 day delay, so give fixes a couple of days to show up.
@axebarma We just updated the app so that you can experience more of CrawlRaven on Free plan. Opportunities and Target Keywords are now usable on the free plan, so you can see what CrawlRaven would surface for your site without paying first. Would love to know your feedback
The "what to do next" framing is the right one. GSC will tell you a page is "Discovered, currently not crawled" and then leave you guessing whether that's a technical problem or a site-quality problem. Does the ranked plan distinguish between genuinely technical fixes and pages that just need stronger internal links or better content? That distinction is where I've burned the most hours on my own site.
@podcast_ai The four detectors, striking distance, cannibalization, CTR gap, decay, all run on pages that already have search data. "Discovered, currently not crawled" has none yet, so none of them touch it. Right now we deep-link to Google's own URL Inspection view for that page instead of making the call ourselves.
You're right it's the harder problem. A robots block is a config fix. A page Google crawled, judged thin, and skipped indexing is a content problem. Telling them apart takes more than GSC's status field: internal links to the page, content length, how it compares to pages that did get indexed.
@podcast_ai We share precisely this in the opportunities section. It shows weather you need better content or stronger links. We just made the Opportunities and Target Keywords visible for free plans as well. You can see what CrawlRaven would surface for your site without paying first. let me know if the suggestions meet your expectations.