Brizy subdomain pages fail to be crawled by Naver Search Ads

Ggdp Ggdp

• June 29, 2026 02:23

Hello Brizy Support Team,

I am using Brizy free subdomain pages for landing pages.

The affected URLs are:

https://bus-ad.brizy.site/
https://seoul-subway.brizy.site/

These pages open normally in regular browsers, but Naver Search Ads URL crawling diagnostics suddenly started showing:

- Crawl failed
- Index failed
- HTTP response error: No response

These pages were working before, and I have not recently changed the page content or settings.

Could you please check whether these Brizy subdomain pages have been blocked, restricted, flagged, or affected by any security/filtering rules?

If any page violates Brizy’s conditions, please let me know which page and what needs to be changed so I can fix it immediately.

Thank you.

0

• 

  KC George

  • June 29, 2026 06:09

  Hello there,

  I've added a user-agent rule to https://bus-ad.brizy.site/robots.txt that specifically grants Naver Search Advisor access. Can you crawl https://bus-ad.brizy.site/ again using the Naver Search Ads URL crawler and check the results? If you continue to receive "Crawl failed", "Index failed", or "No response" errors, we will investigate whether a firewall rule is blocking the Naver Search engine.

  0
• 

  Ggdp Ggdp

  • June 29, 2026 06:43

  Hello,

  Thank you for your help.

  I have submitted a recrawl request in Naver Search Ads for:

  https://bus-ad.brizy.site/

  The result has not been updated yet, so I will check again later and let you know if the issue still remains.

  Also, could you please apply the same Naver user-agent rule to the other affected URL as well?

  https://seoul-subway.brizy.site/

  Both pages were showing the same issue in Naver Search Ads URL crawling diagnostics.

  Thank you.

  0
• 

  KC George

  • June 29, 2026 07:25

  I have added the same user-agent rule under CMS > Project Settings > SEO for https://seoul-subway.brizy.site/ as well. You can see it at https://seoul-subway.brizy.site/robots.txt

  

   

  0
• 

  Ggdp Ggdp

  • June 29, 2026 08:06

  Hello,

  Thank you for applying the Naver/Yeti user-agent rule.

  I submitted a recrawl request in Naver Search Ads, but the URL still shows the same errors even after the latest crawl attempt.

  For https://bus-ad.brizy.site/, Naver Search Ads shows:

  • Crawl failed

  • Index failed

  • Crawling allowed

  • HTTP response error: No response

  The latest diagnostic result says: “The target URL crawled at 16:00 on June 29, 2026 is in crawl failed status.”

  The attached screenshot is in Korean, but the key result is that crawling is allowed, while the HTTP response still fails with “No response.”

  Since the diagnostics screen shows “Crawling allowed,” it seems the robots.txt rule is accepted. However, Naver Search Ads still cannot receive an HTTP response from the page.

  Could you please investigate whether a firewall rule, security rule, IP restriction, User-Agent filtering, or another server-side setting is blocking or timing out the Naver Search Ads crawler?

  Thank you.

  0
• 

  KC George

  • June 29, 2026 12:07

  A developer is looking into this issue. We will get back to you once we have an update.

  0
• 

  KC George

  • June 30, 2026 12:47

  Hello there

  We checked and the Naver Search Ads crawler is not on our blacklist - its User-Agent returns a normal HTTP 200 on both sites. To investigate further, would you be able to send us more details about the request the crawler makes? For example, we would like these additional details about the crawling request

  • Source IP
  • Timestamps
  • Full URLs
  • Request headers, especially User-Agent

  Do you have a more detailed view of the crawling request from the Naver URL Diagnosis Tool?

  Can you also try adding a custom domain or custom subdomain to your landing pages and check if the crawler behaves differently with your pages.

  0

Please sign in to leave a comment.