seo-platform-detect

The profile decides three things no module can decide on its own: which platform-conditional check ids fire, which findings are not_applicable because the platform owns the thing, and which fix adapter fix will reach for. Run it once per audit, right after the snapshot, before dispatch.

Detection is orthogonal to the vertical: seo-vertical-detect answers what kind of site is this, this skill answers what is it built on. Both feed one profile.json.

When to run

In the normal /audit and /geo flow you do not run this yourself: audit.mjs already calls the same detect() over the run's homepage snapshot and persists the result as <run_dir>/profile.json. Read that file first. Run the script directly only when you need a signal the headless pass could not use — --path <project> for repo/package signals, --probe for the WordPress plugin verdict — or when you are working outside the runner. Either way it is one run per audit, before the dispatch envelopes are built; every subagent reads the same profile.

How to run