Home / SEO Processes / Monthly Meeting Process

Monthly Meeting Process

Last Edited: 2026-06-29 01:32

Process SLAs

• Meeting Cadence: Conducted monthly per client.
• Follow-Up: Action items created within 24 hours of meeting completion.

Global Rules

• PRIORITY: The Account Manager must prioritize client-led questions and concerns at the opening of the meeting before executing standard reporting items.
• ITERATION: If a client's concerns align with validated negative performance trends, the Account Manager must immediately pivot the strategy by creating and assigning remediation tasks during the meeting.

PROCESS MAP

GATE 0 - PRE-MEETING PREPARATION & DATA DIGESTION

• Owner: Account Manager (AM)
• Contributors: Analyst / Specialist (SEO/Content)
• Entry Criteria / Required Inputs:
  • Upcoming client meeting scheduled.
  • Raw performance reports and analytics data.
• Required Outputs:
  • All necessary performance and SEO reports run.
  • Data input is completely populated in reporting templates.
  • Data analyzed by a specialist/analyst.
  • Account Manager reviews and fully understands the analyzed information, key trends, and insights prior to the meeting.

➡️ The Account Manager must not initiate the meeting without reviewing the pre-meeting analysis and understanding the key findings.

GATE 1 - MEETING INITIATION & NO-SHOW PROTOCOL

• Owner: Account Manager (AM)
• Contributors: Client
• Entry Criteria / Required Inputs:
  • Gate 0 preparation complete.
  • Scheduled meeting time reached.
• Required Outputs:
  • Standard Flow: Meeting successfully initiated, rapport established, and floor explicitly given to the client for opening input.
  • No-Show / Reschedule Flow:
    • If the client is missing after 5–10 minutes (dependent on rapport), the AM must reach out via phone call, email, and text (via TextRequest).
    • If the client responds that they cannot make it, coordinate rescheduled times or provide the reschedule link.
    • If the client is a confirmed no-show (no immediate response to initial outreach), email them the reschedule link and initiate the content continuity proposal (see Iteration Rule).
    • Avoid: Allowing a client no-show or scheduling delay to stall the content roadmap execution without sending fallback selections and a proceed-by date X (Content Cycle Stall).

Iteration Rule (No-Show Content Protocol): To prevent delays in the content delivery cycle, the no-show follow-up email must:

1. Recommend our proposed content selections and options.
2. Inform the client they are free to provide details/feedback, or we will reach out for more if needed.
3. State that if they prefer us to proceed regardless (using our best judgment), we will look to proceed by a specific date X.
4. List alternative options if they prefer something else, and request they reschedule sooner rather than later to avoid delaying the content cycle.

➡️ If the client is present, proceed to Gate 2. If the client is a no-show, the no-show content protocol must be executed to keep the content delivery cycle moving.

GATE 2 - SEO PERFORMANCE & SERP ANALYSIS

• Owner: Account Manager (AM)
• Contributors: Client
• Entry Criteria / Required Inputs:
  • Whitespark dashboard and local ranking data Rank Report Benchmarking Procedure.
  • Competitor analysis tab.
  • Live Search Engine Results Pages (SERPs) for target keywords.
• Required Outputs & Process Flow:
  • Whitespark & KPI Review: Walk through the current key performance indicators and local ranking trends.
  • Ground-Truth Calibration: Reconcile our dashboard data with what the client is actually experiencing on the ground (call volume and lead quality).
  • Data Reconciliation Rules: Must be executed during ground-truth calibration:
    • Misconceptions: If positive data contradicts client concerns, use reporting to educate and correct misconceptions.
    • Remediation: If negative data matches client concerns, validate the issue, pivot the strategy, and log remediation tasks.
  • Competitive & Local Pack Review: Analyze local pack visibility and compare directly against competitors.
  • Live SERP Spot-Check: Click through to a live SERP to demonstrate real-time performance and establish that the report is a static snapshot.
  • Algorithm Education: Contextualize live SERPs by educating the client on current search environments (Core updates, organic/local pack diversity link, spam updates, and content quality).
  • Handling Poor Results:
    • Own the Data: Start with the bad news immediately, own it objectively, and explain why (e.g., algorithm updates, indexing delays, or a lack of supporting pages).
    • Do Not Linger: Deliver the bad news quickly, then transition directly to positive metrics to focus the discussion on them. Do not hover or analyze the poor data live; save any necessary recaps of both for the final summary at the end.
    • Do Not Dig Deeper: If a client pushes, briefly review the last report, but do not dig further. Do not analyze messy/negative reports or aimlessly search for positive stats in the moment (avoid Panic Digging). Firmly explain that we need to assess it further, as there could be plenty of reasons.
    • No Client Blaming: Objectively frame our client relationships as an active partnership where clients who engage most succeed most.

