website redesign
DESCRIPTION
Website redesign, if not done in the proper manner, could spell doom for a site in the search rankings. Soumya Shankar & Vishal, who work as SEO professionals with Convonix, have created a resourceful presentation on the factors that need to be taken care of, while you are redesigning a website. Our website design & usability team follows these processes with the utmost care, and have successfully managed to replace entire websites, without seeing major fluctuations in rankings.TRANSCRIPT
Website RedesignPrecautions, Next steps &Best Practices
By Soumya Shankar &
Vishal ShahSEO Team at
Convonix
Why?
• Outdated
• Unprofessional
• Change in
Business GoalsWhy?
Or just change for the better
Why?
• "Pretty" than
functional
• Complex
Navigation/Disorga
nized ArchitectureWhy?
Simply Bad
Why?
CMS migration
Why?
Common Mistake
Redesign First, SEO later
Pre-Launch
Initial Steps
R-E-S-E-A-R-C-H !• Analyze Site• Gather Data/Current Stats
• Define Objectives• Decide Timeline• Understand Limitations
Pre-Launch
Make Use of Analytics
Pre-Launch
Wireframe & Navigation
Keywords
Pre-Launch
SEO Elements• URL• Content• Title• Meta tags• Heading Tags• Alt/Title Attributes
Pre-Launch
URL Re-writes?
• Dynamic URL
• Feasibility
• 301 Redirects
Pre-Launch
Precautions
Keep it Simple.
Precautions
• Putting off
existing users
• Page Load Time
• Shorter Funnels
Precautions
Changing Domain
Name
Precautions
•Flash and
JavaScript
•Team Work
•Launch when the
traffic is low
•Analyze Incoming
links
Precautions
Before you go Live!• Analytics Code
• Sitemap
• Testing
• Check for Duplication
• Custom 404
Post Launch Audit• Check Tracking code• Webmaster Tools• Build Links• Compare with previous stats
Benchmarking
• Ranking Report• Pages Indexed• Analytics Parameters• Site crawl
Tips for Server ShiftShifting from Server A
to Server B: 1. Copy site to server B while maintaining a copy on Server A
2. Check the functionality of the site on Server B. Check forms, navigation and other elements
3. Once the functionality is checked, change the DNS to server B. A copy of site on server A needs to be maintained for 72 hours for the DNS to propagate 4. After 72 hours, the site on server A can be taken down 5. If there are any changes in the URL Structure, setup 301 redirects on server B to take care of the URL changes.
Summary• Do your homework thoroughly
• Design a checklist & stick to it at every stage
• Balance SEO & Usability• DO NOT expect miracles overnight
• Stay Alert!
Thank you.