You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bifromq.apache.org by "visoar (via GitHub)" <gi...@apache.org> on 2026/08/12 13:20:42 UTC

[I] [SEO] Define indexation policy for versioned docs and remove duplicate SERP metadata [bifromq-sites]

visoar opened a new issue, #70:
URL: https://github.com/apache/bifromq-sites/issues/70

   Part of #66.
   
   ## Problem
   
   The sitemap currently contains 412 URLs. Of 394 documentation URLs, 337 are under versioned paths. A static audit of the production build found:
   
   - 81 duplicate-title groups
   - 79 duplicate-description groups
   - repeated titles across up to 14 category/content pages
   - titles such as `Auth Provider`, `Event Collector`, `Setting Provider`, and `High Availability` repeated across as many as eight releases
   - descriptions such as `Prerequisites` repeated across 40 pages
   
   Historical docs are useful, but identical snippets and near-duplicate pages make it difficult for search engines and users to identify the current answer. All versions currently self-canonicalize and appear in the sitemap.
   
   ## Proposed work
   
   - Classify releases as current, supported historical, or archived.
   - Keep current and intentionally supported historical documentation indexable.
   - Add the release number to versioned page titles and visible version context near the H1.
   - For archived versions, choose between `noindex,follow`, removal from the sitemap, or canonicalization to a verified equivalent current page. Do not canonicalize pages whose behavior differs by version.
   - Remove low-value generated category routes from the sitemap when they duplicate a content page and provide no unique navigation value.
   - Add a “latest version” link/banner on historical pages without obscuring version-specific instructions.
   
   ## Acceptance criteria
   
   - [ ] The release/indexation matrix is documented.
   - [ ] Versioned pages have distinct, version-aware titles.
   - [ ] The sitemap contains only canonical, intentionally indexable URLs.
   - [ ] Archived pages follow the documented robots/canonical policy.
   - [ ] Duplicate title and description groups are reduced and the remaining duplicates are justified.
   - [ ] Build-time SEO checks prevent accidental reintroduction.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Docs] Define a community-approved indexation policy for versioned documentation [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #70:
URL: https://github.com/apache/bifromq-sites/issues/70#issuecomment-5268247268

   Updated after an ASF-specific policy review: the scope now prioritizes public dev-list governance, Incubator/brand compliance, ASF privacy rules, vendor neutrality, and user/community outcomes. External third-party tracking and SEO link-building are explicitly out of scope.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Docs] Define an indexation policy for versioned documentation [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #70:
URL: https://github.com/apache/bifromq-sites/issues/70#issuecomment-5277075340

   ## Initial GSC processing evidence (2026-08-13)
   
   The canonical property is now owner-verified and `https://bifromq.apache.org/sitemap.xml` was submitted successfully: 124 URLs, 0 sitemap warnings, 0 sitemap errors.
   
   Representative URL Inspection results:
   
   - Current `/docs/get_started/intro/`: `Submitted and indexed`; fetch successful; indexing allowed; user and Google canonical match.
   - Historical `/docs/3.3.x/get_started/intro/`: discovered through the new sitemap, currently not indexed.
   - Archived `/docs/3.2.x/cluster/intro/`: the inspection result still reflects Google’s 2026-08-12 pre-rollout crawl and old duplicate/canonical handling. It must be checked again after recrawl before it can serve as evidence for the deployed `noindex` policy.
   
   Keeping #70 open for the public dev-list policy confirmation and post-recrawl evidence; the sitemap submission itself is healthy.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Docs] Define an indexation policy for versioned documentation [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #70:
URL: https://github.com/apache/bifromq-sites/issues/70#issuecomment-5541944666

   ## GSC follow-up (2026-09-04)\n\nA fresh URL Inspection API check still does not provide the required post-rollout recrawl evidence:\n\n- Current : , , fetch successful, user/Google canonical match; however, the reported last crawl is 2026-08-01, before the rollout.\n- Historical : ; Google has not reported a crawl or fetch yet.\n- Archived : still reports the pre-rollout 2026-08-12 crawl, , and indexing allowed. This remains old evidence and does not represent the deployed  rule.\n\nThe sitemap was last downloaded on 2026-08-28 with 0 warnings and 0 errors. It currently reports 181 submitted URLs because commit  added 57 indexable  pages. That contradicts this issue's version-indexation policy. PR #94 restores the intended 124-URL set by keeping Development accessible but  and out of the sitemap, and adds a generated-site regression check.\n\nKeep this issue open. Re-run the three inspections after #94 deploys and Google recrawls the affected URLs.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Docs] Define an indexation policy for versioned documentation [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #70:
URL: https://github.com/apache/bifromq-sites/issues/70#issuecomment-5371498071

   Status reconciled on 2026-08-21.
   
   The issue body now records the merged/deployed #74 and #80 evidence and marks every technical acceptance item complete. The only remaining item is a representative post-rollout GSC inspection after Google recrawls the current, 3.3.x historical, and 3.2.x archived/noindex samples.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Docs] Define an indexation policy for versioned documentation [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #70:
URL: https://github.com/apache/bifromq-sites/issues/70#issuecomment-5542276750

   The version-indexation policy is implemented and deployed, including the Development-documentation regression fix in #94. The live sitemap is back to 124 URLs and Development pages are accessible with noindex while excluded from the sitemap. Remaining Google recrawl evidence is already tracked in #67, so this issue no longer needs separate handling.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Docs] Define an indexation policy for versioned documentation [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #70:
URL: https://github.com/apache/bifromq-sites/issues/70#issuecomment-5542184961

   ## Development indexation fix deployed (2026-09-04)
   
   PR #94 merged as `4dfeb4af` and deployment run [33884762531](https://github.com/apache/bifromq-sites/actions/runs/33884762531) completed successfully. Live verification now shows:
   
   - exactly 124 sitemap URLs: 57 latest-release docs, 49 historical 3.3.x docs, and 18 shared pages;
   - zero `/docs/development/` URLs in the sitemap; and
   - live Development pages remain accessible with `noindex, nofollow`.
   
   The technical regression is resolved and protected by the generated-site check. This issue still remains open only because Google has not yet recrawled the representative current, historical, and archived URLs recorded above.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Docs] Define an indexation policy for versioned documentation [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar closed issue #70: [Docs] Define an indexation policy for versioned documentation
URL: https://github.com/apache/bifromq-sites/issues/70


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Docs] Define an indexation policy for versioned documentation [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #70:
URL: https://github.com/apache/bifromq-sites/issues/70#issuecomment-5275513504

   Post-#74 deployment verification (partial acceptance; keeping this issue open):
   
   Implemented and verified:
   - [x] #74 merged as `8ede95a5cf750249cd1710da0b58e095ff10fddf`.
   - [x] Master deployment succeeded: https://github.com/apache/bifromq-sites/actions/runs/31662011013
   - [x] Deployed 3.3.x pages are labeled historical/unmaintained and remain indexable.
   - [x] Deployed 3.2.x and earlier pages remain accessible and include `noindex, nofollow`, archived version labels, and the unmaintained notice.
   - [x] The deployed sitemap contains 124 intentional indexable URLs, including 49 from 3.3.x and none from 3.2.x or earlier.
   - [x] Final #80 validation enforces per-page canonical paths and exact 124/124 canonical/sitemap parity.
   - [x] Build-time regression checks are active in the deploy workflow.
   
   Still required before closure:
   - [ ] Link the public dev-list confirmation of the release/indexation matrix and rationale.
   - [ ] After search engines process the new sitemap/noindex rules, record representative GSC inspection or coverage evidence in #67/#70.
   
   The deployed technical policy is complete, but the public governance/search-processing evidence is not yet linked, so #70 remains open.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org