➡️ If negative trends are validated, the AM must create a remediation task in the task manager before moving to traffic review.

GATE 3 - TRAFFIC & ANALYTICS REVIEW

• Trigger: Client focus shifts from local rankings to overall website traffic, or as dictated by the agenda.
• Owner: Account Manager (AM)
• Contributors: Client
• Entry Criteria / Required Inputs:
  • Online Access Statistic Dashboard.
  • Year-over-Year (YoY) comparison data.
• Required Outputs:
  • Website visitor traffic reviewed.
  • Traffic metrics framed strictly under YoY comparison to avoid seasonal skewing.

Iteration Rule: If the client attempts to compare Month-over-Month (MoM) traffic, the AM must redirect the conversation to YoY metrics and explain the impact of seasonality.

➡️ Analytics review must rely on YoY standards; MoM traffic data must not be used to justify performance status.

GATE 4 - CONTENT ROADMAP & PRIORITIZATION

• Owner: Account Manager (AM)
• Contributors: Client, SEO (via output handoff)
• Entry Criteria / Required Inputs:
  • Client content database and current roadmap (refer to Content Roadmap Process).
  • Bottom-of-Funnel (BoFU) list (Service pages, City pages, Symptom/Modifier pages).
• Required Outputs:
  • Next content batch finalized, prioritizing Bottom-of-Funnel (BoFU) assets.
  • Voice extraction integrated into the content order, attempting to capture the contractor's input, voice, or stats for the content.

Iteration Rule: Foundational core pages (Home, About Us, Meet the Team) and BoFU pages must be completed and live before sequencing any Middle-of-Funnel (MoFU) or Top-of-Funnel (ToFU) assets (e.g., general blogs).

➡️ Captured brand phrasings and finalized content requirements must be packaged and assigned to the writing team (refer to Content Process for delivery).

GATE 5 - STRATEGIC CONSULTATION & UPSELL

• Owner: Account Manager (AM)
• Contributors: Client, Leadership (for resource gaps)
• Entry Criteria / Required Inputs:
  • Broader marketing strategy resources and local search AI advancement guidelines.
  • Centrally developed consulting deliverables (when available).
• Required Outputs:
  • Final sweep complete (aligning SEO with client's external marketing/internal initiatives).
  • Consultation delivered regarding broader growth, AI search trends, and upsell opportunities.

Iteration Rule: If the AM identifies gaps in consulting resources or needs specific collateral to support upsell discussions, a request must be sent to Leadership.

➡️ Meeting concluded, and post-meeting follow-up action items sent to the client within 24 hours.

POST-MEETING CHECKLIST

• Whitespark SEO Report: KPI review and local ranking trends completed and formatted (primary report).
• Analytics Report (Optional): Overall YoY traffic metrics report completed (if covered).
• Content Order: Upcoming content roadmap order submitted to the writing team, incorporating captured contractor input, voice, or stats for the content.
• Task Logs: Meeting action items and remediation tasks were recorded and added to the task manager.
• No-Show Proposal: Recommended content selections sent to the client with proceed-by date X (if the client was a no-show).
• Meeting Follow-Up: Follow-up email sent to client (addressing requested items or coordinating rescheduled times with a link if they missed the meeting).