Why your cloaked affiliate links silently rot
The failure mode: link cloakers default to
Pretty Links vs ThirstyAffiliates here:
Pretty Links
— Pros: per-link redirect type toggle, sane defaults
— Cons: free tier locks redirect-type choice behind Pro
ThirstyAffiliates
— Pros: 307 option, link-health add-on
— Cons: 404 checker is a paid extension
My pick: for a site that swaps networks more than once a year, use
Gotcha nobody mentions: Cloudflare 'Cache Everything' page rules will cache a 301 even if your plugin sets no-cache — check the edge, not just the plugin.
Bottom line: 301 your evergreen links, 307 anything a network can rotate.
—
Если тема зашла, посмотри @SpreadBench
The failure mode: link cloakers default to
301 redirects on /go/ or /recommends/ links. A 301 is permanent and aggressively cached — by browsers, by the CDN, sometimes for months. When the affiliate network rotates your tracking URL or you switch from CJ to Impact, returning visitors keep hitting the OLD cached destination. You lose commissions and never see it in logs.Pretty Links vs ThirstyAffiliates here:
Pretty Links
— Pros: per-link redirect type toggle, sane defaults
— Cons: free tier locks redirect-type choice behind Pro
ThirstyAffiliates
— Pros: 307 option, link-health add-on
— Cons: 404 checker is a paid extension
My pick: for a site that swaps networks more than once a year, use
307 (temporary) so nothing gets cached permanently. Slightly worse for crawl signals, far safer for revenue.Gotcha nobody mentions: Cloudflare 'Cache Everything' page rules will cache a 301 even if your plugin sets no-cache — check the edge, not just the plugin.
Bottom line: 301 your evergreen links, 307 anything a network can rotate.
—
Если тема зашла, посмотри @SpreadBench
TablePress vs WP Table Builder: the comparison-table showdown
Both build affiliate comparison tables in WordPress. They are not the same animal.
TablePress
Pros:
— Data lives in a real table you can import/export as CSV
— Free core handles 90% of basic spec tables
Cons:
— Out of the box it renders a plain HTML table, no buttons, no badges
— The good stuff (responsive stacking, row highlighting) is paid add-ons
WP Table Builder
Pros:
— Drag-and-drop cells, so star ratings and CTA buttons take minutes
— Better for visually rich "best of" blocks
Cons:
— Tables are stored as page-builder markup, painful to bulk-edit 40 rows
— Slower to update when 30 products change price
Gotcha nobody mentions: TablePress tables are a nightmare to mark up as a real comparison structure for rich results, because the output is a generic table. You will be hand-adding schema either way.
My pick: TablePress for data-heavy SaaS/spec roundups you update often. WP Table Builder for a single hero "top 5" you design once.
Bottom line: pick by edit frequency, not by looks.
Both build affiliate comparison tables in WordPress. They are not the same animal.
TablePress
Pros:
— Data lives in a real table you can import/export as CSV
— Free core handles 90% of basic spec tables
Cons:
— Out of the box it renders a plain HTML table, no buttons, no badges
— The good stuff (responsive stacking, row highlighting) is paid add-ons
WP Table Builder
Pros:
— Drag-and-drop cells, so star ratings and CTA buttons take minutes
— Better for visually rich "best of" blocks
Cons:
— Tables are stored as page-builder markup, painful to bulk-edit 40 rows
— Slower to update when 30 products change price
Gotcha nobody mentions: TablePress tables are a nightmare to mark up as a real comparison structure for rich results, because the output is a generic table. You will be hand-adding schema either way.
My pick: TablePress for data-heavy SaaS/spec roundups you update often. WP Table Builder for a single hero "top 5" you design once.
Bottom line: pick by edit frequency, not by looks.
Deep dive: dedicated review-schema plugins vs your theme's built-in
Verdict score: 6/10 for most standalone review-schema plugins.
The pitch is seductive: drop a block, get star-rating rich results. Reality is messier.
What they do well:
— Generate valid Review/AggregateRating JSON-LD without you touching code
— Let non-coders add pros/cons and rating breakdowns
Where they fall apart:
— Many still emit self-serving Review markup on your own product pages, which Google has openly deprecated for first-party reviews
— Two plugins both injecting schema = duplicate or conflicting markup, and you will not notice until rich results vanish
Who it's FOR: editorial sites reviewing third-party products, where review snippets are still eligible.
Who it's NOT for: brands reviewing their own SaaS, you will get filtered.
Gotcha nobody mentions: validators say "valid" while Search Console quietly drops the snippet for policy, not syntax. Validation is necessary, not sufficient.
Bottom line: the plugin is the easy 20%; eligibility is the 80% it can't fix.
Verdict score: 6/10 for most standalone review-schema plugins.
The pitch is seductive: drop a block, get star-rating rich results. Reality is messier.
What they do well:
— Generate valid Review/AggregateRating JSON-LD without you touching code
— Let non-coders add pros/cons and rating breakdowns
Where they fall apart:
— Many still emit self-serving Review markup on your own product pages, which Google has openly deprecated for first-party reviews
— Two plugins both injecting schema = duplicate or conflicting markup, and you will not notice until rich results vanish
Who it's FOR: editorial sites reviewing third-party products, where review snippets are still eligible.
Who it's NOT for: brands reviewing their own SaaS, you will get filtered.
Gotcha nobody mentions: validators say "valid" while Search Console quietly drops the snippet for policy, not syntax. Validation is necessary, not sufficient.
Bottom line: the plugin is the easy 20%; eligibility is the 80% it can't fix.