-
-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pre-rendering pages #6284
Comments
btw, I already proposed this poc a long time ago
|
nice, I have must missed it.
would be that startup plan enough? https://prerender.io/pricing/ - prerenders is being triggered on visit I guess?
well, let's go with that one than, happy to give it a shot. |
@preschian can you briefly describe what is difference between using prerender.io and your manual construct prerendering? cc pretender pricing https://prerender.io/pricing/ Which features we have and won't have? |
I think the main difference is in terms of simplicity. with manual construct, we need to maintain the content for the selected routes (html/template output for bot) with prerender.io, the content will be served automatically |
hmmm, okay, let's do release, we will test and evaluate and maybe can get back in week to this if things will still not work well, moving to p4 till then |
lmk if we want to make this more priority again. since, right now we are fixing seo stuff, I think it should be easier if we use prerender.io |
prerender.io pricing look a bit expensive, and I think we'll definitely overpass free tier plan. I'll ask a random question but Can this work with Nuxt3 and SSR mode? |
this is not a random question btw (good question instead XD). when we use nuxt3 and enable ssr mode we dont need prerendering stuff. so we can drop prerendering worker stuff nuxt3 uses nitro, and it already supports cloudflare pages https://nitro.unjs.io/deploy/providers/cloudflare#cloudflare-pages |
okay, let's go with it. I've commented on that here
I would use prerender for most critical pages for SEO engines as they can do one thing well. For collections states we will stick with our existing
Is this... for real true? That's like we are at 99% of the race till the finish... so making this p1 again as we are suffering a lot from not being indexed 😅 Ref |
One of things i think why we are not indexed on google is that our pre-render is not there and in the past we've been using Netlify which has somehow built in pre-render back then
Now I'm researching what we can use for prerendering, found this one
Good Q, if we can have something with CF workers?
To be continued as need wrap my head around
The text was updated successfully, but these errors were encountered: