Sample Pack

See the decision, not only the score.

The sample opens with the deliverable anatomy: what the implementer sees, what the reviewer changed, and why a candidate can be rejected.

Deliverable anatomy first

One route contains several implementation decisions.

The workbook is not a list of keyword matches. It is a route schedule with enough context to act and enough review evidence to challenge.

Exact source and destination
Final anchor wording
Placement inside the visible source context
Priority and review state
Reason, implementation note, or rejection reason

Download synthetic sample CSV ↓

REC-014 / approved routeImplementation pack · synthetic

Field

Reviewed value

Why it exists

Source

/guides/content-audit-process/

Locates the edit

Target

/services/seo-content-strategy/

Confirms destination

Anchor

SEO content strategy

Approved language

Placement

After audit priorities paragraph

Preserves context

Inspection note: use one contextual sentence; do not add the route to a generic sidebar or footer.

Reviewed valueImplementation note

Quality signalThe rejected recommendation is evidence of review, not evidence of failure.

Route 01

Approved as written.

The source context and target purpose align, and the final anchor fits the sentence without overstating the destination.

APP-001

Implementation record

Approved

Source page/guides/content-audit-process/

Target page/services/seo-content-strategy/

Final anchorSEO content strategy

PriorityHigh

PlacementAfter the paragraph explaining how audit findings become editorial priorities.

ReasonThe source explains the diagnostic process. The target provides the service that acts on those findings.

Implementation noteUse one contextual sentence. Do not add the link to a sidebar or footer.

Route 02

Useful relationship, edited instruction.

The review keeps the route but changes the anchor to sound natural in the source context.

EDT-001

Implementation record

Approved after edit

Source page/blog/b2b-content-calendar/

Target page/services/content-marketing/

Final anchorcontent marketing workflow

PriorityHigh

PlacementIn the section about turning topics into production briefs.

ReasonThe source discusses editorial planning and the reviewed anchor fits the source context.

Implementation noteOriginal anchor was too commercial. Implement only the edited wording.

Route 03

Rejected after inspection.

A shared marketing theme did not create a useful next step for the reader.

REJ-001

Implementation record

Rejected

Source page/blog/marketing-automation-tools/

Target page/services/seo-content-strategy/

Final anchorSEO content strategy

PriorityCandidate

PlacementNear the conclusion.

ReasonSuperficially related marketing topic.

Implementation noteDo not implement.

Rejection reasonTopic relationship too weak in the visible source context.

Column logic

The columns form an operating system for implementation.

Each field exists because someone downstream will otherwise have to reconstruct the decision.

WHERE

Source, target, placement

Locate the edit and preserve the intended context.

WHAT

Final anchor and note

Specify the language and any constraints.

WHY

Reason and priority

Explain the reader and site-structure logic.

DECIDE

Review state

Keep approval, edits, rejection, and uncertainty visible.

Honest sample boundary

This sample proves the format, not SEO outcomes.

The examples are synthetic. They do not claim customer results, reviewer identity, rankings, traffic improvements, or implementation success.

A production pack depends on the agreed crawl, visible page context, business priorities, reviewer judgement, and the limitations recorded in the final handoff.

Approved next route

Check availability only after inspecting the evidence.

If private-beta requests are open, a written scope must still confirm the site, inputs, exclusions, deliverables, timing, price, review process, and terms before work begins.

Check fit-review availability Inspect the Sample Pack