Title: WordPress error Duplicate Entry
Last modified: February 12, 2024

---

# WordPress error Duplicate Entry

 *  Resolved [fabio.vito83](https://wordpress.org/support/users/fabiovito83/)
 * (@fabiovito83)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/wordpress-error-duplicate-entry/)
 * Dear Support,
 * Suddenly the following error is shown on my website for all product pages:
 * **WordPress database error:** [Duplicate entry ‘3384-0’ for key ‘PRIMARY’]
   `INSERT
   INTO ``wp_yoast_indexable_hierarchy` (`indexable_id`, `ancestor_id`, `depth`,`
   blog_id`) VALUES ('3384', '0', '0', '1')
 * Could you please help me to fix it?
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fwordpress-error-duplicate-entry%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Support [Maybellyne](https://wordpress.org/support/users/maybellyne/)
 * (@maybellyne)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/wordpress-error-duplicate-entry/#post-17422987)
 * Hello [@fabiovito83](https://wordpress.org/support/users/fabiovito83/),
 * Thanks for using the Yoast SEO plugin; please ensure you have updated to v22.0,
   then try the steps below:
    1. Install & activate the [Yoast Test Helper plugin](https://wordpress.org/plugins/yoast-test-helper/)
    2. Go to Tools > Yoast Test
    3. Locate the Yoast SEO section and click on the ‘_Reset indexables tables & migrations_‘,‘
       _Reset Prominent words calculation_‘, and ‘_Reset Internal link counter_‘ buttons.
       After each click, the page will reload to confirm that the specific reset was
       successful.
    4. Go to SEO > Tools, and under SEO data, click the “Start SEO data optimization”
       button to allow Yoast to rescan your content.
 * Please let us know if the reported issue remains after resetting the optimized
   data.
 *  [muranoglassitaly](https://wordpress.org/support/users/muranoglassitaly/)
 * (@muranoglassitaly)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/wordpress-error-duplicate-entry/#post-17430374)
 * Hello [@maybellyne](https://wordpress.org/support/users/maybellyne/),
 * I have a similar issue, I have followed the first 3 steps successfully. However,
   when I tried to do the 4th step, I got this message: “SEO data optimization is
   disabled for non-production environments.” I realized that this is because I 
   am working on a staging environment, not a live website.
 * I read your comment on this topic here: [https://wordpress.org/support/topic/why-is-reindex-disabled-in-non-production/#post-17050126](https://wordpress.org/support/topic/why-is-reindex-disabled-in-non-production/#post-17050126)
   and I understand that this is a feature to prevent unnecessary load on non-production
   sites. My question is: are the first 3 steps enough to fix the issue I reported
   on my staging site (knowing that I have to do full deployment on later stage)?
   Or do I need to do something else to enable the SEO data optimization on my staging
   site?
 * I appreciate your help and support. Please let me know if you need any more information
   from me.
 *  Plugin Support [Maybellyne](https://wordpress.org/support/users/maybellyne/)
 * (@maybellyne)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/wordpress-error-duplicate-entry/#post-17431872)
 * Hello [@muranoglassitaly](https://wordpress.org/support/users/muranoglassitaly/),
   you will still need to run the SEO data optimization. I will recommend waiting
   till you have moved to production before running it.
 *  Thread Starter [fabio.vito83](https://wordpress.org/support/users/fabiovito83/)
 * (@fabiovito83)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/wordpress-error-duplicate-entry/#post-17432984)
 * Dear Maybellyne,
 * I do not feel comfortable to operate on the production site. Productions sites
   are not meant to be used for testing and/or fixing. What happens if your testing
   plugin will not work properly and will break the site?
 * Is there a way for your to allow the database reparation due to the YOAST plugin
   from the staging? why the Yoast Helper Test plugin has this limitation?
 * Best regards,
 * Fabio
 *  [devnihil](https://wordpress.org/support/users/devnihil/)
 * (@devnihil)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/wordpress-error-duplicate-entry/#post-17435648)
 * [@fabiovito83](https://wordpress.org/support/users/fabiovito83/) We understand
   if you don’t want to initially perform this on a live site. What you could do
   is first test on a staging site, and prior to performing it on the live site 
   take a backup of the site so in the event of any problem you can easily restore
   the site.
    We recommend creating regular backups of your site and database for
   your site’s health and safety. A backup is crucial before editing the database
   directly and provides you with a safety net if something were to go wrong. Learn
   more about the [benefits of regular backups](https://yoast.com/help/how-to-backup-your-wordpress-site/).

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘WordPress error Duplicate Entry’ is closed to new replies.

 * ![](https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908)
 * [Yoast SEO - Advanced SEO with real-time guidance and built-in AI](https://wordpress.org/plugins/wordpress-seo/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-seo/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-seo/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-seo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-seo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-seo/reviews/)

 * 5 replies
 * 4 participants
 * Last reply from: [devnihil](https://wordpress.org/support/users/devnihil/)
 * Last activity: [2 years, 3 months ago](https://wordpress.org/support/topic/wordpress-error-duplicate-entry/#post-17435648)
 * Status: resolved