Support » Plugin: Yoast SEO » Canonical URL doesn’t follow Event URL slug for The Events Calendar plugin

  • Resolved lijndiensten

    (@lijndiensten)


    The events calendar allows for setting a custom URL slug for the main events page, from ‘events’ to – say ‘calendar’.

    The canonical url-tag placed by the Yoast-plugin does not respect this setting and maintains the default ‘events’ as slug. This results in most cases in the canonical url returning a 404, because the events page resides at example.com/calendar and not on example.com/events.

    From the The Events Calendar settings:

    Evenementen URL slug
    De slug gebruikt voor het opbouwen van de evenementen-URL. Je huidige evenementen-URL is: https://example.nl/agenda/

    From the pages <head>:

    <link rel=”canonical” href=”https://example.nl/events/&#8221; class=”yoast-seo-meta-tag”>

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @lijndiensten,

    Thanks for reaching out about the canonical URL of your events archive page. When you change the events slug, I agree the canonical URL doesn’t reflect the change. This is because your previously optimized data is now invalid or incomplete; the invalid data must be removed. Please try the following:

    1. Install & activate the Yoast Test Helper plugin
    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.

    Thread Starter lijndiensten

    (@lijndiensten)

    Hello Maybellyne, that fixed it, thanks a lot!

    Plugin Support Maybellyne

    (@maybellyne)

    I’m glad that resolved the issue!

    This thread was marked resolved as the original poster confirmed the issue no longer occurs on their site.

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