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/foundation-check.md

View on GitHub
# Foundation check

Use for an SEO/technical audit or the relevant pages in a visibility check. The audit scope comes from `seo-jobs.md`: site-wide checks plus important pages and representative templates, expanded when variation warrants it. Record URLs checked, coverage and discovery limits. Every item is **pass / fail / not checked** from observed evidence; a sampled pass applies only to that sample. Diagnose technical issues here and give engineering the implementation handoff. A blocker outranks copy polish on the affected page.

## Site-wide (once)
| Check | How (no paid tools) | Class |
|---|---|---|
| robots.txt | fetch `/robots.txt`; look for `Disallow` on key paths and these user agents. **Retrieval** (blocking removes you from that engine): Googlebot, Bingbot, OAI-SearchBot, ChatGPT-User, PerplexityBot, Claude-SearchBot, Claude-User. **Training** (a policy choice, not a citation fix): GPTBot, Google-Extended (does not affect AI Overviews or AI Mode, which use Googlebot), CCBot, ClaudeBot | blocker if a retrieval bot is blocked |
| CDN / bot management | needs a shell: `curl -A "OAI-SearchBot" -sI <url>` vs a normal browser agent (also PerplexityBot); a 403 or a challenge page means blocked. No shell → "not checked — this chat can't test bot access" and a one-line developer check. CDNs' default AI-bot blocking catches many sites | blocker |
| Indexed at all | Search Console if shared; else the paid top-up's first lookup (the site-wide `site:` check, step 3), run only after the human's one yes — never during the free pass; the free pass can only hint at indexing (a web search for the brand's site). Bing: Bing Webmaster Tools if shared, else "not checked" (never scrape Bing results pages). ChatGPT search is widely reported to lean on Bing's index — unconfirmed by OpenAI — so Bing indexing is a cheap hedge | blocker if absent |
| Duplicate host | the platform's default domain (`*.webflow.io`, `*.myshopify.com`, `*.vercel.app`) redirects or canonicalises to the real domain | blocker if the duplicate is the one indexed |
| Search Console / Bing Webmaster Tools | asked in intake (one optional question covers both; Bing unknown → "not checked") | fix if missing |
| Sitemap | `/sitemap.xml` or the robots.txt `Sitemap:` line returns 200 and lists the money pages | polish |
| Templated page sets | in the sitemap, any set of dozens of pages on one pattern (`/brand/<name>`, `/city/<name>`, `/vs/<name>`): sample 3–5, check whether each has unique, useful content or near-identical boilerplate, and whether they're indexed. Read them before any copy fix | top of the risk list if thin: a proposal to improve, consolidate or noindex, with risk and undo |
| Organization markup on home/About | view-source for JSON-LD | polish (entity) |
| Measurement tags (homepage and one money page) | in the page source: which analytics runs (Google Analytics 4 / Tag Manager, Plausible, Fathom, PostHog, Mixpanel, Segment) and which ad pixels (Meta, Google Ads, LinkedIn, TikTok). It decides how the measurement fix is written: the AI-referral baseline goes into the analytics the site already has; no analytics at all → that becomes part of the measurement fix | blocker for measuring results, not for ranking — say which |

## Per page
| Check | How | Class |
|---|---|---|
| Indexed | `site:domain.com/path` (paid, counted) or Search Console URL Inspection if shared | blocker |
| robots meta / X-Robots-Tag | view-source for `noindex`; `curl -sI` for the header | blocker |
| Status and redirects | `curl -sIL`: final 200; ≤ 1 hop; 301 not 302 for permanent moves; no redirect to the homepage | blocker (4xx/5xx, loops); polish (chains) |
| Canonical | expected canonical target, absolute and returns 200; intended indexable unique pages normally self-reference; duplicate variants point to the intended primary page | blocker if it contradicts the intended indexable page |
| Content visible without JavaScript | `curl` the page and search for the key paragraph and the price; most AI crawlers do not run JavaScript | blocker for AI answers |
| Title / H1 / meta | present, unique, matches the question's intent; title ≲ 60 characters, head term first, brand last | polish (often the fastest win) |
| Answer-first | the first 40–60 words under the H1 answer the question with the entity named and facts stated | polish (core AEO fix) |
| Structured data | read the theme's or CMS's existing JSON-LD first (most Shopify themes already output Product); eligible types valid (Product/Offer, Organization, LocalBusiness, SoftwareApplication, Article, Breadcrumb); values match the visible text; no review markup on Organization; Rich Results Test / validator.schema.org | polish (Product errors on a store page = priority polish) |
| Speed | PageSpeed Insights API `https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=<url>&strategy=mobile`; use field (CrUX) data when present. Good: LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1. Poor: LCP > 4s, INP > 500ms, CLS > 0.25 (75th percentile, 28 days) | polish unless poor on a money page |
| Internal links | find links from navigation, hubs and relevant pages with useful anchors; exact inbound counts need a complete crawl or supplied crawl export, otherwise report only the checked links | issue when important pages are hard to discover or link targets are broken |
| hreflang (multi-region only) | reciprocal, valid codes, x-default | blocker if wrong |

## Hosts without a fetch tool, or with a limited one
Some hosted fetch tools open only URLs already in the chat and cannot set a user agent: list the URLs you need in the chat so they can be opened. Never ask the human for view-source or other technical steps: mark what you cannot see "not checked — <why>" and gather those items into a short developer checklist in the report.

## Traffic-drop entry (with Search Console)
Tell apart: (1) crawl/indexing (pages dropped out; robots or noindex change), (2) a core update (drop aligned to a published update date across many pages), (3) AI Overviews taking clicks (impressions flat or up, clicks down — not a ranking loss and never reported as one), (4) seasonality (same dip last year).

## Technical audit extensions (when the site uses them)

| Structure | Evidence to collect | Diagnosis / handoff |
|---|---|---|
| Facets, parameters and pagination | representative filtered/sorted URLs, canonical/robots/index controls, navigation links and sitemap inclusion | conflicting intent or uncontrolled duplicate variants; propose intended index/crawl rules with risk/undo, preserving useful search and user paths |
| Migration or domain/URL change | supplied old/new mappings, important old URLs, redirect targets/chains, internal links and sitemap/canonical/hreflang alignment | broken or mismatched mappings and remaining old signals; state mappings/logs not available and engineering checks still needed |
| Duplicate or competing pages | sitemap inventory, overlapping intents, page content and query/page data when available | consolidate only where intent genuinely overlaps; identify a matching destination and preserve traffic/conversion paths |
| Rendering and templates | raw vs rendered key content, links and markup on important template variants | missing content or links in the crawler-visible version; hand over the exact affected template/URLs and observed difference |

A full crawl or crawl export and Search Console/log access strengthen large-site diagnosis; name what was unavailable. Do not convert an unavailable check into a pass or a guessed site-wide defect. Site-speed engineering and migration execution remain proposals, separate from this diagnosis.
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: 194kUpdated Claude CodeCodexVerifiedInstall