{"id":14998,"date":"2026-10-30T23:11:38","date_gmt":"2026-10-30T22:11:38","guid":{"rendered":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/"},"modified":"2026-10-30T23:25:19","modified_gmt":"2026-10-30T22:25:19","slug":"wordpress-redirects-another-site-malicious-redirect","status":"publish","type":"post","link":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en","title":{"rendered":"WordPress redirects to another site: recognise and resolve a malicious redirect"},"content":{"rendered":"<style>body.postid-14998 article p,body.postid-14998 article li{color:#595959}body.postid-14998 h3.entry-title.mkdf-post-title{display:none!important}@media(max-width:768px){body.postid-14998 #menu-icon{position:absolute!important}body.postid-14998 #mkdf-back-to-top{display:none!important}}<\/style>\n<h1>WordPress redirects to another site: recognise and resolve a malicious redirect<\/h1>\n<p><strong>Your WordPress site sends some visitors to another domain, yet looks normal when you are logged in?<\/strong> A conditional redirect can target visits from Google, mobile devices or first-time visitors. That deserves investigation, but it does not by itself prove a hack. A migration rule, a plugin, an advertising integration or an incorrect cache configuration can also change the journey.<\/p>\n<p>Limit visitor exposure while preserving the evidence needed to establish the source. Removing a suspicious line without finding which layer produced it can hide the symptom while leaving the original access route open. This guide explains how to scope an authorised defensive investigation with your hosting provider or a specialist, without turning the public website into a testing ground.<\/p>\n<h2>First distinguish an expected redirect from an unexplained one<\/h2>\n<p>Redirecting HTTP to HTTPS, choosing a single version with or without \u201cwww\u201d, moving domains or selecting a translated page can all be legitimate. A payment provider may also take a customer to an external domain as part of an approved checkout. Compare the destination with the journey your business actually intended, rather than treating any address change as hostile.<\/p>\n<p>Concern increases when the destination is unknown, offers a fake browser update, displays unrelated content or varies between visitors without an explainable business rule. An advertising tracking domain is not automatically malicious either. Establish who authorised it, what it loads next and exactly when the visitor leaves the website. The final destination matters as much as the first visible hop.<\/p>\n<p>Start by gathering expected redirects and recent changes: a migration, a new language, CDN settings or a marketing plugin. A CDN is an intermediary service that can distribute and cache website content. Checking its configuration prevents the accidental removal of useful rules, while requiring someone to account for behaviours that nobody recognises or owns.<\/p>\n<h2>Why it may happen only on mobile or after a Google visit<\/h2>\n<p>A rule can depend on the browser, the referring page, a cookie or whether the visitor is logged in. An administrator typing the address on a desktop therefore may not follow the same path as a prospect arriving from Google on a phone. A normal page in your everyday session is not evidence that every visitor receives the same response.<\/p>\n<p>Google\u2019s official <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9044101?hl=en\">Security Issues documentation<\/a> describes hacked content and redirects that depend on factors such as referrers or browsers. Legitimate features can use those variables too. A mobile-versus-desktop difference tells the investigator what to compare; it does not, on its own, identify a malicious plugin or establish that an attacker is responsible.<\/p>\n<p>Keep paid and organic search separate. A Google advertisement can use tracking links or point to an incorrect landing page. If the visitor reaches another domain before contacting your website at all, the advertising journey needs investigation as well. Record whether the report concerns an ad or a normal search result instead of automatically assigning every Google-related redirect to WordPress.<\/p>\n<h2>Capture the journey before changing the site<\/h2>\n<p>Build a short, reproducible incident note without asking customers to revisit a potentially harmful page. Do not continue browsing the unknown destination or download anything it offers. A specialist can inspect network traces in an isolated environment; your team\u2019s first job is to supply a reliable starting point rather than deliberately trigger a risky chain on a normal work device.<\/p>\n<ul>\n<li>The exact starting URL, date, time and time zone.<\/li>\n<li>The entry route: direct visit, organic result, advertisement, shared link or social platform.<\/li>\n<li>The device, browser and whether the person was logged in.<\/li>\n<li>The observed destination, a screenshot and whether the behaviour repeats or appears intermittently.<\/li>\n<li>Recent changes to WordPress, hosting, the CDN and advertising tools.<\/li>\n<\/ul>\n<p>Network traces can contain tokens, account identifiers and personal information. Share them through a restricted channel and remove unnecessary sensitive details before wider circulation. Retain available logs and request a protected copy of the files and database before cleanup. The official <a href=\"https:\/\/wordpress.org\/documentation\/article\/faq-my-site-was-hacked\/\">WordPress hacked-site FAQ<\/a> supports documenting the incident and keeping material that will help the investigation.<\/p>\n<h2>Identify the layer that sends the visitor away<\/h2>\n<p>The investigation should follow the actual request path. If the server immediately returns a redirect response with a destination, hosting, proxy and CDN rules, alongside WordPress redirect mechanisms, become priorities. If a page appears and then sends the visitor away, browser-executed code and external resources deserve closer examination. These observations narrow the search; neither is a complete diagnosis.<\/p>\n<p>On authorised URLs only, the specialist compares direct entry with the reported referrer, a fresh session with an existing one, and mobile with desktop behaviour. Keep each test\u2019s context explicit. Changing the browser, network and page simultaneously makes the result hard to interpret. Changing one relevant condition at a time produces a comparison that can support or weaken a specific hypothesis.<\/p>\n<p>Inspection can then cover server rules, site address settings, redirect and cache plugins, the theme, mandatory \u201cmu-plugins\u201d, database content and third-party scripts. A change in an external tag manager or advertising supplier can affect visitors without an obvious edit in WordPress files. A single malware scan may not examine every part of this chain, so its scope and limitations should be recorded.<\/p>\n<h2>Contain exposure without destroying evidence or orders<\/h2>\n<p>If visitors are being taken to fraud or dangerous downloads, do not leave that route open throughout a lengthy investigation. Agree proportionate containment with your provider: suspend an identified integration, restrict an affected area or serve a maintenance page from a controlled environment. A maintenance page generated by the compromised WordPress installation may itself be affected by the same redirect.<\/p>\n<p>Before altering the site, preserve its current state and available logs outside public access. Record changes and prepare a rollback. Do not delete every plugin or wipe the installation simply to \u201cstart clean\u201d without preserving it first. That can remove evidence, destroy business content and make it harder to establish how the unwanted change became possible.<\/p>\n<p>For a shop, restoring an older backup can also erase recent orders and customer updates. The restore-versus-cleanup decision therefore needs an explicit plan for preserving valid transactions. If the redirect reveals a wider compromise, the <a href=\"https:\/\/say-digital.io\/blog\/hacked-wordpress-site-regain-control-prevent-repeat\/?lang=en\">WordPress incident recovery guide<\/a> covers the broader access and reopening decisions. This article stays focused on diagnosing the redirect journey rather than repeating the entire recovery process.<\/p>\n<h2>Fix the cause, then replay the affected conditions<\/h2>\n<p>Remediation follows the findings. An incorrect but legitimate rule needs correction and documentation. Confirmed injected content requires removal, verification of affected components against trusted sources and treatment of the identified entry point. A vulnerable extension, stolen access or compromised external integration may be involved. The handover should distinguish evidence from an unconfirmed explanation, including when the entry point remains uncertain.<\/p>\n<p>Relevant credentials and secrets must be renewed in a coordinated way from a clean environment. WordPress, server and CDN caches then need attention in the appropriate order. Purging a cache can remove an infected copy but does not clean the source that generated it. Conversely, a stale copy can keep the symptom visible after a source-level correction. The official <a href=\"https:\/\/developer.wordpress.org\/advanced-administration\/security\/hardening\/\">WordPress hardening guidance<\/a> connects access control, updates, backups and monitoring to continued operation.<\/p>\n<p>Acceptance testing should reproduce the reported conditions: the same page, relevant entry route, fresh sessions, mobile and desktop. Check the final destination and intermediate steps, then verify useful journeys such as contact forms and checkout. Retain the observations and testing limits. One successful administrator visit, or the absence of a Google warning, does not establish that the affected customer path has been restored.<\/p>\n<h2>What to ask Say Digital to scope<\/h2>\n<p>To turn an intermittent report into an actionable diagnosis, share the journey record and request a written scope: evidence preservation, affected layers, containment, cleanup where required, root-cause correction and reopening criteria. Say Digital\u2019s <a href=\"https:\/\/say-digital.io\/infrastructure\/gouvernance-IT\/\">IT governance service page<\/a> is the verified entry point for discussing that responsibility. It is not an automatic promise that every incident can be resolved before examination.<\/p>\n<p><a href=\"https:\/\/say-digital.io\/infrastructure\/hebergement-cloud-vps\/\">Cloud and VPS hosting<\/a> addresses a recurring operational need separate from a one-off cleanup. Establish who owns log review, updates, backups and alerts after the intervention. You can <a href=\"https:\/\/say-digital.io\/team\/morgan-michaux\/rdv-telephonique-15mn\/\">book a 15-minute call<\/a> to explain the situation without putting passwords in the initial message. Pricing, deliverables and ongoing commitments should be agreed in a written quotation rather than inferred from a general hosting subscription.<\/p>\n<h2>FAQ: WordPress redirects<\/h2>\n<h3>Why can visitors reproduce it when I cannot?<\/h3>\n<p>Your logged-in session, cookies or direct entry may follow a different branch. Compare the reported journey in a controlled environment instead of relying on your dashboard or usual browser alone.<\/p>\n<h3>Can clearing the cache solve it?<\/h3>\n<p>Only if the issue really is an outdated cached copy and the source is correct. An active rule or injected content can immediately produce another problematic copy after a purge.<\/p>\n<h3>Should I remove my redirect plugin?<\/h3>\n<p>Not without inspecting its rules and preserving a backup. It may implement valid business behaviour or be unrelated. Disable only what the investigation justifies and maintain a rollback path.<\/p>\n<section data-say-corpus-links=\"2026-10\">\n<h2>Follow the symptoms you observe<\/h2>\n<p>If Google also flags the site as dangerous, follow the <a href=\"https:\/\/say-digital.io\/blog\/google-site-dangerous-warning-cleanup-security-review\/?lang=en\">cleanup and Google security review process<\/a>. If the redirect returns after a fix, investigate <a href=\"https:\/\/say-digital.io\/blog\/wordpress-hacked-again-after-cleanup-prevent-reinfection\/?lang=en\">reinfection after cleanup<\/a>.<\/p>\n<\/section>\n<h2>Sources<\/h2>\n<p>WordPress: <a href=\"https:\/\/wordpress.org\/documentation\/article\/faq-my-site-was-hacked\/\">FAQ My site was hacked<\/a> and <a href=\"https:\/\/developer.wordpress.org\/advanced-administration\/security\/hardening\/\">Hardening WordPress<\/a>. Google: <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9044101?hl=en\">Security Issues report<\/a>. These sources support the mechanisms and investigation approach; this article claims no client case study or measured incident outcome.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>WordPress redirects on mobile or after Google visits? Distinguish legitimate rules from malicious redirects, preserve evidence and scope a safe fix.<\/p>\n","protected":false},"author":2,"featured_media":14996,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[79,165],"tags":[],"class_list":["post-14998","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-security","category-wordpress"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>WordPress redirects to another site: diagnosis and safe fixes<\/title>\n<meta name=\"description\" content=\"WordPress redirects on mobile or after Google visits? Distinguish legitimate rules from malicious redirects, preserve evidence and scope a safe fix.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"WordPress redirects to another site: diagnosis and safe fixes\" \/>\n<meta property=\"og:description\" content=\"WordPress redirects on mobile or after Google visits? Distinguish legitimate rules from malicious redirects, preserve evidence and scope a safe fix.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en\" \/>\n<meta property=\"og:site_name\" content=\"Say Digital I\/O\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-30T22:11:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-30T22:25:19+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/say-digital.io\/blog\/wp-content\/uploads\/2026\/10\/wordpress-conditional-redirect-security-cover.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"842\" \/>\n\t<meta property=\"og:image:height\" content=\"595\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Lia Amplify\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Lia Amplify\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture est.\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en\"},\"author\":{\"name\":\"Lia Amplify\",\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/#\\\/schema\\\/person\\\/8ee0600139c147afbd1fa3ced079c557\"},\"headline\":\"WordPress redirects to another site: recognise and resolve a malicious redirect\",\"datePublished\":\"2026-10-30T22:11:38+00:00\",\"dateModified\":\"2026-10-30T22:25:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en\"},\"wordCount\":1573,\"image\":{\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/wordpress-conditional-redirect-security-cover.jpg\",\"articleSection\":[\"Security\",\"Wordpress\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en\",\"url\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en\",\"name\":\"WordPress redirects to another site: diagnosis and safe fixes\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/wordpress-conditional-redirect-security-cover.jpg\",\"datePublished\":\"2026-10-30T22:11:38+00:00\",\"dateModified\":\"2026-10-30T22:25:19+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/#\\\/schema\\\/person\\\/8ee0600139c147afbd1fa3ced079c557\"},\"description\":\"WordPress redirects on mobile or after Google visits? Distinguish legitimate rules from malicious redirects, preserve evidence and scope a safe fix.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en#primaryimage\",\"url\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/wordpress-conditional-redirect-security-cover.jpg\",\"contentUrl\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/wordpress-conditional-redirect-security-cover.jpg\",\"width\":842,\"height\":595,\"caption\":\"Illustration unDraw \u2014 Security.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/wordpress-redirects-another-site-malicious-redirect\\\/?lang=en#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"WordPress redirects to another site: recognise and resolve a malicious redirect\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/\",\"name\":\"Say Digital I\\\/O\",\"description\":\"Un site utilisant WordPress\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/say-digital.io\\\/blog\\\/#\\\/schema\\\/person\\\/8ee0600139c147afbd1fa3ced079c557\",\"name\":\"Lia Amplify\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/8817b2616d710fbc77dbbba6c455eebcdd7c8e299ff0dc15b9164e00ab16be69?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/8817b2616d710fbc77dbbba6c455eebcdd7c8e299ff0dc15b9164e00ab16be69?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/8817b2616d710fbc77dbbba6c455eebcdd7c8e299ff0dc15b9164e00ab16be69?s=96&d=mm&r=g\",\"caption\":\"Lia Amplify\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"WordPress redirects to another site: diagnosis and safe fixes","description":"WordPress redirects on mobile or after Google visits? Distinguish legitimate rules from malicious redirects, preserve evidence and scope a safe fix.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/","og_locale":"fr_FR","og_type":"article","og_title":"WordPress redirects to another site: diagnosis and safe fixes","og_description":"WordPress redirects on mobile or after Google visits? Distinguish legitimate rules from malicious redirects, preserve evidence and scope a safe fix.","og_url":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en","og_site_name":"Say Digital I\/O","article_published_time":"2026-10-30T22:11:38+00:00","article_modified_time":"2026-10-30T22:25:19+00:00","og_image":[{"width":842,"height":595,"url":"https:\/\/say-digital.io\/blog\/wp-content\/uploads\/2026\/10\/wordpress-conditional-redirect-security-cover.jpg","type":"image\/jpeg"}],"author":"Lia Amplify","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Lia Amplify","Dur\u00e9e de lecture est.":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en#article","isPartOf":{"@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en"},"author":{"name":"Lia Amplify","@id":"https:\/\/say-digital.io\/blog\/#\/schema\/person\/8ee0600139c147afbd1fa3ced079c557"},"headline":"WordPress redirects to another site: recognise and resolve a malicious redirect","datePublished":"2026-10-30T22:11:38+00:00","dateModified":"2026-10-30T22:25:19+00:00","mainEntityOfPage":{"@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en"},"wordCount":1573,"image":{"@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en#primaryimage"},"thumbnailUrl":"https:\/\/say-digital.io\/blog\/wp-content\/uploads\/2026\/10\/wordpress-conditional-redirect-security-cover.jpg","articleSection":["Security","Wordpress"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en","url":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en","name":"WordPress redirects to another site: diagnosis and safe fixes","isPartOf":{"@id":"https:\/\/say-digital.io\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en#primaryimage"},"image":{"@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en#primaryimage"},"thumbnailUrl":"https:\/\/say-digital.io\/blog\/wp-content\/uploads\/2026\/10\/wordpress-conditional-redirect-security-cover.jpg","datePublished":"2026-10-30T22:11:38+00:00","dateModified":"2026-10-30T22:25:19+00:00","author":{"@id":"https:\/\/say-digital.io\/blog\/#\/schema\/person\/8ee0600139c147afbd1fa3ced079c557"},"description":"WordPress redirects on mobile or after Google visits? Distinguish legitimate rules from malicious redirects, preserve evidence and scope a safe fix.","breadcrumb":{"@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en#primaryimage","url":"https:\/\/say-digital.io\/blog\/wp-content\/uploads\/2026\/10\/wordpress-conditional-redirect-security-cover.jpg","contentUrl":"https:\/\/say-digital.io\/blog\/wp-content\/uploads\/2026\/10\/wordpress-conditional-redirect-security-cover.jpg","width":842,"height":595,"caption":"Illustration unDraw \u2014 Security."},{"@type":"BreadcrumbList","@id":"https:\/\/say-digital.io\/blog\/wordpress-redirects-another-site-malicious-redirect\/?lang=en#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/say-digital.io\/blog\/"},{"@type":"ListItem","position":2,"name":"WordPress redirects to another site: recognise and resolve a malicious redirect"}]},{"@type":"WebSite","@id":"https:\/\/say-digital.io\/blog\/#website","url":"https:\/\/say-digital.io\/blog\/","name":"Say Digital I\/O","description":"Un site utilisant WordPress","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/say-digital.io\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/say-digital.io\/blog\/#\/schema\/person\/8ee0600139c147afbd1fa3ced079c557","name":"Lia Amplify","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/secure.gravatar.com\/avatar\/8817b2616d710fbc77dbbba6c455eebcdd7c8e299ff0dc15b9164e00ab16be69?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/8817b2616d710fbc77dbbba6c455eebcdd7c8e299ff0dc15b9164e00ab16be69?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/8817b2616d710fbc77dbbba6c455eebcdd7c8e299ff0dc15b9164e00ab16be69?s=96&d=mm&r=g","caption":"Lia Amplify"}}]}},"_links":{"self":[{"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=\/wp\/v2\/posts\/14998","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=14998"}],"version-history":[{"count":2,"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=\/wp\/v2\/posts\/14998\/revisions"}],"predecessor-version":[{"id":15030,"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=\/wp\/v2\/posts\/14998\/revisions\/15030"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=\/wp\/v2\/media\/14996"}],"wp:attachment":[{"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=14998"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=14998"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/say-digital.io\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=14998"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}