Skip to content

Fix SEO indexing issue: Update canonical URLs to docs.expanso.io - #134

Closed
aronchick wants to merge 1 commit into
mainfrom
fix-seo-canonical-urls
Closed

Fix SEO indexing issue: Update canonical URLs to docs.expanso.io#134
aronchick wants to merge 1 commit into
mainfrom
fix-seo-canonical-urls

Conversation

@aronchick

Copy link
Copy Markdown
Contributor

Problem

docs.expanso.io has 527 pages in the sitemap but Google indexes ZERO of them due to a dual-canonical bug.

Root Cause

The Docusaurus config had url: bacalhau.org but the site is deployed to docs.expanso.io. This caused canonical tags to point to wrong domain.

Solution

  • Changed url config from bacalhau.org to docs.expanso.io
  • Updated site branding to match Expanso documentation

Impact

This should resolve the 0% indexing rate and allow Google to index all 527 pages properly.

- Changed url config from 'bacalhau.org' to 'docs.expanso.io'
- Updated site title and branding to match Expanso documentation
- This fixes the dual-canonical bug causing Google to index 0/527 pages

The issue was that Docusaurus was generating canonical tags pointing to bacalhau.org
while the site is deployed to docs.expanso.io, causing Google to see duplicate content
and not index any pages. This change ensures all canonical URLs correctly point to
docs.expanso.io where the content is actually hosted.
@aronchick

Copy link
Copy Markdown
Contributor Author

Closing this PR as it contains an incorrect canonical URL configuration. This PR was changing canonicals to docs.expanso.io instead of docs.bacalhau.org, which would create SEO issues. Bacalhau docs should have canonicals pointing to their actual deployment location (docs.bacalhau.org or bacalhau.org/docs, depending on current redirect setup). A proper SEO audit and fix will be submitted separately.

@aronchick aronchick closed this Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants