WhereGoes

207 Multi-Status

2xx success

WebDAV response where the body carries an XML document with individual status codes for several sub-requests or separate resources in one batch.

Common causes

  • A PROPFIND walks a collection and reports per-member results.
  • A batch endpoint mixes successes and failures in one call.
  • A multi-resource update partially succeeded.

How to fix it

  • Parse and surface each inner status instead of treating 207 as plain success.
  • Keep the XML body well formed and namespaced for clients.
  • Use 200 with a JSON array for simple batch APIs where XML is unnecessary.

What it means for redirects and SEO

Batch and WebDAV responses are hard for crawlers to parse, so keep indexable HTML out of 207 bodies. Link checkers usually report the inner statuses individually. Client-side rendering can hide content served only as 207.

Related codes