Tyler

Hi @peacepilgrim,

Thank you for reaching out. If your pretty links have been crawled by a search engine in the past, then it’s possible that it could be accessible within the search results even though it’s no longer displayed on your blog.

You could add a “Disallow” rule to your sitemap and exclude all of your pretty links, or if your pretty links have a slug prefix such as “recommends” then you could specify that URI and it should prevent search engines from crawling any pretty link that contains the slug prefix.

Kind regards,

Hi @johnowebcoop,

Thank you for reaching out. This can sometimes occur if our migration scripts didn’t run correctly after updating to a newer version. Could you please try going through the steps in our I save a Link but it doesn’t appear documentation and see if one of those suggestions helps bring those other pretty links back?

Kind regards,

Hi @peacepilgrim,

Thank you for reaching out. If you don’t believe the clicks from these IP addresses are legitimate, then you can exclude them from the Clicks page in Pretty Links by navigating to Wp-Admin -> Pretty Links -> Options -> Reporting and adding those two IP addresses separated by a comma.

I hope this helps!

Kind regards,

Hi @peacepilgrim,

Thank you for reaching out. This is a feature built in to Pretty Links. If you omit the title of the pretty link when it’s being created, then we’ll attempt to automatically fill it out by accessing the target URL you provided for the pretty link and looking at its <title> tag. If the <title> tag is present, then we’ll use that as the link’s title.

I hope this helps!

Kind regards,

Hi @ekaboom,

Thank you for getting back to me. Are you not able to access the PHP file when you’re using multisite, or are you able to access the file but the redirect using that header() function doesn’t run?

I look forward to hearing from you!

Kind regards,

Hi @ekaboom,

Thank you for reaching out. The redirect from the PHP file to the WordPress page likely won’t work since WordPress isn’t being loaded on that PHP file so the code in Pretty Links that handles the redirection can’t run.

I’d recommend adding a call to the header() function at the top of your PHP file you want to redirect, and then you could issue the redirect to your WordPress page using the “Location” header. I’ll provide an example of how that may look below:

header( "Location: https://domain.com/wordpress-page", true, 301 );

This will perform a 301 redirect to https://domain.com/wordpress-page when that PHP file is accessed.

I hope this helps!

Kind regards,

Hi @engrrajonahmed,

Thank you for reaching out. The slug for the Pretty Links can be changed by you when setting up the pretty link, so if you’d like to not include numbers in the slug then you could change the slug by editing the pretty link on the Pretty Links page (Wp-Admin -> Pretty Links): https://share.cspf.co/RBuz0Dem

I hope this helps!

Kind regards,

Hi @banijadev,

I just wanted to follow up on this and let you know that this deprecation notice has been fixed in the latest version of Pretty Links (3.5.3).

I hope this helps!

Kind regards,

Hi @bulutozturk1993,

Thank you for reaching out. This deprecation notice should be removed in the latest version of Pretty Links we just released (3.5.3).

I hope this helps!

Kind regards,

Hi @beogeek,

Thank you for reporting those findings from MonsterInsights to us. I’m not aware of any recent changes to the hook they’re using for tracking server-side redirects within Pretty Links (prli_before_redirect), but I’m glad to hear they were able to locate and straighten out the issue. Please let us know if that update fixes the issue for you.

Kind regards,

Hi @beogeek,

Thank you for that. It looks like whenever I click the pretty link anchored to that “adding more fans”, it’s redirecting me to https://www.bootstrapfarmer.com/products/grow-rack-fans?dt_id=415611%3Bap%3A135483.

When viewing the logs in the browser console, the https://collabs.shop/8fyo90 link (the URL you’re using as the target for the pretty link) is actually performing an additional 302 redirect to the bootstrapfarmer.com site: https://share.cspf.co/X6un4jAx

This may be why Google is recording it as an external redirect since the URL just redirects the user to another page (bootstrapfarmer.com in this case).

You may need to update the target URL for the pretty link so that it links directly to https://www.bootstrapfarmer.com/products/grow-rack-fans?dt_id=415611%3Bap%3A135483, and that should allow Google to pick up the appropriate information.

I hope this helps!

Kind regards,

Hi @beogeek,

Thank you for getting back to me and providing that information. Would it be possible to provide me with the URL to one of your pages/posts where the issue is occurring? I got with one of our developers, and they mentioned that Pretty Links shouldn’t cause this so there might be another plugin or some code in the theme that’s altering the link.

I look forward to hearing from you!

Kind regards,

Hi @banijadev,

Thank you for reaching out. Pretty Links can handle redirects from sites using both HTTPS or HTTP.

I hope this helps!

Kind regards,

Hi @beogeek,

Thank you for reaching out. Just to confirm, is this happening for all of the links on your site, or just the ones created with Pretty Links?

Would it be possible to provide me with a screenshot of what Google Analytics is reporting for those links, and a screenshot of how you have one of your pretty links configured on the Pretty Links Edit page (Wp-Admin -> Pretty Links -> Edit)?

I look forward to hearing from you!

Kind regards,

Hi @banijadev,

Thank you for reaching out and bringing this to our attention. I got with our development team, and we’ll get this deprecation notice addressed in the next release of Pretty Links.

Kind regards,