Group pages by the offer they actually support
Group landing pages around real service lines so traffic can inform delivery priorities. A site-wide gain can hide a decline in the service the business is trying to grow.
Service-level traffic reporting needs a documented page map. A broad blog can support more than one offer, while a service page has a more direct purpose. Avoid assigning every informational visit to a sales category with false precision.
A worked example
A hypothetical guide explains both analytics and lead capture. The team can label it shared educational content rather than crediting all its visits to one service. Its links to specific offers provide additional context without proving that every visitor was ready to buy.
How to apply it
- Create service landing-page groups and a separate shared-content category.
- Version changes when pages are added, moved or reassigned.
- Review relevant search queries and supported next-step activity for each group.
What the result can establish
Report unassigned or shared traffic honestly. A service-group increase can reflect newly included pages rather than improved performance. Pair volume with inquiry fit and avoid treating the allocation rule as a record of a visitor’s intent.
Reference: Google: Search Console performance report.
Supporting documentation
Google: Search Console performance reportGoogle Analytics: recommended events