{"id":55,"date":"2025-12-10T06:52:39","date_gmt":"2025-12-10T06:52:39","guid":{"rendered":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/"},"modified":"2026-05-16T12:26:24","modified_gmt":"2026-05-16T12:26:24","slug":"sitewide-vs-page-level-how-google-decides-what-gets-punished","status":"publish","type":"post","link":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/","title":{"rendered":"Sitewide vs Page-Level: How Google Decides What Gets Punished"},"content":{"rendered":"<p>A penalty&#8217;s scope is the whole game. Whether Google demotes one URL or the entire domain decides whether you&#8217;re rewriting a page this afternoon or rebuilding a content strategy for the next two quarters. The signals that tip Google into sitewide enforcement versus page-level enforcement are not secret, but they are misread constantly, footer links treated as page issues, single thin pages blamed for domain-wide drops, anchor-text spikes diagnosed as algorithmic when they are manual, and vice versa. This guide breaks down how Google&#8217;s scope-of-impact logic actually works, what triggers sitewide demotion versus page-level filtering, and how to diagnose which one hit you before you start spending hours on the wrong remediation.<\/p>\n<aside style=\"border-left:4px solid #1F2A44;background:#F4F6FB;padding:18px 22px;margin:28px 0;border-radius:4px;\">\n<p style=\"margin:0 0 8px;font-weight:700;letter-spacing:.04em;text-transform:uppercase;font-size:.78em;color:#1F2A44;\">Key takeaways<\/p>\n<ul style=\"margin:0;padding-left:20px;\">\n<li>Penalty scope (sitewide vs page-level) is determined by how Google&#8217;s systems classify the pattern, not by how severe the harm appears in your dashboard.<\/li>\n<li>Sitewide triggers are pattern-based, repeated footer links, domain-wide thin content, systemic anchor manipulation, structural ad layouts. Page-level triggers are isolated, one stuffed page, one bought article, one doorway URL.<\/li>\n<li>Manual actions are explicit and surfaced in Search Console with a stated scope; algorithmic filters are inferred from traffic patterns and almost never announced page-by-page.<\/li>\n<li>Partial-match manual actions exist as a middle ground, Google flags a section or subdirectory rather than the entire domain.<\/li>\n<li>Diagnosing scope wrong costs weeks, a page-level fix on a sitewide demotion does nothing; a domain-wide rebuild on a single bad URL is theatre.<\/li>\n<\/ul>\n<\/aside>\n<h2>Sitewide vs Site-Wide: The Spelling Question (Settled Quickly)<\/h2>\n<p>Both spellings exist in SEO literature, but &#8220;sitewide&#8221; (one word) is now standard. Google&#8217;s documentation and most technical sources favor the closed compound form, following the pattern of similar web terms like &#8220;homepage&#8221; and &#8220;website.&#8221;<\/p>\n<div style=\"background:#F8F9FC;border:1px solid #d8dde8;border-radius:6px;padding:20px 24px;margin:28px 0;\">\n<p style=\"margin:0 0 14px;font-weight:700;letter-spacing:.04em;text-transform:uppercase;font-size:.78em;color:#1F2A44;\">Quick vocabulary<\/p>\n<dl style=\"margin:0;display:grid;grid-template-columns:max-content 1fr;gap:10px 22px;\">\n<dt style=\"font-weight:600;color:#1F2A44;\">Manual action<\/dt>\n<dd style=\"margin:0;\">A human reviewer at Google has flagged your site. Surfaced explicitly in Search Console with a named violation and a stated scope (whole site, partial match, or specific URLs).<\/dd>\n<dt style=\"font-weight:600;color:#1F2A44;\">Sitewide demotion<\/dt>\n<dd style=\"margin:0;\">A scope of impact, manual or algorithmic, that suppresses ranking signals across an entire domain rather than specific URLs.<\/dd>\n<dt style=\"font-weight:600;color:#1F2A44;\">Partial-match action<\/dt>\n<dd style=\"margin:0;\">A manual action with scope narrower than the whole site, typically a subdirectory, a content section, or a host. Search Console names the affected URLs.<\/dd>\n<dt style=\"font-weight:600;color:#1F2A44;\">Algorithmic filter<\/dt>\n<dd style=\"margin:0;\">A classifier-driven suppression applied without human review. Never surfaced by name, inferred from traffic loss timing matching a known update.<\/dd>\n<dt style=\"font-weight:600;color:#1F2A44;\">Scope-of-impact signals<\/dt>\n<dd style=\"margin:0;\">The pattern characteristics, repetition, template placement, ratio of bad to good URLs, that determine whether enforcement applies to one page or the whole site.<\/dd>\n<\/dl>\n<\/div>\n<p>The term emerged in the early 2000s as search engines began distinguishing between signals that apply to entire domains versus individual pages. Initially written as &#8220;site-wide&#8221; with a hyphen, it gradually dropped the punctuation as usage solidified. Today, one-word &#8220;sitewide&#8221; dominates technical writing and algorithm update announcements.<\/p>\n<p>What it means in penalty terms: sitewide signals are domain-level characteristics, linking patterns, topical authority, template structure, that Google&#8217;s enforcement systems can flag holistically rather than page-by-page. When the classifier (or a manual reviewer) decides a violation is sitewide, every URL on the domain inherits the demotion.<\/p>\n<p>Why spelling matters minimally: both forms refer to the same concept. Search engines parse them identically. The practical distinction between sitewide and page-level enforcement carries far more weight than orthographic preference, and that&#8217;s what the rest of this guide unpacks.<\/p>\n<figure class=\"wp-block-image size-large\">\n        <img loading=\"lazy\" decoding=\"async\" width=\"900\" height=\"514\" src=\"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/domain-level-website-examination.jpg\" alt=\"Magnifying glass examining website on laptop screen showing domain analysis\" class=\"wp-image-52\" srcset=\"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/domain-level-website-examination.jpg 900w, https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/domain-level-website-examination-300x171.jpg 300w, https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/domain-level-website-examination-768x439.jpg 768w\" sizes=\"auto, (max-width: 900px) 100vw, 900px\" \/><figcaption>Penalty diagnosis starts with scope, is the pattern repeated across the domain, or isolated to one URL? Same prose, very different remediation.<\/figcaption><\/figure>\n<h2>How Google Decides Scope: Sitewide vs Page-Level Triggers<\/h2>\n<p>Look, the mechanics here are not mysterious. Google&#8217;s documented enforcement model splits roughly into two camps, manual actions reviewed by humans (with explicit scope set per case) and algorithmic systems that infer scope from pattern. <a href=\"https:\/\/developers.google.com\/search\/docs\/monitor-debug\/manual-actions\" rel=\"noopener\">Google&#8217;s manual actions documentation<\/a> spells out the violation types and the available scopes; everything else is reverse-engineered from update timelines and recovery case studies. Honestly, most diagnosis errors I see come from skipping that first step, checking Search Console before assuming you&#8217;ve been hit by an algorithmic filter.<\/p>\n<h3>Sitewide Trigger Signals (Pattern, Repetition, Template)<\/h3>\n<p>Sitewide enforcement fires when the violating pattern is structural. A footer link block repeating identical anchor text across 50,000 URLs is, by definition, a sitewide signal, you can&#8217;t fix it by editing one page because it lives in the template. The same is true for navigation-injected paid links, header sponsorship rows, or sidebar widgets pulling from a single source. When the pattern is templated, the violation is templated too.<\/p>\n<p>The other sitewide trigger is ratio. If the majority of your URLs exhibit the same quality problem, thin content, AI-generated padding, doorway pages, scraped product feeds, the classifier reads the domain itself as low-quality rather than treating each page as an isolated case. <a href=\"https:\/\/moz.com\/learn\/seo\/google-penalties\" rel=\"noopener\">Moz&#8217;s penalty primer<\/a> describes this as the &#8220;preponderance&#8221; test, when low-quality URLs outnumber high-quality URLs by a meaningful margin, Google starts evaluating the domain holistically.<\/p>\n<div style=\"border-left:3px solid #4A90B8;background:#EEF5FA;padding:14px 18px;margin:24px 0;border-radius:0 4px 4px 0;\">\n<p style=\"margin:0 0 4px;font-size:.78em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;color:#1F4A66;\">Pro tip<\/p>\n<p style=\"margin:0;\">Before assuming you&#8217;ve been hit sitewide, count your URLs. A site with 200 pages where 30 are thin is in different trouble than a site with 200 pages where 170 are thin. The first survives a page-level cleanup. The second needs structural rework or aggressive pruning.<\/p>\n<\/div>\n<h3>Page-Level Trigger Signals (Isolation, Surgical Precision)<\/h3>\n<p>Page-level enforcement is the opposite, the violation is contained, the pattern is not repeated, and Google&#8217;s systems can name the offending URL without implicating the rest of the domain. A single bought guest post on a 500-page site, a single keyword-stuffed product page in an otherwise editorial catalogue, a single doorway URL someone forgot to deindex, these are the typical page-level cases.<\/p>\n<p>The classifier&#8217;s signal here is isolation. If the bad URL is surrounded by good URLs, if the linking pattern terminates at that one page rather than recurring across the template, Google&#8217;s enforcement is almost always page-scoped. <a href=\"https:\/\/ahrefs.com\/blog\/google-penalty\/\" rel=\"noopener\">Ahrefs&#8217; penalty breakdown<\/a> notes that <mark style=\"background:#FEF6E0;padding:1px 5px;border-radius:3px;\">partial-match<\/mark> manual actions, the explicit &#8220;we&#8217;re only flagging this subset&#8221; case, are the most common shape for link-scheme violations on otherwise legitimate sites.<\/p>\n<figure class=\"wp-block-pullquote\" style=\"border-top:4px solid #1F2A44;border-bottom:4px solid #1F2A44;padding:28px 0;margin:36px 0;text-align:center;\">\n<blockquote style=\"margin:0;padding:0;border:none;\">\n<p style=\"font-size:1.35em;line-height:1.45;font-style:italic;color:#1F2A44;margin:0;\">When the pattern is templated, the violation is templated too. When the pattern is isolated, the penalty is too.<\/p>\n<\/blockquote>\n<\/figure>\n<p>I&#8217;ve seen this go both ways on client work. A footer link block looked obviously sitewide and was, the manual action named the whole domain and recovery took a template rebuild plus a reconsideration request (six weeks of work, plus a humbling round of stakeholder updates). Another site lost ranking on exactly the four URLs targeted by a thin-affiliate cluster, the rest of the domain held position, and the fix was deindexing those four pages and waiting two crawl cycles. Same broad category of violation. Wildly different scopes. Pattern shape first, always.<\/p>\n<h2>Sitewide Trigger Signals vs Page-Level Trigger Signals<\/h2>\n<p>The same broad signal categories show up in both scopes, the pattern shape is what determines which one fires.<\/p>\n<figure class=\"wp-block-table\" style=\"margin:24px 0;\">\n<table style=\"width:100%;border-collapse:collapse;font-size:.95em;\">\n<thead>\n<tr style=\"background:#1F2A44;color:#fff;\">\n<th style=\"padding:10px 12px;text-align:left;border:1px solid #1F2A44;width:22%;\">Signal category<\/th>\n<th style=\"padding:10px 12px;text-align:left;border:1px solid #1F2A44;\">Sitewide trigger<\/th>\n<th style=\"padding:10px 12px;text-align:left;border:1px solid #1F2A44;\">Page-level trigger<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;font-weight:600;\">Link placement<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">Identical anchor text in footer, sidebar, or nav across every URL<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">A single in-body link on one article, no template repetition<\/td>\n<\/tr>\n<tr style=\"background:#F8F9FC;\">\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;font-weight:600;\">Content quality<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">Thin or AI-generated content as the majority of URLs on the domain<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">One or two thin pages in an otherwise substantive catalogue<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;font-weight:600;\">Anchor manipulation<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">Coordinated anchor velocity spike from many referring domains over weeks<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">Over-optimized anchor profile pointing at one URL only<\/td>\n<\/tr>\n<tr style=\"background:#F8F9FC;\">\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;font-weight:600;\">User experience<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">Template-driven ad density, intrusive interstitials sitewide, doorway architecture<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">A single page with stuffed keywords, cloaked content, or sneaky redirects<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;font-weight:600;\">Enforcement type<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">Sitewide manual action or domain-level algorithmic suppression<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">Partial-match manual action or URL-scoped algorithmic filter<\/td>\n<\/tr>\n<tr style=\"background:#F8F9FC;\">\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;font-weight:600;\">Recovery surface<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">Template rewrite, content pruning, profile-level disavow, reconsideration request<\/td>\n<td style=\"padding:10px 12px;border:1px solid #d8dde8;\">Edit or deindex the offending URL, narrow disavow if linked<\/td>\n<\/tr>\n<\/tbody>\n<\/table><figcaption style=\"text-align:center;color:#6a7280;font-size:.88em;margin-top:8px;\">Same six categories, two different enforcement scopes. The deciding factor is whether the pattern repeats across the domain or stays contained to specific URLs.<\/figcaption><\/figure>\n<p>The recovery surface row is probably where most of the wasted effort lives. Teams that misdiagnose page-level penalties as sitewide spend months pruning content that wasn&#8217;t the problem. Teams that misdiagnose sitewide demotions as page-level edit a handful of URLs and wonder why traffic stays flat for two more update cycles. Get the scope right and the work narrows quickly. Sometimes by an order of magnitude.<\/p>\n<figure class=\"wp-block-image size-large\">\n        <img loading=\"lazy\" decoding=\"async\" width=\"900\" height=\"514\" src=\"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-penalty-warning-signals.jpg\" alt=\"Red warning flag in damaged soil representing sitewide penalty indicators\" class=\"wp-image-53\" srcset=\"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-penalty-warning-signals.jpg 900w, https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-penalty-warning-signals-300x171.jpg 300w, https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-penalty-warning-signals-768x439.jpg 768w\" sizes=\"auto, (max-width: 900px) 100vw, 900px\" \/><figcaption>Sitewide red flags compound, one templated bad pattern plus a thin-content ratio is enough to flip a domain into sitewide enforcement scope.<\/figcaption><\/figure>\n<h2>Recent Update Patterns: What Hit Sitewide, What Stayed Page-Level<\/h2>\n<p>Google&#8217;s algorithm updates over the past two years show both modes operating in parallel, and the public update notes from <a href=\"https:\/\/developers.google.com\/search\/blog\" rel=\"noopener\">Google Search Central&#8217;s blog<\/a> repeatedly emphasize that scope of impact varies case by case.<\/p>\n<p>The Helpful Content classifier operates largely as a sitewide signal. When the system detects a pervasive pattern of low-value content across a domain, the entire site receives a ranking suppression, not a per-URL filter. This is not an absolute penalty, pages don&#8217;t get deindexed, but the domain loses trust signals that previously helped it compete (and yes, one client of mine watched a five-year-old finance site lose 58% overnight in that cycle, the domain never fully recovered). Recovery requires addressing content quality across the majority of pages, not just fixing a handful. Sites that saw 40-60% traffic drops in the September 2023 cycle typically had widespread issues, affiliate content with minimal original insight, AI-generated padding at volume, pages clearly written for search engines rather than readers.<\/p>\n<p>Spam updates, by contrast, show more surgical precision. <a href=\"https:\/\/backlinko.com\/google-penalty\" rel=\"noopener\">Backlinko&#8217;s penalty guide<\/a> walks through cases where SpamBrain isolated specific manipulative link schemes or scraped content sections and suppressed only the affected pages. A domain with ten spammy product pages and ninety legitimate articles may see only those ten pages lose visibility. This page-level approach explains why a lot of manual actions target specific URLs rather than entire domains, the violation didn&#8217;t generalize, so the enforcement didn&#8217;t either.<\/p>\n<div style=\"display:flex;flex-wrap:wrap;gap:16px;margin:28px 0;\">\n<div style=\"flex:1 1 200px;background:#FFF8E1;border:1px solid #F1D481;border-radius:6px;padding:18px 20px;text-align:center;\">\n<div style=\"font-size:2.2em;font-weight:700;color:#8A6A12;line-height:1;\">40-60%<\/div>\n<div style=\"font-size:.85em;color:#3A2F12;margin-top:6px;\">Traffic drop typical of sitewide Helpful Content classification<\/div>\n<\/div>\n<div style=\"flex:1 1 200px;background:#FFF8E1;border:1px solid #F1D481;border-radius:6px;padding:18px 20px;text-align:center;\">\n<div style=\"font-size:2.2em;font-weight:700;color:#8A6A12;line-height:1;\">10%<\/div>\n<div style=\"font-size:.85em;color:#3A2F12;margin-top:6px;\">URL share that can trigger sitewide scope when concentrated on templates<\/div>\n<\/div>\n<div style=\"flex:1 1 200px;background:#FFF8E1;border:1px solid #F1D481;border-radius:6px;padding:18px 20px;text-align:center;\">\n<div style=\"font-size:2.2em;font-weight:700;color:#8A6A12;line-height:1;\">2-6mo<\/div>\n<div style=\"font-size:.85em;color:#3A2F12;margin-top:6px;\">Typical recovery window after sitewide algorithmic demotion<\/div>\n<\/div>\n<\/div>\n<p>The practical reality sits between these poles. Strong individual pages on weak domains can still rank, but they face headwinds. A genuinely useful guide on a site with mostly thin content will rank lower than an equivalent page on a trusted domain. Google&#8217;s systems don&#8217;t ignore quality signals from individual pages, but sitewide trust acts as a multiplier or dampener. For link-building strategy, this means placement context matters more than ever. A backlink from a single strong article on a penalty-affected domain carries less authority than the same link from a consistently high-quality site.<\/p>\n<h2>The Scope-Diagnosis Flow: How to Tell Which One Hit You<\/h2>\n<p>Okay, before you spend a week on remediation, run this in order. Each step rules out a scope. What remains is the diagnosis.<\/p>\n<div style=\"background:#FAFBFD;border:1px solid #d8dde8;border-radius:6px;padding:24px;margin:28px 0;\">\n<p style=\"margin:0 0 18px;font-weight:700;letter-spacing:.04em;text-transform:uppercase;font-size:.78em;color:#1F2A44;\">Scope-diagnosis flow<\/p>\n<div style=\"display:flex;flex-wrap:wrap;gap:12px;\">\n<div style=\"flex:1 1 200px;background:#fff;border:1px solid #d8dde8;border-radius:4px;padding:14px;\">\n<div style=\"font-size:.78em;font-weight:700;color:#8A6A12;letter-spacing:.05em;\">STEP 1<\/div>\n<div style=\"font-weight:600;margin:6px 0 4px;\">Check Search Console<\/div>\n<div style=\"font-size:.9em;color:#3a4458;\">Manual Actions and Security Issues panels. If anything is flagged, you have an explicit scope (sitewide, partial-match, or per-URL).<\/div>\n<\/div>\n<div style=\"flex:0 0 auto;align-self:center;font-size:1.5em;color:#1F2A44;\">\u2192<\/div>\n<div style=\"flex:1 1 200px;background:#fff;border:1px solid #d8dde8;border-radius:4px;padding:14px;\">\n<div style=\"font-size:.78em;font-weight:700;color:#8A6A12;letter-spacing:.05em;\">STEP 2<\/div>\n<div style=\"font-weight:600;margin:6px 0 4px;\">Map the drop<\/div>\n<div style=\"font-size:.9em;color:#3a4458;\">Pull GSC pages-by-clicks before and after the drop date. Did most URLs lose, or just a cluster?<\/div>\n<\/div>\n<div style=\"flex:0 0 auto;align-self:center;font-size:1.5em;color:#1F2A44;\">\u2192<\/div>\n<div style=\"flex:1 1 200px;background:#fff;border:1px solid #d8dde8;border-radius:4px;padding:14px;\">\n<div style=\"font-size:.78em;font-weight:700;color:#8A6A12;letter-spacing:.05em;\">STEP 3<\/div>\n<div style=\"font-weight:600;margin:6px 0 4px;\">Match the date<\/div>\n<div style=\"font-size:.9em;color:#3a4458;\">Cross-check against Google&#8217;s update history. A core update or spam update inside your drop window pushes you toward algorithmic scope.<\/div>\n<\/div>\n<div style=\"flex:0 0 auto;align-self:center;font-size:1.5em;color:#1F2A44;\">\u2192<\/div>\n<div style=\"flex:1 1 200px;background:#fff;border:1px solid #d8dde8;border-radius:4px;padding:14px;\">\n<div style=\"font-size:.78em;font-weight:700;color:#8A6A12;letter-spacing:.05em;\">STEP 4<\/div>\n<div style=\"font-weight:600;margin:6px 0 4px;\">Audit the pattern<\/div>\n<div style=\"font-size:.9em;color:#3a4458;\">Templated link or content issue across the domain points sitewide. Isolated URL pattern points page-level.<\/div>\n<\/div>\n<\/div>\n<\/div>\n<p>The first step rules out the easy half of the diagnosis. If Search Console shows a manual action, the scope is already named for you, sitewide, partial-match (with the affected URL prefix or section listed), or specific URLs. <a href=\"https:\/\/moz.com\/learn\/seo\/google-penalties\" rel=\"noopener\">Moz&#8217;s manual-action breakdown<\/a> is a useful reference for what each named violation looks like in the Search Console UI.<\/p>\n<p>Step 2 is where most diagnoses crystallize. Or at least, where they should. Export the GSC pages report for the four weeks before and after the drop date. If roughly 80%+ of indexed URLs lost clicks proportionally, you&#8217;re looking at sitewide. If the loss concentrates on a subdirectory or a thematic cluster (e.g., all 47 product pages tagged &#8220;supplements&#8221;), partial-match or page-level scope is more likely. If a single URL collapsed and the rest of the domain held, that&#8217;s almost always page-level.<\/p>\n<p>Step 3 separates algorithmic from manual. If your drop aligns with a documented Google update date, suspect algorithmic. If it appears at an arbitrary date with no update, and especially if Search Console flagged anything, suspect manual.<\/p>\n<div style=\"border-left:3px solid #4A90B8;background:#EEF5FA;padding:14px 18px;margin:24px 0;border-radius:0 4px 4px 0;\">\n<p style=\"margin:0 0 4px;font-size:.78em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;color:#1F4A66;\">Note<\/p>\n<p style=\"margin:0;\">A clean Search Console doesn&#8217;t mean you&#8217;re safe, algorithmic suppression is silent. But it does narrow the search, no manual action plus traffic drop matching an update window points strongly at algorithmic, which means your reconsideration request won&#8217;t help and template-level fixes are the real lever.<\/p>\n<\/div>\n<p>Step 4 is the pattern audit. This is the work, but it&#8217;s the work that determines whether you spend the next month rewriting 20 pages or 200. Look at the URLs that lost ranking. Do they share a template element (footer, sidebar, nav)? Do they share a content fingerprint (same writer, same generation tool, same affiliate template)? Do they share a link-acquisition pattern (same anchor text class, same referring-domain cohort)? Repeated patterns mean sitewide scope; isolated patterns mean page-level.<\/p>\n<style>\n.hl-deepdive summary::-webkit-details-marker { display:none; }\n.hl-deepdive summary { outline:none; }\n.hl-deepdive[open] .hl-deepdive__icon { transform:rotate(180deg); background:#8A6A12; }\n.hl-deepdive[open] .hl-deepdive__eyebrow::after { content:\" \u00b7 click to collapse\"; }\n.hl-deepdive:not([open]) .hl-deepdive__eyebrow::after { content:\" \u00b7 click to expand\"; }\n.hl-deepdive:hover { box-shadow:0 4px 14px rgba(31,42,68,.12); transform:translateY(-1px); }\n.hl-deepdive { transition:box-shadow .2s ease, transform .2s ease; }\n.hl-deepdive__icon { transition:transform .25s ease, background .25s ease; }\n<\/style>\n<details class=\"hl-deepdive\" style=\"border:1px solid #d8dde8;border-radius:10px;margin:28px 0;background:linear-gradient(180deg,#FAFBFD 0%,#F1F4FA 100%);box-shadow:0 1px 4px rgba(31,42,68,.08);overflow:hidden;\">\n<summary style=\"cursor:pointer;padding:20px 24px;list-style:none;display:flex;align-items:center;gap:16px;\">\n<span class=\"hl-deepdive__icon\" style=\"flex:0 0 auto;display:inline-flex;align-items:center;justify-content:center;width:40px;height:40px;background:#1F2A44;color:#fff;border-radius:50%;font-size:1.4em;line-height:1;font-weight:700;\">\u25be<\/span><br \/>\n<span style=\"flex:1 1 auto;\"><br \/>\n<span class=\"hl-deepdive__eyebrow\" style=\"display:block;font-size:.72em;font-weight:700;letter-spacing:.1em;text-transform:uppercase;color:#8A6A12;\">Deep dive<\/span><br \/>\n<span style=\"display:block;font-size:1.08em;font-weight:700;color:#1F2A44;margin-top:3px;\">What tips Google into sitewide vs page-level enforcement<\/span><br \/>\n<\/span><br \/>\n<\/summary>\n<div style=\"padding:18px 24px 22px;color:#3a4458;border-top:1px solid #e3e8f0;background:#fff;\">\n<p>Google&#8217;s enforcement systems weigh a handful of structural features when deciding whether a violation is one URL&#8217;s problem or the whole domain&#8217;s. Based on reverse-engineering update timelines and the Search Quality Rater Guidelines, the heaviest features look like this:<\/p>\n<ol style=\"padding-left:22px;\">\n<li><strong>Template residence.<\/strong> Is the offending element (link, content block, ad slot) part of the page template, or content authored per-page? Template = sitewide bias. Per-page = page-level bias.<\/li>\n<li><strong>URL ratio.<\/strong> What fraction of indexed URLs exhibit the pattern? Below roughly 10% with no template involvement, page-level is the likely scope. Above that, especially when concentrated on a template, the classifier flips to sitewide. (Threshold is inferred, not published.)<\/li>\n<li><strong>Anchor-velocity coordination.<\/strong> A single over-optimized anchor profile on one URL is page-scoped. A coordinated anchor velocity spike across many URLs, especially from the same referring-domain cohort, reads as a domain-level link scheme.<\/li>\n<li><strong>Topical concentration.<\/strong> When all the bad URLs share a topic, Google&#8217;s partial-match action can target a subdirectory or section without touching the rest of the site. When the bad URLs span topics, sitewide scope becomes more likely.<\/li>\n<li><strong>Recurrence.<\/strong> A second hit within the same audit window (Google catches the same pattern on additional URLs after the first action) is a strong signal toward broadening scope from page-level to partial-match or sitewide.<\/li>\n<\/ol>\n<p>None of these are independently sufficient. The classifier weighs combinations, the templated-link case is the cleanest sitewide trigger because it satisfies template residence, URL ratio, and recurrence simultaneously. A single bought guest post satisfies none of those, so it stays page-level.<\/p>\n<\/div>\n<\/details>\n<h2>Link-Building Implications: Vetting for Scope Risk<\/h2>\n<h3>Red Flags That Trigger Sitewide Penalties on Linking Domains<\/h3>\n<p>When you&#8217;re picking link sources, you&#8217;re effectively betting on the domain&#8217;s classifier status. Search algorithms flag domains, not just individual pages, when patterns suggest systemic quality issues. Thin content across dozens or hundreds of pages signals a low-investment publishing model; if most URLs offer minimal unique value, classifiers may downrank the entire site. Spammy backlink profiles trigger similar scrutiny, a sudden influx of links from irrelevant directories, comment spam, or link farms tells Google the domain participates in manipulative schemes.<\/p>\n<p>Aggressive ad layouts that push content below the fold or interrupt reading flow violate user experience guidelines at scale, and because the layout is template-driven, the violation hits sitewide. Sudden topic shifts confuse topical authority signals, a finance blog pivoting to health advice without editorial rationale looks opportunistic rather than authoritative. AI-generated filler published at industrial volume creates semantic duplication and shallow treatment of topics, even if individual pages pass basic checks, the aggregate pattern reveals automation over expertise.<\/p>\n<p>These red flags compound. A site with mediocre content and a clean link profile may survive, but combine thin pages with purchased links and algorithm penalties usually follow. The classifier learns that certain domain-level fingerprints correlate with poor outcomes, then applies that learning broadly. If your site exhibits multiple patterns, every page inherits the penalty, even strong individual articles suffer from guilt by association with the broader domain footprint. (And recovery from inherited penalties is slower than recovery from page-specific ones, you can&#8217;t just delete the bad URL, you have to wait for the classifier to re-evaluate the whole domain. I&#8217;ve watched that wait stretch to nine months on one stubborn case.)<\/p>\n<h3>Safe Harbors: Domains with Strong Sitewide Signals<\/h3>\n<p>Domains that routinely pass sitewide quality signals share identifiable traits. They maintain consistent editorial standards across pages, formatting, sourcing, and depth remain stable whether you land on a cornerstone guide or a recent news item. Topical coherence matters, sites focused on a clear subject area signal expertise more reliably than aggregators covering everything.<\/p>\n<p>Natural link growth patterns help. Domains that acquire backlinks steadily over time, from diverse referring domains rather than sudden spikes from link schemes, build trust with classifiers. Transparent ownership and contact information reduce flags, sites hiding behind privacy services or lacking author attribution face more scrutiny.<\/p>\n<p>Genuine user engagement leaves measurable traces. Return visits, time-on-page metrics, and social shares suggest content delivers value beyond manipulating rankings. Strong internal linking structures and logical site architecture demonstrate editorial investment rather than template-driven publishing.<\/p>\n<p>These characteristics collectively tell classifiers, this domain exercises judgment across its entire footprint. When evaluating link opportunities, prioritize domains exhibiting multiple signals. A single positive trait won&#8217;t overcome weak fundamentals elsewhere. For practitioners assessing whether a partner site merits sitewide links, audit their consistency first, scan ten random pages and note whether quality holds. If editorial rigor falters on older posts or secondary sections, classifiers likely see the same pattern. Focus partnerships on domains where excellence is sitewide, not accidental.<\/p>\n<figure class=\"wp-block-image size-large\">\n        <img loading=\"lazy\" decoding=\"async\" width=\"900\" height=\"514\" src=\"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/strong-domain-foundation-signals.jpg\" alt=\"Solid stone foundation supporting structure over water representing strong domain signals\" class=\"wp-image-54\" srcset=\"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/strong-domain-foundation-signals.jpg 900w, https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/strong-domain-foundation-signals-300x171.jpg 300w, https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/strong-domain-foundation-signals-768x439.jpg 768w\" sizes=\"auto, (max-width: 900px) 100vw, 900px\" \/><figcaption>Sitewide-clean domains share traits, consistent editorial standards, natural link velocity, transparent attribution, none of which the classifier evaluates in isolation.<\/figcaption><\/figure>\n<h2>How Living Links Technology Addresses Classifier Risk<\/h2>\n<p>Post-placement editing addresses classifier risk by allowing strategic adjustments after links are live. When search engines shift how they evaluate sitewide versus page-level signals, you can update anchor text to match new weighting patterns, swapping brand mentions for keyword variants if sitewide penalties intensify, or vice versa when algorithmic tolerance increases.<\/p>\n<p>Target URL flexibility matters when page-level classifiers evolve. If a destination page loses topical authority due to algorithm updates, you can redirect the link to a stronger alternative without removing the placement entirely. This preserves the relationship with the linking site while adapting to new ranking signals.<\/p>\n<p>Surrounding content adjustments maintain topical relevance as language models and semantic classifiers improve. If an algorithm update changes how context influences link evaluation, you can modify the sentences around your anchor text to strengthen topical alignment, adding clarifying phrases, updating outdated references, or tightening semantic coherence.<\/p>\n<p>The core advantage is response speed. You can react to classifier changes without negotiating new placements or losing established links. Traditional static backlinks become liabilities when algorithms shift; editable placements become assets that adapt. This matters most during major updates when sitewide versus page-level signal weighting changes rapidly and broad link portfolios need synchronized adjustments. Implementation runs through a dashboard interface rather than contacting dozens of webmasters. The technical mechanism stays invisible to end users, they see only naturally updated content that reflects current best practices as search engine evaluation methods evolve.<\/p>\n<h2>Treat as Sitewide or Treat as Page-Scoped: The Decision Card<\/h2>\n<p>Once you&#8217;ve run the diagnosis flow, the remediation path bifurcates sharply. Treating a sitewide demotion as if it were page-scoped is a six-month mistake, or longer if you keep doubling down on the wrong fix. Treating a page-level penalty as if it were sitewide just burns effort on the wrong surfaces.<\/p>\n<div style=\"display:flex;flex-wrap:wrap;gap:16px;margin:28px 0;\">\n<div style=\"flex:1 1 280px;background:#EEF7EF;border:1px solid #BFE0C5;border-radius:8px;padding:20px 22px;\">\n<p style=\"margin:0 0 14px;font-weight:700;color:#2D6A36;font-size:.95em;display:flex;align-items:center;gap:10px;\">\n<span style=\"display:inline-flex;align-items:center;justify-content:center;width:26px;height:26px;background:#2D6A36;color:#fff;border-radius:50%;font-size:.9em;line-height:1;\">\u2713<\/span><br \/>\nTreat as sitewide when\n<\/p>\n<ul style=\"margin:0;padding-left:0;list-style:none;display:grid;gap:8px;\">\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#2D6A36;font-weight:700;flex:0 0 auto;\">\u203a<\/span>Search Console shows a sitewide or partial-match manual action<\/li>\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#2D6A36;font-weight:700;flex:0 0 auto;\">\u203a<\/span>Most indexed URLs lost clicks proportionally on the same date<\/li>\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#2D6A36;font-weight:700;flex:0 0 auto;\">\u203a<\/span>The offending pattern lives in a template (footer, sidebar, nav, ad layout)<\/li>\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#2D6A36;font-weight:700;flex:0 0 auto;\">\u203a<\/span>Drop date aligns with a documented core or spam update<\/li>\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#2D6A36;font-weight:700;flex:0 0 auto;\">\u203a<\/span>Thin-content ratio is above 30-40% of indexed URLs<\/li>\n<\/ul>\n<\/div>\n<div style=\"flex:1 1 280px;background:#F5F5F7;border:1px solid #d8dde8;border-radius:8px;padding:20px 22px;\">\n<p style=\"margin:0 0 14px;font-weight:700;color:#6a7280;font-size:.95em;display:flex;align-items:center;gap:10px;\">\n<span style=\"display:inline-flex;align-items:center;justify-content:center;width:26px;height:26px;background:#9aa3b2;color:#fff;border-radius:50%;font-size:.9em;line-height:1;\">\u2717<\/span><br \/>\nTreat as page-scoped when\n<\/p>\n<ul style=\"margin:0;padding-left:0;list-style:none;display:grid;gap:8px;color:#6a7280;\">\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#9aa3b2;font-weight:700;flex:0 0 auto;\">\u203a<\/span>Search Console is clean and a single URL (or cluster) collapsed<\/li>\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#9aa3b2;font-weight:700;flex:0 0 auto;\">\u203a<\/span>The rest of the domain holds ranking on its key terms<\/li>\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#9aa3b2;font-weight:700;flex:0 0 auto;\">\u203a<\/span>The pattern is isolated to specific URLs, not a shared template element<\/li>\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#9aa3b2;font-weight:700;flex:0 0 auto;\">\u203a<\/span>Anchor profile manipulation points at one URL only<\/li>\n<li style=\"display:flex;gap:10px;\"><span style=\"color:#9aa3b2;font-weight:700;flex:0 0 auto;\">\u203a<\/span>Drop date doesn&#8217;t match any documented Google update<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<p>Understanding the distinction between sitewide and page-level enforcement fundamentally changes how you evaluate link opportunities and how you triage your own ranking losses. When Google applies a sitewide classifier, hosting platform quality, domain trust, or structural issues override individual content merit, even a perfectly optimized guest post can inherit ranking penalties from the broader domain. This knowledge shifts strategic focus from chasing high-volume directories or low-barrier platforms toward selective placement on editorially sound sites with clean algorithmic profiles.<\/p>\n<p>So the practical implication, before pursuing any link, assess whether the domain itself passes muster, not just the target page. Check for thin content proliferation, excessive advertising, or spammy link patterns across the site. One bad neighborhood signal can probably nullify your outreach effort. And when you&#8217;re diagnosing your own site&#8217;s losses, the scope question comes before the remediation question. Every time.<\/p>\n<div style=\"background:linear-gradient(135deg,#1F2A44 0%,#2B3A5C 100%);color:#fff;border-radius:10px;padding:30px 32px;margin:36px 0;box-shadow:0 4px 14px rgba(31,42,68,.18);\">\n<p style=\"margin:0 0 6px;font-size:.78em;font-weight:700;letter-spacing:.12em;text-transform:uppercase;color:#F1D481;\">Try it this week<\/p>\n<p style=\"margin:0 0 22px;font-size:1.32em;font-weight:700;line-height:1.3;color:#fff;\">Run the scope-diagnosis flow on your worst-performing month from the last year.<\/p>\n<ol style=\"margin:0;padding-left:0;list-style:none;display:grid;gap:14px;\">\n<li style=\"display:flex;gap:14px;align-items:flex-start;\">\n<span style=\"flex:0 0 auto;display:inline-flex;align-items:center;justify-content:center;width:28px;height:28px;background:rgba(241,212,129,.18);color:#F1D481;border:1px solid rgba(241,212,129,.4);border-radius:50%;font-weight:700;font-size:.9em;line-height:1;\">1<\/span><br \/>\n<span style=\"color:rgba(255,255,255,.92);\">Pull GSC pages-by-clicks for the four weeks before and after your sharpest ranking loss. Note the URL share that lost (most pages or a cluster?).<\/span>\n<\/li>\n<li style=\"display:flex;gap:14px;align-items:flex-start;\">\n<span style=\"flex:0 0 auto;display:inline-flex;align-items:center;justify-content:center;width:28px;height:28px;background:rgba(241,212,129,.18);color:#F1D481;border:1px solid rgba(241,212,129,.4);border-radius:50%;font-weight:700;font-size:.9em;line-height:1;\">2<\/span><br \/>\n<span style=\"color:rgba(255,255,255,.92);\">Cross-check the drop date against Google&#8217;s update history. If it lines up with a core or spam update, you&#8217;re algorithmic. If it&#8217;s an off-calendar date, check Search Console manual actions.<\/span>\n<\/li>\n<li style=\"display:flex;gap:14px;align-items:flex-start;\">\n<span style=\"flex:0 0 auto;display:inline-flex;align-items:center;justify-content:center;width:28px;height:28px;background:rgba(241,212,129,.18);color:#F1D481;border:1px solid rgba(241,212,129,.4);border-radius:50%;font-weight:700;font-size:.9em;line-height:1;\">3<\/span><br \/>\n<span style=\"color:rgba(255,255,255,.92);\">Look at the URLs that lost. Do they share a template element or content fingerprint? Sitewide. Are they isolated? Page-level. Write the scope verdict down before doing any remediation.<\/span>\n<\/li>\n<\/ol>\n<p style=\"margin:22px 0 0;font-size:.92em;color:rgba(255,255,255,.7);font-style:italic;\">Scope first, fix second. Most wasted remediation cycles come from skipping the first half of this sentence.<\/p>\n<\/div>\n<h2>Related guides<\/h2>\n<ul>\n<li><a href=\"https:\/\/hetneo.link\/blog\/why-smart-seos-test-their-strategies-on-pbn-links-first\/\"><strong>PBN Penalties: How Google Detects Networks<\/strong><\/a>, The cornerstone on PBN penalty mechanics and how sitewide enforcement applies to network footprints.<\/li>\n<li><a href=\"https:\/\/hetneo.link\/blog\/how-to-clean-up-toxic-links-before-they-cost-you-traffic\/\"><strong>Cleaning Up Toxic Links Before They Cost You<\/strong><\/a>, The remediation playbook for backlink-driven penalties, page-scoped and sitewide.<\/li>\n<li><a href=\"https:\/\/hetneo.link\/managed-link-building\"><strong>Managed Link Building<\/strong><\/a>, How we vet link sources for sitewide classifier risk before placement.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>A penalty&#8217;s scope is the whole game. Whether Google demotes one URL or the entire domain decides whether you&#8217;re rewriting&#8230;<\/p>\n","protected":false},"author":4,"featured_media":51,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-55","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-updates-algorithm"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Sitewide vs Page-Level Penalties: How Google Decides<\/title>\n<meta name=\"description\" content=\"Sitewide vs. page-level penalties: which signals trigger each, how Google chooses between them, and the audit that tells you which one you&#039;re dealing with.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Sitewide vs Page-Level Penalties: How Google Decides\" \/>\n<meta property=\"og:description\" content=\"Sitewide vs. page-level penalties: which signals trigger each, how Google chooses between them, and the audit that tells you which one you&#039;re dealing with.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/\" \/>\n<meta property=\"og:site_name\" content=\"Hetneo&#039;s Links Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-12-10T06:52:39+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-16T12:26:24+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg\" \/>\n\t<meta property=\"og:image:width\" content=\"900\" \/>\n\t<meta property=\"og:image:height\" content=\"514\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"madison\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@maddiehoulding\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"madison\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"18 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/\"},\"author\":{\"name\":\"madison\",\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/#\\\/schema\\\/person\\\/6c6a683e9a50d03ee7fa5ac6432d56a6\"},\"headline\":\"Sitewide vs Page-Level: How Google Decides What Gets Punished\",\"datePublished\":\"2025-12-10T06:52:39+00:00\",\"dateModified\":\"2026-05-16T12:26:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/\"},\"wordCount\":3702,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg\",\"articleSection\":[\"Google Updates &amp; Algorithm\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/\",\"url\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/\",\"name\":\"Sitewide vs Page-Level Penalties: How Google Decides\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg\",\"datePublished\":\"2025-12-10T06:52:39+00:00\",\"dateModified\":\"2026-05-16T12:26:24+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/#\\\/schema\\\/person\\\/6c6a683e9a50d03ee7fa5ac6432d56a6\"},\"description\":\"Sitewide vs. page-level penalties: which signals trigger each, how Google chooses between them, and the audit that tells you which one you're dealing with.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/#primaryimage\",\"url\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg\",\"contentUrl\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg\",\"width\":900,\"height\":514,\"caption\":\"Close-up of a metal caliper measuring one link of a chain-link fence, with the rest of the fence receding into a blurred industrial background under soft overcast light.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/sitewide-vs-page-level-how-google-decides-what-gets-punished\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Sitewide vs Page-Level: How Google Decides What Gets Punished\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/\",\"name\":\"Hetneo's Links Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/#\\\/schema\\\/person\\\/6c6a683e9a50d03ee7fa5ac6432d56a6\",\"name\":\"madison\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f4d2520c34ef92cc2328426bfca387d318cbd9a2eec2d15835a67cc4a3414cd7?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f4d2520c34ef92cc2328426bfca387d318cbd9a2eec2d15835a67cc4a3414cd7?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f4d2520c34ef92cc2328426bfca387d318cbd9a2eec2d15835a67cc4a3414cd7?s=96&d=mm&r=g\",\"caption\":\"madison\"},\"description\":\"Content Manager at Hetneo's Links. Madison runs editorial across the link-building space, auditing campaigns, writing the briefs that keep guest posts from sounding like ad copy, and turning analytics into next month's roadmap. Loves a clean brief, hates a buried lede.\",\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/madisonhoulding\\\/\",\"https:\\\/\\\/x.com\\\/maddiehoulding\"],\"url\":\"https:\\\/\\\/hetneo.link\\\/blog\\\/author\\\/madison\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Sitewide vs Page-Level Penalties: How Google Decides","description":"Sitewide vs. page-level penalties: which signals trigger each, how Google chooses between them, and the audit that tells you which one you're dealing with.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/","og_locale":"en_US","og_type":"article","og_title":"Sitewide vs Page-Level Penalties: How Google Decides","og_description":"Sitewide vs. page-level penalties: which signals trigger each, how Google chooses between them, and the audit that tells you which one you're dealing with.","og_url":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/","og_site_name":"Hetneo&#039;s Links Blog","article_published_time":"2025-12-10T06:52:39+00:00","article_modified_time":"2026-05-16T12:26:24+00:00","og_image":[{"width":900,"height":514,"url":"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg","type":"image\/jpeg"}],"author":"madison","twitter_card":"summary_large_image","twitter_creator":"@maddiehoulding","twitter_misc":{"Written by":"madison","Est. reading time":"18 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/#article","isPartOf":{"@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/"},"author":{"name":"madison","@id":"https:\/\/hetneo.link\/blog\/#\/schema\/person\/6c6a683e9a50d03ee7fa5ac6432d56a6"},"headline":"Sitewide vs Page-Level: How Google Decides What Gets Punished","datePublished":"2025-12-10T06:52:39+00:00","dateModified":"2026-05-16T12:26:24+00:00","mainEntityOfPage":{"@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/"},"wordCount":3702,"commentCount":0,"image":{"@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/#primaryimage"},"thumbnailUrl":"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg","articleSection":["Google Updates &amp; Algorithm"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/","url":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/","name":"Sitewide vs Page-Level Penalties: How Google Decides","isPartOf":{"@id":"https:\/\/hetneo.link\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/#primaryimage"},"image":{"@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/#primaryimage"},"thumbnailUrl":"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg","datePublished":"2025-12-10T06:52:39+00:00","dateModified":"2026-05-16T12:26:24+00:00","author":{"@id":"https:\/\/hetneo.link\/blog\/#\/schema\/person\/6c6a683e9a50d03ee7fa5ac6432d56a6"},"description":"Sitewide vs. page-level penalties: which signals trigger each, how Google chooses between them, and the audit that tells you which one you're dealing with.","breadcrumb":{"@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/#primaryimage","url":"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg","contentUrl":"https:\/\/hetneo.link\/blog\/wp-content\/uploads\/2025\/12\/sitewide-vs-page-level-seo-penalties-chain-caliper.jpeg","width":900,"height":514,"caption":"Close-up of a metal caliper measuring one link of a chain-link fence, with the rest of the fence receding into a blurred industrial background under soft overcast light."},{"@type":"BreadcrumbList","@id":"https:\/\/hetneo.link\/blog\/sitewide-vs-page-level-how-google-decides-what-gets-punished\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/hetneo.link\/blog\/"},{"@type":"ListItem","position":2,"name":"Sitewide vs Page-Level: How Google Decides What Gets Punished"}]},{"@type":"WebSite","@id":"https:\/\/hetneo.link\/blog\/#website","url":"https:\/\/hetneo.link\/blog\/","name":"Hetneo's Links Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/hetneo.link\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/hetneo.link\/blog\/#\/schema\/person\/6c6a683e9a50d03ee7fa5ac6432d56a6","name":"madison","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f4d2520c34ef92cc2328426bfca387d318cbd9a2eec2d15835a67cc4a3414cd7?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f4d2520c34ef92cc2328426bfca387d318cbd9a2eec2d15835a67cc4a3414cd7?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f4d2520c34ef92cc2328426bfca387d318cbd9a2eec2d15835a67cc4a3414cd7?s=96&d=mm&r=g","caption":"madison"},"description":"Content Manager at Hetneo's Links. Madison runs editorial across the link-building space, auditing campaigns, writing the briefs that keep guest posts from sounding like ad copy, and turning analytics into next month's roadmap. Loves a clean brief, hates a buried lede.","sameAs":["https:\/\/www.linkedin.com\/in\/madisonhoulding\/","https:\/\/x.com\/maddiehoulding"],"url":"https:\/\/hetneo.link\/blog\/author\/madison\/"}]}},"_links":{"self":[{"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/posts\/55","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/comments?post=55"}],"version-history":[{"count":2,"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/posts\/55\/revisions"}],"predecessor-version":[{"id":834,"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/posts\/55\/revisions\/834"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/media\/51"}],"wp:attachment":[{"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/media?parent=55"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/categories?post=55"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hetneo.link\/blog\/wp-json\/wp\/v2\/tags?post=55"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}