Preserving Parse.ly integration when migrating to a new content management system (CMS) or changing domains

When redesigning your site or moving to a new content management system (CMS), there are a few issues to be aware of to ensure your Parse.ly data remains accurate.

Redirects

The behavioral data that Parse.ly collects from your visitors contains the URL they were viewing at that point in time.  Our crawlers expect that URL to either resolve to a web page, or redirect to a web page where metadata can be found.

If your links are changing, you should set up 301 Moved Permanently redirects that map to the same content in the new site or CMS.

301 redirects are also strongly recommended by search engines in order to ensure your ranking within search engine results pages isn’t penalized.

Parse.ly Metadata

If you are using the parsely-page meta tag, you should ensure that the link and post_id fields are appropriately set.  It’s alright if these two fields change as a result of your redesign/migration but if they are changing we ask that you e-mail support@parsely.com so that we can perform a recrawl and rebuild of your historical data (note: Parse.ly rebuilds may require an extra fee to cover machine costs).

Also, if you are changing your metadata implementation by, for example, moving from a custom crawler to the parsely-page meta tag, please e-mail support@parsely.com so that we can make the appropriate updates and schedule a recrawl and rebuild of your historical data. More information about recrawls can be found in our help documentation.

If you have any questions, please contact our Customer Success team at support@parsely.com.