Practical WordPress advice for website owners
WordPress Redirects Only on Google or Mobile? How to Find the Cause

In this guide
- Why your own normal visit does not settle the report
- Ask for a report that can be investigated safely
- Comparison checklist: change one condition at a time
- Example: a deep search result is the missing clue
- What the technical investigation should distinguish
- Contain the affected journey while findings are reviewed
- Check the original conditions after remediation
- Frequently asked questions
A customer follows a Google result on a phone and lands on a spam website. You open the same WordPress homepage on your laptop and everything appears normal. That difference should be investigated rather than dismissed.
Conditional behavior is a useful signal, not a diagnosis. It may involve compromised website code, a third-party service, browser state or an unexpected link in the journey. The task is to reproduce the legitimate route safely and identify where the behavior changes.
Why your own normal visit does not settle the report
Your browser may be signed in, hold different cookies or follow a different address. A customer may enter through an old search result or a specific product page. Even two visits on the same phone can differ because of cached content or session state.
Wordfence’s official hacked-site guide notes that unwanted behavior can be concealed from administrators. This supports taking credible visitor reports seriously; it does not prove that a particular device difference is malware.
Ask for a report that can be investigated safely
Request the original legitimate page address, the search phrase or starting page, approximate time, device/browser and a screenshot if already available. Ask whether the address changed before or after the page appeared.
Do not ask the customer to repeat a dangerous journey, bypass a browser warning or enter credentials. Avoid turning the destination into a public clickable link. A specialist can inspect requests in an appropriately isolated environment if further testing is required.
Comparison checklist: change one condition at a time
For the legitimate page, an investigator can record a small comparison rather than trying many changes at once:
- Entry route: direct navigation versus the reported search result.
- Session: ordinary logged-out browser versus an existing administrator session.
- Device: the affected mobile browser versus a desktop browser.
- Page: the reported landing page versus a different known page.
- Timing: the current response versus a previously captured response.
The purpose is defensive observation. Do not implement device-targeting rules, change visitor identities or weaken protections to force a result. If a test encounters a harmful destination, stop and preserve the observation.
Example: a deep search result is the missing clue
Consider a business whose owner always tests the homepage. A customer instead arrives at an older service URL from Google. That older URL could follow a different redirect chain or load content that the homepage does not use.
Comparing the exact landing address gives the investigator a concrete starting point. The issue might be an unauthorized change, an obsolete redirect or a third-party dependency. The example is illustrative and deliberately leaves the cause open until evidence is available.
What the technical investigation should distinguish
Ask whether the unwanted step occurs in an HTTP response, browser-executed content, a link destination or an external service. That distinction helps determine whether the work belongs in website files, stored content, hosting/CDN settings or an integration.
Cached responses can complicate the picture. Preserve useful evidence before clearing everything, then check the relevant cache layers after correcting the underlying problem. Deleting a cookie on your own device is not equivalent to repairing the website.
If there are other symptoms—unknown accounts, injected pages or host alerts—include them. If unrelated websites misbehave only on one device, that device and its browser extensions may also need assessment. Avoid blaming a host or plugin without supporting evidence.
Contain the affected journey while findings are reviewed
Pause advertising and prominent links into the affected route where appropriate. If the issue appears broad or exposes visitors to harmful content, involve the host about containment outside WordPress. Keep a safe contact channel available for customers.
Do not change every redirect, tracking integration or search setting simultaneously. Uncoordinated changes make it harder to establish which step caused the issue and can break valid routes.
Check the original conditions after remediation
A useful verification plan returns to the same legitimate URL and entry conditions that produced the report. Include logged-out mobile browsing and critical business functionality. Record what passed, what could not be reproduced and any access limits.
If Google reports a Security Issue, review that report separately after technical cleanup. Its findings and review process are described in Google’s Security Issues documentation. A clean direct visit is not itself a Google review outcome.
Request a free investigation quote for search-only or mobile redirects. Send Nithu the exact legitimate landing page and the conditions reported by visitors. I confirm scope and pricing before work; do not send passwords or authentication cookies through the public form.
Frequently asked questions
Why can I not see the redirect when logged in?
Your session may receive different content or behavior. That can be relevant to an investigation, but the difference alone does not establish the underlying cause.
Does Incognito mode prove whether a website is hacked?
No. It provides a different browser state, not a complete security assessment or protection from harmful content.
Should I remove Google Analytics or every advertising script?
Not without evidence. Review the affected requests and dependencies. Unnecessary blanket changes can disrupt measurement while leaving the real source untouched.
What should I report if it happens only once?
Record the address, route, time, device and visible result. An intermittent event may still be useful when compared with logs and other customer reports.
Prepared for website owners by Nithu / Suthakaran Nithursan. Dated incident facts link to their primary sources. Illustrative scenarios are examples, not client results or guarantees.