The mandate
Build a search system around customer needs, not a spreadsheet of keywords.
Uses a business-specific checklist for SaaS, ecommerce, local service, marketplace, publisher, agency, or other models.
The SEO Agent selects the correct business-type branch, audits technical access, maps intent and entities to useful pages, and defines how the system will be measured and maintained.
What to bring
Bring the site, search model, priority market, current evidence, and conversion goal.
The same checklist cannot serve SaaS, ecommerce, local services, marketplaces, and publishers. The brief must make the business and page model explicit.
- 01
The website, domain, product area, or planned launch being reviewed.
- 02
The business model used to select the correct SEO checklist branch.
- 03
The audience, geography, language, and commercial market in scope.
- 04
Existing pages, rendering, analytics, indexation evidence, migrations, and known technical issues.
- 05
The search outcome, customer action, conversion, and review horizon.
What you receive
A technical baseline and page system that can be implemented and rechecked.
Technical findings, the intent-to-page map, and topical clusters remain tied to unique value, proof, internal links, conversion, and refresh ownership.
- 01
Technical SEO baseline
seo/technical-audit.mdReady when
Indexation, rendering, canonicals, sitemaps, and performance checks are reproducible.
- 02
Intent, keyword, and page map
seo/search-map.jsonReady when
Each search intent maps to a customer need, page, and conversion.
- 03
Topical cluster and internal-link plan
seo/content-clusters.mdReady when
Hubs, supporting pages, evidence, ownership, and refresh cadence are explicit.
The method
Classify the search model before prescribing pages or structured data.
The SEO plan joins crawl and rendering evidence with customer intent, entity clarity, content architecture, and qualified conversion.
- 1
Classify
Select the business-type branch and define audience, geography, page model, and conversion.
- 2
Audit
Reproduce technical findings across rendering, indexation, canonicals, sitemaps, and performance.
- 3
Map
Connect customer intent and entities to useful pages, proof, clusters, links, and structured data.
- 4
Measure
Define qualified outcomes, validation methods, owners, refresh triggers, and the next review.
Signals & guardrails
Search volume is evidence, not proof that a page deserves to exist.
Scaled pages without unique value, unsupported claims, duplicate intent, unowned refresh work, or unverifiable technical findings stop the plan.
Signs the work is useful
- Qualified organic conversions
- Indexed target pages
- Non-brand query visibility
Reasons to pause
- Volume estimates are treated as demand proof
- Generated pages lack unique value or verifiable claims
Approval boundary
This entrypoint declares no open-world effect. Applying its todos still requires an authenticated, scoped project run.
Technical appendix
The exact contract behind the profile.
Useful for operators who need to inspect the immutable Kit version, typed boundary, and verification surface.
- Kit
- company-suite@0.1.0
- Entrypoint
- review-seo
- Function
- plan-seo
- Runtime
- python@3.12
- Input
- specialist-brief.schema.json
- Output
- specialist-plan.schema.json
Verification
specialist-plan-quality · seo-readiness · business-type SEO checklist
Connected systems
Web research · Analytics