I have my project in production and I have dynamic pages where the URL is created by the database, meaning that when the client registers, a specific URL is created for that registration, thus becoming https://mydomain.com/url.
It works normally, but in the console, when opening the page, it gives a 404 error, and because of this, Google can’t index the page. I use Nginx as the server.
Does anyone have any ideas on what to do?
Hi @Apptrix 
When you say “it works normally”, do you mean it used to work and stopped working all of a sudden?
Could you share with us a few screenshots of how things are setup on your side so we can try to figure out what may be going on?
Joyce,
Thank you for getting back to me. When I say it works normally, I mean that functionally and visually there are no errors, only in the console. I’m attaching a screenshot to make it clearer.
And here’s the link.
https://nivertrix.com/na-brasa-eventos/
Although the 404 error in the console doesn’t affect users, it does impact SEO because Google can’t map it.
@Joyce any feedback?
Hi @Apptrix
Ah ok, I see what you mean.
It looks like some resources can’t be found, including a couple of Phosphor icons.
I’m not sure it has an impact on SEO because it doesn’t look like crucial content for search engine bots. For example, the two Phosphor ones look like fonts that are not available. Search engines don’t care about this.
That said, if you want to clean things up, you could try to identify why the page is attempting to fetch these resources and remove them or fix them in your app.
For example, that first one from Supabase: when I visit the page, it makes the call (and fails). Is that because I’m not logged in? If it is, then maybe the app should check if the user is logged in before making the call.
Does that help?
Hello @Joyce , thanks for your response again.
The problem itself is the 404, the rest of the error can be disregarded, Google cannot index the 404, and although the page appears without problems for the user, it always gives this 404 return.
Hi @Apptrix
Mmm ok, I haven’t seen this before.
Could you share a video of how things are built inside the WeWeb editor and, in preview mode, show us the flow that the user follows to land on this page?
That will help us reproduce your use case and hopefully find a solution for you.
Thanks!
@Joyce, any idea?
