409 Conflict

What it means

HTTP 409 Conflict means the request was valid on its own but collides with how the resource currently stands. The classic case is an edit conflict: two clients try to update the same record, and the second one's change is based on a version that has since moved on. The server rejects it rather than silently overwrite someone else's work.

When it happens

It happens with concurrent edits to the same resource, attempts to create something that already exists, or version-control-style conflicts where the client's assumed state no longer matches the server's.

How to fix it

• Fetch the current state of the resource, reconcile the differences, and retry the request.
• Use version identifiers or ETags so clients edit against the latest version.
• For creation conflicts, check whether the resource already exists before trying to create it again.

SEO impact

None directly. It is an API-level state conflict and does not apply to indexable HTML pages.