optbrew 0.0.0-stage → 0.1.2

package/skills/optbrew/modules/mblode-seo/references/nextjs-implementation.md

@@ -0,0 +1,65 @@
+# Next.js Implementation
+
+Read the installed version's documentation under `node_modules/next/dist/docs` (possibly at the workspace root) before changing APIs. The checks below name observed failure modes; they are not a permanent version compatibility table.
+
+## Metadata
+
+- Set `metadataBase` for the production origin and emit the page's preferred canonical. Verify basePath behavior in a production build, especially generated versus static Open Graph images.
+- Preserve DNS ownership verification. Use `metadata.verification` only for a supplied token and the selected verification method.
+- Choose descriptive titles and descriptions for the page purpose. Check truncation and redundancy as presentation concerns, not fixed 50/60/44-character validity gates. Title templates apply to child routes; inspect the resolved title and social title separately.
+- Nested metadata objects such as `openGraph` can replace parent values rather than deep-merge. Restate or share the fields that should survive. Avoid an inherited homepage `openGraph.url` on every route.
+- Set preview controls deliberately. `max-image-preview:large` permits larger previews; `max-snippet:-1` permits unrestricted snippet length. These are permission controls, not ranking boosts or guaranteed excerpt lengths. Preserve intentional restrictions and check current engine controls.
+- Use author/entity attribution where it describes the content. A person, product, organization and website are distinct entities; `sameAs` identifies the same entity, not every associated organization.
+
+## Sitemaps and rendering
+
+Implement sitemaps from the authoritative public route inventory. Use content modification dates or omit them; availability-gated pages must follow the same gate as their routes. Fetch emitted XML and its URLs after building.
+
+A generated sitemap collection may need an explicit index or discovery entries. Verify the installed version's `generateSitemaps` parameters and output paths instead of reconstructing them from memory. Sitemap caches and upstream CDNs can outlive the app deploy; verify the public response.
+
+Server-render the principal text and navigational anchors on indexable hubs and detail pages. Client Components can prerender; mounting guards, viewport-dependent state and effect-only fetching can still remove the useful initial HTML. Keep a useful visible fallback for readers without JavaScript and enhance it after hydration. Verify the visual transition, not just raw text counts.
+
+Cache Components changes available route configuration and caching APIs. Verify support before adding `dynamic`, `revalidate` or `fetchCache` exports. Choose content-aware invalidation and account for CDN caching separately.
+
+## Status codes and redirects
+
+A `notFound()` or redirect after streaming starts may produce a 200 shell with metadata or a client redirect. For routes that require a true 404 or 3xx, validate existence or redirect before streaming using a supported routing boundary. Test the actual status with an invented path and a migrated URL.
+
+Redirect specificity and basePath prefixing affect matching. Check bare roots, trailing slashes, query strings and Markdown twins. Preserve legitimate deep paths, avoid loops, and verify the final destination's status and canonical.
+
+For Next versions that use `proxy.ts`, use the documented exported handler, runtime and matcher format. Check the compiled behavior for exact versus descendant matches. Do not migrate unrelated middleware solely because an SEO file changed.
+
+## Markdown twins and llms.txt
+
+Inspect existing `llms.txt` and `*.md` handlers before adding another. Typical App Router shape: a route handler or `proxy.ts` rewrite that serves the markdown source at the HTML path with `.md` appended (directory URLs use `index.md`). On `Accept: text/markdown`, return that body with `Content-Type: text/markdown; charset=utf-8` and `Vary: Accept`; HTML Accept stays on the existing page. Confirm the matcher does not exclude `.md` or `llms.txt`.
+
+Honor Accept `q=0` and verify CDN `Vary` on both representations, as in `answer-engines.md`. AFDocs pass/fail for `llms.txt` shape, in-page directives, and coverage is `agent-ready`, not this file.
+
+## Structured data
+
+Use types appropriate to the visible page and current supported search features. Stable `@id` references can connect entities across consistent JSON-LD blocks; one `@graph` is an optional organization convention. Script count alone is not an error.
+
+Derive markup from the same data as the rendered content. Check claims, links, dates, prices, reviews and author identities against what the page actually provides. Some schema properties need no literal visible label; the underlying claim still needs to be accurate and supported. Validate rich-result eligibility separately from JSON syntax and schema vocabulary validity.
+
+Escape `<` when embedding serialized JSON-LD in a script:
+
+```tsx
+<script
+  type="application/ld+json"
+  dangerouslySetInnerHTML={{
+    __html: JSON.stringify(data).replaceAll('<', '\\u003c'),
+  }}
+/>
+```
+
+Check the current feature documentation before promising FAQ, Article, Product or other rich results. A schema.org type can remain valid after a Google presentation feature is retired.
+
+## Images, headers and performance
+
+Read generated social image URLs from the built output and fetch them. Do not infer extensions, host or basePath resolution from filenames. A declared OG URL whose response is HTML or 404 is a defect.
+
+Metadata may stream for one user agent and block in the head for another. Exercise the framework's HTML-limited bot path as well as browser/Google-style requests, especially for pages that read build-only filesystem assets. Verify server behavior, not a grep that counts escaped RSC metadata twice.
+
+A nonce CSP may require dynamic rendering and reduce caching. Do not add it solely to silence an SEO scanner. CORP is a browser response policy, not proof that a server-side social scraper cannot fetch an image. Diagnose the real request, MIME type and delivery failure.
+
+Keep the LCP resource discoverable early, reserve layout space and measure interaction delays. Use supported image priority/loading APIs for the installed version. Field measurements and lab diagnostics belong in separate evidence columns.

