• Resolved fpeppe

    (@fpeppe)


    I have enabled the rich snippet feature on the Trustindex widget, but it’s not displaying correctly on my website, dadart.it. Could you help me resolve this issue? I would appreciate guidance on what might be causing the problem and how to fix it.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Laca

    (@lacadev)

    Hi @fpeppe

    Thank you for bringing this issue to our attention!
    We’re looking into it and will get back to you as soon as possible with a solution.

    We appreciate your patience and understanding.

    Kind regards,
    Laca from Trustindex

    Plugin Support Laca

    (@lacadev)

    Hi @fpeppe

    We’ve resolved the issue related to the rich snippet.
    Could you please check and confirm if everything looks correct on your end as well?

    https://search.google.com/test/rich-results/result?id=OQDvO2e89aJYgUfxaSTffA

    Kind regards,
    Laca from Trustindex

    Thread Starter fpeppe

    (@fpeppe)

    Hi,

    Thank you for looking into this. Unfortunately, the issue with the rich snippet is not fully resolved on my end. I still don’t see the review snippet appearing. However, when I manually test the code for inserting the rich snippet, it does appear correctly.

    Could you please investigate this further?

    FPEPPE

    Plugin Support Laca

    (@lacadev)

    Hi @fpeppe,

    The rich snippet added by the widget can be seen in the source code of the page. The rich snippet is not visible on the frontend of your website; it is read by Google’s index.

    https://snipboard.io/6N3cim.jpg

    I apologize if I misunderstood your issue. Could you please provide more details about your concern? The explanation above may not fully address your question.

    Kind regards,
    Laca from Trustindex

    Plugin Support Lídia from Trustindex

    (@liditrudex)

    Let us know if we can help you with anything!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.