preferred-sourcelisted

# Preferred Source **First:** Read the file `~/.claude/skills/seo-references/core.md` before proceeding. Apply the methodology and voice defined there to all output. **Also read:** `~/.claude/skills/seo-references/data-pull-patterns.md` for MCP tool parameter reference. This is an opt-in ranking *frequency and badge* signal. It does not override relevance. It is not a blog program, not a Map Pack substitute, and not a CTA to wallpaper onto every property in a portfolio. Docs: https://developers.google.com/search/docs/appearance/preferred-sources ## Do not force it Issue a **fit verdict** before any snippet. | Verdict | Site type | Action | |---|---|---| | **SHIP** | Newsroom, magazine, research/explainers, company writing on the **root host** | JS popup on the pages people actually finish | | **MAYBE** | Local-service site on the root domain; SaaS/product with real articles on the same host | One button on the 2–3 highest-intent public pages. Not the main lever versus Map Pack or BOFU pages | | **SKIP** | Game, dashboard, calculator-as-app, login-walled tool, `example.com/blog` subdirectory | Print why, stop. Do not invent a blog so you have somewhere to paste the div | Eligibility is the **host**, not a folder. `example.com` and `shop.example.com` can be preferred sources. `example.com/blog` cannot — that path is not a source. Subdomains are separate sources from the root. Do **not** recommend starting informational blogs. Core.md still holds: purchase-intent pages,