Unique Data Input Audit (Onboarding)

Unique Data Input Audit (Onboarding)

1. 01

   Inventory the client's proprietary data assets before any template is designed

   List pricing tables, live inventory counts, review corpora, license records, and location hours. Pages built on data the client already owns survive duplicate-content scrutiny; pages built on paraphrased competitor copy do not.

2. 02

   Count how many distinct page permutations the data can honestly support

   A 40-city service footprint with 6 services yields 240 defensible pages. If the arithmetic lands under 50, the engagement is a content project, not a programmatic one, and should be scoped and priced that way.

3. 03

   Score each data field for refresh frequency and volatility

   Pricing and inventory change weekly and justify automated regeneration. Static company history does not. Volatile fields are what keep generated pages from going stale across a 12-month retainer.

4. 04

   Confirm the client can supply structured exports, not PDFs or screenshots

   Ask for CSV, API, or database read access on day one. Agencies that accept a spreadsheet emailed monthly end up rebuilding the pipeline by month three.

5. 05

   Map every page template to a single search intent and a single query pattern

   One template per intent family, such as service-plus-city or product-plus-compatibility. Mixing intents inside one template produces pages that answer nothing well.

6. 06

   Run a thin-content risk review against the client's existing indexed URLs

   Flag any new template that would compete with pages already ranking. Cannibalization shows up as flat aggregate traffic even when page count triples.

7. 07

   Document the data-to-page lineage in a shared schema file the client signs off on

   Field name, source system, refresh cadence, and owning template. This file becomes the scope boundary when the client requests new page types mid-retainer.