---
title: "Rule Engine Update: Site Reputation Abuse (EEA), Favicon Checks, and Preferred Sources — v1.4.4"
date: 2026-08-29
version: 1.4.4
slug: rule-engine-update-1-4-4
description: "SEOCode v1.4.4 adds a new warning for Google's EEA-adjusted site reputation abuse policy enforcement and updates rules for favicon validation and preferred sources markup."
tags:
  - rule-engine
  - changelog
  - technical-seo
  - google-search
---

Rule Engine Update v1.4.4 — Site Reputation Abuse (EEA), Favicon Checks, and Preferred Sources

Google's adjusted enforcement of the site reputation abuse policy in the European Economic Area is now flagged in pull requests — along with updated checks for favicons and preferred sources markup.

New Rules

site-reputation-policy-eea — Site reputation abuse policy adjusted for EEA

Severity: Warning

What it checks:
This rule flags sites that may be hosting third-party content in a way that could be interpreted as exploiting the site's existing ranking signals — specifically under Google's site reputation abuse policy. The new rule accounts for the fact that Google has adjusted how it enforces this policy within the European Economic Area (EEA), meaning the enforcement approach differs from the global baseline.

The policy itself is unchanged in its intent: hosting third-party content on a site to piggyback on that site's authority — regardless of whether the site owner is directly involved in or overseeing that content — is prohibited. What has changed is the regional enforcement posture for EEA-based sites.

Why it matters for SEO:
A violation of the site reputation abuse policy can result in a manual action against part or all of your site. If your site operates in the EEA, the enforcement path may look different from what Google's global documentation describes, which creates ambiguity that can lead to unintentional non-compliance.

What you need to do:
If your site is based in or serves the EEA and you host any third-party content — sponsored sections, partner-contributed pages, syndicated content, affiliate hubs — review Google's updated site reputation abuse policy documentation for EEA-specific guidance. If SEOCode flags this rule in a PR, it means content or configuration changes in that PR warrant a manual review against the policy before merging.

Updated Rules

favicon-aspect-ratio — Favicon incorrect size, aspect ratio, or unsupported file format

What changed: The rule's description, name, fix template, and source reference have all been updated to reflect current Google documentation.

What it checks:
This rule validates that your site's favicon meets Google's requirements for use in Search results — specifically that the image is square (1:1 aspect ratio), meets minimum size requirements, and uses a supported file format.

Why it matters for SEO:
Google displays favicons in mobile search results next to your site name. An incorrectly sized, non-square, or unsupported favicon will be replaced by a generic placeholder. This doesn't affect ranking directly, but it does affect click-through appearance and brand recognition in the SERP.

What you need to do:
If this rule fires in a PR, check the updated fix template in the SEOCode annotation — the guidance has been revised to align with the latest Google documentation. Ensure your favicon is square, at least 48×48px, and served in a supported format (PNG, ICO, SVG, or WebP).

preferred-sources-feature — Missing preferred sources markup or configuration

What changed: The rule's description, fix template, and source reference have been updated.

What it checks:
This rule checks whether your site has the appropriate markup or configuration in place to signal preferred sources to Google — relevant for sites that want to influence how Google identifies authoritative or preferred versions of their content.

Why it matters for SEO:
Without correct preferred sources configuration, Google may surface versions of your content that you did not intend as canonical or authoritative. This is particularly relevant for publishers, news sites, and any site where content appears in multiple forms or locations.

What you need to do:
Review the updated fix template in the SEOCode PR annotation if this rule fires. The description and recommended implementation steps have been revised — if you previously addressed this rule based on older guidance, it is worth re-checking your implementation against the updated documentation.

Sources & References

1. Google Search Central Documentation Changelog

Catch SEO issues before they ship

SEOCode reviews every pull request against the latest Google SEO rules — automatically. No manual audits. No surprises after deploy.

It checks for missing metadata, broken structured data, hreflang errors, robots.txt issues, and more — right inside your existing GitHub workflow.

Try SEOCode →