[WIP] Apply SEO fixes to links and meta tags

[Copilot]

• Explore repository structure and identify target files
• Analyze current state of HTML files for SEO elements
• WebSite/en/index.html: Fix BreadcrumbList URL to English canonical, update meta description, add robots meta
• WebSite/index.html: Add robots meta tag (index,follow)
• WebSite/blog.html: Add robots meta tag (index,follow), verify canonical/og:url
• WebSite/portfolio.html: Change robots from noindex to index,follow
• Validate HTML syntax of all changes
• Run code review
• Run security scan

Original prompt

Create a new branch named seo/fix-hreflang-og-robots-index based on the develop branch and apply the following conservative non-invasive SEO fixes across these files: WebSite/en/index.html, WebSite/index.html, WebSite/blog.html, WebSite/portfolio.html. Commit changes and open a PR from seo/fix-hreflang-og-robots-index into develop. Provide PR URL and concise PR description (English + Japanese) and reviewer checklist.

Required edits (precise):

1. WebSite/en/index.html (English home)

• Ensure a self-canonical exists and equals: https://breadmotion.github.io/WebSite/en/index.html (add or replace ).
• Add explicit hreflang alternate links (each on its own line):
• Set to https://breadmotion.github.io/WebSite/en/index.html (must match canonical).
• Localize BreadcrumbList JSON-LD 'name' values to English (e.g. "Home") and ensure breadcrumb item URLs point to the en canonical where appropriate.
• Ensure is an English SEO-friendly short sentence (e.g. "PanKUN — Portfolio and works (Unity, C#, UE5, Discord bots, and developer tools).").
• Do not modify body/layout content.

2. WebSite/index.html (Japanese home)

• Confirm or set self-canonical to https://breadmotion.github.io/WebSite/ (keep as-is if already correct).
• Add/ensure hreflang alternates (each on its own line):
• Ensure equals https://breadmotion.github.io/WebSite/.
• Do not modify body/layout content.

3. WebSite/blog.html and WebSite/portfolio.html

• Replace with in both files.
• Ensure each file has that points to the page's canonical URL:
  • blog.html -> https://breadmotion.github.io/WebSite/blog.html
  • portfolio.html -> https://breadmotion.github.io/WebSite/portfolio.html
• Ensure matches the canonical in each file.
• Do not modify body/layout content.

4. Minor consistency

• Expand any inlined multiple href/hreflang tags into separate lines for readability in the modified files.
• Confirm or add on both home pages.

Constraints and expectations:

• Do NOT change sitemap.xml or robots.txt.
• Keep edits minimal and conservative; only head/meta/JSON-LD and robots meta where specified.
• Validate head tag syntax to avoid malformed HTML.
• Commit messages (use one or multiple commits) should be concise, e.g.:
  • chore(seo): align en canonical/og
  • chore(seo): add hreflang alternates
  • chore(seo): enable indexing for blog & portfolio
  • chore(seo): localize breadcrumb JSON-LD (en)

PR details:

• Branch: seo/fix-hreflang-og-robots-index (created from develop)
• Base: develop
• Title: "SEO: Fix hreflang, OG canonical and enable index for blog & portfolio"
• PR body: include English and Japanese summary, reason, and a reviewer checklist (see below).

Reviewer checklist to include in PR body:

• Root redirect unchanged (root index.html still redirects to /WebSite/)
• WebSite/en/index.html: canonical and og:url are https://breadmotion.github.io/WebSite/en/index.html, BreadcrumbList names are English
• WebSite/index.html: canonical and og:url are https://breadmotion.github.io/WebSite/
• hreflang alternates present on both home pages (ja, en, x-default)
• WebSite/blog.html & WebSite/portfolio.html: meta robots are index,follow and canonical/og:url match
• No layout/content changes beyond head/meta/JSON-LD and robots meta
• Run Google Rich Results Test on a sample blog post to confirm BlogPosting JSON-LD validity

Testing notes for reviewer (add to PR body):

• Open WebSite/en/index.html and verify og:url/canonical and breadcrumb names.
• Open WebSite/blog.html and WebSite/portfolio.html and verify robots and canonical/og:url.
• Run Google Rich Results Test for a sample blog post (e.g. /WebSite/blog/blog_00001.html) to ensure structured data is valid.