package/skills/optbrew/modules/mblode-seo/references/research-protocol.md

@@ -0,0 +1,37 @@
+# Research Protocol
+
+Produce a decision about demand and product fit, not a table of plausible numbers. Use supplied exports as supplied evidence; for a request for fresh research, pull current data or label the access/freshness gap.
+
+## Demand and intent
+
+Confirm the audience, product capability and outcome before selecting queries. Keep the promoted product distinct from a competitor named in a query: a Windows-capable alternative can legitimately target demand for a competitor that has no Windows app. Missing comparison details become verification items in the brief, not an invented contradiction. Inspect the actual results and existing site coverage to distinguish definitions, comparisons, implementation and purchase intent. Add a modifier when it disambiguates; do not force one onto an already-specific query or declare every broad noun unwinnable.
+
+Default to global scope unless the request or established market specifies a country. Preserve a tool's actual scope; an Australian figure is not global. Record the reported time window and pull date, including whether volume is a monthly average or a particular month.
+
+Query the primary and relevant secondary terms in the connected keyword tool. Use property-scoped Search Console queries, public discussions, support/sales evidence and product usage as additional demand signals. Lack of vendor volume for a niche term is not proof of no demand. Prefer improving an existing relevant page over creating a competing one.
+
+## Prompt metrics
+
+House reporting uses the vendor's **Exact** prompt match figure. Match definitions vary by vendor; record the definition, engine, locale, sampling/estimation method and date window where available. Do not define Phrase or Exact universally by word order, or substitute keyword volume for prompt demand.
+
+When Exact is absent, report `No data (Exact unavailable)` rather than substituting Phrase, broad or a related prompt. A Phrase figure may be separately labeled as context, never placed in the Exact column. Distinguish a measured zero from missing data. Vendor-estimated demand and repeated prompt-panel visibility are separate measurements.
+
+## Evidence table
+
+| Query or prompt | Metric and value | Source and match definition | Scope/engine | Window and pull date |
+|---|---|---|---|---|
+| <actual term> | <keyword volume, Exact prompt volume, or No data with reason> | <tool/export and metric definition> | <country/global, engine where applicable> | <reported window; retrieved date> |
+
+Do not merge unlike populations into one metric or fill blanks from memory. If sources disagree, preserve both scopes and reconcile definitions before selecting an authoritative number. Historical exports can inform context when labeled; they are not a current pull.
+
+## Question map and decision
+
+Use natural evaluator questions: what it is, when to use it, alternatives, implementation, evidence and limitations. Mark questions already covered and identify material gaps. Hypothesized fan-out queries are brainstorming, not observed engine behavior; do not manufacture separate pages for every wording.
+
+Mine questions from where buyers ask them in their own words: support and sales threads, community forums and Reddit, review sites and competitor help centres. Record each question with its source URL or ticket reference and date, so the brief can cite provenance; a question with no source is a hypothesis.
+
+Before recommending `create`, run the gap check for the target query or prompt. Read the current top organic results and, where the page targets AI search, a repeated prompt panel per engine. Record who is cited and two or three specific things the current answers miss or get wrong: an unanswered evaluator question, stale product facts, no first-hand evidence, no honest limitation. The gap must be something the site can actually supply. No named gap means no new page: recommend `update`, `consolidate` or `defer` instead, and say so.
+
+Recommend create, update, consolidate, defer or validate based on demand evidence, attainable intent, differentiated value and the conversion path. State confidence and the next evidence needed. Quantitative evidence can be `No data`; a small validation may still be justified by explicit qualitative evidence.
+
+Treat vendor correlation studies as dated, sample-dependent research. Preserve engine, sample selection and non-causal limitations. Branded searches, independent mentions and videos can be tracked where useful, but none is a universal strongest predictor or a guaranteed lever.

