Signal
/bpm/130 dropped 3.95 positions week-over-week, falling out of the top 10.
| Metric |
Previous week |
Current week |
| Average position |
7.85 |
11.80 |
| Impressions |
165 |
20 |
| Clicks |
0 |
0 |
The impression count also collapsed from 165 → 20, suggesting Google is surfacing the page far less frequently across BPM-related queries, not just ranking it lower for a fixed query set.
Hypothesis
A competitor page may have gained authority on "130 BPM" queries, or Google's understanding of the page's intent shifted (thin/programmatic content on a BPM sub-page can rank inconsistently). The simultaneous impression drop reinforces a demotion rather than simple position shuffling.
Suggested action
- Review the
/bpm/130 page content — ensure it has meaningful, unique content beyond a bare BPM value (e.g. tempo feel, common songs at 130 BPM, compatible time signatures).
- Check Search Console's URL Inspection tool to confirm the page is still indexed and mobile-usable.
- If
/bpm/* pages are thin/templated, consider either enriching them with unique content or consolidating them behind a single /bpm hub with anchor links.
Signal
/bpm/130dropped 3.95 positions week-over-week, falling out of the top 10.The impression count also collapsed from 165 → 20, suggesting Google is surfacing the page far less frequently across BPM-related queries, not just ranking it lower for a fixed query set.
Hypothesis
A competitor page may have gained authority on "130 BPM" queries, or Google's understanding of the page's intent shifted (thin/programmatic content on a BPM sub-page can rank inconsistently). The simultaneous impression drop reinforces a demotion rather than simple position shuffling.
Suggested action
/bpm/130page content — ensure it has meaningful, unique content beyond a bare BPM value (e.g. tempo feel, common songs at 130 BPM, compatible time signatures)./bpm/*pages are thin/templated, consider either enriching them with unique content or consolidating them behind a single/bpmhub with anchor links.