301 Redirects: protocol for project coordinators and developers

Project Coordinators will need to instruct the developers to create 301 redirects if a page exists on a site, but will be changing its URL.

You must make sure the 301 redirects are done correctly, because if it is not your client could lose thousands of Google views that apply to their search link equity, rendering them essentially starting from scratch, which is quite disastrous from an SEO perspective. You can make a spreadsheet in Excel or a Google doc, or simply list them in LGED. But the essential message must be that there is an OLD URL that will now change to a NEW URL, and the PC (not the developer) is responsible for determining those. There are two main types.

One, the Orenstein model, where the URL is kept, but page names are changed:

OLD: http://www.orensteinsolutions.com/services/teen-psychologist-counseling-therapy/

NEW: http://www.orensteinsolutions.com/teen-counseling/

There is also second type, the Joseph Weiss type, where the URL is completely new:

OLD: http://www.drjosephsweiss.com/contact

NEW: http://www.theanxietydocseattle.com/contact