Problem
Bing currently has limited or delayed presentation quality for mist-arch.com search results. The site has core SEO foundations in place, but Bing search result snippets, sitename/logo signals, indexing freshness, and metadata interpretation still need a careful follow-up pass.
This is a formal client project. SEO improvements should be conservative, low-risk, and grounded in code-level signals we control. Do not treat Bing crawl/index latency as a code defect without evidence from current production HTML.
Scope
Audit and improve low-risk SEO signals that affect search-engine result presentation, especially Bing:
- title and description templates
- route-specific Open Graph and Twitter metadata
- canonical URLs and hreflang alternates
- JSON-LD for Organization, WebSite, and appropriate architecture/local business schema
- robots.txt and sitemap coverage
- favicon, logo, site name, and brand identity signals
- semantic heading structure
- image alt text quality
- performance and accessibility items that affect crawl/render quality
- automated SEO tests and SEO maintenance documentation
Acceptance criteria
- Current production HTML is audited separately from Bing Webmaster snapshots and crawl/index latency.
- Any code changes are limited to low-risk SEO metadata, structured data, semantic markup, tests, or documentation unless the project owner explicitly approves broader changes.
- PR includes before/after evidence for affected routes, using local or production HTML inspection where possible.
- PR links this issue and documents scope, verification commands, screenshots or live proof if relevant, docs impact, risk/rollback, and owner decision needs.
- GitHub Actions pass before review/merge decision.
- SEO documentation is updated if behavior, verification steps, or search submission guidance changes.
Verification
Suggested checks for implementation PRs:
- npm run typecheck
- npm run lint
- npm run build
- npm run test:e2e
- git diff --check
- HTML metadata inspection for /zh, /en, /zh/about, /en/about, sitemap.xml, and robots.txt
- Structured data validation or parsed JSON-LD inspection for affected pages
- Bing Webmaster observations recorded separately as external crawl/index state
Out of scope without explicit owner approval
- merge, release, production deploy, or preview promotion
- Bing Webmaster manual operations, URL submission, or account actions
- production credentials or sensitive account usage
- broad visual redesigns
- customer-visible product behavior changes
- major brand/content-positioning rewrites
- unrelated SEO experiments or keyword stuffing
Problem
Bing currently has limited or delayed presentation quality for mist-arch.com search results. The site has core SEO foundations in place, but Bing search result snippets, sitename/logo signals, indexing freshness, and metadata interpretation still need a careful follow-up pass.
This is a formal client project. SEO improvements should be conservative, low-risk, and grounded in code-level signals we control. Do not treat Bing crawl/index latency as a code defect without evidence from current production HTML.
Scope
Audit and improve low-risk SEO signals that affect search-engine result presentation, especially Bing:
Acceptance criteria
Verification
Suggested checks for implementation PRs:
Out of scope without explicit owner approval