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/gap-to-fix.md

View on GitHub
# From gap to fix

Use for AI-answer visibility patterns and fixes. Counts follow `prioritising.md`; an audit or planning request uses its branch in `seo-jobs.md`.

## Find the pattern (countable statements only)
1. Take the cited URLs from lost and partial rows; classify each by source type.
2. Count by stage and surface. Write statements a reader can check: "6 of 8 lost comparison runs cite rivals' own 'vs' pages; Halden has none." "Category answers cite three listicles; Halden is in none." "Brand answers call Shiftwise 'an AI workforce platform' (its 2022 positioning) — traced to its Crunchbase profile."
3. For each lost key question, open the passage the engine lifted from the winner and the brand's nearest page. Note what the winner has: a first sentence that answers outright, the entity named, numbers (price, size, counts), a comparison table, a visible date, a page that matches the intent at all.

## Lever by cause
| Cause | Fix type | This-week visibility fix? |
|---|---|---|
| Our page blocked, unindexed, JS-only, wrong canonical | foundation fix (exact line or setting) | yes — blockers first |
| Our page exists but can't be lifted | rewrite: title, meta, H1, answer-first opening, fact block, Q&A block, internal links | yes |
| Near-winner on Google (positions ~4–15, or impressions high and clicks low) | title/meta rewrite, refresh, internal links from strong pages | yes |
| No page for the intent | page brief to make-content (comparison, alternatives, use-case, location page) | no — listed beside the selected fixes |
| Name collision (engines answer about a namesake: "is <brand> legit" returns another company) | a visible one-line "who we are — not <namesake>" on About and the homepage, the brand's full name in every page title, consistent profiles, `alternateName` / `sameAs` in the existing Organization markup | yes — usually fix #1 |
| Wrong or old brand description in answers | entity fix: exact field values on the profile the engine cites, plus our About page and Organization markup | yes |
| Absent from cited listicles / review roundups | inclusion request: one drafted email to the page's editor naming the page, the gap and the facts (the human sends it) | yes, if the cited page is maintained and plausibly updated |
| Review platforms thin (count, recency), or reviews filed under an old name or domain | the ask: a review-request flow brief to email-lifecycle (a post-purchase or post-install ask with the direct review link; Google Business Profile reviews where the business has one); an old-domain profile → claim it and point it at the current site, or ask the platform to merge (replying to reviews is not covered yet) | yes (the brief) |
| Old, duplicate or wrong pages (a retired range, a merged page, old claims still live) | **301 redirect to the matching page + update internal links** (the default); noindex only when no equivalent page exists. First check what still points there — live ads, emails, profiles: a redirect keeps them working; a noindexed page left live for ads still shows its old claims, so fix the claims or move the ads | yes |
| Reddit/forum threads cited, brand absent | name the threads; a disclosed founder reply the human may post | only as the disclosed reply |
| YouTube videos cited | video brief to make-content | no |
| Answer from training memory (no search) | name it; entity and third-party fixes help over months; nothing promised this week | no |
| No Search Console / no Bing Webmaster Tools | verification + sitemap submission, exact steps for the site's CMS | yes — 15 minutes, and it unlocks the next run's data |
| Retrieval crawler blocked (robots or CDN) | a proposal with the exact robots line or CDN setting and the risk | yes, after the human's yes |

## Hard limits
- No Wikipedia article about the brand (notability and conflict-of-interest rules). Wikidata only with ≥ 2 independent published sources, each statement referenced.
- No posts that hide the poster's tie to the brand; no fake reviews; no incentive tied to a positive rating, no undisclosed incentives, no review gating. A platform's own disclosed review programme (G2, Capterra gift-card campaigns) is fine.
- No llms.txt as a fix: no major engine has confirmed using it; Google says it uses no special AI files or markup.
- Schema is hygiene, not a citation lever: valid Product/Offer, Organization (+sameAs), LocalBusiness, SoftwareApplication, Article, Breadcrumb. FAQ rich results are no longer shown by Google (removed for all sites May 2026); a visible Q&A block still helps engines lift answers, and FAQPage markup is optional and harmless.
- Competitor facts on our pages need a public source and must respect the human's stance on naming rivals.

## The inclusion request (template, drafted not sent)
```
To: [editor or contact found on the page; "find on the page" if none]
Subject: [Page title] — a [category] option for [the page's audience]
Hi [name], your "[page title]" ([URL], updated [date]) covers [category] for [audience]. [Brand] is [one-line description, canonical]. For your readers: [2–3 checkable facts — price, the one difference, a proof point from the approved claims]. [One reason the editor's readers gain: a data point only the brand has, a real side-by-side test they can reproduce, or an honest "when not to use us" line — not just "happy to give you a free account".] Happy to set you up to test it. [Name, role, brand]
```
Many "best X" lists are affiliate-driven; if the cited lists all carry affiliate links, say so and note that an affiliate programme may be the real ask (a decision for the human, not drafted here).
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