Quick snapshot, in plain terms

• Give a short snapshot of the immediate issue that brought your team to explore an SEO and content platform now.
• How large was the recent organic traffic change for your primary domain, by percentage range? Options: Loss > 50%, Loss 20–50%, Loss 5–20%, Flat (+/−5%), Growth > 5%
• On which keyword clusters or content verticals did you see the biggest declines or competitor gains?
• Which members of your team feel the impact day to day (roles)? Options: Head of Content, SEO Director, Content Operations Manager, Technical SEO Lead, Product/Engineering
• Tell me about the last time your team tried to recover traffic, what steps were taken and what outcome followed.

When the numbers land on the scoreboard

• If leadership asked you to show a fix within one quarter, what would you prioritize and why?
• Name the top two metrics your leadership expects to move to consider the effort successful. Options: Organic sessions, Conversion rate from organic, SQLs from organic, Revenue attributed to organic, Keyword ranking for target commercial terms
• How is organic traffic currently attributed to pipeline in your reporting? Options: Direct last click, First touch + multi-touch model, Multi-touch with rules, No clear attribution, manual mapping, Other
• List the analytics and attribution systems that feed your quarterly pipeline numbers.
• Which single KPI, if unchanged by the end of the pilot, would cause leadership to cancel the project?

Where the work repeatedly stalls

• What's the recurring technical or editorial failure that erodes improvements week after week?
• How often do indexing, sitemap, or canonical issues appear on your site health reports? Options: Weekly, Monthly, Quarterly, Rarely, Unknown
• Who currently owns technical SEO fixes and how many open items are in their backlog?
• Describe the review and approval path a content change follows from draft to live.
• If a CMS or platform restriction blocked half of recommended fixes, would you pause, accept a reduced scope, or allocate engineering resources immediately? Options: Pause until fixed, Proceed with reduced scope, Allocate engineering time immediately, Reprioritize recommendations

The other options on your table

• Who else is on the shortlist and what feature or proof point drew your team to them?
• Which of the following options are you actively evaluating? Options: Existing incumbent vendor, New platform vendor, Large agency/consultancy, Build internal capability, No decision yet
• Name the conditions that would need to hold true for you to keep your current approach rather than contract an outside vendor.
• Has anyone inside proposed solving the core issues without an external vendor, and what scope and timeline did they suggest?
• What single weakness in the incumbent or internal approach would be fatal to your business if left unaddressed?

Who signs, who stalls, and the approval dynamics

• Identify the person or role most likely to raise objections and explain the reason they would.
• List the stakeholders who must be involved in acceptance criteria, technical approvals, and budget signoff. Options: CMO/Head of Marketing, VP Content/SEO Director, Head of Revenue Ops, CFO/Finance, Legal/Compliance, Engineering Lead, Product
• When an SEO change risks editorial voice or conversion, who typically mediates the tradeoff? Options: Head of Content, Product/UX, Conversion Optimization Team, SEO Director, Other
• Estimate the internal approval timeline from pilot success to purchase decision, in business days. Options: <15 days, 15–30 days, 31–60 days, 61–90 days, >90 days
• Assuming the pilot meets its target uplift, who has authority to sign the contract and what is a realistic approval window in business days?

Can we actually get access and integrate

• Identify any single credential, integration, or legal approval that would stop work on day one.
• Do you have CMS admin access you can grant for a time-boxed audit? Options: Yes, admin access available, Yes, read-only access only, No, requires engineering request, No, cannot grant
• Provide the names of the analytics properties or reporting views that hold canonical traffic and conversion data.
• Is there a dedicated engineering resource who will be assigned to integrations, and can they commit weekly hours? Options: Yes, full time for the pilot, Yes, part time (estimated hours), No dedicated resource but can source as needed, No resource available
• Are there regulatory, legal, or vendor restrictions that require review before we begin? Options: Yes, legal review required, Yes, vendor contracts required, No known restrictions, Unsure
• Should CMS and analytics access not be available within 4 weeks, would you prefer to delay the pilot or proceed with a reduced scope? Options: Delay the pilot, Proceed with reduced scope, Run alternate manual assessment, Undecided

What a successful trial must prove

• Describe the specific audit findings that would convince leadership to proceed immediately.
• Select the primary sample size for the pilot audit from your top keyword clusters. Options: Top 50 keywords, Top 100 keywords, Top 250 keywords, Top 500 keywords
• How many keyword clusters should we include to feel representative for your product or vertical? Options: 5–10 clusters, 11–25 clusters, 26–50 clusters, 50+ clusters
• Which of the following success criteria should be included in the audit report? Options: Confirmed content gaps with prioritization, Sample integration proof of concept, Ranking opportunity validation, Pipeline attribution test, Technical indexability report
• Assuming the audit confirms content gaps and feasible integrations across your top clusters, what internal step would accelerate procurement to a 30 day decision? Options: Pre-approved budget, Executive sponsor introduction, Signed letter of intent, Fast-track procurement review, Other

