chore(seo): establish search indexing and webmaster baseline

[zoeyrose]

Outcome

Give Atrinik maintainers authoritative visibility into how the canonical public site is discovered, crawled, and indexed by Google and Bing, without adding browser analytics, tracking, cookies, or JavaScript.

Why

robots.txt currently permits crawling and advertises the canonical sitemap, while sitemap.xml lists the four public routes. However, manual public searches have not reliably surfaced atrinik.org, and search-result sampling cannot establish whether pages are discovered, excluded, or awaiting processing.

Search Console and Bing Webmaster Tools are the appropriate sources for diagnosing that state. Search engines still decide whether and when to index a page; this issue establishes control and evidence rather than promising rankings.

Scope

• Verify an https://atrinik.org Google Search Console domain property using an explicitly authorized ownership method, preferably a Cloudflare DNS TXT record.
• Verify Bing Webmaster Tools through its supported Search Console import or a separately authorized verification method.
• Submit https://atrinik.org/sitemap.xml to both services and record the initial processing outcome.
• Inspect every canonical, indexable production route for:
  • successful HTTP response;
  • crawl permission;
  • canonical URL;
  • indexing eligibility;
  • sitemap inclusion;
  • redirect or duplicate-canonical problems.
• Confirm www.atrinik.org redirects permanently to the apex and does not create a second indexed site.
• Confirm Cloudflare Pages previews remain excluded through the provider-managed X-Robots-Tag: noindex boundary and that /404.html remains noindex.
• Keep the route inventory, sitemap, canonical metadata, and repository validation synchronized as pages are added.
• Document verification ownership, sitemap submission, inspection procedure, and recovery steps in repository-owned deployment documentation. Record roles and process, not personal account details, credentials, private exports, or verification secrets.
• Create focused follow-up issues for any coverage, redirect, canonical, crawl, or rendering defect found during inspection.
• Do not invent lastmod, changefreq, or priority data that cannot be sourced accurately.

Acceptance criteria

• An authorized maintainer confirms that the Google Search Console and Bing Webmaster Tools properties cover the canonical production site.
• Both services have received the canonical sitemap, and the received/processed state or any reported error is documented.
• Every current indexable production route has been inspected; actionable exclusions or errors have linked follow-up issues.
• Production pages are indexable, previews remain excluded, the 404 remains excluded, and the www hostname resolves to the canonical apex.
• Repository validation fails when the public route contract and sitemap diverge.
• Operational documentation identifies ownership and recovery without publishing credentials, private search data, or personal account information.
• No analytics tag, tracking pixel, browser JavaScript, third-party embed, application cookie, or new live-service dependency is introduced.
• npm run check, npm run build, and git diff --check pass.

Dependencies

Coordinate the canonical-domain and deployment checks with #3. Keep the route and information-architecture contract aligned with #4.

DNS verification requires explicit authorization from the owner of the production Cloudflare zone; this issue does not itself authorize a DNS change.