What's the single fastest signal that an agency calling itself white-hat isn't operating that way?

Page-volume pricing on the content deliverable. The scaled content abuse policy (formalized in the March 2024 spam-policy refresh) reads the volume produced for the algorithm rather than for the reader as the trigger, regardless of whether the content came from a model, a scraper, or a content farm of human writers. An agency quoting X articles per month at Y price per article is structurally aligned with what the policy targets. Methodology-grounded engagements ship fewer pages, deeper primary-source grounding per page, named authors, and quote at retainer cadence rather than per-article volume.

How important is the named-author rendering versus just claiming EEAT as a value?

The named-author rendering is the EEAT signal Google's quality systems train against. The Quality Rater Guidelines integrate EEAT across the Page Quality rating scale, and the December 2022 update added Experience as the first signal alongside Expertise, Authoritativeness, and Trustworthiness. An article with a named author who has a standalone Person schema node, a knowsAbout array documenting domain expertise, an Article.author pointer, and a contributor profile page with documented credentials surfaces the EEAT signal at the architecture layer. An article that lists no author and points to no Person entity surfaces no signal. An agency that talks about EEAT as a value but ships articles without the rendering is selling the vocabulary.

Is a project-shaped engagement ever the right answer for a white-hat program?

A standalone diagnostic engagement is appropriate as a one-off when the operator wants the methodology-grounded read on the site before deciding on the retainer. Past the diagnostic, the work the rankings actually require runs in quarters and years because Google's continuous-evaluation systems read sitewide quality, link-profile health, and EEAT signal continuously. A project-shaped contract that promises to lift the rankings inside a three-month sprint is structurally mismatched with the cadence the systems evaluate against. The operator pays for a sprint and gets the lift the cadence allows, which is usually the diagnostic the retainer would have started with.

What does Search Essentials adherence look like in a deliverable spec?

Each deliverable maps against specific Search Essentials sections. The technical requirements section governs the crawl, render, and indexation workstream: deliverables include canonical strategy, robots and sitemap hygiene, rendering parity audit, Core Web Vitals work against the published thresholds. The spam policies section governs the content and link workstreams: deliverables include the editorial standard document, the link-acquisition outreach pattern, the disavow position. The key-practice section governs the on-page workstream: deliverables include the named-author rendering, the schema architecture, the citation graph. An agency operating against Search Essentials can name which deliverable maps where.

Why does the disavow position matter as a diagnostic for an agency's methodology?

Penguin 4.0 went live on September 23, 2016 and shifted from sitewide demotion to URL-level real-time discounting of manipulative links. The implication is that the algorithm zero-weights manipulative links in place as it crawls, which made the disavow tool largely redundant for the algorithmic-discounting use case. The tool stays necessary for the explicit unnatural-links manual-action surface, where Google requires documented outreach-removal effort before the disavow file is accepted. An agency selling disavow audits as a default service is operating on the pre-2016 model and will charge the operator for work the algorithm already does. An agency that scopes disavow only for the manual-action case is operating against the actual algorithmic surface.

TIER 3 · ETHICAL SEO AGENCY COMPARISON

Ethical SEO Agency Comparison.

A methodology-grounded framework for evaluating white-hat SEO agencies against each other. The criteria the algorithm actually runs against: Google Search Essentials adherence at the operating level, EEAT operationalized at the schema layer, Helpful Content System literacy with the March 2024 integration understood, Penguin 4.0 link-acquisition discipline, scaled content abuse policy stance, retainer-versus-project commitment cadence. The framework reads against any shortlist.

See how we work → Read the practice notes

The framework sits inside Natural SEO Services: a methodology-grounded practice that operationalizes the published Google systems by their actual names.

The criteria the evaluation runs against

Six axes the algorithm actually evaluates against, and the agency-side reads on each.

The evaluation framework draws from the published Google systems each axis maps to. Search Essentials governs the technical and content surface contract. EEAT operationalization at the schema layer is the rendering of the signal Google's quality systems train against. The Helpful Content System integration, Penguin 4.0's URL-level link evaluation, and the scaled content abuse policy each govern a workstream the engagement has to operate against. The retainer-versus-project cadence governs whether the engagement can run at the time horizon the continuous-evaluation systems require.

Search Essentials adherence at the operating level, not just in the pitch deck.

