How to remove /r/recordID in generated URLs

Hi,
I am porting a web site from Wordpress to Softr.
The current web site has clean URLs such as

With softr using dynamic blocks it becomes

Such URLs are not ideal for the following reasons:

  • Unreadable URLs discourage clicks in searches
  • People are less likely to copy/paste ugly URLs
  • Clean slugs help rankings for keywords in URLs
  • Google may deprioritize what it sees as dynamically generated or low-trust URLs

I have applied what is described here .

I have read related topics posted in the community but did not find a final answer. Is there a way to get rid of /r/record id in the URL to have SEO friendly URLs?

Thanks in advance for your help

Hi @wautersfred

There is no way to remove the record ID (like recoieI9SpU8onBoI) from the URL since it is the unique identifier by which the page displays the correct records. You can add an SEO slug to item details pages to include the slug in the URL, but that won’t remove the record ID.

Please check this article for more details on how to se SEO slugs for item detail pages.

Hi Sveta,
this means I am forced to use static pages to have URLs with a clean slug without this record ID. Correct?

Could you tell me which are from your experience the drawbacks from SEO point of view of having the record ID in the URL?

Thanks!

yes, you will need to use static pages, if you do not want to have record IDs in the urls.

Instead of a list block, you can use a Feature grid static block for showing up all the posts on one page and you’ll need to have separate pages for each page, again with static blocks on it. When you have all the posts created in separate pages, you can return to the main page when the Feature grid is and connect the posts to the feature grid. Please check the attached screenshot for reference.

On the details page, you can have another feature grid block to show the blogs related to the that specific blog post.

Unfortunately, we do not have blog templates, but this article here too might be helpful with your use case.