Pretty Links plugin review and common issues

Geographic redirects require ThirstyAffiliates Pro. Go to ThirstyAffiliates → Affiliate Links → [link] → Geo Locations tab. Add country codes and their corresponding destination URLs (e.g., GB → your Amazon.co.uk affiliate URL, DE → your Amazon.de affiliate URL, default → your Amazon.com URL). Geographic detection uses IP geolocation — if testing from the same country as the default destination, the redirect appears not to work. Test with a VPN set to a different country to verify geographic routing. Also ensure ThirstyAffiliates’ GeoIP database is up to date.

Go to ThirstyAffiliates → Settings → Automatic Linking and find the “Maximum links per post” setting. Set a maximum number (e.g., 1 or 2) for how many times each keyword can be linked per post. Also configure “Link the same affiliate link once per page” to prevent the same destination URL from appearing more than once. The keyword limit applies per keyword per post — different keywords can still link separately. For posts where auto-linking is inappropriate (resource pages, tables of contents), use the ThirstyAffiliates per-post setting to disable auto-linking for specific posts.

Health checks use your WordPress server to fetch the destination URL and check the HTTP response code. False positives occur when: (1) the destination website blocks server-side requests (bot detection) — many affiliate platforms block automated HTTP requests while allowing browser access; (2) the destination URL uses JavaScript-based redirects that don’t return a standard HTTP 200 response; (3) your server’s IP is blocked by the destination site; (4) the destination URL requires cookies or session state. If the link works in a browser but fails health checks consistently, mark it as “verified” in ThirstyAffiliates to suppress the false warning.

ThirstyAffiliates supports link categories (Link Categories custom taxonomy). Create categories for each affiliate program (Amazon, Commission Junction, ShareASale, Rakuten, etc.). When creating or editing affiliate links, assign them to the appropriate program category. In the ThirstyAffiliates links list, filter by category to see all links from a specific program. This organization makes program-wide audits and updates easier — if a program changes its URL structure, filter by that program’s category to find and update all affected links.

ThirstyAffiliates adds a “TA” button to the WordPress Classic Editor and a block to the Gutenberg editor. In Classic Editor, highlight the text to link, click the “TA” button, and search for the affiliate link by name or URL — select it to insert it as a standard link. In Gutenberg, the ThirstyAffiliates block allows searching and inserting links via the standard link tool (Ctrl+K) by searching for the affiliate link name. For shortcode insertion anywhere, use the ThirstyAffiliates shortcode: [thirstylink id=”X” link=”Y”].

Yes — ThirstyAffiliates works with Amazon Associates links. Create affiliate links using your Amazon affiliate URLs and ThirstyAffiliates cloaks them to your branded URLs. ThirstyAffiliates Pro adds Amazon Product Advertising API integration, which allows automatically generating affiliate links for products by ASIN and displaying product information (title, image, price, description) pulled from Amazon’s API without manually copying URLs. Note that Amazon’s Associates program terms around link cloaking should be reviewed — compliance requirements vary by market.

ThirstyAffiliates tracks clicks per affiliate link with date-range filtering. The reporting shows total clicks per link and click trends over time, but does not natively show which specific posts or pages generated each click. For post-level attribution (knowing that your “Best Hosting” post generated 50 clicks to your Bluehost link this month), use Google Analytics event tracking or MonsterInsights alongside ThirstyAffiliates — GA tracks click events with the referring page URL, providing the post-level attribution that ThirstyAffiliates’ own tracking does not.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.