Google Search Essentials (the document the Webmaster Guidelines were renamed to in October 2022) is the public contract every white-hat agency operates against. The evaluation is whether the agency reads the spam-policy section, the technical requirements, and the key-practice section as the acceptance contract for the work shipped, or whether the document gets referenced once in the sales pitch and then ignored. A useful diagnostic question for any shortlisted agency: name three specific Search Essentials sections the engagement will be measured against in the first quarter, and how the deliverables map to each.

EEAT operationalized at the schema layer, not declared as a value.

The Experience-Expertise-Authoritativeness-Trustworthiness framework is integrated across the Page Quality rating scale Google's quality systems train against. An agency that operationalizes EEAT renders the signal at the architecture layer: named author on every article, standalone Person schema with knowsAbout array, Article.author pointer, Organization entity nesting, contributor profile pages with documented credentials. An agency that lists EEAT as a value on its services page and does none of the rendering work is selling the vocabulary, not the signal.

Helpful Content System literacy with the March 2024 integration understood.

The Helpful Content System launched August 18, 2022 as a continuous sitewide quality signal. The March 5, 2024 core update retired the standalone signal and integrated it across the core ranking systems. Recovery from a Helpful Content demotion no longer rolls back through a single signal toggle; it requires broad continuous quality improvements across the publication. An agency that still talks about the HCS as a standalone signal is operating on the pre-March-2024 model and will misdiagnose any post-integration demotion an operator brings in.

Penguin 4.0 link-acquisition discipline and the disavow position.

Penguin 4.0 (September 23, 2016) shifted from sitewide demotion to URL-level real-time discounting of manipulative links. The implication for link-acquisition methodology is that paid placements, exchange networks, and private blog network coverage pass no PageRank because Penguin zero-weights them in place as it crawls. A methodology-grounded agency routes link acquisition through outreach to publications covering the topic, original research that earns citation, and digital PR landing genuine placement. The disavow tool stays in the workflow only for the explicit unnatural-links manual-action case, because Penguin already neutralizes the algorithmic surface. An agency selling disavow audits as a default service is operating on the pre-2016 model.

Scaled content abuse policy stance and the production cadence.

The March 2024 spam-policy formalization names scaled content abuse as the generation of mass page volumes specifically to manipulate search rankings, and explicitly notes the policy applies whether the content is produced through model automation, scraping, human writers, or a combination. A methodology-grounded agency ships fewer pages, deeper primary-source grounding per page, and a named author for every article. An agency quoting page-volume deliverables (X articles per month at Y price per article) is operating against the policy surface and will trigger the same enforcement the policy targets at the production layer.

Retainer-versus-project commitment cadence aligned with how the systems evaluate.

Google's continuous-evaluation systems read sitewide quality, link-profile health, and EEAT signal over quarters and years. A project-shaped engagement (one-off audit, three-month sprint, fixed-deliverable contract) cannot operationalize a methodology that compounds against continuous evaluation. A methodology-grounded white-hat agency runs in retainer cadence: diagnostic, architecture lift, compounding quarters, sustained authority. Project-shaped pricing for an engagement that requires retainer cadence is a structural mismatch with the work the rankings actually require.

SOURCE DOCUMENTS

Methodology-grounded versus typical white-hat positioning

The published systems read the difference, and the engagements run at different depths.

Methodology-grounded

Operationalizes the published systems

Typical white-hat agency

Pitches the values, ships the deliverables

Search Essentials reference

Names specific Search Essentials sections each deliverable maps against. Treats the document as the operating contract for the work shipped, audited per quarter.

References Search Essentials (or older Webmaster Guidelines language) once on the services page. The document does not appear in the deliverable spec or in the QA criteria.

EEAT rendering

Named author on every article, standalone Person schema with knowsAbout array, Article.author pointer, Organization entity nesting, contributor profile pages with documented credentials.

EEAT listed as a value. No standalone Person schema on the deliverables, no named-author byline pattern, no contributor profile architecture.

Helpful Content System reading

Reads the post-March-2024 integration: signals folded across the core ranking systems, recovery is broad continuous quality work rather than a single signal toggle.

Still describes the HCS as a standalone evaluation layer. Recovery framing reads as pre-March-2024 and misdiagnoses post-integration demotions.

Link acquisition methodology

Outreach to publications covering the topic, original research that earns citation, digital PR landing genuine placement. Disavow stays in the workflow only for the explicit unnatural-links manual-action case.

Disavow audits sold as a default service. Link inventory programs without a clear outreach-and-earned-coverage path. Penguin 4.0's URL-level real-time discounting not in the operating vocabulary.