package/skills/optbrew/modules/mblode-seo/references/sources.md

@@ -0,0 +1,47 @@
+# Sources and Freshness
+
+This registry was checked on 2026-09-08; the research table was added on 2026-09-23. Treat the date as provenance, not a promise that vendor behavior remains unchanged. Reopen the relevant official page when deciding a volatile feature, API, policy or reporting capability. Record the source and access date beside consequential claims.
+
+## Primary guidance
+
+| Topic | Source |
+|---|---|
+| Google AI search foundations, formatting myths and measurement | https://developers.google.com/search/docs/fundamentals/ai-optimization-guide |
+| Google generative AI report availability and dimensions | https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports |
+| Bing AI reporting | https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview |
+| OpenAI search versus training and crawler identity | https://developers.openai.com/api/docs/bots |
+| Anthropic crawlers | https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler |
+| Google robots and preview directives | https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag |
+| Sitemaps and meaningful lastmod | https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap |
+| Canonical consolidation | https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls |
+| Localized versions and optional x-default | https://developers.google.com/search/docs/specialty/international/localized-versions |
+| Structured-data eligibility | https://developers.google.com/search/docs/appearance/structured-data/sd-policies |
+| Scaled content abuse and other spam policies | https://developers.google.com/search/docs/essentials/spam-policies |
+| Core Web Vitals | https://web.dev/articles/vitals |
+| Next.js implementation | Installed `next/dist/docs` first; https://nextjs.org/docs/app as fallback |
+
+## Research, not ranking contracts
+
+https://ahrefs.com/blog/ai-brand-visibility-correlations/ reports associations from a selected established-brand population, not causal effects or universal coefficients. Use the study's current methodology, engine and sample restrictions rather than copying an undated strongest-predictor claim into instructions.
+
+"GEO" as a term comes from Aggarwal et al., "GEO: Generative Engine Optimization", KDD 2024 (https://arxiv.org/abs/2311.09735). Its visibility gains were measured on a benchmark and on Perplexity in 2023; cite it for the definition, not as current evidence that a given tactic works.
+
+Distinguish official engine guidance, vendor observational research, a site-specific experiment and house preferences. Official Google guidance describes Google Search and its AI features, not ChatGPT, Claude, Perplexity or other AI search engines. An industry study can motivate a test; it cannot establish that a specific action will improve this site's visibility.
+
+## Dated research
+
+These figures reached this registry through Man of Many's 2026 Guide to GEO (21 September 2026), a publisher's compilation that prints the publisher, sample and date for each and has a stated commercial interest in third-party editorial. Primaries were not reopened. Open the primary before quoting a figure, and use them to frame a test or a budget conversation, never as a promised effect for one site.
+
+| Finding | Source, sample, date | Limit |
+|---|---|---|
+| 85% of brand mentions in AI answers came from third-party pages, 13.2% from the brand's domain; nearly 90% of third-party mentions were in listicles, comparisons and reviews | AirOps, 21,311 mentions, October 2025 | Mention share, not citation or traffic |
+| Adding schema to 1,885 pages was followed by a 4.6% fall in AI Overview citations | Ahrefs, 11 May 2026 | One engine; schema still serves rich results and entity identity |
+| No relationship between `llms.txt` and AI citations | SE Ranking, about 300,000 domains, 7 November 2025 | Says nothing about coding agents that do read it |
+| 54% of sites that scaled AI-generated content lost 30% or more of peak traffic | Lily Ray, Amsive, 220+ sites, 13 May 2026 | Selected sites |
+| Nearly 65% of AI citations pointed to content from the previous year; news articles persisted in citations 1.4% of the time | Seer Interactive, June 2025; SISTRIX AI Citation Drift, 2026 | Freshness means real updates, not restamped dates |
+| Removing the AI Overview produced 68% more organic clicks per search; 7.1% of clicks on an AIO page came from its citations | Agarwal and Sen, randomised, 1,065 US desktop users, 2026 (SSRN 6513059) | Desktop, US, reported via Digital Content Next |
+| The same prompt returned the same brand list less than once in 100 runs; weekly cited-source turnover of 56% (AI Mode) and 74% (ChatGPT) | SparkToro with Gumshoe, 2026; SISTRIX, 82,619 prompts, 2026 | Why prompt panels need repetitions. Do not cite AirOps' "2.2%" for this: it is the share of cited URLs shared by all three engines for one prompt, not run-to-run stability |
+| The same prompt rarely returned the same brand list twice | SparkToro, 2,961 queries from 600 volunteers, 28 January 2026 | Why a single visibility score misleads |
+| Brand search volume was the strongest tested predictor of AI brand mentions, at a correlation of about 0.33 | Kevin Indig, Growth Memo, 75,000 brands, 4 May 2026 | Strongest, not strong; correlational |
+| Retrieval snippet test for whether an assistant can retrieve a page | Myriam Jessier and Chris Green, September 2026 | Proves retrievability, not trust or citation |
+| Scraper-based rank and AI-visibility tools lost collection from mid-September 2026 | Search Engine Roundtable, 18 September 2026 | Unconfirmed by Google; may ease |

package/skills/optbrew/modules/mblode-seo/references/validation-evidence.md

@@ -0,0 +1,21 @@
+# Validation Evidence
+
+Choose probes for the changed behavior, not a fixed command quota. Record commands, timestamp, exact requested/final URLs, environment/build identity and relevant results. Preserve unrelated processes and edits; use an available port owned by this task for local serving.
+
+## Built-page checks
+
+1. Run the repository's applicable lint/type/build checks. Use a production build when metadata, static generation or prerendering is involved.
+2. Fetch the actual HTML response and parse title, canonical, meta/header directives, headings, anchors and JSON-LD. Do not count SVG titles, escaped payloads or script string matches as HTML elements.
+3. For rendering changes, compare raw HTML with the browser DOM and inspect the visual result with and without JavaScript. Check the affected route pattern, a detail route and a missing path.
+4. For sitemap changes, parse emitted XML, verify advertised URLs and compare lastmod to the content source. For redirects, inspect the complete chain and terminal status/canonical.
+5. For AI access, probe relevant user-agent paths, then distinguish those results from authenticated crawler logs or engine URL inspection. For content negotiation, test both representations and cache request orders.
+6. For AI retrievability, copy a unique 20 to 30 word sentence from the live page and, in a clean session per assistant, ask each relevant engine to search for that exact text and return only matching results. A returned URL proves that engine can retrieve the page, not that it will cite it; a miss points to indexing, robots, CDN/WAF challenges or crawlability before copy.
+7. Check JSON-LD syntax, entity consistency and current rich-result eligibility separately. Multiple consistent blocks are valid; DNS ownership does not require a duplicate meta token.
+
+## Completion evidence
+
+Report each applicable check as passed, failed, not applicable or not measured. A local pass supports local behavior only. After an authorized deployment, wait for readiness, verify deployment identity and repeat the material probes through the real public host/CDN. A deployed source change with an unchanged cached public response remains unverified.
+
+Use Search Console/Bing inspection where available for engine-observed indexing. State `No data` if unavailable; neither sitemap submission nor a crawler 200 response establishes index inclusion.
+
+Report field Core Web Vitals independently of lab diagnostics. Verify current thresholds when assessing performance; conventional good thresholds are LCP <=2.5s, INP <=200ms and CLS <=0.1 at the 75th percentile. Specify URL/origin aggregation, device and date window. Missing field data is not a pass.

package/skills/optbrew/modules/naver-searchadvisor/GUIDE.md

@@ -0,0 +1,75 @@
+> **optbrew policy correction (2026-10-14):** This distribution note takes precedence over conflicting upstream recommendations below. `llms.txt` is an optional proposal, and RSL or training-bot access is a separate provider and rights decision. Their presence, as well as schema presence, is not measured citation improvement. An actual AI citation requires provider output and source evidence. A `site:` query is not complete indexing proof; IndexNow is a discovery notification, not indexing confirmation. Naver `nosourceinfo` concerns its AI-generated source description setting only; do not infer a general citation or indexing effect. Verify the current official policy before applying any provider-specific claim. Do not submit URLs or change crawler controls from this guide without separate authority.
+
+# Naver Search Advisor source guide
+
+Adapted from the pinned upstream SKILL.md. Naver's 55 article bodies are excluded because their copyright is outside the upstream MIT license. The source routing tables below identify topics only. Find each document in [the official document index](references/INDEX.md) and read its current official URL before using a policy or numeric claim. If the page cannot be read, mark that claim unknown. A site: search is not complete indexing proof; IndexNow is a notification, not confirmed indexing. The local audit script gathers evidence only and must not submit to Naver.
+
+The upstream instructions to read local article bodies, search those bodies, or fetch them into this package do not apply to optbrew.
+
+## Optbrew audit input
+
+Run `node skills/optbrew/scripts/audit.mjs --context <run-context.json> --modules naver-searchadvisor --output-dir <run-dir>`. The optbrew collector checks the declared origin, path and resolved IP at each redirect. This module reads only collector-preserved HTML, response headers and any in-scope robots.txt artifact. Its original direct URL CLI is disabled. A Yeti User-Agent response, when supplied, is a bot-specific response observation; it does not prove that a Naver bot visited the site. Module warnings are evidence to review, not automatic optbrew score deductions.
+
+## 라우팅 표 — 요청 → 읽을 문서
+
+| 사용자가 이런 걸 물으면 | 읽을 파일 (`official URLs in references/INDEX.md`) |
+|---|---|
+| 네이버 SEO 처음 시작, 뭐부터? | `01-seo-basic-intro.md`, `12-seo-help.md` |
+| 사이트 등록, 소유확인 | `55-faq-start-register.md` |
+| robots.txt 작성·응답코드·Yeti 허용 | `03-seo-basic-robots.md` |
+| 검색로봇 IP 확인, 방화벽에 막힘 | `07-seo-basic-firewall.md` |
+| 리다이렉트, URL 변경, 사이트 이전 | `04-seo-basic-redirect.md`, `05-seo-basic-migration.md` |
+| HTTP 상태코드 해석 | `08-seo-basic-http.md` |
+| 사이트 폐쇄·종료 절차 | `06-seo-basic-close.md` |
+| SPA/React/Vue가 색인 안 됨 | `09-seo-advanced-javascript.md` |
+| URL 구조 설계 | `10-seo-advanced-url.md` |
+| 색인 효율, 크롤 예산 | `11-seo-advanced-indexing.md` |
+| CSS/JS/이미지 리소스 차단 문제 | `13-resource-and-link.md` |
+| 스팸으로 분류될까? 페널티 사유 | `14-content-abusing.md` |
+| 콘텐츠 어떻게 써야 하나, AI 글 써도 되나 | `15-content-basic.md` |
+| canonical, noindex, nofollow, nosourceinfo | `16-markup-structure.md` |
+| title, description, 오픈그래프, og:image 규격 | `17-markup-content.md` |
+| 모바일 대응, viewport | `18-markup-mobile.md` |
+| 파비콘이 검색결과에 안 나옴 | `19-markup-favicon.md` |
+| 수집요청, 검색제외 요청 | `20-request-crawl.md` |
+| 사이트맵·RSS 제출 | `21-request-feed.md` |
+| 사이트 간단 체크 / URL 검사 도구 | `22-diagnose-site.md`, `23-url-inspection.md` |
+| 서치어드바이저 리포트 해석 | `24`~`28-*.md` (노출/클릭, 진단, 최적화, 수집현황, 사이트상태) |
+| 구조화된 데이터 개념·JSON-LD 형식 | `29-structured-data-intro.md` |
+| 특정 타입 마크업 (식당/리뷰/레시피 등) | 아래 **구조화된 데이터 표** 참조 |
+| 대량 색인 API 연동 | `44-crawl-request-api.md` |
+| IndexNow 도입 | `45`~`48-indexnow-*.md` |
+| 검색에 안 나와요 | `52-faq-serpmissing.md` → `22-diagnose-site.md` |
+| 검색에서 빼고 싶어요 | `53-faq-serpremove.md` |
+| 검색결과 제목/설명이 이상해요 | `51-faq-serpedit.md` |
+| 서브링크가 안 나와요 | `54-faq-sublink.md` |
+
+전체 목록은 `references/INDEX.md`.
+
+## 구조화된 데이터 타입 표
+
+**자가 적용 가능** — 마크업만 하면 되는 타입:
+
+| 타입 | 필수 속성 | 문서 |
+|---|---|---|
+| `Restaurant` | name, openingHours | `39-structured-data-restaurant.md` |
+| `Review` | reviewBody | `38-structured-data-review.md` |
+| `AggregateRating` | ratingValue | `36-structured-data-rating.md` |
+| `Recipe` | recipeInstruction | `37-structured-data-recipe.md` |
+| `HowTo` | text | `34-structured-data-howto.md` |
+| `BreadcrumbList` | name | `33-structured-data-breadcrumb.md` |
+| `ListItem` (캐러셀) | image | `35-structured-data-carousel.md` |
+| `PostalAddress` | streetAddress | `32-structured-data-address.md` |
+| `Movie` | name, actor | `41-structured-data-movie.md` |
+| `TVSeries` | name, actor | `40-structured-data-tvseries.md` |
+| `SoftwareApplication` | name, applicationCategory | `42-structured-data-software.md` |
+| `Organization`/`Person` (연관채널) | name, url, sameAs | `30-structured-data-channel.md` |
+
+**제휴(협의) 필요** — 마크업만으로는 노출되지 않는다. 사용자에게 반드시 알릴 것:
+
+| 타입 | 조건 | 문서 |
+|---|---|---|
+| `JobPosting` (채용정보) | 네이버 제휴제안 + 수집요청 API 연동 필수 | `31-structured-data-job.md` |
+| `VideoObject` (동영상) | 동영상콘텐츠 제휴 + Push 방식 수집 | `43-structured-data-video.md` |
+
+권장 형식은 **JSON-LD 또는 Microdata** (출처: `structured-data-intro`). 검증은 <https://validator.schema.org/>.

package/skills/optbrew/modules/naver-searchadvisor/NOTICE.md

@@ -0,0 +1,59 @@
+> optbrew distribution note: The upstream notice below is preserved for attribution. This bundle excludes all 55 Naver article bodies and the article-fetch tool. Its statements about the upstream repository's contents and workflow do not describe this package.
+
+# 저작권 및 출처 고지 (NOTICE)
+
+## 원문 자료
+
+`references/guide/` 아래 55개 Markdown 문서는 **네이버 서치어드바이저 웹마스터 가이드**
+(<https://searchadvisor.naver.com/guide>)의 공개 문서를 Markdown으로 변환한 것입니다.
+
+- **저작권자: 네이버 주식회사 (NAVER Corp.)**
+- 본 저장소는 네이버(주)와 아무런 관련이 없으며, 공식 제공물이나 승인을 받은 배포물이 아닙니다.
+- 문서 본문에는 어떠한 수정·요약·재해석도 가하지 않았습니다. HTML → Markdown 형식 변환만 수행했습니다.
+- 각 파일은 front matter에 원문 URL(`source`)과 네이버가 명시한 수정일(`updated`)을 보존합니다.
+- 수집 시점: 2026년 7월. 이후 원문이 변경되었을 수 있으므로, **정확한 최신 내용은 항상 `source`의 원문을 확인하십시오.**
+
+재배포 목적은 AI 에이전트가 오프라인에서 정확한 근거 자료를 참조하도록 하는 것입니다.
+AI가 네이버 SEO를 추측이나 구글 SEO 지식으로 답하는 것을 막으려면 원문 접근이 필요하며,
+요약본을 쓰면 그 과정에서 정보가 왜곡되므로 원문을 그대로 두었습니다.
+
+**네이버(주)의 요청이 있을 경우 `references/guide/` 전체를 즉시 삭제하고,
+사용자가 `tools/fetch-guide.mjs`로 직접 내려받는 방식으로 전환합니다.**
+이슈 또는 저장소 소유자에게 연락 주시기 바랍니다.
+
+## 이 저장소가 직접 작성한 부분
+
+다음은 이 프로젝트의 창작물이며 MIT 라이선스를 따릅니다 ([LICENSE](../../licenses/naver-searchadvisor.txt)).
+
+- `SKILL.md` — 스킬 지침, 라우팅 표, 워크플로
+- `scripts/audit.mjs` — 진단 스크립트
+- `tools/fetch-guide.mjs` — 수집 스크립트
+- `README.md`, `NOTICE.md`, `references/INDEX.md`
+
+## 상표
+
+NAVER, 네이버, 서치어드바이저, Yeti는 네이버 주식회사의 상표입니다.
+이 저장소에서는 식별 목적으로만 사용합니다.
+
+---
+
+# Copyright Notice (English)
+
+The 55 Markdown documents under `references/guide/` are Markdown conversions of the publicly
+available **NAVER Search Advisor Webmaster Guide** (<https://searchadvisor.naver.com/guide>).
+
+- **Copyright: NAVER Corporation**
+- This repository is **not** affiliated with, endorsed by, or approved by NAVER Corporation.
+- Document bodies are unmodified — only HTML-to-Markdown format conversion was applied.
+- Each file preserves the original URL (`source`) and NAVER's stated revision date (`updated`)
+  in its front matter. Snapshot taken July 2026 — always verify against the `source` URL.
+
+Redistribution serves to give AI agents offline access to accurate primary sources, preventing
+them from answering Naver SEO questions with guesswork or Google SEO knowledge.
+
+**If NAVER Corporation requests removal, `references/guide/` will be deleted immediately** and
+replaced with a fetch-it-yourself flow via `tools/fetch-guide.mjs`.
+
+Original work in this repository (`SKILL.md`, `scripts/`, `tools/`, docs) is MIT licensed.
+NAVER, Search Advisor, and Yeti are trademarks of NAVER Corporation, used here for
+identification purposes only.

package/skills/optbrew/modules/naver-searchadvisor/references/INDEX.md

@@ -0,0 +1,97 @@
+# 네이버 서치어드바이저 웹마스터 가이드 — 전체 색인
+
+출처: https://searchadvisor.naver.com/guide
+라이선스: 아래 문서 본문의 저작권은 네이버(주)에 있습니다. NOTICE.md 참고.
+수집 문서: 55 / 55
+
+
+## 검색엔진 최적화 기초
+
+- [검색엔진 최적화의 목적](https://searchadvisor.naver.com/guide/seo-basic-intro) — `seo-basic-intro`, 수정 2025-02-10
+- [웹 사이트를 만들 때](https://searchadvisor.naver.com/guide/seo-basic-create) — `seo-basic-create`, 수정 2020-08-03
+- [robots.txt 설정하기](https://searchadvisor.naver.com/guide/seo-basic-robots) — `seo-basic-robots`, 수정 2025-10-14
+- [웹 페이지의 이동](https://searchadvisor.naver.com/guide/seo-basic-redirect) — `seo-basic-redirect`, 수정 2025-03-12
+- [웹 사이트 이전](https://searchadvisor.naver.com/guide/seo-basic-migration) — `seo-basic-migration`, 수정 2025-05-15
+- [웹 사이트 운영을 그만둘 때](https://searchadvisor.naver.com/guide/seo-basic-close) — `seo-basic-close`, 수정 2019-09-21
+- [검색로봇 확인 방법](https://searchadvisor.naver.com/guide/seo-basic-firewall) — `seo-basic-firewall`, 수정 2026-05-11
+- [HTTP 규약(Protocol)](https://searchadvisor.naver.com/guide/seo-basic-http) — `seo-basic-http`, 수정 2025-03-12
+
+## 검색엔진 최적화 고급
+
+- [자바스크립트 검색 최적화](https://searchadvisor.naver.com/guide/seo-advanced-javascript) — `seo-advanced-javascript`, 수정 2025-02-10
+- [검색 친화적인 URL 구축하기](https://searchadvisor.naver.com/guide/seo-advanced-url) — `seo-advanced-url`, 수정 2021-03-24
+- [사이트의 색인 효율성 개선하기](https://searchadvisor.naver.com/guide/seo-advanced-indexing) — `seo-advanced-indexing`, 수정 2021-10-27
+- [SEO 기본 가이드](https://searchadvisor.naver.com/guide/seo-help) — `seo-help`, 수정 2024-12-11
+- [리소스와 링크 관리](https://searchadvisor.naver.com/guide/resource-and-link) — `resource-and-link`, 수정 2024-08-26
+
+## 콘텐츠 가이드라인
+
+- [웹 콘텐츠 스팸사례](https://searchadvisor.naver.com/guide/content-abusing) — `content-abusing`, 수정 2026-07-03
+- [콘텐츠 작성시 권장 사항](https://searchadvisor.naver.com/guide/content-basic) — `content-basic`, 수정 2026-07-03
+
+## HTML 마크업
+
+- [선호 URL 및 로봇 메타 태그](https://searchadvisor.naver.com/guide/markup-structure) — `markup-structure`, 수정 2025-12-11
+- [콘텐츠 마크업](https://searchadvisor.naver.com/guide/markup-content) — `markup-content`, 수정 2024-05-10
+- [모바일 사용성](https://searchadvisor.naver.com/guide/markup-mobile) — `markup-mobile`, 수정 2020-08-03
+- [파비콘 (Favicon)](https://searchadvisor.naver.com/guide/markup-favicon) — `markup-favicon`, 수정 2025-06-24
+
+## 웹사이트 검색연동
+
+- [수집요청 및 검색제외](https://searchadvisor.naver.com/guide/request-crawl) — `request-crawl`, 수정 2024-08-12
+- [RSS 및 사이트맵 제출](https://searchadvisor.naver.com/guide/request-feed) — `request-feed`, 수정 2021-10-19
+
+## 웹사이트 검증
+
+- [사이트 간단 체크](https://searchadvisor.naver.com/guide/diagnose-site) — `diagnose-site`, 수정 2019-10-24
+- [URL 검사](https://searchadvisor.naver.com/guide/url-inspection) — `url-inspection`, 수정 2024-12-16
+
+## SEO 리포트
+
+- [콘텐츠 노출 및 클릭](https://searchadvisor.naver.com/guide/report-expose-ctr) — `report-expose-ctr`, 수정 2024-10-30
+- [사이트 진단](https://searchadvisor.naver.com/guide/report-diagnosis) — `report-diagnosis`, 수정 2024-07-10
+- [사이트 최적화](https://searchadvisor.naver.com/guide/report-seo) — `report-seo`, 수정 2020-10-30
+- [수집 현황](https://searchadvisor.naver.com/guide/report-crawl-refine) — `report-crawl-refine`, 수정 2024-08-14
+- [사이트 상태](https://searchadvisor.naver.com/guide/site-summary) — `site-summary`, 수정 2025-03-27
+
+## 구조화된 데이터 마크업
+
+- [구조화된 데이터 소개](https://searchadvisor.naver.com/guide/structured-data-intro) — `structured-data-intro`, 수정 2025-03-24
+- [사이트 연관채널](https://searchadvisor.naver.com/guide/structured-data-channel) — `structured-data-channel`, 수정 2026-04-30
+- [채용정보](https://searchadvisor.naver.com/guide/structured-data-job) — `structured-data-job`, 수정 2025-04-09
+- [주소 (Address)](https://searchadvisor.naver.com/guide/structured-data-address) — `structured-data-address`, 수정 2026-04-30
+- [사이트 이동 경로 (BreadcrumbList)](https://searchadvisor.naver.com/guide/structured-data-breadcrumb) — `structured-data-breadcrumb`, 수정 2026-04-30
+- [하우투 (HowTo)](https://searchadvisor.naver.com/guide/structured-data-howto) — `structured-data-howto`, 수정 2026-04-30
+- [캐러셀 (ListItem)](https://searchadvisor.naver.com/guide/structured-data-carousel) — `structured-data-carousel`, 수정 2026-04-30
+- [평점 (AggregateRating)](https://searchadvisor.naver.com/guide/structured-data-rating) — `structured-data-rating`, 수정 2026-04-30
+- [레시피 (Recipe)](https://searchadvisor.naver.com/guide/structured-data-recipe) — `structured-data-recipe`, 수정 2026-04-30
+- [리뷰 (Review)](https://searchadvisor.naver.com/guide/structured-data-review) — `structured-data-review`, 수정 2026-04-30
+- [식당 (Restaurant)](https://searchadvisor.naver.com/guide/structured-data-restaurant) — `structured-data-restaurant`, 수정 2026-04-30
+- [TV 시리즈 (TVSeries)](https://searchadvisor.naver.com/guide/structured-data-tvseries) — `structured-data-tvseries`, 수정 2026-04-30
+- [영화 (Movie)](https://searchadvisor.naver.com/guide/structured-data-movie) — `structured-data-movie`, 수정 2026-04-30
+- [소프트웨어 (Software)](https://searchadvisor.naver.com/guide/structured-data-software) — `structured-data-software`, 수정 2026-04-30
+- [동영상 검색 (Video Search)](https://searchadvisor.naver.com/guide/structured-data-video) — `structured-data-video`, 수정 2026-03-11
+
+## 제휴 API
+
+- [수집요청 API 명세 및 연동](https://searchadvisor.naver.com/guide/crawl-request-api) — `crawl-request-api`, 수정 2025-07-25
+
+## IndexNow
+
+- [IndexNow 소개](https://searchadvisor.naver.com/guide/indexnow-about) — `indexnow-about`, 수정 2023-07-25
+- [API Key 생성하기 ](https://searchadvisor.naver.com/guide/indexnow-api-key) — `indexnow-api-key`, 수정 2023-07-25
+- [페이지 갱신 요청하기](https://searchadvisor.naver.com/guide/indexnow-request) — `indexnow-request`, 수정 2023-07-25
+- [IndexNow - FAQ](https://searchadvisor.naver.com/guide/indexnow-faq) — `indexnow-faq`, 수정 2023-07-25
+
+## 네이버 검색 교육 자료
+
+- [네이버 웹 검색의 기초](https://searchadvisor.naver.com/guide/education-basic) — `education-basic`, 수정 2020-10-30
+- [웹마스터도구 활용 가이드](https://searchadvisor.naver.com/guide/education-wmt-advanced) — `education-wmt-advanced`, 수정 2019-10-20
+
+## FAQ
+
+- [검색노출 제목 및 설명문 갱신](https://searchadvisor.naver.com/guide/faq-serpedit) — `faq-serpedit`, 수정 2024-12-11
+- [웹 검색 미노출](https://searchadvisor.naver.com/guide/faq-serpmissing) — `faq-serpmissing`, 수정 2026-04-29
+- [웹 검색 제외](https://searchadvisor.naver.com/guide/faq-serpremove) — `faq-serpremove`, 수정 2025-10-14
+- [서브링크 노출](https://searchadvisor.naver.com/guide/faq-sublink) — `faq-sublink`, 수정 2024-11-12
+- [사이트 등록 및 소유확인](https://searchadvisor.naver.com/guide/faq-start-register) — `faq-start-register`, 수정 2020-12-11