Hi, has anyone encountered issues with Facebook and Twitter not being able to connect to your Galaxy servers?
For example: Sharing Debugger - Meta for Developers
Meta keeps telling me my privacy policy is a 418.
Similarly, Twitter cards are all timing out.
I can’t for the life of me figure this one out. Every thread I’ve encountered in Facebook’s forums says that it’s got to do with SSL certificates. Wanted to see if anyone else has had a similar experience.
I believe your page is not prerendered or if you use SSR, it is not SSR-ing.
Your home page looks good but the Privacy page doesn’t exist for crawlers.
https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fwww.submithub.com%2Fabout%2Fprivacy
Thanks for sharing - very interesting! Looks like a simple curl to anything except my homepage also results in a 504.
All the pre-render stuff is handled by Galaxy and has been for years. This only seems to have become an issue in the last week or two, but I can’t see anything from my side that would cause it.
If I set up a local pre-render instance, everything works fine. So this is either an issue with Galaxy or with prerender.io. Will report back once I hear from Galaxy customer support.
Hi Jason,
This is indeed a very strange error. We will investigate internally to understand what might be happening.
I used this site, which is great for generating SEO reports for apps/websites. It loaded your page’s content correctly.
I also received your request in our Chat system and will continue following up there.
The url in discussion is this: SEO Monitoring Software: Track SEO Performance in One Place
and is not loading the page.
@jasongrishkoff your privacy page is not in any of your site schemas, and it might not have been indexed by crawlers. This anyway doesn’t mean that it should not be indexed on the first visit by a crawler.
I host my own Prerender server, and I can pre-render a page on demand with a POST call.
await fetch(`https://your_prerender/https://your_page`, { method: 'post' })
I don’t use Galaxy and I am not sure how you can do that or whether you have any UI (such as the one in Prerender.IO) to see dates of last indexing requests for each page.
Thanks to @philippeoliveira for helping resolve this one. This was what they identified:
It seems that your page is loading progressively, which is causing the renderer to time out when attempting to render it.
All working smoothly now 