Skip to content

gooseworks-ai/goose-skills / skills/marketing/improve-search-visibility

improve-search-visibility

Verified

SEO and AI-answer visibility. Use for a site SEO or technical audit with ranked fixes, competitor keyword and topic gaps, a topic cluster, SEO metrics for domains, a programmatic SEO page-set plan, or checking where ChatGPT and Google name the brand. Delivers the requested audit, comparison, map or blueprint with dated evidence and clear data limits. Also covers app store listings and local search. Drafts changes; never edits live. Full pages go to make-content; paid search goes to run-paid-campaigns.

FileKindSize
SKILL.mdskill md11.0 KB
references/app-store-listing.mdmarkdown2.4 KB
references/battlegrounds.mdmarkdown3.8 KB
references/citation-protocol.mdmarkdown8.4 KB
references/entity-and-local.mdmarkdown4.3 KB
references/finished-fix-examples.mdmarkdown8.7 KB
references/foundation-check.mdmarkdown7.5 KB
references/free-pass.mdmarkdown4.7 KB
references/gap-to-fix.mdmarkdown5.5 KB
references/page-map.mdmarkdown4.8 KB
references/prioritising.mdmarkdown2.9 KB
references/question-list.mdmarkdown5.5 KB
references/report-template.mdmarkdown4.6 KB
references/rival-content-map.mdmarkdown4.3 KB
references/run-memory.mdmarkdown15.0 KB
references/seo-data.mdmarkdown6.7 KB
references/seo-jobs.mdmarkdown9.7 KB
skill.meta.jsonconfig6.7 KB
tests/fixture-reports/audit.jsonconfig6.9 KB
tests/fixture-reports/audit.mdmarkdown5.5 KB
tests/fixture-reports/cluster.jsonconfig6.9 KB
tests/fixture-reports/cluster.mdmarkdown4.0 KB
tests/fixture-reports/gaps.jsonconfig5.7 KB
tests/fixture-reports/gaps.mdmarkdown3.8 KB
tests/fixture-reports/metrics-export.jsonconfig3.5 KB
tests/fixture-reports/metrics-export.mdmarkdown1.9 KB
tests/fixture-reports/metrics-missing.jsonconfig3.3 KB
tests/fixture-reports/metrics-missing.mdmarkdown1.8 KB
tests/fixture-reports/metrics-traffic-only.jsonconfig3.9 KB
tests/fixture-reports/metrics-traffic-only.mdmarkdown2.1 KB
tests/fixture-reports/metrics.jsonconfig5.0 KB
tests/fixture-reports/metrics.mdmarkdown3.1 KB
tests/fixture-reports/pseo.jsonconfig9.5 KB
tests/fixture-reports/pseo.mdmarkdown6.5 KB
tests/fixtures/coldfield.jsonconfig21.4 KB
tests/run-fixtures.pyscript7.7 KB
tests/test-by-hand.mdmarkdown9.4 KB

references/prioritising.md

View on GitHub
# Picking priorities

Rank evidence-backed actions for the requested job. Honor the requested count; default to ten audit priorities or five this-week fixes for a recurring AI-visibility check. Fewer real findings means fewer reported, with the reason. A recommendation count never caps the inventory, topic map or page families.

## Score and order

Use (Impact × Confidence) ÷ Effort, each 1–5, with a short reason:
- **Impact:** affected important pages, intents and buyers. For a visibility check, use lost/partial questions × checked engines, weighted toward purchase/comparison. For an audit, use the affected pages/templates, their business importance and available performance evidence. Do not rank cosmetic issues above a real indexing blocker.
- **Confidence:** observed cause and effect mechanism, not a promised ranking lift. A wrong canonical on the intended indexable page: high. A generic claim that Q&A receives more citations: low.
- **Effort:** the actual owner and scope. Separate a one-line setting change from a migration. Use agent and human active time where a task estimate is given.

Order: foundation blockers → false or conflicting brand facts → relevant near-winners → content/intent gaps and supporting off-site actions. State demand evidence when available, otherwise "ranked by relevance and judgment". Missing measurement is a useful recommendation when it prevents diagnosis or verification; it does not automatically displace a confirmed site outage or a requested topic blueprint.

For a recurring visibility check, draw this week's fixes from the page map plus blockers/profiles. Spread across lever types when supported. If cited third-party pages explain losses, start a useful off-site action this week. New-page briefs sit beside these fixes; the full roadmap is not limited to five. Carry worthwhile open fixes forward with their ids before adding new ones.

## What an action contains

Affected page/template · source/date and observed defect/gap · why it matters · exact change or precise engineering handoff · owner · agent/human effort · how to verify · risk/undo for structural changes. Use the fix-writer for finished copy/code only when the required site facts are known. A ten-item audit is a ranked backlog, not a claim all ten ship this week.

## Time to observe results

| Change | Typical observation window |
|---|---|
| Retrieval crawler access | check the response immediately; search pickup after recrawl |
| Changed page or title | days to weeks after recrawl; ranking changes can take months |
| New useful page | weeks to months; indexation and usefulness checked before traffic claims |
| Profiles | moderation first, then engine pickup |
| iOS metadata | next approved app version |
| Training-memory answer | an uncertain model-update timeline, not a this-week outcome |

State these as review windows, not guarantees. Use `run-memory.md` for comparable measurements after a fix is live.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall