Skip to content

ops: decide canonical domains for FerrTrack/FerrVault/FerrGrowth (currently subdomains) #5

@BryanFRD

Description

@BryanFRD

Three product sites currently sit on subdomains of ferrlabs.com because the apex domains weren't acquired:

Site Current Target (TODO)
FerrTrack https://track.ferrlabs.com https://ferrtrack.com
FerrVault https://vault.ferrlabs.com https://ferrvault.com
FerrGrowth https://growth.ferrlabs.com https://ferrgrowth.com

robots.txt and Layout meta tags carry # TODO(domain) markers. Each site has its own sitemap pinned to the subdomain — when domains are acquired, need to:

  1. Acquire domains (registrar choice + WHOIS privacy)
  2. Update DNS (Cloudflare → cluster ingress)
  3. Add Traefik IngressRoute alongside the subdomain (don't break existing)
  4. Update each repo's:
    • astro.config.mjs site: field
    • robots.txt Sitemap URL
    • Per-site Footer/Navbar links (currently link to ferrlabs.com cross-product)
  5. 301 redirect subdomain → apex once stable
  6. Submit sitemap to Google Search Console (new property)

Tracking here so we don't lose context. Each repo can have its own follow-up issue once domains are owned.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions