Recherches récentes
Pas de recherche récente

Matt Dietsche
Adhésion le 24 oct. 2024
·
Dernière activité le 24 oct. 2024
Suivis
0
Abonnés
0
Activité totale
1
Votes
0
Abonnements
0
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Matt Dietsche
Matt Dietsche a créé une publication,
We migrated our old WordPress-based help site to Zendesk's Help Center. Our plan was to set up an Nginx wildcard redirect from our old url structure to the new article url structure used by Zendesk. I thought it would be something like this:
server old.support.domain
location /old/path/to/(?.*) {
rewrite ^ $scheme://new.zendesk.domain/hc/en-us/articles/$article-name redirect;
}
This rewrite would catch any articles where the article name remained the same after migration. The problem is that ZD's url structure includes the article ID, which makes this approach impossible.
new.zendesk.domain/hc/en-us/articles/381290381290312-article-name
Is there a work around for this? Obviously would like to keep the SEO we've built for our support articles. Seems like the alternative is adding a custom redirect for every article, url to url, which is a daunting task with the number of articles we have.
Surely other companies have migrated help content over to Zendesk like this…
Publication le 24 oct. 2024 · Matt Dietsche
0
Abonnés
1
vote
1
Commentaire