Small-business outsourcing research

Research: Metadata and Route Identity Concordance

A full-manifest audit of titles, canonicals, dates, body hashes, indexes, and sitemap membership.

Research: Metadata and Route Identity Concordance evidence workspace

Headline finding. A 200 response is insufficient; route integrity requires agreement across content, canonical, structured date, visible date, index, sitemap, and body identity.

Research question. Does every new article maintain one unique, self-consistent identity from source data through built HTML? The unit of analysis is one canonical route in the September 2 release manifest. The study evaluates an observable publishing control, not whether outsourcing alone causes an outcome.

Methodology. Build every declared route, capture rendered identity fields and normalized body hashes, test pairwise uniqueness, and reconcile Blog and Research counts separately. Freeze the cohort rule before collection and retain timestamps, evidence links, exceptions, reviewer dispositions, and process changes.

Measures. Report eligible units, sampled units, complete records, defect counts by severity, held items, owner-review minutes, and reconstruction minutes. Preserve numerators and denominators for every rate.

Comparison design. Compare like periods or matched work types and annotate changes in topic difficulty, staffing, tools, standards, and release volume. Include an ordinary case and a deliberately incomplete case.

Limitations. Local build behavior may differ from production, and extraction choices influence hashes even when readers see distinct pages. Records may omit informal decisions, reviewers may classify the same defect differently, and an observational result cannot prove revenue, ranking, compliance, or universal performance.

Decision use. Treat the result as evidence for one bounded process adjustment. Keep editorial judgment, risk acceptance, publication approval, and any expansion decision with the business owner.