SEO and content gap analysis

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

1. firm_indexed_content_inventory

   REQUIREDREADbatch

   The firm's published content as the search engines see it: titles, current ranks, traffic, conversion.

   DATA SHAPE

   Per-URL: title, target keywords, current ranks per keyword, traffic, dwell metrics, conversion rate.
   COMMONLY FILLED BY

   • site analytics with page-level metrics
   • search console data from major search engines
   • SEO platform with rank tracking
2. search_demand_signal

   REQUIREDREADbatch

   What people in the firm's market actually search for, at meaningful volumes.

   DATA SHAPE

   Per-keyword: monthly volume, intent classification, difficulty score, related queries.
   COMMONLY FILLED BY

   • SEO research platform (Ahrefs, SEMrush style)
   • search trend data from search engines
   • keyword research database maintained by the team
3. competitive_landscape_corpus

   RECOMMENDEDREADbatch

   What competitors and adjacent content publishers are doing in the firm's topical space.

   DATA SHAPE

   Per-competitor: published content, ranks they hold, recent publications, topical strengths and weaknesses.
   IF MISSING

   Pattern works without competitive data but misses 'they're moving on X, we should respond' opportunities. Recommend for any competitive market.
   COMMONLY FILLED BY

   • competitive intelligence in the SEO platform
   • monitored competitor sites with change detection
   • structured competitor list maintained by marketing
4. commercial_priority_signal

   REQUIREDREADbatch

   Which topics actually drive qualified pipeline for the firm, not just traffic. The single thing that separates useful SEO analysis from vanity-metric SEO analysis.

   DATA SHAPE

   Per-topic: leads generated, pipeline value attributed, customer acquisition cost ratios.
   COMMONLY FILLED BY

   • attribution data linking content to pipeline in the CRM
   • structured topic-to-pipeline mapping maintained by RevOps
   • marketing attribution platform
5. recommendation_destination

   REQUIREDWRITEbatch

   Where the prioritized recommendations land for the content and SEO team.

   DATA SHAPE

   Per-recommendation: action type (write/update/retire/consolidate), target topic, estimated value, supporting evidence, suggested approach.
   COMMONLY FILLED BY

   • dashboard with sortable recommendations
   • monthly report to the content team
   • structured backlog feeding into G28 brief creation
6. outcome_tracking_loop

   RECOMMENDEDREADbatch

   How recommendations get acted on and what results they produce. Used to tune which signals predict actual value.

   DATA SHAPE

   Per-recommendation: was it acted on, what was done, downstream rank and traffic changes, pipeline attribution.
   IF MISSING

   Pattern keeps producing recommendations but can't learn which kinds actually pay back. Recommend at minimum quarterly closure of the loop.
   COMMONLY FILLED BY

   • status tracking on each recommendation
   • quarterly review with the content team
   • outcome data fed back from analytics