Budget, timeline, and the deal threshold

• Enter the timeframe your leadership believes counts as measurable organic improvement, in months. Options: <3 months, 3–6 months, 6–12 months, >12 months
• Select the budget range you have modeled for a phased engagement. Options: <$50k, $50k–$100k, $100k–$250k, $250k–$500k, >$500k
• Provide the specific success metrics you expect in contract acceptance criteria.
• Suppose the program misses contract success metrics at six months, what remediation path would your leadership expect? Options: Extended optimization period, Price adjustment or credit, Project termination, Change of scope
• Choose the internal teams that must approve the budget. Options: Marketing leadership, Revenue/RevOps, Finance/CFO, Legal, Engineering

Readiness checklist and the immediate next step

• What single practical commitment would demonstrate you're ready to run a meaningful pilot in the next 30 days?
• Confirm whether you can provide CMS admin user, analytics read access, and a list of top keyword clusters within 4 weeks. Options: All three available within 4 weeks, Some available, some delayed, No, cannot provide within 4 weeks, Unsure
• Choose the preferred next step to keep momentum: schedule a kickoff, run a scoped audit, or prepare a commercial draft. Options: Schedule kickoff, Run scoped pilot audit, Prepare commercial proposal, Hold internal discussion
• Provide your preferred kickoff window in business days from completion of readiness items. Options: <7 days, 7–14 days, 15–30 days, >30 days

• Solution Experience Session

• Confirm the current state and its cost to your team
• You confirm the opportunity analysis prioritizes topics that would recover lost traffic and improve qualified pipeline.
• Run a time-boxed trial audit across the buyer's top 3 keyword clusters and deliver a prioritized opportunity brief with estimated traffic and pipeline impact.
• You confirm the demonstrated editorial workflow addresses creator friction and approval bottlenecks you described.
• Prove prioritized opportunity analysis using your keyword clusters
• Provide the list of top 3-5 keyword clusters, current editorial workflow steps and approval owners, and sample conversion metrics for pipeline mapping.
• Map opportunity into an editorial workflow tailored to your context
• Provide CMS access level information and analytics reporting sample or credentials required to validate integration feasibility.
• You confirm the technical remediation plan addresses indexing and crawl blockers and is feasible given your CMS and analytics constraints.
• Demonstrate the technical remediation plan and integration feasibility
• You agree on a time-boxed trial audit scope, measurable success criteria, and the seller deliverable to validate outcomes.
• Prepare a sample content brief and a mapped CMS editorial task to review during the trial audit.
• Show pipeline attribution using a buyer example
• Validate this maps to what you described needing
• Agree next evidence actions and success criteria

• Solution Experience Session
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Import and Normalize Content Inventory
• Configure CMS Inline Optimization Interface
• Generate SEO Content Briefs for Priority Topics
• Implement On-Page SEO Updates (titles, metas, headings)
• Execute Internal Linking and Topic Cluster Mapping
• Deploy Structured Data and Schema Markup
• Execute URL Redirects and Canonical Mapping
• Resolve Indexation and Crawlability Issues
• Optimize Site Speed and Core Web Vitals
• Configure Rank Tracking Across Keyword Clusters
• Set Up Editorial Calendar and Workflow Automation
• Integrate Analytics to Source CRM for Pipeline Attribution
• Monitor Rankings and Alert on Algorithmic Drops

Import and Normalize Content Inventory

• Upload an export of your content inventory (CSV or Google Sheet) that includes URL, page title, publish date, content type and CMS ID
• Indicate the source of the export Options: CMS export (name your CMS), Crawl CSV (Screaming Frog/other), Manual spreadsheet, Other
• Enter the approximate unique content URL count in the export Options: Less than 500, 500-2,000, 2,000-10,000, More than 10,000
• Name the CMS account or user who can provide sample page access for mapping and verification
• List any URL patterns or path segments that should be excluded from normalization (example: /private/, /staging/, /archive/)
• Specify the acceptance criterion for inventory import success (for example: >=95% of URLs matched to CMS IDs and required fields populated) Options: Use example acceptance (>=95% match), Define custom acceptance threshold

Configure CMS Inline Optimization Interface

