# TailMux off-site SEO/GEO checklist

Repository changes cannot complete these actions because they require ownership,
credentials, or deployment access. Check each item only after the production
build containing the corresponding route has been deployed.

## 1. Google Search Console

**URL:** https://search.google.com/search-console
**Property:** URL-prefix property for https://tailmux.app/ (or the verified
domain property if CQ Fabrication manages it centrally).

| Action | Verification requirement | Expected outcome |
|---|---|---|
| Add/verify property | DNS, HTML file, tag, or existing Cloudflare-integrated verification under the TailMux owner | Search Console can inspect canonical production URLs. |
| Submit sitemap | https://tailmux.app/sitemap.xml | Main sitemap is read with only indexable HTML canonicals. |
| Inspect primary URLs | /, broad guide, macOS guide, Linux guide, /docs/limitations | Google-selected canonical matches declared canonical and rendered content is visible. |
| Inspect Markdown alternate | one .md URL | It is crawlable for retrieval but excluded from normal index via X-Robots-Tag. |
| Monitor Pages report | noindex, duplicate, crawled-not-indexed, soft-404 groups | Expected intentional exclusions only. |
| Review Performance queries | branded and non-branded map in docs/seo-geo-query-map.md | Establish a dated baseline before content iteration. |

## 2. Bing Webmaster Tools and Copilot search surface

**URL:** https://www.bing.com/webmasters/
**Site:** https://tailmux.app/

| Action | Verification requirement | Expected outcome |
|---|---|---|
| Add/verify site | DNS/meta/file verification under an authorized account | Bing can report crawl/index health. |
| Submit sitemap | https://tailmux.app/sitemap.xml | Sitemap parses without non-HTML alternate duplication. |
| Use URL Inspection | homepage, broad guide, flagship macOS guide, limits page | Bingbot sees 200 SSR HTML, title, canonical, and no accidental noindex. |
| Review crawl information | response errors, blocked URLs, crawl rate | No avoidable 4xx/5xx or bot blocks. |
| Validate robots behavior | Bing-specific group repeats private-path exclusions when such a group exists | Bot-specific directives do not override account/API protections. |

## 3. Cloudflare production, DNS, and bot policy

**URL:** https://dash.cloudflare.com/
**Zone:** tailmux.app

| Action | Verification requirement | Expected outcome |
|---|---|---|
| Confirm canonical host | DNS and redirect rules for HTTP, www, apex, and trailing slash | One public canonical HTTPS host; alternate hosts redirect once. |
| Inspect WAF/Bot events | test or log evidence for Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, Claude-User, PerplexityBot, and user-initiated fetchers | Desired search/retrieval agents receive 200 for public HTML and machine-readable resources. |
| Confirm training policy | observe GPTBot and ClaudeBot against robots policy; decide Google-Extended trade-off explicitly | Policy is deliberate, documented, and not overridden by a WAF rule. |
| Add verified-bot exceptions only if needed | use provider verification, not user-agent string alone | No broad bot bypass or weakened security posture. |
| Set cache behavior | public text files have short, revalidatable caching; immutable only for hash-addressed assets | LLM files, robots, sitemap, and social metadata refresh after deployment. |
| Log dashboard | use fields in seo-geo-measurement-plan.md | Crawler, raw-file, 404, and WAF evidence is reviewable. |

## 4. GitHub repository presence

**Repository:** https://github.com/CQ-Fabrication/tailmux

| Action | Required content | Expected outcome |
|---|---|---|
| Repository description | “Access multiple Tailscale tailnets simultaneously on macOS and Linux.” | Search/result snippets identify the right TailMux entity. |
| Homepage URL | https://tailmux.app | GitHub and search surfaces point to the official site. |
| Topics | tailscale, tailnet, multiple-tailnets, multi-tailnet, macos, linux, networking, vpn, tsnet, developer-tools, zero-trust, cli | Relevant discovery without unrelated tmux framing. |
| README opening | same literal product definition and non-affiliation note | GitHub code/repository retrieval agrees with the site. |
| Releases | concise technical release notes plus canonical documentation/release link | Version discovery is consistent with site metadata. |
| Social preview | verify current og image/title after a release | Shared GitHub links identify the product and category. |

Do not edit repository description, topics, release pages, or organization
settings from this implementation unless an authenticated GitHub workflow and
explicit approval are available.

## 5. Package/distribution metadata

| Surface | URL or location | Manual action |
|---|---|---|
| Homebrew tap | https://github.com/CQ-Fabrication/homebrew-tap | Ensure formula/cask description uses the same multi-tailnet wording and links to tailmux.app. |
| Release asset host | https://assets.tailmux.app | Verify signed release URLs return 200, have durable filenames, and match current version metadata. |
| Install documentation | https://tailmux.app/docs/installation | Test cask/formula commands from a clean environment after each release. |

## 6. Public profiles and launch pages

Only update a profile that is genuinely official and already owned by CQ
Fabrication. For each one, use the same one-sentence definition, canonical URL,
official logo, and non-affiliation wording when space permits.

Potential surfaces:

- CQ Fabrication product page;
- Product Hunt launch assets already present under site/press-kit/producthunt;
- official GitHub organization profile/repository;
- verified social accounts, if any;
- technical community posts that link to the broad guide rather than a generic
  home-page UTM campaign.

Do not create invented social accounts, review profiles, customer testimonials,
or comparison claims.

## 7. Post-deploy validation record

Record the following in the release/operations log:

1. deployment URL and commit SHA;
2. time production changed;
3. robots, sitemap, llms, llms-full, one HTML page, and one Markdown page
   response headers;
4. Search Console/Bing submission time;
5. Cloudflare WAF/crawler result;
6. first crawl and first index/canonical result;
7. any open external follow-up with owner and due date.
