Have something to say?

Tell us how we could make the product more useful to you.

I have a problem with referral links for my users.

When a new user signs up, they have the option to create their own referral link. The format most common across the world is www. anywebsite . com /UniqueReferraldetail However, Base44 tells me that this is not a supported format because “catch-all routing support” is not an standard option. The situation: Base44 currently doesn't support catch-all routing or custom 404 pages. This means URLs like https://anywebsite.com/anyuniquereferral will return a 404 error because there's no actual page at that path. The "Main Page" setting in Base44 only controls what loads at your root URL ( / ), not unmatched routes. The only immediate option offered to me, after I have distributed hundreds of unique referral links in the first format, is to Switch to query parameter format (immediate fix): The working format is: https://anywebsite.com/?ref__=anyuniquereferral Additional response to my support ticket was: For the distributed links: Unfortunately, the hundreds of links you've already shared won't start working automatically You'd need to reach out to those who received the links and provide updated ones in the query parameter format Alternatively, you could create a simple redirect service externally to convert the old format to the new format. But, I do not want to rely on a third party redirect service or deal with integrating it into this app. That will just create more support tickets and finger pointing on why referral links are breaking. Can this be remedied by Base44 providing 404 or catch-all routing support?

Image

Funding Gym About 3 hours ago

💡

Feature Request

Option to disable PWA features / "Install app" prompt

Description: I'm building a website (not an app) with Base44, and when users visit my site on Chrome, they see the "Install app" icon in the URL bar. This is triggered by the PWA manifest that Base44 automatically generates. Request: Please add an option in the app settings to disable PWA features (manifest.json, service worker, etc.) so the site behaves like a standard website without the install prompt. Use case: Some projects are meant to be traditional websites, not installable apps. Having control over PWA behavior would help us deliver the right experience to our users.

Image

Fabio Lopes About 7 hours ago

💡

Feature Request

Feature request: Support for SEO-friendly path-based URLs (e.g. /parking/{slug})

Hello Base44 Team, While working on our application, we analyzed how routing and URL generation currently work in Base44, including the behavior of the built-in createPageUrl function. From what we understand, Base44 uses a proprietary routing system that relies on page names and query parameters (e.g. PageName?param=value) rather than a router based on path parameters (such as React Router). Because of this, it is currently not possible to implement SEO-friendly, path-based URLs like: /parking/{slug} Instead, the platform only supports URLs in the following format: parkingdetails?slug=vip-valet We also understand that this limitation is not something we can change at the application code level, as it is enforced by the Base44 routing architecture itself. That said, we would like to formally request consideration of one of the following enhancements at the platform level: Support for path-based routing with dynamic parameters (e.g. /parking/:slug) An option to map query parameters to clean, SEO-friendly URLs Any form of URL rewriting or aliasing mechanism that would allow path-style URLs while preserving existing routing logic Improving URL structure would be a significant benefit for SEO, user experience, and content sharing, especially for content-driven or marketplace-style applications like ours. At the moment, we are using slugs as query parameters (parkingdetails?slug=vip-valet), which is already an improvement over ID-based URLs, but path-based URLs would be a much better long-term solution. Thank you for considering this request. We would be happy to provide additional details or examples if needed. Best regards, Marcin Górecki

Image

Marcin Górecki About 21 hours ago

💡

Feature Request

Biologist seeks ability to use my apps on a local host - figuring it out is hard

Hi, I don’t plan on stealing anything but I work with proprietary data and I would like to not use a server I can’t control to store and manipulate my data. I am trying to migrate apps from Base44 to a machine in my home (for personal use only) and I’m having a hard time. I’d pay for a tutorial in how to do this!

Image

Elizabeth Bent About 21 hours ago

💡

Feature Request

Feature Request: Per-Page SEO / Noindex Controls for Authenticated Pages

Hi Base44 team, We’re building a healthcare platform on Base44 that includes provider dashboards, availability calendars, and other authenticated pages. Currently, all published pages are automatically included in the sitemap and are publicly crawlable by search engines. For healthcare use cases like ours, it’s critical that internal, authenticated pages do not appear in search engine results. Currently, Base44 does not provide a way to: Add noindex meta tags to specific pages Control robots.txt at the page level Selectively exclude authenticated pages from indexing Because of this, search engines like Bing and Yahoo are surfacing internal app pages (for example, provider availability calendars) in search results, which could confuse users and negatively impact trust. Request: We would greatly appreciate the ability to: Add per-page noindex/SEO controls for authenticated or sensitive pages Optionally manage robots.txt rules at the page level Protect internal pages from indexing without making the entire app private This feature is especially important for healthcare and mental health platforms, where user and provider privacy is a priority. Thank you for considering this request. We’d be happy to provide more context or examples if helpful.

Image

Will Dengler 1 day ago

💡

Feature Request

I was so glad that I read the many posts regarding BASE44 still being in the domain name. I have built over 40 apps on this platform and cant seem to sell any of them for those reasons. Also, many of my customers want Base44 to sync with Quickbooks. I hope this feedback is in the pipelines and somebody is listening. I really like the platform but seems like I will only be using it for demonstration purposes versus production.

Image

LAVETTE Cummings 2 days ago

💡

Feature Request