• Select the CMS editor surfaces where inline optimization hints should appear Options: Block editor/editorial composer, Headless CMS preview pane, WYSIWYG editor, Other
• Upload documentation for available integration methods with your CMS (API key docs, OAuth app flow, SSO config)
• Enter the CMS field names that must be preserved during inline edits (meta title field name, meta description field name, canonical field name)
• Identify the user roles who should see optimization hints in the editor Options: Content author, Editor, SEO reviewer, Content operations
• Indicate required inline workflow actions (suggest only, suggest + auto-apply, submit-for-review) and any approval SLA Options: Suggest only, Suggest + auto-apply, Submit-for-review
• Provide a staging URL where the integration can be tested and a contact who can enable access

Generate SEO Content Briefs for Priority Topics

• Select the source to define priority topics for brief generation Options: Trial audit top clusters, Existing product pages, Content gap list from competitor analysis, Custom topic list
• Attach examples of three competitor pages per target topic to guide brief tone and scope
• Estimate the number of briefs to generate in the initial phase Options: 10, 25, 50, Custom (specify)
• Name the approver for content briefs and state the expected review SLA (role and hours/days)
• List mandatory brief sections you require (target keywords, suggested headings, internal links, evidence links, metadata suggestions)
• Provide any editorial style constraints the briefs must enforce (tone, max word count, technical depth)

Implement On-Page SEO Updates (titles, metas, headings)

• Identify the page templates targeted for on-page updates (product detail, blog post, landing page, category)
• Estimate the page volume planned for phase 1 updates Options: Less than 500, 500-2,000, More than 2,000
• Attach an example of your title/meta naming convention or provide guidance we must follow
• Assign the owner responsible for bulk updates versus inline edits Options: Content operations, Authors, External agency, Technical SEO team
• Specify acceptance evidence for on-page update completion (for example: sample URLs with updated title/meta + crawl report confirming changes) Options: Provide sample URLs + crawl report, Define alternate acceptance evidence
• List any pages where legacy titles or metadata must be preserved for regulatory or legal reasons

Execute Internal Linking and Topic Cluster Mapping

• Submit the list of seed pillar pages (one URL per pillar) for each priority cluster
• Document internal linking rules to follow (nofollow exceptions, max link depth, cross-domain linking allowances)
• Approximate the number of internal link edits per pillar page required in phase 1 Options: 0-5, 6-15, 16+
• Specify the analytics event or landing page path we should use to measure cluster-driven CTR lift
• Identify the person who will approve the topic cluster maps and canonical linking strategy
• List any internal navigation components that must remain unchanged (main nav links, footer link rules) during linking updates

Deploy Structured Data and Schema Markup

• List the page types that require schema markup (article, product, FAQ, breadcrumb, event) Options: Article, Product, FAQ, Breadcrumb, Event, Other
• Provide URLs of existing pages that already include structured data for review
• Indicate the preferred schema format for deployment (JSON-LD, microdata) Options: JSON-LD, Microdata, No preference
• Assign the owner for schema field content (author, product manager, content ops) Options: Author, Product manager, Content operations, Other
• Specify acceptance criteria that will validate schema deployment (for example: zero structured data errors in Search Console and increased eligible rich results) Options: Use example acceptance (no SC errors), Define custom acceptance
• List any third-party widgets or review platforms that provide schema data and must be integrated or excluded

Execute URL Redirects and Canonical Mapping

• Upload the redirect map or legacy-to-current URL list planned for phase 1
• State your redirect status code policy for different URL classes (301 permanent, 302 temporary, other) Options: 301 permanent, 302 temporary, Mixed policy (describe)
• Approximate redirect volume for phase 1 Options: Less than 100, 100-1,000, More than 1,000
• Identify who will implement redirects in the hosting environment (infrastructure team, CDN configuration, external agency) Options: Infrastructure team, CDN, External agency, We need assistance
• List any legacy paths that must remain active for tracking, legal compliance, or partner integrations
• Provide rollback criteria or a contingency plan for redirects if errors are detected after deployment

Resolve Indexation and Crawlability Issues

• Enter your primary sitemap.xml URL and indicate the date it was last regenerated
• List site sections intentionally blocked from crawling (example paths like /private/, /staging/)
• Specify the Search Console properties and index coverage reports we should review
• Describe how parameterized URLs or session IDs are currently handled to avoid duplicate indexation
• Name the contact who can grant temporary access to server logs or authorize a bot-level crawl for diagnosing crawl budget constraints
• List any historical indexation issues (mass noindex, blocked by robots, accidental canonicalization) that require special handling

