Skip to main content

Brizy subdomain pages fail to be crawled by Naver Search Ads

Ggdp Ggdp

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

Comments

10 comments

Date Votes
  • KC George

    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

    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

    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

    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

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

    0
  • KC George

    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
  • Ggdp Ggdp

    Hello,

    After checking the account you inquired about, we confirmed that the site is failing to be crawled, as you mentioned.

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

    First, regarding IP/User-Agent blocking, the blocking method and configuration location can vary depending on the advertiser’s website technology stack, such as WAF, server settings, or security solutions. Therefore, please understand that we are unable to directly verify this externally or provide a universal method for removing the block.

    In general, specific IP ranges or User-Agents may be automatically blocked by a web application firewall (WAF), server security settings, or a bot filtering solution. As a result, requests from Naver crawlers (NaverAdbot / Ads-Naver) may be handled as 404 by the relevant security policy.

    For normal crawling, please contact your website developer and hosting provider and ask them to check the server/WAF/security solution logs for your site to see whether requests from Naver crawlers (NaverAdbot / Ads-Naver), or requests from Naver IP ranges, are being blocked.

    If they are being blocked, those requests need to be allowed or whitelisted.

    The Ads-Naver web crawling server IP range list is provided below.
    125.209.235.167 ~ 125.209.235.186  (20)
    110.93.150.21 ~ 110.93.150.220  (200)
    114.111.32.21 ~ 114.111.32.220  (200)
    211.249.46.21 ~ 211.249.46.220  (200)

    Please refer to it and check again.

    0
  • Ariel H.

    Hi,

    Thank you for your patience.

    We've already asked our senior support team to look into this issue. As this requires further review, it may take a little longer before we receive an update.

    We'll keep you informed as soon as we hear back. We appreciate your patience and understanding.

    Kind regards,
    Ariel H.

    0
  • Ggdp Ggdp

    Hi,

    I’m following up because it has been 6 days since your last update.

    The issue is still affecting our Naver Search Ads campaigns. Could you please check if there is any progress or an estimated timeline?

    Affected URLs:

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

    Thank you.

    0
  • KC George

    Unfortunately, we could not make progress with the troubleshooting due to these reasons

    • At the moment, we do not have access to the web application firewall setup since the only person who has this access is on a long leave and does not return until July 17th.
    • We also could not reproduce the errors with Naver Search Ads URL crawling at our end as campaign setup is a paid service.

    Troubleshooting the above issue does not look feasible for atleast another 10 more days. We apologize for the inconvenience.

    Until we are able to get back to troubleshooting, you may need to look at alternate ways to keep your ad campaign going. Do you have  Naver Search Ads campaigns with landing pages which are published on a custom domain? If those landing pages are crawlable, kindly consider publishing the above two projects on custom domains or custom subdomains.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

Ask a Question