DCG Reporting & the Rank OS Dashboard

DCG Reporting: Tracking the Framework in Practice

A report that only shows "your rank improved" is close to useless without saying which of five underlying dimensions moved, and why. Diagnosis without measurement is intuition. Cost Optimization without tracking is untargeted effort. Growth without KPIs is hope wearing a spreadsheet.

The DCG Framework is only as useful as its reporting layer. Angryturtle's Rank OS is the intelligence layer that makes DCG measurable — it scores every profile, surfaces the constraining factor, and drives the edits, posts, and citation fixes the platform then pushes to Google directly. Because every action and score lives in one system, the reports and action log are generated in-platform and exportable, not agency-only artefacts assembled after the fact.

Reporting in the Diagnosis stage

Diagnosis produces the initial Rank OS baseline: five dimension scores that establish the starting point.

The composite Rank OS score is a weighted average of these five dimensions, and the baseline establishes the starting point every subsequent monthly score gets compared against.

Reporting in the Cost Optimization stage

During Cost Optimization, typically Months 2 and 3, the Rank OS score should improve specifically on the dimension that was identified as the primary constraint in Diagnosis. If NAP Consistency was the lowest dimension, the Month 2 report should show a meaningful NAP Consistency improvement, reflecting citations corrected across priority directories. If Profile Completeness was lowest, the report should show services added, attributes completed, and photos uploaded.

The reporting question at this stage is narrow and specific: did the actions taken this month move the specific dimension that was the constraint? A report showing broad activity but no movement on the actual constraint dimension is a sign the work isn't targeted correctly, whatever else it shows.

Reporting in the Growth stage

Growth stage reporting shifts from "did we fix the errors" to "is the compounding working," and the metrics tracked shift with it.

Monthly reporting covers the Rank OS score across all five dimensions month-on-month, geo-grid SoLV — whether the percentage of top-3 grid points is growing — review velocity against target, GBP Insights covering calls, direction requests, and website clicks month-on-month, and citation score, flagging whether any new errors have been introduced.

Quarterly reporting zooms out further: SoLV against top competitor SoLV, to see whether the market share gap is closing; review count against top competitor review count, for the same reason; and an AIO readiness score, tracking whether the business is building toward AI Overview citation eligibility over the quarter rather than just the month.

The Rank OS as a decision engine, not just a report

The Rank OS isn't only a reporting tool — it's a monthly decision engine that runs a consistent loop. Scores get updated for all dimensions, the lowest-scoring dimension gets identified, and the primary execution priority for next month gets set against that dimension specifically.

This loop keeps execution targeted at the actual constraint, which may shift month to month as different dimensions respond to previous months' effort. A business whose NAP Consistency score climbs from 40 to 85 after two months of remediation might find Review Velocity is now the lowest dimension, even though nothing changed about reviews directly — the other four dimensions simply improved faster.

Why raw rank position alone misleads

A business watching only its average rank position for one keyword can see a number move from 5.2 to 4.1 and reasonably assume things are improving. What that single number can't show is which geographic zones actually improved, whether a specific competitor moved rather than the market shifting broadly, or whether the improvement traces to anything the business actually did versus, say, a competitor's temporary suspension. Rank OS reporting, tied to dimension-level scores and geo-grid SoLV, answers all three of those questions where a single rank-tracking number cannot.

Common mistakes in DCG reporting

Reporting the composite score without the dimension breakdown. A single 0-100 number hides exactly the information that makes the score actionable — which dimension moved and which didn't.

Comparing month-on-month without accounting for seasonality. A dip in Engagement Signals during a national holiday week can look like a problem when it's a predictable seasonal pattern, not a real decline.

Treating quarterly executive reporting as a smaller version of the monthly operational report. Executives generally need SoLV trends and competitive share, not a location-by-location breakdown of GBP field completion — see enterprise local SEO reporting for how the reporting tiers should actually differ by audience.

Not closing the loop between report and next month's priority. A report that identifies the constraint but doesn't translate into a specific next-month action defeats the purpose of tracking dimension scores in the first place.

FAQ

How are the five Rank OS dimensions weighted in the composite score? The weights are configurable rather than fixed, since a franchise network with severe NAP inconsistency and a single-location clinic with strong NAP but weak review velocity have very different priorities reflected in how the composite should be calculated.

Can Rank OS scores be exported for use outside the platform? Yes — reports and the underlying action log are generated in-platform and exportable, which matters especially for enterprise clients who need to feed the data into their own internal reporting.

How is a Rank OS score different from a generic "local SEO score" some tools provide? Rank OS ties directly into the platform's write-back capability — it doesn't just score the profile, it identifies the constraint and drives the specific edits, posts, and citation fixes needed to move that dimension.

Does the reporting cadence change for multi-location accounts? Yes, substantially — see enterprise local SEO reporting for the three-tier structure covering location, regional, and executive audiences separately.

See Angryturtle's Rank OS in action →