Let’s imagine that the store locators and locations / stores pages are being built for a brand that currently has these functionalities LIVE in a different CMS (not Yext) but wants to take advantage of the advantages that Yext offers, so it wants to pass the integrated management of its store locator to Yext .
We have the following structure for the store locator of each country as well as the locations / stores, which are LIVE:
If it is decided to use the same subdomain for the project with Yext to raise the corresponding pages (store locator and stores / stores), how can you redirect from the source urls (the ones that are currently LIVE in another platform) towards the new urls created with Yext that will use the same subdomain?
With our Page Builder offering, our system automatically appends a unique hash to each page URL upon generation (e.g. store.brand.com/es/brand-store-name-address-c0161ea9bf67).
Thus, the source URLs would differ from the Yext-hosted URLs.
(Note, removing the hash in place of a custom-defined slug field is on our product roadmap!)
From there:
Your client would set up a CNAME pointing to our bridge domain
We would set up 301 redirects from the source and target URLs and host them automatically
In that scenario, Yext hosts both sets of pages. To power a new page in our system, we must unpublish the old one - assuming that both pages are powered by the same “entity”.
In your scenario, our system has no “unpublish” control over your client’s existing set of pages. Thus, we can host redirects for them no problem.