Re: Genomelink: Traits pages * Nested URL on Webflow

Hi Tomo,

Please see the detailed reply from the SEO team below. 'The first
structure is the best for SEO. Let me know what your team thinks.

Hopefully this is clear enough. If not I will set up a call with the SEO
manager.

Thanks
Fionn

On Thu, Mar 24, 2022 at 10:05 AM Tomohiro Takano <tomo@genomelink.io> wrote:

> Thanks, if you have any questions, please let me know.
>
> On Thu, Mar 24, 2022 at 10:03 AM Fionn Downhill <
> fionn@healthcaresuccess.com> wrote:
>
>> HI Everybody,
>>
>> Let me talk to our SEO team and get back to you
>>
>> Thanks
>> Fionn
>>
>> On Thu, Mar 24, 2022 at 9:55 AM Tomohiro Takano <tomo@genomelink.io>
>> wrote:
>>
>>> Fionn, Edith
>>>
>>> Fionn, thank you for the call yesterday. I am adding Hudson, Yuta, and
>>> our CTO, Ken, in the following conversations so that they can catch up on
>>> what we are discussing here.
>>>
>>> I did some research, and unfortunately, Webflow does not support the
>>> nested URL structure that your team wants to set up. I find this thread
>>> with the Webflow team's comment on it.
>>> https://discourse.webflow.com/t/nested-url-multiple-levels/131956
>>>
>>> If we want to use the CMS feature for all 200+ traits pages, we can only
>>> have the URLs with the current structure like below.
>>> https://genomelink.io/traits/[CMS-trait-page]
>>>
>>> *Would you discuss what Traits page structure you think we should
>>> explore within your team? *We could have:
>>>
>>> - https://genomelink.io/traits
>>> - https://genomelink.io/*traits/personality*
>>> - https://genomelink.io/*traits/[CMS-trait-page]*
>>> - https://genomelink.io/*traits/sports*
>>> - https://genomelink.io/*traits/[CMS-trait-page]*
>>>
>>> or
>>>
>>> - https://genomelink.io/traits
>>> - https://genomelink.io/*personality-traits*
>>> - https://genomelink.io/*personality-traits/[CMS-trait-page]*
>>> - https://genomelink.io/*sports-traits*
>>> - https://genomelink.io/*sports-traits/[CMS-trait-page]*
>>>
>>> The latter option requires us to manage 5 different CMS Collections and
>>> template pages, which could be more resource-consuming to scale and
>>> maintain pages.
>>>
>>> Lastly, I could confirm that we could change the top Trait page URL as
>>> below, but this requires some system-side setting, so I need to work with
>>> our tech team. After finalizing the entire structure based on the above
>>> considerations, let me do this.
>>> https://genomelink.io/*trait/all*
>>> https://genomelink.io/*traits*
>>>
>>> Let me know what your team thinks. Happy to jump on a call to discuss.
>>>
>>> Tomo
>>>
>>>
>>>
>>>