[P1] Audit: Localized pages are translated but not deeply localized for SEO intent

[baixiangcpp]

Imported from the byteflow.tools deep audit on 2026-06-22.

Problem: the site supports en, zh-CN, zh-TW, ja, ko, de, and fr, but localized pages appear to be mostly direct translations. Local search intent, keyword phrasing, examples, FAQ wording, and terminology are not deeply localized.

Affected pages:

• Locale home pages
• Category pages
• Tool pages
• Cluster/tutorial pages

Reproduction steps:

1. Open /zh-CN, /zh-TW, /ja, /ko, /de, and /fr.
2. Compare titles, headings, tool names, and descriptions against English pages.
3. Search locally relevant terms such as 二维码, 正则表达式, 时间戳, 哈希, JWT 解码.
4. Inspect title/meta content and hreflang mapping.

Expected behavior: localized pages should target local-language search terms and use natural terminology, not only literal translation.

Actual behavior: localization exists, but content depth and keyword adaptation are limited.

Impact: non-English SEO potential is underused, and local-language users may not find or trust the site as easily.

Proposed fix:

• Create locale-specific keyword maps for major tools.
• Rewrite top localized pages with natural local wording.
• Add local examples and FAQs.
• Validate hreflang reciprocity across all languages.
• Prioritize zh-CN and ja for high-intent dev-tool searches first.

Acceptance criteria:

• Top localized tool pages use local keyword variants in title, H1, intro, and FAQ.
• Search works with local-language aliases.
• Hreflang links are reciprocal and canonical tags are locale-correct.
• Localized pages contain examples, not only translated shell text.

[baixiangcpp]

Closed as completed by the canonical BF audit backlog work. This older non-BF audit issue duplicates work now merged through PRs #209-#219, with the BF issues closed and guard/test coverage in place. The remaining non-duplicate follow-up is #7, which stays open because the upstream Next/PostCSS advisory is not fixed yet.