wp_yoast_indexable duplicates

  • Resolved ronnieee

    (@ronnieee)


    6 years ago

    I’ve indexed the SEO data of my site with Yoast 14.2. The wp_yoast_indexable table has some duplicates, perhaps as the process of building the index had to be restarted a few times.

    The rows are identical except for the id, created_at and updated_at fields. The first id of a duplicate is the one that appears in the wp_yoast_indexable_hierarchy table as the ancestor_id, the others do not.

    Is it safe to delete the duplicate rows, or does Yoast somehow clean them up automatically? I don’t want to re-index as it took a long time to create over 100,000 records and the process slows my site down a lot.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Jeroen Rotty

    (@jeroenrotty)

    6 years ago

    Hi @ronnieee,

    Thank you for reaching out!

    When you interrupt the process and then start again, it should continue where it left off. Can you share a screenshot of the records by any chance to see more detail?

    Thread Starter ronnieee

    (@ronnieee)

    6 years ago

    From the complete index I have about 162 unique duplicates, most of them having 2 or 3 duplicates and a few with up to 10.

    Here’s a screenshot of one with 3 duplicates: https://pasteboard.co/JbdmeLc.png

    All fields have identical data except the first three columns in the screenshot.

    Md Mazedul Islam Khan

    (@mazedulislamkhan)

    6 years ago

    This is odd. There shouldn’t be any duplicate items in the database. Would you mind submitting a bug report directly into our development repository so our development team can look into this further for you?

    Jerlyn

    (@jerparx)

    6 years ago

    Hi @ronnieee ,

    We’re closing this thread because we haven’t heard back from you in a while. Should you have further questions, please open a new thread.

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

The topic ‘wp_yoast_indexable duplicates’ is closed to new replies.

  • 4 replies
  • 4 participants
  • Last reply from: Jerlyn
  • Last activity: 6 years ago
  • Status: resolved