Content production cadence

Fewer pages, deeper primary-source grounding per page, named authors with the experience to make the experience signal real. Quoted at retainer cadence, not at per-article volume.

Volume-shaped deliverables (X articles per month, Y price per article). Production method (model, content farm, mixed) treated as a pricing variable; the scaled content abuse policy reads volume as the trigger regardless of method.

Engagement shape

Retainer cadence with quarter-by-quarter scope: diagnostic, architecture lift, compounding quarters, sustained authority. The cadence aligns with how Google's continuous systems evaluate the site.

Project-shaped pricing (one-off audit, three-month sprint, fixed-deliverable contract) for an engagement that requires retainer cadence. The structural mismatch shows up at the second core update.

Reconsideration workflow literacy

When a manual action lands in Search Console, the workflow runs the three required elements: explanation of the issue, documented remediation across every affected page, outcome confirmation. Partial remediation gets a partial rejection and the team knows it.

Reconsideration requests submitted with partial fixes. Crawl-accessibility of the remediated pages not verified. Outreach-removal documentation missing on link-related cases. The rejections accumulate.

Methodology-grounded

Operationalizes the published systems

Search Essentials reference: Names specific Search Essentials sections each deliverable maps against. Treats the document as the operating contract for the work shipped, audited per quarter.
EEAT rendering: Named author on every article, standalone Person schema with knowsAbout array, Article.author pointer, Organization entity nesting, contributor profile pages with documented credentials.
Helpful Content System reading: Reads the post-March-2024 integration: signals folded across the core ranking systems, recovery is broad continuous quality work rather than a single signal toggle.
Link acquisition methodology: Outreach to publications covering the topic, original research that earns citation, digital PR landing genuine placement. Disavow stays in the workflow only for the explicit unnatural-links manual-action case.
Content production cadence: Fewer pages, deeper primary-source grounding per page, named authors with the experience to make the experience signal real. Quoted at retainer cadence, not at per-article volume.
Engagement shape: Retainer cadence with quarter-by-quarter scope: diagnostic, architecture lift, compounding quarters, sustained authority. The cadence aligns with how Google's continuous systems evaluate the site.
Reconsideration workflow literacy: When a manual action lands in Search Console, the workflow runs the three required elements: explanation of the issue, documented remediation across every affected page, outcome confirmation. Partial remediation gets a partial rejection and the team knows it.

Typical white-hat agency

Pitches the values, ships the deliverables

Search Essentials reference: References Search Essentials (or older Webmaster Guidelines language) once on the services page. The document does not appear in the deliverable spec or in the QA criteria.
EEAT rendering: EEAT listed as a value. No standalone Person schema on the deliverables, no named-author byline pattern, no contributor profile architecture.
Helpful Content System reading: Still describes the HCS as a standalone evaluation layer. Recovery framing reads as pre-March-2024 and misdiagnoses post-integration demotions.
Link acquisition methodology: Disavow audits sold as a default service. Link inventory programs without a clear outreach-and-earned-coverage path. Penguin 4.0's URL-level real-time discounting not in the operating vocabulary.
Content production cadence: Volume-shaped deliverables (X articles per month, Y price per article). Production method (model, content farm, mixed) treated as a pricing variable; the scaled content abuse policy reads volume as the trigger regardless of method.
Engagement shape: Project-shaped pricing (one-off audit, three-month sprint, fixed-deliverable contract) for an engagement that requires retainer cadence. The structural mismatch shows up at the second core update.
Reconsideration workflow literacy: Reconsideration requests submitted with partial fixes. Crawl-accessibility of the remediated pages not verified. Outreach-removal documentation missing on link-related cases. The rejections accumulate.

UPDATED 2026-05

How to apply the framework to a shortlist

Four stages from library read to engagement shape, that surface the methodology depth before the contract.

STAGE 0

Read the agency's library

Open the agency's published library. Read three articles on different topics from the past twelve months. Check the byline pattern (named author, contributor page, knowsAbout array). Check the citation graph (do the technical claims link to Search Central, the Quality Rater Guidelines, peer-reviewed research, or do they hang as unsourced assertions). The library is the highest-signal artifact for whether the methodology operates at the depth the rankings reward.

STAGE 1

Read the agency's deliverable spec

Ask for the actual deliverable spec on the engagement the agency is proposing. Count the page-volume metrics. If the deliverable counts pages per month at a per-article price, the engagement is operating against the scaled content abuse policy surface regardless of how the pitch frames it. Ask which Search Essentials sections each deliverable maps against. The answer either lists three or it does not exist.

STAGE 2

Probe the link-acquisition methodology

Ask the agency to name the last three link placements landed for a client in the past quarter, with the publication and the angle that earned the citation. If the answer is generic (we do outreach, we earn links, we focus on quality), the methodology is rhetorical. If the answer names publications, angles, and the source material that earned the placement, the methodology is operational. Also ask the disavow position: a default-disavow-audit answer is the pre-2016 model.

STAGE 3

Read the engagement shape

Confirm the cadence is retainer, not project. A diagnostic that feeds into a multi-quarter program is the methodology-grounded shape. A fixed-deliverable contract or a single audit handoff cannot operationalize a methodology that compounds against continuous evaluation. Read the pricing structure as the artifact: retainer pricing is the structural alignment with how the rankings actually require the work to run.

Common questions

What operators ask before the engagement starts.

01.What's the single fastest signal that an agency calling itself white-hat isn't operating that way?: Page-volume pricing on the content deliverable. The scaled content abuse policy (formalized in the March 2024 spam-policy refresh) reads the volume produced for the algorithm rather than for the reader as the trigger, regardless of whether the content came from a model, a scraper, or a content farm of human writers. An agency quoting X articles per month at Y price per article is structurally aligned with what the policy targets. Methodology-grounded engagements ship fewer pages, deeper primary-source grounding per page, named authors, and quote at retainer cadence rather than per-article volume.
02.How important is the named-author rendering versus just claiming EEAT as a value?: The named-author rendering is the EEAT signal Google's quality systems train against. The Quality Rater Guidelines integrate EEAT across the Page Quality rating scale, and the December 2022 update added Experience as the first signal alongside Expertise, Authoritativeness, and Trustworthiness. An article with a named author who has a standalone Person schema node, a knowsAbout array documenting domain expertise, an Article.author pointer, and a contributor profile page with documented credentials surfaces the EEAT signal at the architecture layer. An article that lists no author and points to no Person entity surfaces no signal. An agency that talks about EEAT as a value but ships articles without the rendering is selling the vocabulary.
03.Is a project-shaped engagement ever the right answer for a white-hat program?: A standalone diagnostic engagement is appropriate as a one-off when the operator wants the methodology-grounded read on the site before deciding on the retainer. Past the diagnostic, the work the rankings actually require runs in quarters and years because Google's continuous-evaluation systems read sitewide quality, link-profile health, and EEAT signal continuously. A project-shaped contract that promises to lift the rankings inside a three-month sprint is structurally mismatched with the cadence the systems evaluate against. The operator pays for a sprint and gets the lift the cadence allows, which is usually the diagnostic the retainer would have started with.
04.What does Search Essentials adherence look like in a deliverable spec?: Each deliverable maps against specific Search Essentials sections. The technical requirements section governs the crawl, render, and indexation workstream: deliverables include canonical strategy, robots and sitemap hygiene, rendering parity audit, Core Web Vitals work against the published thresholds. The spam policies section governs the content and link workstreams: deliverables include the editorial standard document, the link-acquisition outreach pattern, the disavow position. The key-practice section governs the on-page workstream: deliverables include the named-author rendering, the schema architecture, the citation graph. An agency operating against Search Essentials can name which deliverable maps where.
05.Why does the disavow position matter as a diagnostic for an agency's methodology?: Penguin 4.0 went live on September 23, 2016 and shifted from sitewide demotion to URL-level real-time discounting of manipulative links. The implication is that the algorithm zero-weights manipulative links in place as it crawls, which made the disavow tool largely redundant for the algorithmic-discounting use case. The tool stays necessary for the explicit unnatural-links manual-action surface, where Google requires documented outreach-removal effort before the disavow file is accepted. An agency selling disavow audits as a default service is operating on the pre-2016 model and will charge the operator for work the algorithm already does. An agency that scopes disavow only for the manual-action case is operating against the actual algorithmic surface.

ETHICAL SEO AGENCY COMPARISON · DIAGNOSTIC BOOKING FOR Q3 2026

If the framework reads the shortlist and Grove sits inside the shortlist, see how we work.

Two-week diagnostic. The diagnostic itself runs the framework against the site so the engagement starts with the methodology depth visible. Retainer cadence after the read.

See how we work → Email the practice