task: re-measure the 404 share and track failing paths after the redirect fixes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- analytics, documentation, web-dev
Research direction
Start with the GA4 Pages and screens report using the dimensions and search terms described in the issue, then review the redirects shipped in #2353 and record the week-after-deploy results and top paths. Add redirects for remaining paths that map to live pages, configure Search Console or a saved GA4 exploration, and document the saved view in ANALYTICS.md.
Written by the indexing model from the issue text.
Description
Follow-up from #2298, which shipped every repo-side redirect (#2299, #2328, #2329, #2353).
What needs to be done?
Two measurement items were left open, and #2353 needs a second read.
GA4 data starts in late August, so the "Page Not Found" share of 4.4% in #2298 came from a few days and is a weak baseline. For 3-30 September the share was 3.67% (525 views), and many of those visits predate the redirects. Re-measure once #2353 is deployed, and put in place a way to find new gaps without exporting by hand.
How to read the report: Reports > Engagement > Pages and screens, primary dimension "Page path and screen class", secondary "Page title and screen class", search "Not Found".
Definition of done
- Re-run the report for the week after #2353 deploys; record the "Page Not Found" share of views and the top 10 paths here
- Add redirects for any path that is still hit and maps to a live page; list the rest as intentionally not redirected
- Wire Search Console (property for
docs.celo.org) or a saved GA4 exploration, so 404 paths can be seen without a manual export - Note where the saved view lives in
ANALYTICS.md
Priority
medium
Size
S — hours
- Dominant language
- MDX
- Stars
- 89
- Forks
- 396
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 17
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from celo-org/docs
-
Add BlockVectra to the Celo mainnet RPC providers listPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
chore priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
celo-org/docs#2362 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
Selected chart highlights only its values, not its series names and category labelsPossibly taken @Higgs32584 claimed this today. Openbug priority: low ui
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/gridcraft#4390 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bowenliang123/dsh-context#262 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
TRIAGE
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
[Bug] String formatter templates only replace the first occurrence of `{a}`/`{b}`/`{c}`Possibly taken A pull request linked to this issue is open or already merged. Openen pending
Difficulty 2/5 1-3 hours Newbie friendliness 80/100