내 커뮤니티 업적 표시줄을 확대합니다.

Submissions are now open for the 2026 Adobe Experience Maker Awards

Mark Solution

활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.

해결됨

Can adobe sitecatalyst capture broken links - HTTP 404 error ??

Avatar

Level 1

HI,

does anyone in the forum have experience or idea how can we can derive this.

Broken links are not a good experience for the end user and also not for the company owning the website.

So, if we can capture those can easily try to fix it.

 

Thanks

Sumon

1 채택된 해결책 개

Avatar

정확한 답변 작성자:
Community Advisor and Adobe Champion

Keep in mind, the suggested solutions still require that you have tracking on those 404 pages, and you pass the correct tag.

 

There is one minor issue, IF your site redirects all your 404 pages to a generic URL like https://www.domain.com/404.html" then this is the URL that will be tracked in the report... if the URL stays as "https://www.domain.com/ertertertyetyaw" then this will give you proper visibility into which pages are 404ing...

 

If you have the redirect scenario, you may need to work with your developers to pass the "pre-redirected url" so that you can track it with some custom tracking on the 404 page

원본 게시물의 솔루션 보기

3 답변 개

Avatar

Employee Advisor

Hey @sumondutta I believe this should help -https://experienceleague.adobe.com/docs/analytics/components/dimensions/pages-not-found.html?lang=en

 

Pages not found dimension retrieves data from the pageType and g query strings in image requests. If the pageType query string equals errorPage, the g query string (page URL) is recorded. AppMeasurement collects this data using the pageType variable. If the pageType variable is not defined or set to anything other than errorPage, no data for this dimension is collected.

Avatar

Community Advisor

And Adobe has created a pages not found report and a pages not found metric in Workspace.

RobertBlakeley_0-1693870698952.png

 

Avatar

정확한 답변 작성자:
Community Advisor and Adobe Champion

Keep in mind, the suggested solutions still require that you have tracking on those 404 pages, and you pass the correct tag.

 

There is one minor issue, IF your site redirects all your 404 pages to a generic URL like https://www.domain.com/404.html" then this is the URL that will be tracked in the report... if the URL stays as "https://www.domain.com/ertertertyetyaw" then this will give you proper visibility into which pages are 404ing...

 

If you have the redirect scenario, you may need to work with your developers to pass the "pre-redirected url" so that you can track it with some custom tracking on the 404 page