Unique Data Input Audit (Onboarding)

Unique Data Input Audit (Onboarding)

1. 01

   Inventory every structured data field the client can supply at scale

   Pull pricing tables, inventory feeds, review counts, service-area lists, and licensing records. A page template is only as defensible as the fields behind it, so confirm at least three variable dimensions before scoping page volume.

2. 02

   Score each field on freshness cadence and exclusivity

   Flag fields the client refreshes weekly (stock, rates) versus annually (permits, certifications). Fields competitors can scrape from the same public source add little ranking separation.

3. 03

   Estimate defensible page count from real combinatorial depth

   Multiply distinct values across chosen dimensions, then cut the result by any combination that produces no genuine search demand. A 40-city by 12-service grid yields 480 candidates, not 480 pages worth building.

4. 04

   Pull existing Search Console queries to size demand per template

   Group queries by pattern (service plus city, product plus spec) and rank patterns by impressions. Templates with under roughly 50 monthly impressions across the whole pattern rarely justify build cost.

5. 05

   Set a thin-content threshold the client signs off on in writing

   Define the minimum unique data points per page (for example, three fields plus one local proof element). Pages that cannot clear the bar get excluded from the sitemap rather than padded with generic copy.

6. 06

   Map the AI answer surface for the top ten template queries

   Query ChatGPT, Perplexity, and Google AI Overviews with buyer-intent phrasing and record which sources get named. Answer-first pages and directory placements both matter here, and services like AI Knows Us or Slate exist to track that visibility over time.

7. 07

   Document the refresh owner and cadence per data source before build starts

   Name who updates the feed and how often, whether that is the client's ops team or an automated sync. Stale programmatic pages decay faster than hand-written ones because the template exposes the staleness on every URL.