Optimize Site Speed and Core Web Vitals

• Paste current lab or field metrics for Core Web Vitals: LCP, FID or INP, CLS (from PageSpeed Insights or lab tests)
• Indicate which hosting, CDN, and image delivery configurations are adjustable during the engagement
• Indicate whether a build pipeline exists where automated Lighthouse or Core Web Vitals checks can be added Options: Yes - CI pipeline available, No - pipeline not available, Partial - manual builds only
• Identify the approver for changes that remove or modify third-party scripts which may affect analytics
• Enter the acceptable Core Web Vitals target thresholds for production (example: LCP <2.5s, CLS <0.1, INP <200ms)
• List any legacy performance constraints we must avoid touching (custom ad renderers, partner scripts, required tracking pixels)

Configure Rank Tracking Across Keyword Clusters

• Upload or select the keyword clusters to track (CSV with cluster labels or select trial-audit clusters)
• Select the search engines and geographic markets to include in tracking Options: Google (country), Bing (country), Other search engines
• Choose rank check cadence Options: Daily, Weekly, Bi-weekly
• Require mobile-first ranking tracking and device segmentation for cluster reports Options: Yes, No
• Name the contact who will supply seed competitors per cluster for comparative tracking
• List any SERP features to monitor per cluster (featured snippet, knowledge panel, local pack, product listing) Options: Featured snippet, Knowledge panel, Local pack, Product listing, Other

• decision_readiness
• current_state
• gaps
• stakeholders
• desired_state
• success_criteria
• desired_state
• success_criteria
• stakeholders
• gaps
• current_state
• decision_readiness
• stakeholders
• decision_readiness
• current_state
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Subscription Agreement
• Order Form
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Acceptance Criteria & Evaluation Sign-Off
• Service Level Agreement (SLA)
• Data Processing Agreement (DPA)
• Change Order Agreement
• Payment and Invoicing Schedule
• Termination and Transition Plan

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate Decision (around day 90)
• Ongoing Quarterly Success Review

• Update the monitoring dashboard to include the agreed verification checks for the next review.
• Create an editorial workback for the top 5 pages or clusters identified for optimization.
• Schedule follow-up verification checks for each remediation item before the acceptance meeting.
• Restate acceptance criteria and numeric targets
• Record a documented pass or fail for each acceptance criterion listed in Solution Scope with a named signatory where required.
• For any failed criteria, establish a remediation plan with timelines and verification steps.
• Confirm how the acceptance decision will be archived and where stakeholders can find the evidence supporting it.
• Publish the acceptance decision document with criterion-level pass/fail status and the named signatory.
• If applicable, issue the remediation task list with dates and verification tests to change a failed criterion to pass.
• Prepare the post-acceptance monitoring dashboard with links to the metric sources for ongoing review.
• KPI trend review
• Confirm the KPI trajectory for median ranking position and quarterly organic sessions relative to Solution Scope targets and identify any required course corrections.
• Agree the prioritized enhancement and remediation backlog for the coming quarter with clear verification criteria.
• Ensure no critical blockers remain unassigned or without a firm resolution date.
• Publish the prioritized quarterly backlog with acceptance criteria for each enhancement.
• Schedule technical sprints to resolve any high-impact blockers identified in the meeting.
• Re-confirm success criteria and owners
• Confirm all integrations required to start measurement are functioning or have identified remediation plans with dates.
• Verify at least the minimum set of users are onboarded and have performed core tasks in the platform.
• Run a live crawl and tracking verification report for the key site areas and share results.
• Publish an access and onboarding summary showing users provisioned and initial activity counts.
• Log and assign resolution dates for any critical blockers preventing measurement.
• Present first-cycle KPI data
• Establish whether median ranking position for priority keyword clusters and organic sessions from those clusters are on track to meet Solution Scope targets.
• Produce a prioritized remediation plan with target dates that addresses the top 3 causes of any gaps.
• Confirm all materials needed for the acceptance gate are ready and accessible.
• Deliver a diagnostic report tying ranking changes to technical crawl findings and content edits.
• Deployment and integration verification
• Pipeline attribution check
• Present outcome data per criterion
• Compare results to Solution Scope targets
• Early adoption and access review
• Document pass or fail per criterion
• Open issues and blocker burn-down
• Root cause diagnosis for gaps
• Enhancement request prioritization
• Initial technical and editorial blockers
• Agree corrective actions and timeline
• Agree remediation plan for failed criteria
• Agree immediate remediation actions
• Quarter plan and verification criteria
• Confirm readiness checklist for acceptance gate
• Circulate acceptance record and next steps