So the pathPrefix option is meant to crawl Netlify site that will later be deployed to a subpath of the production website, e.g.:
You deploy your site on my-netlify-preview.netlify.app/ but all the links point to /blog/mypage.html, because the site will later be deployed to https://my-prod-website.com/blog
Can’t you configure your site to be deployed on the root?
Otherwise you’ll need to configure your site so the DEPLOY_PRIME_URL points to the /blog path.
Or put a redirection to /blog
Hey Sylvain, thanks for the follow up. We can’t deploy at the root, because the site is behind Cloudfront and we use a reverse proxy to take everything from */blog on Netlify and deploy it as a subdir on our main domain. We use two different platforms for our marketing site and blog. Not ideal, but it’s the way it has to be.
So regarding your solution, I’m not really sure I follow with the DEPLOY_PRIME_URL and how that would work. In the end, I’m looking for a solution that could create the index off of my-site.netlify.app/blog/.
If this is not possible with the Aloglia/Netlify app, I’m sure I can still build this out myself with the JS API, correct?
I’m experiencing an issue with Algolia indexing that I’m seeking assistance with. My Discourse forum is set up to have a subdirectory for specific content, and I’ve configured Algolia accordingly. It seems that Algolia is not correctly indexing content from the designated subdirectory. visit us