I’m trying to apply a paint layout to Redirect assets, but when I preview them, the redirection still occurs instead of displaying the paint layout content.
Since Funnelback skips redirect assets, I need to achieve this behaviour so that I can amend the redirect asset links in the sitemap while the paint layout is applied(in URL).
Could any please advise if there’s a way to disable the default redirection with paint applied, or any recommended workaround to achieve this?
Redirect Pages will set the Location header, so it will be returned before any page contents, and therefore I don’t think there’s a way around that.
Instead, I think you would need another page that would use a query parameter or similar to reference the Redirect Page and display the required information for that.
But what are you trying to achieve in Funnelback? You might be able to resolve this with something else, like a push collection/data source or similar.
Funnelback currently isn’t crawling redirect assets. I’m trying to find a way to make it crawl the redirect links with a paint layout applied through the sitemap, so that it can read the meta tags from the paint layout and index the content correctly.
Generally, Funnelback will want to try and follow redirects, but if the destination pages do not match the include patterns (i.e. if they are from another domain or website), then it won’t crawl and index that content.
Normally that is what you want (i.e. do not include pages from other websites in your site search).
Are the redirects to other pages on the same site? And what is the use case for having redirects included in the search results?
Hi Ian, We have several redirect assets for our external websites, such as “Have Your Say” and “Library Collection.” However, Funnelback is not indexing these redirect assets, which is causing them to be missing from the search results. It is one of the requirement from stakeholders.
Thanks
Because Funnelback follows redirects, it won’t store the URL that is there before it was redirected, and because the URL after the redirect is on another website, it won’t be included in the results.
I think to get around this, you’d need to change the Redirect Page assets to use the delay so it actually uses JS to redirect. See the docs on how to achieve this (try without the paint layout first, I think it would just be some very, very basic HTML with a script tag by default).
This way, when Funnelback crawls that page, it just sees a script tag and not much else, and would leave it alone. Users would still generally be able to get to the destination page, either seeing a temporary message and then getting redirected, or clicking the link shown to go immediately.
On the Funnelback side, you could use external metadata to add what you need (unless Matrix still renders the regular page metadata for the Redirect Page when using the JS redirect method).
Hi Iain, Adding the 0.5-second delay worked - Funnelback was able to index the assets successfully. With anything less than 0.5 seconds, it wasn’t indexing them.
