• Resolved andreadelriva

    (@andreadelriva)


    Greetings

    I’ve recently installed the SSL certificate on an old blog where the content date back in 2013. I’ve never used canonical tags before, and went to read yoast KBs. Yet, I’m left with a question.
    I intend to add self-canonical ULR on each post/page. Which prefix should I use, the old http or https on the advanced SEO tab??

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Michael Ti?a

    (@mikes41720)

    Hi,

    The Yoast SEO for WordPress plugin adds canonical URLs to your WordPress install for all content that has been marked for indexing by the search engines. It does this automatically and in 99.9% of the cases, you don’t have to change anything about them.

    In your WP admin dashboard > Settings > General > WordPress Address & Site Address URL, are these already the HTTPS version?

    Does the canonical tag in the page source of one of your posts or pages currently show as HTTP or HTTPS?

    You can learn more about it here — https://yoast.com/help/canonical-urls-in-wordpress-seo/

    Thread Starter andreadelriva

    (@andreadelriva)

    Hi Michael

    In your WP admin dashboard > Settings > General > WordPress Address & Site Address URL, are these already the HTTPS version?

    Yes

    Does the canonical tag in the page source of one of your posts or pages currently show as HTTP or HTTPS?

    Yes in the page source i’m seeing rec canonoical on https prefix.
    I’m assuming that advanced tab for canonical under post/page if for reblogging if the plugin already update to https all url.

    The problem is Google searcv console that is flagging duplicate content. So I tought that adding self canonnical under post/page would fix that.

    Hi @andreadelriva,

    Do you have a redirect set up in your server configuration files to redirect all HTTP URLs to HTTPS? In Google’s recommendations for Site URL changes, they recommend adding 301 redirects and updating all the links on your site to avoid a duplicate content issue.

    If you’ve already updated your site URL and all links in the database, you can leave the canonical URL field blank to use the default settings. It may take some time, but Google will eventually take note of the redirect to HTTPS for your site and remove this warning.

    Thread Starter andreadelriva

    (@andreadelriva)

    Hi @priscillamc

    Do you have a redirect set up in your server configuration files to redirect all HTTP URLs to HTTPS? In Google’s recommendations for Site URL changes, they recommend adding 301 redirects and updating all the links on your site to avoid a duplicate content issue.

    Yes, 301 redirect to HTTPS on server is configured.
    By updating all links, means? The site URL is updated to https on WP settings.

    AS note, I’m using “let’s encrypt trough” cloudways server system. I’ve also Cloudflare CDN enforcing HTTPS set on page rules etc.

    If you’ve already updated your site URL and all links in the database, you can leave the canonical URL field blank to use the default settings. It may take some time, but Google will eventually take note of the redirect to HTTPS for your site and remove this warning.

    I believe I’ve done that part everywhere was needed. I was just left with the doubt about -selfcanonical to add, cause on search console I was seeing duplicated pages on report. I’m coming to agree that it is probably google just slow.

    If your site is redirecting properly from HTTP to HTTPS then it makes the rel canonical tag redundant. So you can leave it blank. Google will eventually find out that the URLs are redirected to the HTTPS version.

    Thread Starter andreadelriva

    (@andreadelriva)

    Thanks for the insights, marking it resolved.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Canonical URL, http or https?’ is closed to new replies.