Hi Richard,

The normal Umbraco pages are picking up the 404 page set in SEOChecker just fine. It's only the custom pages causing trouble.

I'm on Umbraco 8 and SEOChecker 2.8.2.

I tried to add my own NotFoundHandler according to this documentation https://our.umbraco.com/Documentation/Reference/routing/request-pipeline/IContentFinder#notfoundhandlers , but it doesn't get hit at all when I debug.

Tracking of not found url's is a really helpful feature, so I'd rather not lose out on it.

Please tell me how I can assist you in narrowing down the issue.

Hi Richard,

The attribute does make my own LastChanceFinder get hit. But the 404 page is still the default Umbraco one:

This is my current implementation of the LastChanceFinder:

[ComposeAfter(typeof(SEOChecker.Core.ContentFinder.RedirectContentFinder))]
    public class LastChanceFinder : IContentLastChanceFinder
    {
        bool IContentFinder.TryFindContent(PublishedRequest request)
        {
            IPublishedContent notFoundNode = request.UmbracoContext.Content.GetById(new Guid("943bd6bb-c0fa-4a16-b305-778955f5403a"));

            if (notFoundNode != null)
            {
                request.PublishedContent = notFoundNode;
            }

            return request.PublishedContent != null;
        }
    }

And I register it in my composer like this: composition.SetContentLastChanceFinder<LastChanceFinder>();

But like you said, that will also disable the tracking of 404 errors? That is not what I want.

Am I raising the 404 error correctly by using return HttpNotFound() in a RenderMvcController?

This is the first time I'm working with custom data using NPoco, so I want to make sure the error is not on my end :)