# Locale buttons missing from custom page models

**URL:** <https://forum.builder.io/t/locale-buttons-missing-from-custom-page-models/3891>\
**Category:** Visual Editor Help\
**Tags:** visual-editor\
**Created:** [July 14, 2023, 11:58am UTC](https://forum.builder.io/t/locale-buttons-missing-from-custom-page-models/3891 "2023-07-14T11:58:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ReavoEnd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/reavoend/32/2058_2.png) [@ReavoEnd](https://forum.builder.io/u/ReavoEnd)\
**Post date:** [July 14, 2023, 11:58am UTC](https://forum.builder.io/t/locale-buttons-missing-from-custom-page-models/3891/1 "2023-07-14T11:58:33Z")

</div>

**Builder content link**  
`https://builder.io/content/2a46a9a5b3ed4c19b1a32442796a4a74`

**Builder public api key**  
`64dd5478e25746bf9db3b6c0319905f6`

**What are you trying to accomplish**  
I need to be able to set locale and define locale translations for Pages that are not a member of the default Page model

**Code stack you are integrating Builder with**  
react

---

<div class="post-metadata">

**Author:** ![manish-sharma](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@manish-sharma](https://forum.builder.io/u/manish-sharma)\
**Post date:** [July 14, 2023, 2:24pm UTC](https://forum.builder.io/t/locale-buttons-missing-from-custom-page-models/3891/2 "2023-07-14T14:24:56Z")

</div>

Hello @ReavoEnd,

Can you give us more context on your requirement,

Also, the content link shared doesn’t exist

> [@ReavoEnd](#):
>
> `https://builder.io/content/2a46a9a5b3ed4c19b1a32442796a4a74`

> **[Localizing a Whole Page - Builder.io](https://www.builder.io/c/docs/localization-whole-page)**
>
> Drag and drop with your components, right within your existing site or app. Build and optimize digital experiences for any tech stack, visually.

> [@Localization with Next.js](https://forum.builder.io/t/localization-with-next-js/3299):
>
> Localizing your Next.js App This walkthrough starts from the [next-js-simple](https://github.com/BuilderIO/builder/tree/main/examples/next-js-simple) starter. Add the i18n config to your next.config.js file. We’ll use sub-path routing in this example. // next.config.js module.exports = { i18n: { locales: ['en', 'fr', 'de'], defaultLocale: 'en', } } // With this configuration if you have a pages/blog.js it will // route to /blog, /fr/blog, and /de/blog Now you should be able to access locale in the context of getStaticProps and pass it to options in y…