Will I get duplicate posts?
No, as long as each row keeps its record ID: a known ID is always an update, and retries and repeated files never create a second copy. A few situations can still create one.
- 1 min read
- Updated October 13, 2026
Not if each item keeps the same record ID in every file. A known ID is always an update; uploading the same file twice finds everything unchanged; Retry safely resends the same operation and cannot create a second copy.
Duplicates only appear when the identity changes: new record IDs, a changed title in a configuration without IDs, or content that was already on your site before Content Uploader published to it (it only recognises what it published itself). In each case the review shows the rows as new before you publish.
How Content Uploader avoids duplicates lists every safeguard and every exception.
Was this article helpful?
Related articles
- Reviewing and publishingHow Content Uploader avoids duplicates, and when duplicates can still happenThe safeguards that stop an item being published twice (record IDs, the review, the last check, safe retries) and the few cases where two copies can still happen.
- TroubleshootingI have two copies of the same article on my siteHow to tell which copy Content Uploader owns, why a duplicate appeared, how to remove the extra one safely and how to stop it happening again.
- Importing dataChoose the record IDThe record ID column lets next week's file update an item instead of creating it twice: what makes a good ID, how matching works without one, and what changing it does.
- Getting startedImportant concepts and terminologyThe words this documentation and the app use, in the order you meet them: workspace, site, connector, configuration, record ID, run and more.