Document Library Pro plugin review and common issues

A 404 on a pretty link indicates the rewrite rule is not working. Fix steps: (1) go to Settings → Permalinks and click Save Changes — this flushes WordPress rewrite rules and usually resolves the issue immediately; (2) verify the pretty link slug does not conflict with an existing post or page slug; (3) ensure Pretty Links is active and not deactivated; (4) if using Nginx (not Apache), Nginx does not automatically read .htaccess — server-level rewrite rules may need to be added by your hosting provider; (5) check if a security plugin is blocking the rewrite.

Click tracking relies on Pretty Links processing the redirect before forwarding to the destination. If tracking is stuck at 0: (1) test the pretty link directly in an incognito browser window (not while logged in as admin — some versions exclude admin clicks from tracking); (2) verify the redirect goes through Pretty Links’ PHP processing (not a server-level cached redirect); (3) page caching should not affect click tracking since pretty links redirect without a cached page serving, but check if a caching plugin is serving a cached version of the redirect; (4) verify the database has write access for updating click counts.

Go to Pretty Links → Settings → Auto-Link and configure the auto-link limitations: (1) set a maximum per-page occurrence limit (e.g., maximum 2 links per keyword per page) to prevent the same keyword linking multiple times; (2) enable “Use No Follow” and “Open in New Tab” for all auto-links as appropriate; (3) exclude specific pages or post types from auto-linking; (4) reduce the keyword list to only the most important affiliate keywords rather than all brand names; (5) the auto-link should not add links inside headings or navigation by default — if it is, check for theme-specific hook conflicts and report to Pretty Links support.

Go to Pretty Links → Add New Link. In the Target URL field, paste your full Amazon affiliate URL (including your Associate tag). In the Pretty Link field, enter your chosen path (e.g., /go/kindle or /recommend/book-title). Select redirect type (302 for affiliate links is often recommended over 301 to prevent caching of the redirect by browsers). Enable Nofollow and mark as “Sponsored” for Google compliance with affiliate link disclosure requirements. Save. The pretty link yoursite.com/go/kindle now redirects to your Amazon affiliate URL.

With Pretty Links Pro: after creating the pretty link for the brand’s affiliate URL, go to the link settings and enable Auto-Link. Add the keywords you want to auto-link (e.g., “Bluehost,” “Bluehost hosting,” “Bluehost review”). Set the maximum links per page (typically 1-2 to avoid over-linking). Save. Pretty Links now automatically converts every unlinked mention of those keywords in your posts and pages into affiliate links — retroactively for all existing content and automatically for all future content.

Both plugins handle the core affiliate link cloaking use case. Pretty Links is more beginner-friendly with a simpler interface and the Auto-Link feature makes it particularly strong for bloggers monetizing through affiliate content. ThirstyAffiliates has stronger affiliate-specific features: geographic redirects (send US visitors to Amazon.com, UK visitors to Amazon.co.uk automatically), better link categorization for large affiliate portfolios, and Amazon API integration for automatic link replacement. For general bloggers, Pretty Links is typically the simpler starting point. For serious affiliate marketers with geographic targeting needs or large link libraries, ThirstyAffiliates has more affiliate-specific power.

Amazon Associates program terms historically prohibited link cloaking (hiding the amazon.com destination URL). Pretty Links does allow creating clean links that redirect to Amazon, which technically cloaks the URL. Amazon’s terms on this evolve — check the current Amazon Associates Operating Agreement for the most up-to-date rules on link display requirements. Many affiliates use Pretty Links with Amazon successfully by ensuring the final destination (amazon.com) is disclosed and the redirect is immediate without content modification. Consult the Associates program terms directly for compliance guidance.

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.