-- WARNING: TEST THIS ON A STAGING DATABASE FIRST!
UPDATE posts_table
SET post_content = REPLACE(
    post_content,
    '<a href="https://affiliate-partner.com',
    '<a rel="sponsored nofollow" href="https://affiliate-partner.com'
)
WHERE post_content LIKE '%<a href="https://affiliate-partner.com%';

Pro Tip: Never, ever run a write query like this directly on `prod-db-01` without testing it in a staging environment. A small syntax error in your `REPLACE` function can mangle thousands of posts instantly. Measure twice, cut once.

Solution 2: The ‘Do It Right’ Permanent Fix (Code-Level Change)

The database hack is a patch. The real problem is in the code that’s generating the links. Your goal here is to find the template, component, or function that renders these affiliate links and fix it at the source. This ensures all *future* links are correct, too.

Look for the file in your codebase that handles this. It might be a PHP template, a React component (`.jsx`), or a backend helper function. You’re looking for something like this:

The broken code might look like this (in a simplified PHP example):

<?php
function render_affiliate_link($url, $text) {
    return '<a href="' . htmlspecialchars($url) . '">' . htmlspecialchars($text) . '</a>';
}
?>

The fix is simple and permanent:

<?php
function render_affiliate_link($url, $text) {
    // We add the rel attribute here so it's always included
    return '<a rel="sponsored nofollow" href="' . htmlspecialchars($url) . '">' . htmlspecialchars($text) . '</a>';
}
?>

Once you deploy this change, all new and dynamically rendered links will be correct. You might still need to run the Solution 1 database script to fix the old, hard-coded content that was already saved.

Solution 3: The ‘Break Glass In Case of Emergency’ Fix (Server-Side Rewrite)

This is my “nuclear option.” Let’s say you can’t get a code deploy out for 24 hours but the business is demanding an immediate fix. You can actually modify the HTML response *on-the-fly* at the web server or load balancer level. It feels hacky because it is, but it’s incredibly effective in a pinch.

If you’re using Nginx, you can use the `sub_filter` module. You would add something like this to your server block configuration for the relevant location:

# In your nginx.conf or site-specific conf file
location / {
    # Replace the first instance of a link with the fixed version
    sub_filter_once on;
    sub_filter '<a href="https://affiliate-partner.com' '<a rel="sponsored nofollow" href="https://affiliate-partner.com';
    # ... your other proxy_pass or try_files directives
}

This tells Nginx to inspect the HTML coming from your application server and perform a quick search-and-replace before sending it to the user. It’s a powerful tool, but it adds a tiny bit of latency and can have unintended side effects if your pattern is too broad. Use it as a temporary bridge, not a permanent foundation.

Which Fix Should You Choose?

Here’s how I think about it. Every situation is different, so pick the tool that fits the job.

So, take a deep breath. You haven’t ruined the company. It’s a common oversight that shows you’re moving fast. The mark of a good engineer isn’t never making mistakes; it’s knowing how to analyze the problem, evaluate the trade-offs, and implement a clean fix under pressure. Now, go grab a coffee. You’ve earned it.

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions