seo-vertical-detect
Skill81 starsChanged 2 months agoMITView on GitHub
Classify a website as ecommerce, local-business, blog-publisher, saas, docs, or generic (multiple may apply), and report detected locales, from the persisted PageSnapshot plus the platform detector's vertical hints. Used by seo-orchestrator to decide which conditional modules to run and how to reweight the scores.
In this repository33 other files it gives its agents.
- auditSkill
- compareSkill
- fixSkill
- geoSkill
- scoreSkill
- seo-agent-readinessSkill
- seo-ai-crawlersSkill
- seo-ai-discoverySkill
- seo-core-web-vitalsSkill
- seo-crawlabilitySkill
- seo-crawl-renderSkill
- seo-ecommerceSkill
- seo-eeatSkill
- seo-entity-linkingSkill
- seo-fix-applySkill
- seo-freshnessSkill
- seo-geo-answerblocksSkill
- seo-geo-factdensitySkill
- seo-headings-structureSkill
- seo-images-mediaSkill
- seo-indexabilitySkill
- seo-internal-linkingSkill
- seo-internationalSkill
- seo-localSkill
- seo-meta-onpageSkill
- seo-mobileSkill
- seo-orchestratorSkill
- seo-platform-detectSkill
- seo-renderingSkill
- seo-schema-jsonldSkill
- seo-scoreSkill
- seo-sitemapsSkill
- seo-social-cardsSkill
The file
Files
<!-- Portions Copyright (c) 2026 Enrique Rocha (@soyenriquerocha) - see LICENSE for original authors · tododeia.com · id er-d03758e1 -->seo-vertical-detect
Given the PageSnapshot, classify the site so the orchestrator can route conditional modules. Read references/routing.md for the signal table.
Inputs
Read-only over persisted data — no fetching: the homepage parsed (jsonld[], anchors[], metas[], hreflang[], <html lang>, text_sample) from <run_dir>/pages/<slug>.json, <run_dir>/crawl.json (route patterns, templates), <run_dir>/site/discovery.json (llms.txt presence), and the vertical_hints[] emitted by detect-platform.mjs in <run_dir>/profile.json (e.g. WooCommerce/Shopify → ecommerce; a docs generator → docs). Hints are signals, not verdicts — cite them in signals like any other evidence.
Method
Score each vertical from observable signals (not guesses):
- ecommerce —
Product/OfferJSON-LD, cart/checkout/add-to-cart routes or buttons, price + currency elements,og:type=product. - local-business —
LocalBusinessJSON-LD, NAP block (name/address/phone), maps embed, opening hours, store-locator. - blog-publisher —
Article/BlogPostingJSON-LD, author bylines/author pages, RSS/Atom<link>, dated post archives. - saas — pricing/signup/login routes,
SoftwareApplicationschema, feature/integration/docs pages. - docs — docs/reference routes, sidebar/version nav, dense code blocks, present
llms.txt. - generic — none dominates.
A site can match several; return all that clear the threshold, ranked, plus a primary.
Locales: detect hreflang tags, <html lang>, and locale-prefixed routes (/es/, /fr/). If >1 locale, flag multilingual so M20 (hreflang) activates.
Output
{ "primary": "ecommerce", "also": ["blog-publisher"], "multilingual": true, "locales": ["en","es"],
"signals": { "ecommerce": ["Product JSON-LD on /p/...", "cart route /cart"], "...": [] } }Base every classification on a cited signal in signals — never label a vertical without evidence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

