# \#link-route-resolver

**URL:** https://community.prismic.io/tag/link-route-resolver/170.md

[Latest](https://community.prismic.io/latest.md) · [Categories](https://community.prismic.io/categories.md) · [Tags](https://community.prismic.io/tags.md)

---

## [Nested Dynamic Routes with Nextjs and Prismic](https://community.prismic.io/t/nested-dynamic-routes-with-nextjs-and-prismic/20124)

<div class="topic-metadata">

**Author:** [@ed11](https://community.prismic.io/u/ed11)\
**Replies:** 1\
**Last updated:** [February 24, 2026, 1:01pm UTC](https://community.prismic.io/t/nested-dynamic-routes-with-nextjs-and-prismic/20124 "2026-02-24T13:01:35Z")

</div>

"@prismicio/client": "^7.21.0", "next": "^16.0.7", I want the URL structure: /resources/:resource\_type/:uid My routes look like: const routes: Route = \[ { type: "page", uid: "home", path: "/" }, { type: "p…

---

## [Random 404 errors on second level pages](https://community.prismic.io/t/random-404-errors-on-second-level-pages/20096)

<div class="topic-metadata">

**Author:** [@Fiskbulle](https://community.prismic.io/u/Fiskbulle)\
**Replies:** 2\
**Last updated:** [January 28, 2026, 12:11pm UTC](https://community.prismic.io/t/random-404-errors-on-second-level-pages/20096 "2026-01-28T12:11:04Z")

</div>

I suddenly started to get 404 errors on second level pages I'm not sure what happened or when it happened because everything has been working fine during the development of my website, but when I had to run my build comm…

---

## [Resolvers of 2 level deep return an id instead of the uid](https://community.prismic.io/t/resolvers-of-2-level-deep-return-an-id-instead-of-the-uid/19773)

<div class="topic-metadata">

**Author:** [@flavien.pensato.ext](https://community.prismic.io/u/flavien.pensato.ext)\
**Replies:** 2\
**Last updated:** [June 4, 2025, 9:30am UTC](https://community.prismic.io/t/resolvers-of-2-level-deep-return-an-id-instead-of-the-uid/19773 "2025-06-04T09:30:27Z")

</div>

Describe your question/issue in detail I'm currently implementing a level 2 deep resolvers like this. { type: 'page', resolvers: { segment: 'route\_segment', parent: 'route\_segment.parent', }, …

---

## [Route Resolver Config - API 413 Response, Request Entity Too Large](https://community.prismic.io/t/route-resolver-config-api-413-response-request-entity-too-large/18447)

<div class="topic-metadata">

**Author:** [@d.mullan](https://community.prismic.io/u/d.mullan)\
**Replies:** 0\
**Last updated:** [February 21, 2025, 2:33pm UTC](https://community.prismic.io/t/route-resolver-config-api-413-response-request-entity-too-large/18447 "2025-02-21T14:33:18Z")

</div>

Hi Requests to the content api are returning a 413 error code. I have identified the issue as being the request url exceeding 8192 bytes, which is a cloudfront limit. The reason the requst url is so large is due to the…

---

## [Retaining query parameters](https://community.prismic.io/t/retaining-query-parameters/18397)

<div class="topic-metadata">

**Author:** [@ben7](https://community.prismic.io/u/ben7)\
**Replies:** 1\
**Last updated:** [February 11, 2025, 7:05pm UTC](https://community.prismic.io/t/retaining-query-parameters/18397 "2025-02-11T19:05:17Z")

</div>

I am trying to set up my Nextjs site to retain query parameters as users navigate my site – specifically utm parameters. My approach has been to handle this in my middleware.ts file. From the initial URL I save the quer…

---

## [Slugs & Multi level URLs](https://community.prismic.io/t/slugs-multi-level-urls/2165)

<div class="topic-metadata">

**Author:** [@thejuniperstudio](https://community.prismic.io/u/thejuniperstudio)\
**Replies:** 21\
**Last updated:** [February 11, 2025, 2:41pm UTC](https://community.prismic.io/t/slugs-multi-level-urls/2165 "2025-02-11T14:41:57Z")

</div>

We have a client that wants multi-level URLs (3 deep) on their website. To achieve this we created a SLUG field and updated the LinkResolver so that slugs work effectively. However, when it comes to RichText fields ther…

---

## [Nextjs Dynamic nested paths](https://community.prismic.io/t/nextjs-dynamic-nested-paths/16613)

<div class="topic-metadata">

**Author:** [@solution.stack99](https://community.prismic.io/u/solution.stack99)\
**Replies:** 18\
**Last updated:** [January 30, 2025, 1:03pm UTC](https://community.prismic.io/t/nextjs-dynamic-nested-paths/16613 "2025-01-30T13:03:51Z")

</div>

I have nested paths where I want a child page to be a dynamic page so that the content team can add it. Structure: Resources - Blog (dynamic page) - Blog pages (dynamic page) - Getting Started (dynamic page) …

---

## [\[Link resolver error\] Unknown type Declared type: homepage Expected one of:\\n](https://community.prismic.io/t/link-resolver-error-unknown-type-declared-type-homepage-expected-one-of-n/16054)

<div class="topic-metadata">

**Author:** [@mr\_g](https://community.prismic.io/u/mr_g)\
**Replies:** 12\
**Last updated:** [January 9, 2025, 9:01am UTC](https://community.prismic.io/t/link-resolver-error-unknown-type-declared-type-homepage-expected-one-of-n/16054 "2025-01-09T09:01:10Z")

</div>

I have setup the routes, and file correctly, I dont understand why I am still getting Link Resolver Error. I have also tried to clean .next cache

---

## [Route Resolver Error](https://community.prismic.io/t/route-resolver-error/16089)

<div class="topic-metadata">

**Author:** [@mayerbrandingfireclo](https://community.prismic.io/u/mayerbrandingfireclo)\
**Replies:** 3\
**Last updated:** [December 10, 2024, 10:38am UTC](https://community.prismic.io/t/route-resolver-error/16089 "2024-12-10T10:38:27Z")

</div>

Describe your question/issue in detail Hello, thank you for your help. I am building a SvelteKit based site and having trouble understanding how to properly config the routes. I have a menu with one level deep, lets say…

---

## [Link to prismic page](https://community.prismic.io/t/link-to-prismic-page/16151)

<div class="topic-metadata">

**Author:** [@robbyk](https://community.prismic.io/u/robbyk)\
**Replies:** 1\
**Last updated:** [June 18, 2024, 3:48pm UTC](https://community.prismic.io/t/link-to-prismic-page/16151 "2024-06-18T15:48:16Z")

</div>

I have a link field as part of a repeatable group. Some links are web urls and others are links to prismic documents. The prismic documents urls do not work. How do I fix this? I'm using the nextjs snippets provided by y…

---

## [GSC report shows 404 errors on urls containing 'undefined'](https://community.prismic.io/t/gsc-report-shows-404-errors-on-urls-containing-undefined/15910)

<div class="topic-metadata">

**Author:** [@alex.troy](https://community.prismic.io/u/alex.troy)\
**Replies:** 5\
**Last updated:** [May 30, 2024, 1:15pm UTC](https://community.prismic.io/t/gsc-report-shows-404-errors-on-urls-containing-undefined/15910 "2024-05-30T13:15:40Z")

</div>

Hello! I've got a long list of urls showing as 404 in GSC. Almost all of them have 'undefined' in the url. i.e. - https://oursite.com/undefined/en-gb, https://oursite.com/en-ie/product/undefined/en-gb, or https://oursi…

---

## [Why the default locale does not appear on the home page](https://community.prismic.io/t/why-the-default-locale-does-not-appear-on-the-home-page/15936)

<div class="topic-metadata">

**Author:** [@nilenarrator](https://community.prismic.io/u/nilenarrator)\
**Replies:** 2\
**Last updated:** [May 16, 2024, 3:11pm UTC](https://community.prismic.io/t/why-the-default-locale-does-not-appear-on-the-home-page/15936 "2024-05-16T15:11:08Z")

</div>

Hello there, I have 2 locales ar-eg and en-gb with ar-eg being the default locale the ar-eg will show with other pages like /ar-eg/about for example but for the homepage it's just localhost:3000 how to append the defau…

---

## [I can't get prismic dynamic pages and routing to work in next.js](https://community.prismic.io/t/i-cant-get-prismic-dynamic-pages-and-routing-to-work-in-next-js/15856)

<div class="topic-metadata">

**Author:** [@jestersimpps](https://community.prismic.io/u/jestersimpps)\
**Replies:** 1\
**Last updated:** [May 6, 2024, 2:58pm UTC](https://community.prismic.io/t/i-cant-get-prismic-dynamic-pages-and-routing-to-work-in-next-js/15856 "2024-05-06T14:58:21Z")

</div>

First of all, I like prismic so far. But... it is really hard to find good documentation. I have been struggling for 3 hours now just trying to set up a link from my landing page to a dynamic sub-page (document) i don't…

---

## [Fetch data with getByUID using two root types in NextJS](https://community.prismic.io/t/fetch-data-with-getbyuid-using-two-root-types-in-nextjs/15803)

<div class="topic-metadata">

**Author:** [@Fiskbulle](https://community.prismic.io/u/Fiskbulle)\
**Replies:** 17\
**Last updated:** [May 6, 2024, 7:25am UTC](https://community.prismic.io/t/fetch-data-with-getbyuid-using-two-root-types-in-nextjs/15803 "2024-05-06T07:25:32Z")

</div>

I am trying to get my head around an issue of having two custom root document types (page and article) and also fetching the data correctly. I understand how to use a sub directory for a different document type and it wo…

---

## [Extending route resolver grandparent limit](https://community.prismic.io/t/extending-route-resolver-grandparent-limit/11595)

<div class="topic-metadata">

**Author:** [@design-development](https://community.prismic.io/u/design-development)\
**Replies:** 5\
**Last updated:** [March 12, 2024, 3:25pm UTC](https://community.prismic.io/t/extending-route-resolver-grandparent-limit/11595 "2024-03-12T15:25:36Z")

</div>

Hi, is there any way to extend the route resolver grandparent limit to great-grandparent and even possibly great-great-grandparent? We have an existing site that we're migrating over that has a very nested url structure…

---

## [Route Resolver Error: An invalid API response was returned](https://community.prismic.io/t/route-resolver-error-an-invalid-api-response-was-returned/15420)

<div class="topic-metadata">

**Author:** [@soulfarm.dev](https://community.prismic.io/u/soulfarm.dev)\
**Replies:** 11\
**Last updated:** [March 7, 2024, 5:05pm UTC](https://community.prismic.io/t/route-resolver-error-an-invalid-api-response-was-returned/15420 "2024-03-07T17:05:28Z")

</div>

Hi! I've started to get the following error: Error: An invalid API response was returned I'm using Next.JS (latest version) Slice machine latest version This is my slicemachine.config.json { "repositoryName": "sou…

---

## [linkResolver with Nuxt to cover Language](https://community.prismic.io/t/linkresolver-with-nuxt-to-cover-language/15398)

<div class="topic-metadata">

**Author:** [@jh1](https://community.prismic.io/u/jh1)\
**Replies:** 1\
**Last updated:** [March 4, 2024, 11:16am UTC](https://community.prismic.io/t/linkresolver-with-nuxt-to-cover-language/15398 "2024-03-04T11:16:17Z")

</div>

Hello! I have a linkResolver like so: import { type LinkResolverFunction } from '@prismicio/client'; const linkResolver: LinkResolverFunction = (document) =\> { const language = document.lang === "en-eu" ? "/en" : "/…
