Why SvelteKit route slugs are indexed by the Google Search Console?
I have a full-stack SvelteKit application that uses SSR (no prerendering), and the Google Search Console indexes not only my resolved routes, but also the unresolved routes with slugs, like this:
How is it possible?
Solution
The bug has been fixed, I guess by an update of SvelteKit. Marking it as resolved.
- Connection Refused Between SSR Next.js and Laravel API
- Nextjs with react-leaflet - SSR, webpack | window not defined, icon not found
- Dynamic meta deta is not updating as expected due to production static site generation
- How to render component only client side with Remix?
- Angular 18 with SSR: Setting optimization to true ignores library loaded inside scripts
- SvelteKit: disable SSR
- How to get ngx-toastr to close in angular 17.3.8 (standalone) with SSR
- NextJS: Why NextResponse.redirect is not triggering on production
- How to use Context API in Next JS 13 with server-side components?
- The default export is not a React Component in page: "/" NextJS
- React Tsx - document is not defined
- The argument 'path' must be a string, Uint8Array, or URL without null bytes. Received '\x00@astro-page:astro/assets/endpoint/node' on Heroku deploy
- How to deploy an Angular 18 SSR application, with Docker, docker-compose, and NGINX?
- How to detect the device on React SSR App with Next.js?
- ReferenceError with lottie-react on Next.js 13 - SSR Incompatibility?
- react leaflet map error in server side rendering
- Angular: from renderModule to CommonEngine: A required Injectable was not found in the dependency injection tree
- Angular Universal (SSR), with Leaflet and ngx-leaflet
- My routeGuard will always execute the if statement first
- How to get context.modules for vite react ssr-manifest.json
- in NEXTJS Warning: Expected server HTML to contain a matching <div> in <div>
- How can I deploy my angular app in plesk web host edition?
- Accessing Cookie client-side with Next JS
- Calling Javascript from a SSR Page Blazor .NET core
- What is the best scalable way to implement a ContextProvider to fetch and filter data
- Is it unnecessary to render static content in a server component and then pass it to a client component via a prop in NextJS
- Children of NuxtLink rendered twice (hydration error?)
- Blazor: Properly resolve scoped service from App.razor (.NET 8)
- Angular SSR - route identifier with dot
- GraphQL Apollo Client refusing to not use cache in Next.js