URLs with swcfpc=1 parameter getting indexed

  • Resolved Aquif Shaikh

    (@shaikhaquif)


    4 years, 4 months ago

    Hello,

    From what I know, swcfpc=1 parameter that is added to each link on the page is supposed to be visible only to logged-in users. However, that does not seem to be the case, at least not always. I see organic traffic from Google coming to a URL containing that parameter as shown is SS below. So it’s obvious that Google actually indexed the URL in question.

    https://prnt.sc/tkx8ai

    And I realized it when I contacted the support team of my page builder who pointed out that the swcfpc=1 parameter could be a reason I am facing an issue with a button (Though it wasn’t the case). But the fact that he could see swcfpc=1 parameter even without logging in shows that Google too might be seeing it, and that explains why I see organic traffic from Google.

    Just to clarify, tve=true parameter in the link stated above is used by my page builder while editing the contents of my page. It seems since I am using Table of contents on my page that links to content on the same page, the plugin while trying to add the swcfpc=1 parameter picks up the link used by page builder instead of the original link. You can check the SS of my Table of contents plugin below. The tve=true parameter disappeared after I removed the plugin. So, it is definitely the plugin that is causing the issue.

    https://prnt.sc/tkx9ca

    Would it be possible to just stop adding the swcfpc=1 parameters by default to links on a page? For now, I have disabled the plugin from an SEO perspective. But I really hope you can work on it as I feel this plugin does considerably speed up my page.

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

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Aquif Shaikh

    (@shaikhaquif)

    Just an update. This is what I see in the incognito mode. So yes, I am absolutely right.

    https://prnt.sc/tkxpti

    https://prnt.sc/tkxt6o

    And that’s after I removed the plugin and cleared all possible cache. Something just isn’t right.

    Plugin Contributor iSaumya

    (@isaumya)

    @shaikhaquif Are you using any other caching plugin along with this one?

    Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    Hello,
    maybe the cache buster parameter is added to all internal links on page you are editing with the page builder, so when you click on save button they are stored together with the cache buster.

    Please check if you see the cache buster on internal links added with the page builder before click on save button.

    What is the page builder you are using on your website?

    Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    On version 4.3.0 I added an automatic 301 redirect to “cleaned URL” when a logged out user (like a crawler) try to visit an URL with the cache buster in it.

    However it’s strange and I have to investigate why this happens. I think the code adds the cache buster on internal links in some editor and these are stored into the DB after clicking the save button, but this seems not happens on default wordpress editor.

    If you can, please give me more details.

    Bye!

    Plugin Contributor iSaumya

    (@isaumya)

    I completely agree with you Salvatore. This doesn’t happen while using WP native editor. We have never seen this issue as we strongly follow WP native guidelines and never use any page builder whatsoever. With Gutenberg or classic editor this issue is not there.

    As page builders don’t use the wp hooks properly this can be the reason. They just see what links they are getting in admin and save that to database instead of using wp functions to get the links.

    Plugin Contributor iSaumya

    (@isaumya)

    Also @salvatorefresta, I think you should give an option in the settings page to enable the cache buster 301 redirect as enabling it by default will be a big issue.
    In many cases when any client report an issue with a page, sometimes to test we open the page on an incognito window and check out with vs without cache buster to see if page caching is causing the issue.
    If you made the 301 redirect by default and no settings to disable it, that means no way to test the edge case. Hope you’ll understand.

    Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    I will add the option on next release okay?

    Plugin Contributor iSaumya

    (@isaumya)

    @salvatorefresta Thanks. Looking forward to it. ??

    Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    Option added! Please wait the next release ??

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘URLs with swcfpc=1 parameter getting indexed’ is closed to new replies.