Skip to content

Commit 73d9510

Browse files
committed
make improving docs more actionable
1 parent f532dc3 commit 73d9510

File tree

1 file changed

+26
-16
lines changed

1 file changed

+26
-16
lines changed

analytics/improving-docs.mdx

Lines changed: 26 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -3,28 +3,38 @@ title: "Improving your docs"
33
description: "Use analytics data to make your documentation better"
44
---
55

6-
Use your analytics data to enhance the user experience of your docs and identify improvement opportunities.
6+
Improve your docs based on quantitative and qualitative data from your analytics dashboard.
77

8-
## Use overview metrics
8+
## Cross-analytics insights
99

10-
**Review popular content**: Ensure your most-visited pages contain current, accurate information and consider expanding successful topics.
10+
Combine information from multiple analytics sources to get a holistic view of your documentation.
1111

12-
**Monitor traffic patterns**: Track changes in visitor counts and page views to understand the impact of updates or new content.
12+
### Correlate traffic and satisfaction
13+
- High traffic + low feedback scores = Popular pages with a bad user experience. Prioritize fixing these pages.
14+
- Low traffic + high feedback scores =
15+
hidden gems worth promoting or expanding
16+
- High traffic + high feedback scores = your documentation's greatest hits
1317

14-
**Analyze referrer sources**: Understand how users find your docs to optimize external linking and SEO.
18+
### Match search intent with content performance
19+
- High search volume + low page views = discoverability problem
20+
- Popular search terms + low-confidence results = content gap opportunity
21+
- Top searches + negative feedback on matching pages = content quality issue
1522

16-
## Act on feedback data
23+
### Identify user journey problems
24+
- Popular referrer sources + high bounce rates = landing page mismatch
25+
- Frequent searches + immediate negative feedback = users can't find what they need
26+
- High code snippet feedback + low page ratings = implementation examples need work
1727

18-
**Address negative feedback**: Investigate pages with poor ratings to identify and resolve user pain points.
28+
### Find strategic opportunities
29+
- Rising search trends + no existing popular pages = new content opportunities
30+
- Declining traffic + stable positive feedback = promotion/SEO needed
31+
- Consistent negative feedback across referrer sources = fundamental content issues
1932

20-
**Celebrate positive feedback**: Use highly-rated pages as examples of effective documentation patterns.
33+
## Putting insights into action
2134

22-
**Track feedback trends**: Monitor changes in satisfaction over time, especially after making updates.
35+
Use these cross-analytics patterns to prioritize your documentation improvements:
2336

24-
## Optimize with search data
25-
26-
**Improve content discoverability**: Review top search queries to ensure relevant pages are easy to find and well-organized.
27-
28-
**Fill content gaps**: Pay attention to low-confidence searches that might indicate missing documentation or topics that need better coverage.
29-
30-
**Update popular content**: Ensure pages that match frequent search terms are current and comprehensive.
37+
- **Fix high-impact problems first**: Popular pages with poor feedback scores affect the most users
38+
- **Fill verified content gaps**: Low-confidence searches with high volume indicate clear user needs
39+
- **Promote hidden successes**: High-rated pages with low traffic deserve better discoverability
40+
- **Align search and content**: Ensure your most-searched topics have comprehensive, well-organized pages

0 commit comments

Comments
 (0)