Q2 What’s the first step in making sure there’s anything to worry about when you are presented with a redesigned website? How to quickly diagnose a problem? #vcbuzz
-
>>> If you can't catch things Before they happen, you need to look at URLs pre/post change, as well as map out and compare the navigation structures and internal links. Also note any "content" changes, including different elements for links/headings etc.
#VCBuzz >>>
>>>
Ideally, you should change one thing at a time (content, code, structure).
The more that changes, the longer it takes G to re-associate,
and this can cause long-term fluctuations/negative impacts,
and it compounds (1x = N, 2x = 2N+, 3x = 3N+).
#VCBuzz
>>>
-
-
>>> If you've caught things Before they are done, ensure as little changes as possible. That may mean rewriting nav code, or implementing "rewrites" (not the same as "redirects"!). If content lives on /this/that/12.html you want it there, not /thisx/that-12/
#VCBuzz >>> -
>>> Then, over time, replace a selection at a time, altering the rewrites to be redirects (category by category, pagetype by pagetype etc.). This reduces the impact, and gives more stable results, as G has less to process.
#VCBuzz >>> - Antwoorden weergeven
Nieuw gesprek -
Het laden lijkt wat langer te duren.
Twitter is mogelijk overbelast of ondervindt een tijdelijke onderbreking. Probeer het opnieuw of bekijk de Twitter-status voor meer informatie.