🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
Blog post - adding pictures (#393)
JMeng1dcd38709f99f
diff --git a/docs/public/blog/channelfilter.png b/docs/public/blog/channelfilter.pngnew file mode 100644index 000000000..b64b96d4aBinary files /dev/null and b/docs/public/blog/channelfilter.png differdiff --git a/docs/public/blog/countryfilter.png b/docs/public/blog/countryfilter.pngnew file mode 100644index 000000000..96fcb345cBinary files /dev/null and b/docs/public/blog/countryfilter.png differdiff --git a/docs/public/blog/customdaterange.png b/docs/public/blog/customdaterange.pngnew file mode 100644index 000000000..e6773be5aBinary files /dev/null and b/docs/public/blog/customdaterange.png differdiff --git a/docs/public/blog/devicefilter.png b/docs/public/blog/devicefilter.pngnew file mode 100644index 000000000..c9a118a9eBinary files /dev/null and b/docs/public/blog/devicefilter.png differdiff --git a/docs/public/blog/main.png b/docs/public/blog/main.pngnew file mode 100644index 000000000..002ea49b9Binary files /dev/null and b/docs/public/blog/main.png differdiff --git a/docs/public/blog/pages.png b/docs/public/blog/pages.pngnew file mode 100644index 000000000..ae4d418ecBinary files /dev/null and b/docs/public/blog/pages.png differdiff --git a/docs/public/blog/performancedashboard.png b/docs/public/blog/performancedashboard.pngnew file mode 100644index 000000000..4a82871f7Binary files /dev/null and b/docs/public/blog/performancedashboard.png differdiff --git a/docs/public/blog/referrerfilter.png b/docs/public/blog/referrerfilter.pngnew file mode 100644index 000000000..bcccbd8a2Binary files /dev/null and b/docs/public/blog/referrerfilter.png differdiff --git a/docs/src/content/blog/website-traffic-drop.mdx b/docs/src/content/blog/website-traffic-drop.mdxindex 7df200092..96306e8c7 100644--- a/docs/src/content/blog/website-traffic-drop.mdx+++ b/docs/src/content/blog/website-traffic-drop.mdx@@ -32,12 +32,14 @@ First things first – let's figure out if this is actually a sudden drop or ifFirst, take a look at the amount of traffic that has dropped. You can use the main tab on Rybbit to find this information:-Head to your **Main tab** in Rybbit and start looking at different time periods:+Head to your [main tab](https://demo.rybbit.io/1/main) in Rybbit and start looking at different time periods:* Compare the last 7 days to the week before* Look at the past 30 days versus the 30 days before that* If you have the data, check year-over-year numbers+<img src="/blog/main.png" alt="Rybbit's main dashboard" />+What you're looking for here is patterns. Is this a sudden cliff where traffic just fell off overnight? Or has it been a gradual slide? If it's sudden, definitely check Google's Search Status page to see if they were having crawling or indexing issues around the same time.## **Step 2: Which pages are getting affected?**@@ -52,6 +54,8 @@ You should first ascertain which pages have seen drops in traffic, it’s quiteThe embedded graphs make it super easy to spot which pages used to get steady traffic but suddenly tanked. Those are your priority pages to investigate further.+<img src="/blog/pages.png" alt="Rybbit's page tab" />+## **Step 3: Assessing Technical Performance**If this is really the reason why your website dropped in traffic, then count yourself lucky. Oftentimes this is an easy problem to fix, your website might be slower than usual, or a component might not be working properly and this is causing your bounce rate to be higher than usual or is causing people to drop from your website due to poor performance.@@ -62,6 +66,8 @@ Rybbit has several great features that allow you to investigate potential techni###### *Performance:*+<img src="/blog/performancedashboard.png" alt="Rybbit's performance dashboard" />+If you notice that one of your pages has tanked in performance, you can use the performance tab to find the LCP (LCP measures loading performance. LCP marks the time when the largest content element becomes visible in the viewport.), if a page has a really high LCP, it’s likely that people are simply deciding not to go on the page.Once you recognize that a certain page has performance issues, you can begin the process of fixing the issue.@@ -72,6 +78,8 @@ Once you recognize that a certain page has performance issues, you can begin theUnderstanding which channels are contributing to your traffic decline is crucial for focusing your investigation efforts. You can use the filter function on each channel to look for trends:+<img src="/blog/channelfilter.png" alt="Rybbit's Channel Filter feature" />+(Example: I set the filter to use Channel is Organic Search to look for any drops, the graph shows that traffic has actually grown over the past 14 days).Pay special attention to which sources show the steepest declines. Organic search drops are typically the most impactful and require the most thorough investigation.@@ -79,15 +87,20 @@ Pay special attention to which sources show the steepest declines. Organic searc### Filtering on referrers:You can likely find even more actionable information if you filter on referrers as well, as you can see here we set the filter to only look for events that have Google as a referrer.+<img src="/blog/referrerfilter.png" alt="Rybbit's referrer filter" />## **Step 5: Is the drop in certain geographies or devices or timeframes?**Once you have identified if the drop is truly a drop and pages have been affected, you should start looking for any patterns in geographics or devices, use Rybbit’s filter function to filter on device type as well as country:+<img src="/blog/countryfilter.png" alt="Rybbit's country filter" />(Using Rybbit to filter for a specific country)+<img src="/blog/devicefilter.png" alt="Rybbit's device filter" />+(Using Rybbit to filter for a specific device type).You can also use set time filter on custom range to compare different time frames:+<img src="/blog/customdaterange.png" alt="Rybbit's custom date range filter" />## **Step 5: Digging Into Specific Scenarios**