Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-seo
saas-seo
UnverifiedSaaS SEO, GEO & Agentic Readiness hub — technical, schema, AI search, llms.txt, and drift.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| references/backlink-quality.md | markdown | 3.4 KB |
| references/cwv-thresholds.md | markdown | 7.5 KB |
| references/eeat-framework.md | markdown | 7.2 KB |
| references/eeat-scoring-guide.md | markdown | 1.5 KB |
| references/free-backlink-sources.md | markdown | 6.2 KB |
| references/local-schema-multilocation.md | markdown | 1.4 KB |
| references/local-schema-types.md | markdown | 8.0 KB |
| references/local-search-behavior.md | markdown | 2.8 KB |
| references/local-seo-signals.md | markdown | 7.7 KB |
| references/maps-api-endpoints.md | markdown | 6.1 KB |
| references/maps-free-apis.md | markdown | 6.0 KB |
| references/maps-gbp-checklist.md | markdown | 6.0 KB |
| references/maps-geo-grid.md | markdown | 4.3 KB |
| references/quality-gates.md | markdown | 5.9 KB |
| references/schema-types.md | markdown | 9.2 KB |
| references/thinking-framework-validate-act.md | markdown | 3.1 KB |
| references/thinking-framework.md | markdown | 6.6 KB |
references/thinking-framework.md
View on GitHub# The 10-Principle Audit Synthesis Framework
This is the canonical methodology claude-seo uses to assemble raw findings
into strategically coherent recommendations. Every full-site audit and
deep-page analysis walks through these ten principles before producing the
final action plan.
The principles group into four phases:
| Phase | Principles |
|---|---|
| **PERCEIVE** | OBSERVE (external) · OBSERVE (internal) · LISTEN |
| **ANALYZE** | THINK · CONNECT (lateral) · CONNECT (system) |
| **VALIDATE** | FEEL · ACCEPT |
| **ACT** | CREATE · GROW |
A recommendation that has not passed through all four phases is a finding,
not a recommendation.
---
## PERCEIVE
### 1. OBSERVE: the external input
Collect signals without interpreting them. For a website audit this means:
- Raw HTML + rendered HTML (via `python scripts/seo/render_page.py`)
- Schema.org markup actually present (via `seo-schema`)
- SERP visibility for the site's published topics (via `seo-dataforseo` /
Google APIs when available)
- Backlink + brand-mention landscape (via `seo-backlinks`)
- Core Web Vitals field data from CrUX (via `python scripts/seo/pagespeed_check.py`)
- AI-search citation patterns (via `seo-geo`)
- Competitor pages on the target's primary keywords
**Discipline:** do not score yet. Do not classify yet. Just collect.
### 2. OBSERVE: internal metacognition
Audit your own assumptions about the site before assembling
recommendations. Common assumption traps in SEO:
- Assuming the homepage represents the site (often it doesn't: programmatic
pages or category pages drive traffic)
- Assuming "low traffic" means "low value" (intent-matched low-volume can
outconvert high-volume informational queries)
- Assuming the brand wants what the analyst thinks is "best practice"
(their constraint might be brand voice, legal, or trade-offs you don't
see)
- Assuming a CMS limitation is unfixable (often it isn't)
- Assuming a 1.x finding still applies in 2.x (Google updates change the
ground)
**Discipline:** for each major recommendation, ask "what assumption is
this resting on?" If the answer surprises you, surface the assumption in
the report so the user can reject it explicitly.
### 3. LISTEN: active receptivity
Read what the site, user intent, and platform signals are actually saying,
not what you expect them to say.
- Read the page's existing copy before recommending a rewrite. The brand
voice is data.
- Read the SERP for target keywords before deciding what page type to
build. The SERP is Google's revealed preference for that intent.
- Read user reviews / community discussions / Reddit threads for what
customers actually ask about (versus what the marketing team thinks
they ask about).
- Read the user's prior conversations + memory if available; they may
have ruled out approaches already.
**Discipline:** if a recommendation contradicts the SERP for the same
intent, the SERP wins unless you can explain why this site is the
exception.
---
## ANALYZE
### 4. THINK: critical processing
Reduce the findings to first principles:
- What is the **page type** (informational, transactional, navigational,
local, commercial-investigation) and does the current layout serve
that intent?
- What is the **eligibility floor** for AI features (indexed + can be
shown with a snippet)? If the page is not indexed, no AI work
matters yet.
- What is the **highest-leverage constraint** binding the site right
now? (Often: a single technical defect (non-indexable, slow LCP,
missing canonical) that gates everything else.)
- What does **Google's primary-source guidance** say about the
recommendation? When community claims and Google contradict, defer
to Google (see `.claude/skills/saas-seo-geo/references/google-ai-optimization-guide.md`).
**Discipline:** the highest-leverage constraint goes first in the action
plan, even if it's less interesting than the "growth" recommendations.
### 5. CONNECT: lateral / associative
Combine findings from sub-skills that the user wouldn't naturally pair.
Examples that frequently produce the highest-value recommendations:
- `seo-content` thin-content finding × `seo-cluster` SERP-overlap data →
consolidate three weak pages into one cluster hub.
- `seo-schema` missing Product schema × `seo-ecommerce` UCP-not-declared
→ both close the same agent-era buying gap; bundle as one
recommendation.
- `seo-geo` low AI-citation rate × `seo-backlinks` brand-mention
underweight → mentions matter 3× more than backlinks for AI
citations; reframe link-building budget into PR / Reddit / YouTube.
- `seo-technical` SPA detection × `seo-content` missing main-content
→ JS-blocked content is the upstream cause of the content finding.
**Discipline:** any single sub-skill finding that survives connection
unchanged should be skeptical; it might be a symptom, not a cause.
### 6. CONNECT: system orchestration
Wire the validated recommendations into an executable sequence:
- Which recommendation **unblocks** the most others? Do that first.
- Which recommendations **depend** on each other? Sequence them.
- Which recommendations can be **parallelized**? Surface that to the
user so they can dispatch them.
- Which recommendations need a **tool that's not yet installed** (e.g.
Firecrawl for site crawl, DataForSEO for SERP data)? Flag the gap.
**Discipline:** the action plan is a dependency graph, not a list. If
two recommendations cannot be done in either order, say so.
---
## How to invoke the framework
Every full-site audit (`/seo audit`) and deep-page audit (`/seo page`)
walks through PERCEIVE → ANALYZE → VALIDATE → ACT before emitting the
action plan. The Critical / High / Medium / Low priority bucketing
happens **after** the validation phase, not instead of it.
Single-purpose commands (`/seo schema`, `/seo images`, `/seo technical`,
etc.) can skip the full loop when the user is asking a narrow question, but
their recommendations should still pass at least THINK + ACCEPT before being
emitted (does this rest on a sound first principle, and is the falsifiability
surfaced?).
## When to escalate to the user
These principles are claude-seo's; they are not the user's. Surface them
for the user when:
- A recommendation requires accepting an assumption you'd rather not own
(CONNECT-lateral often produces these; surface the link and let the
user confirm).
- The validation phase flagged a brand-voice / operator-capacity / hard
constraint you can see but cannot resolve.
- The audit found no upstream constraint and is recommending an
optimization that may be premature.
---
Phases 3 and 4 (VALIDATE and ACT): `thinking-framework-validate-act.md`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |