emma150377

Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Forum: Plugins
    In reply to: [All-In-One Security (AIOS) – Security and Firewall] AIOS blocks real Googlebot – Search Console redirect error
    Thread Starter emma150377

    (@emma150377)

    2 weeks, 6 days ago

    Hi,

    I finally got access to the raw server access logs (via our hosting panel). I checked the exact timestamps that Search Console itself reports as the “last crawl” for the affected old URL, on two separate recrawl attempts (24 Sep and 1 Oct):

    • 24 Sep 2026, 23:20:48 (local time) – Googlebot UA – server response: 301
    • – 1 Oct 2026, 00:06:12 (local time) – Googlebot UA – server response: 301

    Both match Search Console’s own “last crawled” timestamps to the second. In both cases the raw access log shows a clean 301 redirect for the Googlebot UA – no 403, no empty body. I also scanned the full day’s log (24 Sep) for any 403 response to any Googlebot UA anywhere on the site: none found at all.

    So at the exact moments Google itself says it tried (and failed) to crawl this URL, our server log shows it actually got a normal, successful redirect – the same as any other visitor. This seems to rule out a server/firewall-level block at the time of those specific crawls, at least for the status code itself.

    Given this, I’m running out of ideas on our side. Could this be some kind of delay or caching issue on Google’s side (re-displaying a stale result from before the fix), or is there something else server-side that wouldn’t show up as a non-200/301 status code in a basic access log (e.g. an empty or truncated body sent with a 301, or a timing issue)? Any other diagnostic angle you’d suggest would be very welcome.

    Thanks again for your help.

    Forum: Plugins
    In reply to: [All-In-One Security (AIOS) – Security and Firewall] AIOS blocks real Googlebot – Search Console redirect error
    Thread Starter emma150377

    (@emma150377)

    2 weeks, 6 days ago

    Hi,

    Thanks for the detailed follow-up. I checked all four points you mentioned:

    1. IP detection method (Settings > Advanced Settings): currently set to REMOTE_ADDR (the default).
    2. 2. “Block fake Googlebots” setting: confirmed still disabled (I had turned it off about two weeks ago; a plugin update since then moved this option to Firewall > PHP Rules > Internet Bots, but the value itself is unchanged – still off).
    3. 3. Permanent Block List: 47 IPs currently listed, none related to Google (searched for “google”, zero matches).
    4. 4. Audit log: searched for “googlebot” across 1,085 entries – zero matches. AIOS doesn’t appear to be logging any Googlebot-related activity at all, blocked or otherwise.

    I don’t have direct access to the raw server access logs (shared hosting panel) to check for a 403 response to a Googlebot UA specifically – I’ll try to get that if needed.

    Regarding your question about the URL: yes, https://reddingue.com/couple/est-ce-quil-veut-vraiment-une-relation-serieuse/ is the exact URL that Google Search Console is trying (and failing) to crawl/index – it’s an old URL that 301-redirects to the current one. The destination URL loads fine and is already indexed; it’s specifically the old redirecting URL that Search Console reports as failing with “Redirect error” on recrawl, even though the redirect itself tests clean with curl (single 301 hop, no loop) for both a standard UA and a UA containing “Googlebot”.

    Given that AIOS itself shows no sign of blocking (setting off, nothing in the block list, nothing in the logs), I’m starting to wonder if the cause is outside AIOS entirely – maybe at the hosting/server level. Any other ideas on what else could produce this specific pattern (works for every UA except one containing “Googlebot”)?

    Thanks again for your help.

Viewing 2 replies - 1 through 2 (of 2 total)