SEO Champion Coverage

accepted domains and sites

manual and automatic priority signals

site manifests and proposal review

standards summary surface

imported SEO evidence summaries

imported source freshness

imported traffic metrics from GSC, Bing, and GA4

imported Moveroo quote and booking metrics

imported sitewide monitoring summaries

imported URL discovery summaries

action queue generated from accepted truth and imported evidence

agent capability directory and bounded agent APIs

Source refresh orchestration

Rebuild as Laravel workers and scheduled jobs

Source health and refresh failures

Import current source state, rebuild failure diagnosis

Technical SEO checks

Rebuild modular check runner and preserve latest detailed evidence

Site Standards Runs

Rebuild run creation, processing, proof bundle, and run detail

Website Standard sign-off

Rebuild as Bossman Standards module with versioned rules and daily checks

Fleet Guardrails evidence join

Import or reference rules, rebuild evidence mapping in Standards module

Agentic readiness checks

Rebuild as modular evidence family

Google Issue lifecycle

Import open/recent cases, rebuild case/evidence/action workflow

Opportunities and decisions

Preserve decisions and rebuild opportunity case files

Query Ownership Bundles

Preserve latest useful bundles, rebuild as growth/ownership module

Annotations and learning notes

Import material annotations and active learning notes

Agent capability manifest

Migrate useful capability knowledge into Bossman directory

Priority actions

Continue rebuilding from Bossman accepted read models

Proof bundle workflow

Rebuild proof bundle generation for runs and imports

Domain and source registry

Bossman should remain accepted truth. Champion source rows are evidence.

GSC, GA4, and Bing traffic summaries

Bossman has per-site metrics for priority. It does not yet expose query/page drill-downs.

Source refresh orchestration

Current Bossman has a protected source-freshness bridge, but direct GSC, GA4, and Bing refresh clients are not native yet.

Source health and refresh failures

Freshness evidence exists. The richer failure/retry workflow is still Champion-owned.

Technical SEO checks

Bossman has native site-foundation checks and imported Champion summaries; broader families still need rebuild.

Site Standards Runs

Bossman exposes imported standards-run proof bundles, but cannot yet create/process native standards runs.

Visual QA requests

Keep parent-first flow from standards run to bounded repo QA request.

Website Standard sign-off

Bossman has a standards surface, but not the full Level 1/Level 2 evidence contract.

Fleet Guardrails evidence join

Bossman should become the durable human/API surface for standards.

Repo Standard evidence

Current Bossman knows manifests; Champion has richer repo-standard checks.

Fleet migration artifact scan

Useful for WordPress residue, empty images, spacing, shortcodes, and migration debris.

Image quality checks

Keep current evidence, but brand/image issues are intentionally deferred until site brand passes.

Language/readability/copy evidence

Useful for site cleanup, but should be sampled and bounded.

Agentic readiness checks

Includes llms.txt, OKF, ARD, source-visible forms, navigation, accessibility, and layout signals.

URL discovery ledger

Bossman sees counts and examples, not the full decision ledger.

URL Work Queue

Champion has lease/run history and approved-check/fetch/promote/discovery steps.

Google Issue lifecycle

Bossman exposes imported Google Issue case summaries, but native cases, events, actions, and URL inspection are still pending.

Google URL Inspection queue

Do not auto-inspect all URLs. Keep high-value, reasoned, approved queue semantics.

Google property health

Useful for sitemap/property warnings without treating emails as truth.

Opportunities and decisions

Major lost functionality risk. Candidate cache alone is not enough; decisions and monitoring records matter.

Opportunity monitoring

Needed to know whether past changes need 14/30 day review.

Domain Growth Analysis

Keep run/items history if useful, but it should not block first migration.

Query Ownership Bundles

Important for avoiding cross-site cannibalisation and wrong-page edits.

Query/page maps

Useful for agent and human page decisions, but high-volume data should not power request-time pages directly.

Tracked search phrases and SERP logs

Useful shared SERP evidence, but needs bounded refresh workers.

Route internal linking plans

Tables exist but old plan count was low. Keep model, do not prioritise before ownership.

Index inventory

Important for orphan/operational/noise URL separation.

Page launch and change monitoring

Preserves why movement is expected and when to review.

Sitewide monitoring

Bossman currently imports monitor/snapshot summaries.

Bing technical evidence

Bossman should expose bounded examples before creating repo work.

Bing AI visibility

Useful agent/search visibility signal.

IndexNow readiness/proof

Bossman should not submit automatically without an approved runner.

On-page SEO and copy decisions

Useful to avoid rediscovering known content issues.

Annotations and learning notes

These explain past changes and prevent bad interpretation of traffic movement.

Agent requests

Old requests can be archived unless still open. Capability knowledge matters more than old token rows.

Agent capability manifest

Bossman must be the new first-call API for agents.

Priority actions

Bossman has an action queue, but not every Champion lane contributes yet.

Proof bundle workflow

Proof bundles are the difference between "check said so" and usable evidence.

Auth/tokens

Old Champion tokens should not be treated as Bossman credentials.

Raw high-volume metric history

GSC/Bing/GA4 raw rows are useful, but dangerous as request-time tables.

ability to run fresh technical SEO checks from the SEO system

ability to create and process Site Standards Runs

full standards-run proof bundles and run detail pages

opportunity case files, decisions, and monitoring follow-ups

query ownership proof bundles and cannibalisation guardrails

Google Issue lifecycle detail, including evidence/events/actions

URL Inspection queue semantics and quota-safe processing

URL Discovery decision ledger and URL Work Queue processing

tracked search phrase and SERP reuse workflow

route internal-linking planning workflow

annotations and learning notes that explain prior changes

agent capability knowledge that has not yet been copied into Bossman

1. A native SEO Evidence module with detailed evidence pages and bounded agent APIs.

2. A native Standards Run workflow with queued processing and proof bundles.

3. A native Technical SEO check runner by check family.

4. A native Source Refresh worker for GSC, GA4, and Bing.

5. A Google Issues module that preserves cases, evidence, events, actions, and URL inspection queue behaviour.

6. An Opportunities module that preserves current decisions and monitoring.

7. A Query Ownership module or archived, searchable ownership evidence.

8. A URL Discovery and URL Work Queue module, or a deliberate decision to pause that workflow.

9. A migrated Agent Capability Directory that fully replaces the Champion first-call manifest.

10. A read-only Champion archive/export with verified counts for data not imported into current Bossman tables.

site evidence detail pages

evidence snapshot detail payloads

run and proof links where available

source freshness and action context

bounded agent endpoint for one site