feat(seo): reconcile URLs and author page-one redirects

This commit is contained in:
DeCentN2Madness committed 2026-10-11 00:43:45 +00:00
1 parent 8646792d46
commit 8192ea71c4
11 files changed
+689 -77

No files matched your search

+17 -1
View File
@@ -20,7 +20,16 @@
- HubSpot `?hsLang=...` duplicates are excluded from generated routes.
- AMP variants are excluded because Astro pages are responsive and static.
- Blog pagination and author archive variants are not preserved as separate generated pages.
- Historical note: the initial migration did not preserve Blog pagination or
author archives. Phases 6B.2 and 6B.3 replaced that limitation with generated
English, Spanish, and Arabic Library/author routes derived from the eligible
content catalog. The two English page-6 families remain intentionally absent
until Phase 6C supplies the nine missing source-supported articles.
- Library and author `/page/1` duplicates are represented by nine synchronized
repository redirect definitions, including the three existing service
aliases. Redirect activation on deployed hosts remains separately gated.
- `/search` is a static Library-only compatibility route. It is self-canonical,
`noindex`, sitemap-excluded, and outside the hreflang graph.
- Brief aliases `/aba`, `/autismevaluations`, and `/learnersocialclub` redirect to preserved source URLs.
## Manual Review
@@ -30,5 +39,12 @@
- Organization JSON-LD is emitted globally; service-specific schema still
requires business review.
- Validate social preview images after deployment.
- Activate and verify the approved redirects on the intended hosting stack.
- Decide and test host-level no-slash normalization for prerendered routes;
Astro's static output does not enforce that transport behavior by itself.
- Reconcile the nine missing English articles before accepting
`/library/page/6` or `/library/author/rula-diab/page/6` for cutover.
- Author archives remain `noindex,follow`, sitemap-excluded, and without
hreflang pending separate content/indexability approval.
- Add additional page-specific JSON-LD only after business review of the
appropriate schema.