Diagnose it by cross-referencing the general policy category Google’s Manual Actions report gives you, things like “Scaled content abuse” or “Thin content with little or no added value,” against the specific, concrete examples and definitions Google publishes for that category in its spam policies documentation, then systematically auditing the site sections most likely to match those examples. Search Console’s Manual Actions report almost always names a policy category rather than listing every specific offending URL, especially for site-wide actions, so the diagnostic work is translating a general label into specific findings on your own site, not waiting for Google to hand you a URL list.
Why Google doesn’t give you the specific URLs
The Manual Actions report, found in Search Console, is built to communicate which policy was violated and, in many cases, provide a sample of affected pages, but for site-wide or pattern-based violations, Google generally doesn’t enumerate every individual URL involved. This is documented behavior, not a bug or a withheld courtesy: Google’s spam policies apply to patterns of behavior across a site (a template generating thousands of low-value pages, a site-wide pattern of manipulative practices), and providing an exhaustive URL list for a violation that might touch tens of thousands of pages isn’t how the reporting is designed to work. The category name itself, is this “Scaled content abuse,” “Thin content,” “Cloaking,” or another named policy, is the primary diagnostic starting point Google gives you.
The diagnostic method
Start by reading Google’s actual spam policies documentation for the specific category named in the notification, not a general summary of it. Each category on Google’s spam policies page includes concrete, specific examples of what triggers that classification. “Scaled content abuse,” for instance, explicitly names patterns like generating large volumes of pages with auto-generated or spun text, content produced primarily to manipulate rankings without adding value for users, and templated content with minimal unique substance. “Thin content” has its own distinct examples, focused on pages that provide little original value regardless of production method or scale. Matching the specific examples under the named category against your own site’s structure is the actual diagnostic work: which sections of the site most closely resemble the pattern Google describes.
Once you’ve identified the policy category’s specific triggering pattern, cross-reference it against your site using whatever sample data Search Console did provide (even a small sample of flagged URLs is useful for identifying which template or content pattern is implicated) and a systematic audit of the site sections that structurally match the category’s description. If the action names scaled content abuse and Search Console’s sample includes a few URLs from a specific programmatic template, audit the entire output of that template for the specific issues named in the policy (lack of unique value, templated or auto-generated text, absence of genuine differentiation between pages), rather than assuming the problem is isolated to only the sampled URLs.
Process-of-elimination auditing is legitimate here precisely because Google’s category naming, while general, is specific enough to rule out most of a typical enterprise site. A manual action for “Thin content” doesn’t require auditing an entire e-commerce catalog; it requires identifying which specific page types or templates produce content with minimal original value, which is usually a narrower, identifiable subset even without a complete URL list from Google.
When a site plausibly matches more than one category
A complication that shows up often on large, multi-template enterprise sites is that the notification names one category, but the audit turns up patterns that could reasonably be described under a different or additional category too, a templated location-page set that reads as both “Scaled content abuse” and “Doorway pages” depending on which specific pattern you emphasize, for instance. When this happens, don’t treat the notification’s named category as the exhaustive scope of what needs fixing. Google’s manual action reflects the primary policy violation identified for that action, not necessarily a certification that every other template on the site is clean. Auditing only the narrowest possible reading of the named category, while leaving a clearly adjacent violation on a different template untouched, risks a reconsideration request that resolves the named issue but leaves the site exposed to a second manual action once the remaining pattern is separately identified.
The practical approach is to fix what’s actually broken, using the named category as the entry point into the audit rather than as a boundary around it. If the audit surfaces a content pattern that clearly matches a second policy’s concrete examples, even one not named in the current notification, remediate it in the same pass. This isn’t scope creep, it’s addressing the reality that manual actions are triggered by identifiable patterns, and a site with one such pattern often has organizational or process reasons (the same templating approach, the same content-generation vendor, the same lax review step) that produced more than one instance of policy-adjacent content, even if only one was flagged this time.
It’s also worth building a standing internal reference, rather than re-reading the spam policies documentation from scratch each time a notification arrives, because the concrete examples under each category get updated periodically as Google observes new manipulation patterns emerging across the web. A team that audited against “Scaled content abuse” a year ago and built remediation practices around that version of the examples may find the category has since been clarified or expanded to cover a pattern the site has since started using in an unrelated content initiative. Treating the spam policies page as a static reference checked once, rather than as documentation that gets revisited whenever a new content template or programmatic approach is being planned, is a common reason a site that resolved one manual action later triggers a second one for a pattern that would have been caught by the same diagnostic discipline applied earlier.
Practical implication
Treat the category name as the actual diagnostic input, not as a frustratingly vague placeholder waiting to be supplemented by more specific information from Google. Read the specific spam policy page for that exact category and note every concrete example or pattern it describes. Cross-reference those specific patterns against your site’s structure, prioritizing any sample URLs Search Console did provide as a starting point for identifying the implicated template or content type, then extend the audit to the full output of that template or pattern rather than assuming the visible sample represents the complete scope of the issue. Document the specific violation instances found during this audit as part of the reconsideration request, since Google’s reconsideration process evaluates the remediation evidence you provide, and a request built on a precise understanding of what pattern violated the named policy, backed by specific examples of what was fixed, is stronger than a general claim that content was “cleaned up” without demonstrating the fix addresses the actual, specific pattern the policy category describes. Don’t assume Google will confirm your diagnosis is correct before you submit the reconsideration request; the audit and remediation need to be done based on your own analysis of the category definition, since Google generally doesn’t pre-validate a diagnosis before the formal reconsideration review.
