A lot of SEO teams still talk about page-level and sitewide signals as if Google has to pick one and crown a winner. Google’s ranking systems guide says the real answer is less dramatic: its ranking systems are designed to work primarily at the page level, but sitewide signals and classifiers also help Google understand individual pages.

That means a strong domain doesn’t give every weak page a free hall pass. It also means one ugly section doesn’t automatically sink every URL on the site.

Start With the Page That’s Actually Underperforming

If a page isn’t ranking, the first question should be whether it deserves to rank. Does it match the searcher’s intent? Does it answer the question clearly and accurately? Does it offer anything more useful than the pages already ranking? Can Google crawl and index it, and can users reach it through a sensible internal-link structure?

Too many teams skip those questions and jump straight to broad theories about domain authority, trust, or “the whole site getting hit.” Sometimes the simpler explanation is that the page is thin, vague, poorly targeted, technically blocked, or buried, as if somebody forgot it existed.

Before blaming a sitewide signal, check the URL’s indexing status, canonical selection, internal links, content quality, search intent, and query-level performance.

A Sitewide Decline Isn’t Proof of a Sitewide Signal

Sitewide patterns still matter, but the distinction needs some care. Google doesn’t publish a complete list of its sitewide signals and classifiers, so SEOs shouldn’t label every recurring problem a confirmed sitewide ranking factor.

Messy templates, confusing navigation, duplicate page types, weak internal linking, or large sections of low-value content can still make SEO harder because they affect many URLs at once. A migration error, robots directive, template change, algorithm update, tracking problem, or drop in search demand can also create what looks like a sitewide decline.

In other words, seeing traffic fall across a domain tells you the scope of the symptom. It doesn’t automatically identify the cause.

As Search Engine Journal’s coverage explained, Google’s clarification knocks down two lazy assumptions: good sitewide signals can’t carry every mediocre page, and weak sitewide signals don’t doom every strong page. The update clarified how Google already worked; it didn’t announce a new ranking factor.

Triage in Two Buckets

The practical move is to investigate ranking problems in two connected buckets.

Start at the page level. Review the important URLs that lost visibility, the queries they previously ranked for, their indexing status, their content, and the competing results. Determine whether the decline affects individual pages, one template or directory, or most of the site.

Then step back and look for repeating patterns. Check whether the affected pages share the same template, internal link depth, content process, canonical setup, navigation path, or technical issue. Fixing one page won’t solve an issue that the CMS reproduces across thousands of URLs.

That order matters. Starting with the affected pages gives you evidence. Looking for shared patterns tells you whether the fix needs to expand.

Google’s clarification shouldn’t trigger another round of ranking mythology. It should make SEO triage more disciplined: diagnose the page, measure the scope, identify the pattern, and only then decide whether you’re dealing with a page-level problem, a broader site issue, or both.