Sitemap/robots.txt, custom 404, redirects, per-page SEO, and CSP — deployment questions #578
Unanswered
tblackmon-create
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi team — really enjoying working with Instatic so far. A few questions as we get close to launching a client site, some of which might be missing features and one might be a bug:
Sitemap.xml / robots.txt — Both return 404 on our deployment. Is there a way to have these auto-generated, or a place to supply static files at the domain root?
Custom 404 page — Unknown URLs return a bare JSON body (
{"error":"Not found"}) instead of an HTML page. Is there a setting for a custom 404, or is this on the roadmap?Server-level redirects — We're migrating an old site with a couple hundred URLs that need to map to new ones. We checked Data, Settings, and Plugins in the admin and did not find a redirects feature. Is this possible at the hosting layer (e.g. on Railway), or planned?
Per-page/per-post SEO fields do not appear to affect output — This might be a bug: individual Posts have
seoTitle/seoDescriptionfields in the editor, and we have filled them in, but every page on the published site (including individual post pages) renders the identical site-wide default<title>/meta description instead. Is there a step we're missing to wire these up, or is this not yet implemented?CSP and third-party scripts — The default
script-src 'self'policy blocks things like Google Analytics. Is there a supported way to allow-list specific third-party scripts per-project?Any pointers appreciated — trying to figure out what's possible before our launch date, and what we should plan to build around instead. Thanks for the great tool!
All reactions