Medium Interactive

MDI HTTP Referer Block enables WordPress site owners to detect and control user experience based on the origin of traffic. By analyzing the HTTP referrer (both server-side via PHP and client-side via JavaScript when headers are missing), this plugin makes it easy to apply different behavior for visitors arriving from ads, social platforms, or syndicated search networks.
You can define specific referrer domains or patterns, and when a visitor matches those conditions, the plugin can:
<ul>
<li>Display a small notification (server-side) showing the detected referrer host or path.</li>
<li>Hide or reveal specific elements on your site using CSS selectors.</li>
<li>Redirect visitors from certain sources to a different URL.</li>
</ul>
This gives marketers, advertisers, and site owners fine control over how different audiences see the site.
Example use cases:
<ul>
<li>Hide contact forms when users arrive through syndicated search traffic to prevent spam or low-quality leads.</li>
<li>Hide pricing details when a user comes from social media to encourage engagement before pricing exposure.</li>
<li>Redirect visitors from affiliate networks to a dedicated landing page.</li>
<li>Show a simple banner confirming that the user arrived via a partner campaign.</li>
</ul>
The plugin sets a tracking cookie (<code>mdi_syndicated_ref</code>) to remember the detected source for the configured number of days, ensuring consistent visibility rules on repeat visits.
MDI HTTP Referer Block helps you tailor on-site experiences dynamically based on real visitor origin — simple, server-side controlled, and privacy-respecting.
For a full guide on blocking syndicated search traffic (e.g., Google Ads Performance Max), see: 
https://mediuminteractive.com/how-to-block-syndicated-search-traffic-from-performance-max-campaigns-in-google-ads/

MDI HTTP Referer Block

Hide elements or redirect users based on referrer domains. Useful for blocking partners, scrapers, or altering content per source.

m.greiling

EN:
Displays google image search results in admin backend. Exploits information from HTTP_REFERER data of many wordpress statistic tools. 
The requirement for this to work is that the statistic tool captures the HTTP_REFERER with a timestamp or date field in the same record.
Settings:
Thumbnail size depends on user theme, usually 150×150 pixels – this can be changed 
Set how many thumbnails are displayed (realtime) 
Set how many thumbnails are displayed by month (rank 1 – n) 
Set in which table information is stored (without leading prefix) 
Set name of column containing HTTP_REFERER (works best with TEXT or VARCHAR > 500) 
Set name of column containing DATE or DATETIME or TIMESTAMP 
The URL of your blog will be removed through processing. Additional strings like outdated or old URL can also be removed, when entered.
DE:
Zeigt die Bilder im Backend an, die in der Google-Bildersuche aufgerufen wurden und auf den Blog führten. Die Darstellung im Backend erfolgt in der Thumbnail-Größe des Themes. Suchbegriffe, die mitübertragen wurden, werden ebenfalls angezeigt.
Einstellungen:
Thumbnail-Größe, die während dem Hochladen in die Mediathek automatisch generiert wurde (z.B. 150×150). 
Anzahl der Bilder, die bei der ‘Live’-Ansicht angezeigt werden sollen (Ohne Tabellen-Präfix) 
Wie viele Bilder sollen in der monatlichen Übersicht angezeigt werden (Plätze 1 – n) 
Name der Spalte, in der der HTTP_REFERER abgelegt wurde (am Besten ist der Datentyp TEXT oder ein VARCHAR > 500) 
Name der Spalte, in der ein Datum zu dem Aufruf abgelegt wurde (DATE, DATETIME oder TIMESTAMP) 
Während der Verarbeitung wird die URL des Blogs entfernt, sollte der Blog während der statistischen Erfassung die URL einmal gewechselt haben, kann hier ein String eingetragen werden, der ebenfalls entfernt wird
<h3>Known issues</h3>
EN:
Header Images won’t be displayed correctly
DE:
Header-Bilder werden nicht korrekt angezeigt

imgResultsFromReferer

Displays google image search results in admin backend. Exploits information from HTTP_REFERER data of many wordpress statistic tools.

MDI HTTP Referer Block vs imgResultsFromReferer