Research · Published:
Research: Measuring Sitemap and Release Manifest Agreement
A route-level comparison tests whether the public sitemap contains every intended article once and under the right family.
Headline signal: Four identity fields compared for every released route (OutsourcedAssistants.com study protocol).
Research question and scope: How often does a dated release manifest agree with the sitemap served after deployment? The unit of analysis is one manifest route paired with its canonical sitemap entry. This protocol concerns a local daily article workflow. It does not evaluate a worker's general ability or claim a result for all publishers.
Methodology: Compare host, family, slug, and occurrence count after the deployment reaches terminal success. Record missing, duplicate, stale, and wrong-family entries separately, then confirm the article response before classifying impact. Declare the route sample, observation window, reviewer, exclusions, and pass rule before collecting results. Retain the original records so a later reviewer can distinguish planned measures from explanations added afterward.
Classify evidence as a public source fact, local observation, calculation, interpretation, example, or recommendation. Link material factual claims to the precise source section and record the access date. A source supports what it says, not every operational conclusion a team might draw from it.
Record ordinary items, returned items, exceptions, owner overrides, and unresolved cases separately. Include review time beside production time. A fast output that requires extensive source reconstruction has shifted work to the editor.
Inference limits: Agreement shows consistency between two observed artifacts at one time. It does not prove search-engine discovery, indexing, ranking, or future availability. The result applies only to the stated sample, workflow, sources, and observation period. It cannot establish causation without a design that addresses plausible competing explanations.
Limitations: Caching, overlapping deployments, redirects, sitemap partitioning, and an incomplete manifest can distort the comparison. Source pages may change after observation. Reviewer judgment, cache state, rare cases, workload mix, and missing records can alter the measured result. Disclose deviations and unresolved questions rather than filling gaps with estimates.
Use the findings for a bounded decision: keep the routine, revise one instruction, narrow access, add reviewer coverage, or pause the lane. Publishing, policy, privacy, payment, legal interpretation, and unusual commitments remain with the accountable owner.
Sources
- Google Search Central: Creating helpful, reliable, people-first content
- W3C Web Content Accessibility Guidelines 2.2
- NIST Privacy Framework
- CISA: Secure Our World
Frequently asked questions
Does this protocol prove that outsourced assistants improve publishing performance?
No. It examines one declared workflow and supports only conclusions bounded by its sample, measures, and limitations.
What records should the team retain?
Keep the preregistered question, sample definition, source notes, timestamps, outcomes, reviewer decisions, exclusions, and final interpretation.