public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Major site redesign, SEO, and 301 redirects
Date: Wed, 30 Sep 2015 08:36:47 +0100	[thread overview]
Message-ID: <201509300836.56159.michaelkintzios@gmail.com> (raw)
In-Reply-To: <560B2CC3.6030901@gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 3306 bytes --]

On Wednesday 30 Sep 2015 01:28:51 Alan McKinnon wrote:
> On 29/09/2015 22:00, Tanstaafl wrote:
> > Hi all,
> > 
> > I am not a web (or SEO) guy, but I manage our DNS and have for a long
> > time.
> > 
> > The boss has contracted with a web development company to do a full
> > redesign of our website.
> > 
> > Our website has hundreds of thousands of pages, and years of SEO behind
> > it. The guys who was her until recently was adamant that we must be very
> > carefl with the redesign so as not to totally break SEO, and possibly
> > getting blacklisted by Google.
> > 
> > The web developers are insisting that they need full access to our DNS
> > (hosted by DNSMadeEasy), and the only reason I can think of for this is
> > they plan on setting up HTTP redirects (DNSMadeEasy equivalent of a 301
> > redirect) for these pages - but hundreds of thousands of them?
> 
> I've been thinking about this some more.
> 
> We all assumed "full access" means "so we can change stuff". Maybe it
> really means they want to see what's in "dig axfr" (a zone transfer)
> which they normally can't see. There are TXT records in DNS that they
> might be interested in.
> 
> It would be wise to clarify with the devs exactly what it is they are
> looking for.
> 
> And overall, in your shoes I would be firm, adamant and above all polite
> and say that infrastructure changes go through you and you alone, and
> must be vetted by you with full transparency.
> 
> > Wouldn't this be better done at the web server level? Or am I just
> > ignorant?
> > 
> > Would love to hear experiences (good and bad), and a recommendation for
> > what I should do.
> > 
> > thanks

I couldn't agree more with all the warnings that have been posted.  However, 
it may simply be that they want to build a new website and they want to 
redirect your DNS from your currently hosted server to theirs.  Are they 
offering SaaS, or will you be hosting the new website on prem?  In any case, 
they could just ask you to do this, if you agree.  Given that "possession is 
nine-tenths of the law" I would not let them anywhere near your DNS records - 
period.

With regards to being blacklisted by Google, you have to be careful indeed.  
Google will blacklist bad code and malicious code.  If your code is clean, you 
don't fill your metadata with repetitive cr*ap and your topic is not faced 
with a competition of millions selling exactly the same undifferentiated 
product, then you should be OK in organic listing rankings.  Having mirrored 
websites on different DNS' will also blacklist you, although DNS or http 
redirects are of course legit.

A lot of so called SEO companies are not actually streamlining the content and 
metadata, but exploiting paid-for Google Ads and in a non-transparent way to 
milk the customer, on top of the Google charges.  Most of these companies set 
up Google Ads once and rarely if ever come back to to tune it.  I couldn't 
care to list the number of websites we switched off Google Ads and saw no 
discernible different in the rankings.

BTW, although SEO is not rocket science its not something you would leave to 
your marketing people alone, or for that matter to your coding people alone.  
You need both.  
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-09-30  7:37 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 20:00 [gentoo-user] Major site redesign, SEO, and 301 redirects Tanstaafl
2015-09-29 20:19 ` J. Roeleveld
2015-09-29 20:39   ` Alan McKinnon
2015-09-30  0:02     ` [gentoo-user] " James
2015-10-01 11:22       ` Tanstaafl
2015-10-01 11:25         ` Alan McKinnon
2015-09-30  0:28 ` [gentoo-user] " Alan McKinnon
2015-09-30  7:36   ` Mick [this message]
2015-10-01 11:26     ` Tanstaafl
2015-10-01 11:35   ` Tanstaafl
2015-10-01 11:58     ` Alan McKinnon
2015-10-01 12:21       ` Tanstaafl
2015-10-01 14:35         ` Mick
2015-10-01 23:00           ` Walter Dnes
2015-10-02  7:41             ` Mick
  -- strict thread matches above, loose matches on Subject: below --
2015-09-19 19:36 [gentoo-user] update problems lee
2015-09-19 19:57 ` Alan McKinnon
2015-09-19 22:17   ` Rich Freeman
2015-09-19 22:46     ` Alan McKinnon
2015-09-20  0:37       ` Philip Webb
2015-09-20 11:52         ` Neil Bothwick
2015-09-20 12:06           ` Rich Freeman
2015-09-22 20:11             ` [gentoo-user] " James
2015-09-26  9:47     ` [gentoo-user] " lee
2015-09-26 11:33       ` Alan McKinnon
2015-09-27 19:17         ` lee
2015-09-27 21:29           ` Alan McKinnon
2015-09-28 22:52             ` lee
2015-09-28 23:46               ` Alec Ten Harmsel
2015-09-29 18:56                 ` lee
2015-09-29  0:09               ` Neil Bothwick
2015-09-29 18:45                 ` lee
2015-09-29 19:36                   ` Alan Mackenzie
2015-10-03 17:27                     ` lee
2015-10-01  9:39                   ` Neil Bothwick
2015-10-01 11:10                     ` Rich Freeman
2015-10-01 13:27                       ` Neil Bothwick
2015-10-03 18:10                     ` lee
2015-10-03 20:01                       ` allan gottlieb
2015-09-20 14:25   ` lee
2015-09-20 17:24     ` J. Roeleveld
2015-09-20 17:31       ` Rich Freeman
2015-09-26 13:51         ` lee
2015-09-26 15:09           ` Rich Freeman
2015-09-27 19:35             ` lee
2015-09-26 16:28           ` Neil Bothwick
2015-09-26 13:10       ` lee
2015-09-26 15:31         ` J. Roeleveld
2015-09-26 16:47         ` Neil Bothwick
2015-09-26 18:16           ` Alan McKinnon
2015-09-26 20:58             ` Neil Bothwick
2015-09-19 20:05 ` Neil Bothwick
2015-09-19 20:11   ` Alan McKinnon
2015-09-19 20:12   ` Mick
2015-09-20 15:28   ` lee
2015-09-20 15:57     ` Rich Freeman
2015-09-20 16:29     ` Alan McKinnon
2015-09-26 15:00       ` lee
2015-09-27 13:14         ` Alan McKinnon
2015-09-20 16:35     ` Neil Bothwick
2015-09-21  1:29   ` Paul Colquhoun
2015-09-19 21:29 ` Daniel Frey
2015-09-20 18:07   ` [gentoo-user] " James
2015-09-20 19:35     ` Daniel Frey
2015-09-20 20:59       ` Dale
2015-09-22 15:55         ` James
2015-09-22 16:03           ` Alan McKinnon
2015-09-22 16:39             ` James
2015-09-22 17:17               ` Alan McKinnon
2015-09-22 16:42             ` Neil Bothwick
2015-09-22 17:08               ` Alan McKinnon
2015-09-22 17:35               ` James
2015-09-22 18:08                 ` Neil Bothwick
2015-09-22 19:05             ` Dale
2015-09-20 20:24     ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201509300836.56159.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox