SEO Services List.
The SEO service surface area covers the technical foundation, the on-page work, the off-page link and reputation profile, the schema and entity architecture, the content cadence, and the local and review-surface signals where they apply. Each service runs against a named Google system. Grove's engagement scope is set by the diagnostic and integrates the services the engagement actually needs, paced across quarters rather than packaged as a generic stack.
The SEO Services List hub is the catalog reference for natural SEO work. Each named service points at the commercial page that covers it in depth.
Technical audit, Core Web Vitals, rendering parity, schema implementation.
Technical audit reads the engagement against the Search Essentials technical requirements: crawlable URL structure, indexable response codes, render parity between Googlebot and the user, sitemap and robots.txt discipline. The audit surfaces the load-bearing technical remediations.
Core Web Vitals work runs against the field-data thresholds Page Experience evaluates. The diagnostic identifies the load-bearing metric (LCP, INP, or CLS) and the source of the failure; the remediation runs through the engineering implementation. The full coverage lives at Core Web Vitals for organic SEO.
Rendering parity work ensures the DOM Googlebot reads matches the DOM the user reads. JavaScript-rendered sites often ship a stripped DOM to Googlebot; the work surfaces the parity gap and routes the rendering implementation toward full parity. The parity work overlaps with the cloaking spam-policy boundary, which the methodology runs against explicitly.
Schema implementation lands the entity architecture at the layout layer. Article and Person and Organization nesting on content pages; Service schema on commercial pages; Local Business schema on location pages; FAQ and HowTo schema where the content matches the type. The implementation is validated through the Rich Results Test before it is considered done. The full reference lives at the schema markup examples hub.
Helpful Content remediation, editorial cadence, topical authority build.
Helpful Content remediation reads the existing content layer against the integrated Helpful Content signal. The diagnostic surfaces pages whose patterns read as search-engine-first rather than reader-first; the remediation runs through the published checklist as editorial criteria. Pages that fail multiple checklist questions are reshaped or noindexed; the underlying signal recalibrates as the publication-level pattern shifts. The full coverage lives at the Helpful Content Update audit service page.
Editorial cadence runs the new-content pipeline against the methodology's discipline. Substantive depth per piece. Named authors with documented expertise. First-hand experience surfacing. Citation graph onto primary sources. The cadence is paced at the publication's actual capacity to produce substantive content rather than at a generic page-count target.
Topical authority build runs the content hierarchy that signals subject-matter coverage to the continuous ranking systems. The hierarchy maps the topic into tiers and the internal linking concentrates the signal toward the commercial pages. The full reference lives at the topical authority SEO hub.
The content services operate against the Helpful Content System integration the March 2024 core update set and against the Reviews System expansion the April 2023 update set. Recovery from past demotions and build of new authority both run through the same editorial discipline.
Link acquisition, brand entity signal, citation graph build.
Link acquisition runs through the white-hat strategies the engagement's surface supports: digital PR around original research, broken-link reclamation on authoritative pages, resource-page outreach on aggregator surfaces, named-author response through Connectively and Featured.com. The selection follows from the engagement's content capacity and named-author capacity. The full operationalization lives at the white hat link building service page and the link building strategies hub.
Brand entity signal work runs the publication's visibility across the wider web. The Knowledge Graph integration runs through the Organization schema, the sameAs identity chain, and the structured-data references the Knowledge Graph reads. Unlinked brand mentions in the wider editorial coverage contribute to the entity signal layer.
Citation graph build runs the publication's references onto primary sources Google's quality systems read as authoritative. Every substantive piece carries citations to research, government surfaces, standards bodies, or named experts. The citation graph reads to the Quality Rater Guidelines and the Reviews System as the foundation of the authoritativeness signal.
The off-page work operates against the Penguin 4.0 URL-level link evaluation and against the link spam policy boundary. Manipulative acquisition produces zero-weighted links; earned acquisition produces links the ranking systems count continuously.
EEAT entity architecture, local pack qualification, review-surface work.
EEAT entity architecture runs the Person and Organization schema, the named-author surfacing, the credential graph at the Person.hasCredential layer, and the citation graph at the Article.citation layer. The work is implementation-heavy in the first quarter and editorial-cadence-heavy across subsequent quarters as the publication history accumulates. The full coverage lives at the EEAT SEO services page.
Local SEO work runs the Google Business Profile, the Local Business schema, the local citation graph, and the review acquisition layer where the engagement carries a location surface. Local pack qualification runs against the relevance, distance, and prominence signals Google's local ranking documentation describes. Engagements without a physical-location surface skip the local services entirely.
Review-surface work runs against the Reviews System's continuous evaluation. The Reviews System reads first-hand testing, original analysis, the pros-and-cons treatment, and the demonstrated use signal across review-shaped content. Engagements with review-oriented surfaces (comparison pages, buying-guide pages, audit-style content) run the review-surface work against the published criteria.
The integrated EEAT layer is what the Helpful Content System integration in March 2024 weights most heavily on YMYL-adjacent surfaces. Engagements in regulated verticals (finance, health, legal-adjacent) run the EEAT services with the heaviest emphasis because the signal threshold is highest there.
What operators ask about scope before the engagement starts.
- 01.Does Grove offer all of these services on every engagement?
- No. The engagement scope is set by the diagnostic. Most engagements run the technical audit and remediation as Quarter 1 work, the EEAT entity architecture and named-author surfacing as Quarter 1 work, the Helpful Content System content remediation across Quarters 1 and 2, and the link acquisition cadence across Quarters 2 onward. Local SEO is included when the engagement carries a location surface. Schema implementation is included on every engagement because every engagement needs the entity architecture.
- 02.Are services priced individually or bundled?
- Bundled into the retainer. The retainer cadence covers the integrated work across the surfaces the diagnostic identified. The pricing aligns with the engagement scope and the methodology cadence, not with a per-service line-item list. Engagements with smaller surface area carry smaller retainers; engagements with larger surface area carry larger retainers. The diagnostic at the end of week two carries the actual scope and budget proposal.
- 03.What is the minimum scope Grove engages on?
- Two weeks for the diagnostic, then a minimum twelve-month retainer for the build and compound phases. The published time horizon explains the minimum: signal integration runs across multiple core updates and the underlying acquisition compounds across quarters. Shorter engagements produce work the methodology has not had time to integrate against the ranking signal; the work would not earn its budget.
- 04.How does Grove split the work with the operator's existing team?
- Most engagements run alongside an internal team or a technical-implementation partner. The diagnostic identifies which work runs through Grove, which work runs through the operator's team, and which work runs through a third-party partner. The Helpful Content remediation, the EEAT entity architecture, the link acquisition, and the editorial cadence often run through Grove. The engineering implementation of technical fixes often runs through the operator's development team or a partner. The split varies per engagement and is set explicitly in the engagement letter.
- 05.What is not in scope for a Grove engagement?
- Paid search management. Conversion rate optimization beyond the SEO surface. Pure social media management. Email marketing. The boundary is the organic search discipline. Adjacent channels carry their own specialist agencies, and the engagement is more effective when each specialist runs the channel they are deepest in. Grove integrates with operator-side teams and other agencies where the channels overlap.
- 06.How does the service list change over time?
- Google's published systems shift; the service list shifts to track them. The Helpful Content System integration in March 2024 reshaped the content service. The Reviews System expansion in April 2023 expanded the EEAT service. The Core Web Vitals INP transition in March 2024 reshaped the technical service. The catalog is maintained against the current published surface; the methodology runs against what Google actually publishes and enforces today.
If you want the service catalog scoped against the engagement the diagnostic actually surfaces, see how we work.
Two-week diagnostic. The retainer engagement runs the services the diagnostic identified across quarters and years.