Skip to content
PreferiumJoin the waitlist

SEOGoogle

Google's site-reputation manual actions have a different effect in the EEA

Google announced different EEA treatment for site-reputation manual actions from 30 August 2026. Notifications and other ranking systems still need attention.

A globe split into two halves on a plinth: one side lush and coloured beside a green tree, the other grey stone beside a bare tree, onlookers on each side.
Jump to a section

Google announced different treatment of site-reputation manual actions for searchers inside the EEA from 30 August 2026. The distinction concerns the searcher’s location, not simply where the affected publisher is based.

What happened (added 19 September 2026): The change was due to take effect on 30 August 2026. As of 19 September 2026 we had found no later revision of Google’s announcement.

The policy concerns how third-party content uses a host site

Google’s site-reputation abuse policy covers third-party content published mainly to benefit from the host site’s established ranking signals. The presence of a guest article, affiliate link or partner section alone does not establish a violation.

A manual action is applied after human review and appears in Search Console. It is separate from the automated ranking systems that may also affect a site’s pages.

The announced regional difference

Google says the impact of a site-reputation manual action does not apply to searchers in the EEA, while it can affect the relevant part of a site in results outside the EEA. The EEA includes the EU countries, Iceland, Norway and Liechtenstein.

Notifications remain. An owner can still receive a Search Console manual-action notice even when the site’s main audience is in the EEA. A domestic ranking chart may therefore fail to show an effect occurring in another market.

This does not mean every European reader will see unchanged results. Google also says an affected section may be separated in its systems and, over time, rank independently from the rest of the site. Other ranking changes remain possible.

Review the content and the audience

The policy guidance describes factors including presentation, content quality, editorial responsibility and duplication across sites. Google says no single factor decides the case. Read the examples and exceptions alongside those factors before classifying a client’s partner content.

For an agency, the immediate work is to inventory relevant sections, establish who controls their content and check the manual-actions report. Keep reporting segmented by the markets the client serves.

Do not treat the EEA distinction as a general exemption from the policy or a reason to ignore a notice. Record the affected URLs, the notice and the actions taken. For the separate automated rollout, see our August spam-update article.

Want this running under your brand?Preferium AI Edge is a white-label platform agencies resell to their clients: your brand, your Stripe, your packages and prices. Registration opens to agencies from the waitlist first.Talk to usJoin the waitlistHow white label works

Build your agency on Preferium

Partner registration opens by invitation from the waitlist, and there is no date yet. Read the agency agreement and how partner billing works before you decide.

  1. Connect a client site
  2. Set the control level
  3. Run under your brand

Privacy choices

Choose which optional technologies Preferium AS may use. All of them are off until you choose.

Analytics: Google Analytics 4 counts page views. Google may receive the page address, referrer, network address, browser and device details, and online identifiers. Browser storage: _ga, _ga_*: Up to 730 days. Renewed on activity. The browser may shorten the storage period.

Provider: Google Ireland Limited. Google may transfer data to the United States.

See the cookie notice, the privacy notice and theterms.

Necessary technologies Used for site functions

Preferium AS and Cloudflare deliver the site and protect forms against abuse. A local preference remembers if you pause animation. When optional tracking is available, the site can also remember your documented privacy choices.

Consent receipt
Provider: Preferium AS. HttpOnly receipt that documents and retrieves your consent choice. Name in the browser: __Host-preferium_consent. Storage period: The receipt is valid for up to 180 days without rolling renewal.
Local privacy choices and pending rejections
Provider: Preferium AS. Local storage of privacy choices and pending rejections. The entry alone can never allow optional technologies; a valid server receipt is required. Name in the browser: preferium-consent-v2. Storage period: Until the entry is overwritten or the browser site data is cleared. No automatic timed deletion is configured.
Privacy choice synchronization between tabs
Provider: Preferium AS. The latest message that synchronizes privacy choices and pending rejections between tabs. The message can only close optional technologies and trigger a new server check. Name in the browser: preferium-consent-sync-v1. Storage period: Until the entry is overwritten or the browser site data is cleared. No automatic timed deletion is configured.
Motion pause preference
Provider: Preferium AS. Session storage restores the requested accessibility preference between pages in this tab. Nothing is sent to a server. Name in the browser: preferium-motion-paused. Storage period: Until this browser tab session ends.
Cloudflare Turnstile
Provider: Cloudflare. Abuse protection that loads only on forms where Turnstile is necessary. Storage period: Short-lived control value tied to a form submission.
Analytics

Helps us understand how the site is used, when you consent.

Provider: Google Ireland Limited. The data may include the page address, referrer, network address, browser/device, online identifiers and usage events.

_ga, _ga_*
Processes site usage for aggregated analytics after specific consent. Storage period: Up to 730 days. Renewed on activity. The browser may shorten the storage period.

You can withdraw your choice via Privacy choices. That stops further optional loading but does not recall data already sent to Google. We attempt to delete known first-party values; the browser may prevent deletion of third-party values.

How Google uses and is responsible for data · How Google uses information from partner sites · Google privacy policy