Launched this week
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.
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.
How often does it re-analyze new findings once I've worked on first few??
CrawlRaven
@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.
CrawlRaven
@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.
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.
CrawlRaven
@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.
Zivy
Congrats on the launch @aditi_chaturvedi ! One question: how do you prioritize recommendations when multiple issues overlap? For example, if a page has technical SEO problems, content decay, and keyword cannibalization at the same time, how does CrawlRaven decide what should be fixed first?
CrawlRaven
@harkirat_singh3777 Every opportunity gets an impact score from 0 to 100, and the list sorts by it. Impact is search demand weighted by how winnable the fix looks. There's also a confidence score based on how much data backs it, so a big number off thin data doesn't jump the queue.
Note: Technical SEO isn't live yet.
Pulling GSC and GA4 into one place is the part I always end up duct-taping together myself. Does the 200-point crawl check anything for AI search / GEO yet or is it still classic SEO? That's where I keep hitting walls lately.
CrawlRaven
@berkaybuilds Classic SEO today, and GSC-only. GA4 ships next, so the "one place" part isn't done yet. What's live is Search Console data with four detectors on it: striking distance, content decay, CTR gaps, cannibalization. No GEO checks in there.
Once GA4 shipped, the first AI thing I'd add is pulling ChatGPT, Perplexity, Claude and Gemini referrals out of source/medium into their own channel, tied back to the pages earning them.
Would love to know more about the current challenges that you are facing.
Just finished wiring up GA4 + Search Console for my own product this week,
and the part that took longest wasn't the setup — it was figuring out what to
actually do with the data once it was flowing. Submitted a sitemap, saw
"couldn't fetch," and had no idea whether that was a real problem or just
Google being slow.
The "what to write, what to update, what to fix first" framing is the part
I'd pay for. Does the ranked plan work for a site with almost no traffic yet,
or does it need existing GSC data to be useful?
CrawlRaven
@transferiq Do you have target keywords that you want to rank for? If yes, it will work even when your existing traffic is not as much.