1. Welcome to the feedback forum. Here's some tips for giving your suggestions the best shot:
    • Search before posting: See if someone else has already posted your suggestion. If you add your support to an existing, you're more likely to bubble up the request.
    • Keep one suggestion to one thread: Try not to club lots of different suggestions together in one thread. Otherwise, people will get confused about what they're voting for and we might miss your feedback.
  2. Kayako Download customers: we will continue to develop and support Kayako Download beyond July 2017, alongside the new Kayako for existing customers.

    Find out more.

  3. The forum you are viewing relates to Kayako Classic. If you signed up or upgraded to the new Kayako (after the 4th July 2016), the information in this thread may not apply to you. You can visit the forums for the new Kayako here.

Add SEO meta title, description, and custom URL for Knowledge Base Articles

Discussion in 'Kayako product feedback and suggestions' started by Robert P, Nov 25, 2019.

  1. Robert P

    Robert P New Member

    Hi All,

    It would be nice if we are able to do the following for the Kayako Classic Knowledge Base articles:
    a.) being able to assign a meta title (not just the article title)
    b.) being able to assign a meta description
    c.) customize the URL of the article so it would become more user friendly

    We would like to have these features/customizations for SEO purposes.
    We have been asking Kayako Support for this, and it looks like they are not willing to work on it in the immediate future.

  2. supportskins

    supportskins Kayako Guru

    We can customize Kayako to work the way you want. Feel free to contact us.
  3. Robert P

    Robert P New Member

    thanks for the offer, but we'll wait for suggestions from the community for now.
  4. Robert P

    Robert P New Member

    We are still trying to figure this out and continuing to communicate with Kayako support.

    Any ideas guys?
  5. Robert P

    Robert P New Member

    We still don't have a solution for this. Any suggestions will be greatly appreciated.
    Maybe point to file or workaround.
  6. Robert P

    Robert P New Member

    Can anybody help? We are still stuck on this. :-(
  7. bear

    bear Kayako Guru

    There isn't any community any longer. There wasn't likely any "widespread adoption" of the new pricing for "classic" as they'd claimed, and most, if not all, forum members have moved on. You're on your own, more or less. Sorry.
  8. supportskins

    supportskins Kayako Guru

    Unfortunately thats true.
  9. Robert P

    Robert P New Member

    @bear @supportskins - yeah, it is really sad. i think this issue has been more than 2 years now and we keep on bumping Kayako support about this.
    it indeed feels lonely here. are we the only one Kayako Classic? LOL!

    One of the reasons why we stick to Kayako Classic is it was really very difficult or practically impossible to migrate over to their new "online" service.
    If I remember it correctly - we had a HUGE data back then (much more today) and synchronizing to their new cloud service would be very difficult.

    have you encountered a similar challenge before and how were you able to deal with huge data?
    by huge data I think we have hundreds of gigs.
  10. bear

    bear Kayako Guru

    Here on this forum? This isn't much of a support channel, never really was after the sale of the company (and not the best before, with a few exceptions). One or two devoted employees helped where they could, the rest of the time they directed users to open tickets. The rest of the contributors were end users, most of which have moved on.
    If that was your plan, the classic version seat licensing was about the same in cost, I think (unless buying new, which jumped astronomically). If you plan to pay anyway, and it's working locally, why use the SAAS version at all?
  11. Evgeny Kuchkov

    Evgeny Kuchkov Established Member

    What are you trying to achieve with meta? How are you planning to use it? From my point of view the easiest solution would be using tags (the ones that are in Organizations and tickets`swtags` table). By saying the easiest I mean the least code fixing from my point of view.

Share This Page