Q: Credits consumed for viewing data already seen

Many users feel they aren't receiving enough value from their credit allotment because SemDash deducts credits each time they revisit a page within the same session—e.g., navigating from page two back to page one.

Would you consider implementing data caching for the same search session (or for an hour or so?)

While you emphasized the importance of fresh data for each request, many users believe that caching previously viewed information for a short period does not compromise data quality. Their primary concern is running out of 10,000 credits in a single day.

If you believe that fresh data and credit consumption are essential when revisiting previously viewed pages, would you consider introducing a toggle switch allowing users to cache data if they prioritize increased usage of SemDash over concerns about data changing within minutes?

WaSumoPLUSEdited Apr 13, 2025
Founder Team
Hazem_Semdash

Hazem_Semdash

Apr 15, 2025

A: we just updated the entire system. We combined live data with caching your results in your browser for 30 mins.

meaning: if you a search for long tail keywords for "affiliate marketing" and view first 3 pages, that data will be cached in your browser for 30 mins. everytime you request the same info it will be served from the temp cached data without making a live call nor deduct any credits.

You can test it in the long tail keywords, domain keywords, people also ask tools. I hope you like the new update :)

Share
Helpful?
Log in to join the conversation
WaSumoWaSumoPLUS
Verified Purchaser badge

Verified purchaser

Posted: Apr 15, 2025

Thank you — I'm sure many eyes are on this topic.

Verified Purchaser badge

Verified purchaser

Posted: Apr 16, 2025

Hazem, this is great!!

Maybe, replace the 30-minute cache with a permanent one that lasts until someone clicks a "Refresh data" button. ?

Founder
Posted: Apr 16, 2025

Hi Rik, i saw your email about that point and its valid. still need to analyze the idea further though, but i have it on mind!

Posted: Apr 16, 2025

I wholeheartedly support this idea. The data should be cached permanently until I decide to run the report again.