If any of the target files on develop differ from expectations, update them conservatively and list files that required manual inspection in the PR description. Provide the PR URL on completion.

Do not include secrets.

This pull request was created as a result of the following prompt from Copilot chat.

Create a new branch named seo/fix-hreflang-og-robots-index based on the develop branch and apply the following conservative non-invasive SEO fixes across these files: WebSite/en/index.html, WebSite/index.html, WebSite/blog.html, WebSite/portfolio.html. Commit changes and open a PR from seo/fix-hreflang-og-robots-index into develop. Provide PR URL and concise PR description (English + Japanese) and reviewer checklist.

Required edits (precise):

1. WebSite/en/index.html (English home)

• Ensure a self-canonical exists and equals: https://breadmotion.github.io/WebSite/en/index.html (add or replace ).
• Add explicit hreflang alternate links (each on its own line):
• Set to https://breadmotion.github.io/WebSite/en/index.html (must match canonical).
• Localize BreadcrumbList JSON-LD 'name' values to English (e.g. "Home") and ensure breadcrumb item URLs point to the en canonical where appropriate.
• Ensure is an English SEO-friendly short sentence (e.g. "PanKUN — Portfolio and works (Unity, C#, UE5, Discord bots, and developer tools).").
• Do not modify body/layout content.

2. WebSite/index.html (Japanese home)

• Confirm or set self-canonical to https://breadmotion.github.io/WebSite/ (keep as-is if already correct).
• Add/ensure hreflang alternates (each on its own line):
• Ensure equals https://breadmotion.github.io/WebSite/.
• Do not modify body/layout content.

3. WebSite/blog.html and WebSite/portfolio.html

• Replace with in both files.
• Ensure each file has that points to the page's canonical URL:
  • blog.html -> https://breadmotion.github.io/WebSite/blog.html
  • portfolio.html -> https://breadmotion.github.io/WebSite/portfolio.html
• Ensure matches the canonical in each file.
• Do not modify body/layout content.

4. Minor consistency

• Expand any inlined multiple href/hreflang tags into separate lines for readability in the modified files.
• Confirm or add on both home pages.

Constraints and expectations:

• Do NOT change sitemap.xml or robots.txt.
• Keep edits minimal and conservative; only head/meta/JSON-LD and robots meta where specified.
• Validate head tag syntax to avoid malformed HTML.
• Commit messages (use one or multiple commits) should be concise, e.g.:
  • chore(seo): align en canonical/og
  • chore(seo): add hreflang alternates
  • chore(seo): enable indexing for blog & portfolio
  • chore(seo): localize breadcrumb JSON-LD (en)

PR details:

• Branch: seo/fix-hreflang-og-robots-index (created from develop)
• Base: develop
• Title: "SEO: Fix hreflang, OG canonical and enable index for blog & portfolio"
• PR body: include English and Japanese summary, reason, and a reviewer checklist (see below).

Reviewer checklist to include in PR body:

• Root redirect unchanged (root index.html still redirects to /WebSite/)
• WebSite/en/index.html: canonical and og:url are https://breadmotion.github.io/WebSite/en/index.html, BreadcrumbList names are English
• WebSite/index.html: canonical and og:url are https://breadmotion.github.io/WebSite/
• hreflang alternates present on both home pages (ja, en, x-default)
• WebSite/blog.html & WebSite/portfolio.html: meta robots are index,follow and canonical/og:url match
• No layout/content changes beyond head/meta/JSON-LD and robots meta
• Run Google Rich Results Test on a sample blog post to confirm BlogPosting JSON-LD validity

Testing notes for reviewer (add to PR body):

• Open WebSite/en/index.html and verify og:url/canonical and breadcrumb names.
• Open WebSite/blog.html and WebSite/portfolio.html and verify robots and canonical/og:url.
• Run Google Rich Results Test for a sample blog post (e.g. /WebSite/blog/blog_00001.html) to ensure structured data is valid.

If any of the target files on develop differ from expectations, update them conservatively and list files that required manual inspection in the PR description. Provide the PR URL on completion.

Do not include secrets.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.