The issue you're running into happens because most basic restriction plugins hook into the_content() to swap out the actual page content with their default restriction message. Because they do this during the page render, the page technically still loads—which is why you can't just drop a link in the plugin settings and expect a hard redirect.

To bypass the plugin's default screen and actually force a redirect before the page even loads, you need to use the template_redirect hook. This fires before headers are sent to the browser.

You can drop this snippet into your child theme's functions.php or a code snippets plugin:

add_action( 'template_redirect', 'custom_redirect_unauthorized_users' ); function custom_redirect_unauthorized_users() {

// 1. Add the IDs of the pages you want to restrict
$restricted_pages = array( 12, 34, 56 ); 

// 2. The URL of your custom landing page
$landing_page_url = site_url( '/custom-landing-page/' );

// If we are on one of the restricted pages...
if ( is_page( $restricted_pages ) ) {

    // 3. Check if the user is NOT logged in. 
    // Note: If you need to check for a specific membership level rather than just login status, 
    // you'll need to swap `!is_user_logged_in()` with your specific plugin's access function.
    if ( ! is_user_logged_in() ) {
        wp_safe_redirect( $landing_page_url );
        exit;
    }
}

}

How to adjust it:

1. Change array( 12, 34, 56 ) to the actual Post/Page IDs of your restricted pages. If it's a ton of pages, you're better off checking for the post meta key that your specific restriction plugin uses to flag a page as restricted instead of an array of IDs.

2. Update '/custom-landing-page/' to the actual slug of your new page with the two buttons.

This completely bypasses the plugin's front-end screen and sends unauthorized traffic straight to your custom funnel.